blue-build
alternate branch tag generation regression relative to startingpoint
the tag generation based on other branch names is broken:
https://github.com/secureblue/secureblue/pkgs/container/silverblue-main-hardened/versions staging is getting published as "cd9d6ba-39 br-staging-39" instead of "39-staging" and "staging"
I think the br- prefix makes sense here, but with the other stuff I believe I discussed this with @gmpinder earlier. Maybe here, maybe some parts where somewhere else.
Anyway, I am of the opinion that there should at least be a br-staging tag that is the same as the latest tag but for the staging branch. The necessity of that prefix can be discussed.
I'm fine with adding an exception for staging, but we should either leave it at that extra branch name being designated for testing or allow all branches to not have a br- prefix.
No need to add an exception just for us, we'll be fine without it. If the intention wasn't to preserve this functionality, then to close this ticket could be as simple as documentation for the new behavior
We'll be sure to sign images so long as the public and private keys are accessible in the pipeline
No need to add an exception just for us, we'll be fine without it. If the intention wasn't to preserve this functionality, then to close this ticket could be as simple as documentation for the new behavior
@xynydev where would this go?
Not sure what you mean by that question. My earlier comment explains my stance on the topic.
Not sure what you mean by that question. My earlier comment explains my stance on the topic.
Where would the documentation go?
Either a new page in the docs, but I think it'd belong to a reference page for the cli, which has yet to be made.
Such a page should document the public API of cli in great detail. The build --push tagging info would be a part of that.