-
Notifications
You must be signed in to change notification settings - Fork 5
Conversation
but on the second thought it's gonna be hard to maintain the duplication and it doesn't bring that much value since we have that checks running on every push to
Once we agreed on this workflow, I'm gonna add to the FE repo the simplified version of this workflow which is gonna be triggered by any commit to the |
We can skip this and be sure that pipelines are passing before triggering the job |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving this and keeping an eye on the IT ticket. Please be sure to merge it clean
RC pipleline
Problem:
EVEREST-428
Everest needs a workflow for building release branches.
Solution:
Create a manually triggering workflow. It would accept the version we want to create the RC for and would create the
release-*.*.*
branches in the backend, cli, frontend and catalog repos. It will update tags in the deployment scripts (so no manual intervention needed to run it from the rc-branch), build and push the new image to the registry.