Specify release tag for UBlue build
Does anyone here know how to build and deploy ublue with the
testing tag instead of the latest tag? I tried
but it sets the tag of the image repo to be :$COMMIT-testing-$VERSION (:c109c8b-testing-40). Any help/link to the right docs would be appreciated.
(I got the alt-tags line from this documentation: https://blue-build.org/reference/recipe/#alt-tags-optional)
My repo is https://github.com/TKK13909/TKKOS and the recipe is at https://github.com/TKK13909/TKKOS/blob/testing/recipes/recipe.ymlGitHub
GitHub - TKK13909/TKKOS
Contribute to TKK13909/TKKOS development by creating an account on GitHub.
GitHub
TKKOS/recipes/recipe.yml at testing · TKK13909/TKKOS
Contribute to TKK13909/TKKOS development by creating an account on GitHub.
Solution:Jump to solution
If you set
alt-tags: to testing, then it should push an image with the tags testing, testing-$VERSION, $TIMESTAMP-testing-$VERSION, and $COMMIT_SHA-testing-$VERSION when built on your main branch8 Replies
That should produce more than the commit tag on the main branch. There are other rules in place if you're building from another branch or a PR
Here are the different test cases for the various pipelines that can be run https://github.com/blue-build/cli/blob/main/process/drivers/github_driver.rs#L217-L271
GitHub
cli/process/drivers/github_driver.rs at main · blue-build/cli
BlueBuild's command line program that builds custom Fedora Atomic images based on your recipe.yml - blue-build/cli
So are you trying to build from a
testing branch?Solution
If you set
alt-tags: to testing, then it should push an image with the tags testing, testing-$VERSION, $TIMESTAMP-testing-$VERSION, and $COMMIT_SHA-testing-$VERSION when built on your main branchWhen building from a branch that isn't main, the tags will be
br-$BRANCH_REF-testing-$VERSION and $COMMIT_SHA-testing-$VERSIONthank you :)
how do i set this as solved now?
Added an issue to print the pushed images at the end of the log https://github.com/blue-build/cli/issues/223
GitHub
feat: Display list of images that were pushed at the end of the log...
This would be similar to how Earthly displays the images that were pushed. This would make it easier to know what images were built without having to scroll back in the logs to see.
You can right-click on the message that you want to be marked as a solution and go to
Apps and select Mark Solutionah ok