Matt Thalman

ACR cleanup is pruning mirrored images that we want to be keeping

1

The ACR cleanup pipeline is [configured](https://github.com/dotnet/docker-tools/blob/7d5c35e09f19bd7b3b333aa7065c0d0d9e4bd9e3/eng/pipelines/cleanup-acr-images.yml#L41-L45) to prune dangling images in the `mirror` repo. The problem is that many of the mirrored tags are multi-arch tags because that is what...

Build job optimization based on build cache

1

This is part of a set of phases outlined by https://github.com/dotnet/docker-tools/issues/186. This phase would optimize the build for cases where a particular build job would end up not producing any...

The various pipelines that exist for the .NET Docker builds have a lot of parameters that are not described. They rely on tribal/historical knowledge held by the repo maintainers. This...

CopyAcrImagesCommand should base its processing on image info, not manifest

1

Currently the logic in `CopyAcrImagesCommand` enumerates the contents of the manifest and correlates that data with the contents of the image info to determine what tags should be published. This...

There are times when a complex feature in Image Builder and/or the common infrastructure that needs to be iterated on until completion. Each time a change is made to the...

As a result of the changes from https://github.com/dotnet/docker-tools/issues/486 and https://github.com/dotnet/core-eng/issues/10097, all of the build agents being used by our builds now have PowerShell Core installed. This means we can take...

Produce multi-arch tags during the build stage of the builds

2

The `build` command pushes _all_ tags of the images it built to the specified staging location. This is unnecessary and incorrect because some of those tags may be multi-arch. Given...

Currently Image Builder updates readmes and tag YAML files in the mcrdocs repo with a direct commit. There was recently a case where such a commit introduce duplicate tag references...

This tracks the https://github.com/microsoft/mcr/issues/686 (internal MSFT link) issue for providing vulnerability scan results of published images to customers.

Investigate whether stages pipeline variable can be removed

1

AzDO now supports the selection of which stages should be run when queuing a build. In theory, this would mean the [`stages` variable](https://github.com/dotnet/docker-tools/blob/f5dc3c6f4bc8ad430fe4faae000dfd77fdd04927/eng/common/templates/stages/build-test-publish-repo.yml#L23) could be obsolete. This should be investigated...