Added logging to diagnose CI build failures #532
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
|
@fheinecke Image is available for testing. |
karl-johan-grahn
approved these changes
Sep 27, 2023
|
@karl-johan-grahn Image is available for testing. |
|
The issue could possibly be that the token need to be persisted, can you instead update the push workflow to: - name: Check out code
uses: actions/checkout@v4
with:
token: ${{ secrets.STAKATER_GITHUB_TOKEN }}
persist-credentials: true
fetch-depth: 0 # otherwise, you will fail to push refs to dest repo |
|
@MuneebAijaz Yikes! You better fix it before anyone else finds out! Build has Failed! |
|
@MuneebAijaz Images are available for testing. |
MuneebAijaz
approved these changes
Oct 25, 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.
It looks like CI push builds to master are periodically failing, leaving releases in a bad state:
When this happens a new chart version is published, but a new tag is not cut. This can cause issues with downstream projects that use this service, and makes it difficult to tell what changes are included in a given release.
It looks like the issue is caused by some form of intermittent permissions issue. I have not been able to reproduce this on my local fork, but I also cannot fully test the workflow as it requires access to other services (such as dockerhub) that my fork does not have. This PR does not attempt to solve the issue, but attempts to add some logging information to help determine the root cause.