When we work in complex environment we should follow the best practices to choose how to organize people and projects on our Azure DevOps Organization.
Low quality blog post. This is a personal note/reminder. I quickly post here a reference WCF config file to avoid the content-lenght error when uploading some content. The key config section here was <system.webServer></system.webServer> <?xml version="1.0" encoding="utf-8"?> <!-- For more information on how to configure your ASP.NET application, please visit https://go.microsoft.com/fwlink/?LinkId=169433 --> <configuration> <system.web> <compilation … Continue reading WCF config to avoid content-length error
Azure Feeds used to be scoped to an organization. However, to enable public feeds and to become more consistent with the rest of Azure DevOps, feeds created through the new create feed UI are now project-scoped.
Interesting and well explained naming of registries, namespaces and repo.
When referring to an image, an artifact, a registry, a tag, what exactly is the reference? Do we mean:
For the sake of clarity of communications, there are several elements that make up an artifact or image name, and they are fairly important when we think about artifacts moving from one registry to another. See Choosing a Docker ContainerRegistry for more context
Should we really refer to an image, tied to a specific location? As humans, would we really say the fully qualified name, or would we use shorthand references? And what terminology would, or should we use? There are several terms we use interchangeably, which I’ll call out their meanings:
- Image / Artifact
- Unique Registry
- Repo (repository)
Images & Artifacts
The first thing you may notice is I reference Images and Artifacts interchangeably. It turns out the infrastructure we use to store…
View original post 1,619 more words