Print configurations built in CI run #209
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
achilleas-k
force-pushed
the
ci-report-builds
branch
from
c19dcf3 to
13988a6
Compare
achilleas-k
force-pushed
the
ci-report-builds
branch
from
13988a6 to
2ed52cb
Compare
In the check-build-coverage step at the end of the CI pipeline, also collect all the build configurations that were built in the specific pipeline (identified by the CI_COMMIT_SHA) in the build info and print it in the log. This makes it a tiny bit more convenient to check which images were rebuilt and see if any images weren't rebuilt when they were meant to or were rebuilt when they weren't expected to.
supakeen
force-pushed
the
ci-report-builds
branch
from
2ed52cb to
7fbb47c
Compare
supakeen
approved these changes
Oct 17, 2023
thozza
approved these changes
Oct 17, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In the check-build-coverage step at the end of the CI pipeline, also collect all the build configurations that were built in the specific pipeline (identified by the CI_COMMIT_SHA) in the build info and print it in the log.
This makes it a tiny bit more convenient to check which images were rebuilt and see if any images weren't rebuilt when they were meant to or were rebuilt when they weren't expected to.
I also considered having Schutzi post the list in the PR, but I think that might get spammy with PRs that get rebased a lot. Let's rely on the job log for now and see how it goes.