Upload devel containers via GitHub Actions #2706
Merged
+128
−229
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
Also update deployment_tools.
mattdurham
reviewed
Feb 12, 2025
dehaansa
approved these changes
Feb 12, 2025
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.
Moving the uploading of devel containers away from Drone. Also updating deployment_tools via GitHub Actions instead of Drone.
I tested the container image steps up by triggering a build which uploads them as
ptodev/alloyinstead ofgrafana/alloy. As expected, the build ran ok up until the very end when it failed as it couldn't authenticate forptodev.I have not tested the step which uploads to deployment_tools. I think that's ok, since it's not too crucial. Let's see how the build goes on
mainfirst.