Update CircleCI configuration for pushing to container registries #43
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Towards giantswarm/roadmap#2979
Context: announcement in
#news-dev
on SlackThis PR was created through automation by Team Honeybadger, to make sure that the container images built for this repository are available in the right registries.
For that, the CircleCI configuration is modified to use the new push-to-registries job instead of the old
push-to-docker
. This means that there is only one job for all registry pushes, and it simplifies the configuration by removing many parameters that are now set automatically or as defaults.Notes
push-to-registries
, the branch protection rules in this repository will likely require updating before the required checks can be green.To the responsible team
Please,
ci/circleci: push-to-registries
has been executed successfully.requires
)filters
. Especially if this PR replaces several jobs with one, and the previous jobs had different filters, make sure that the filter includes all cases.Please get this done until December 5, so that we can move on with the next migration steps. Thank you!