Skip to content
This repository has been archived by the owner on Mar 4, 2024. It is now read-only.

EVEREST-428-rc-pipeline #160

Merged
merged 68 commits into from
Sep 20, 2023
Merged

EVEREST-428-rc-pipeline #160

merged 68 commits into from
Sep 20, 2023

Conversation

oksana-grishchenko
Copy link
Contributor

@oksana-grishchenko oksana-grishchenko commented Sep 14, 2023

EVEREST-428 Powered by Pull Request Badge

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.

.github/workflows/rc.yml Outdated Show resolved Hide resolved
@oksana-grishchenko
Copy link
Contributor Author

  1. Do we need to duplicate the required checks in the RC pipeline? I suggested to add this requirement

Required checks should pass before triggering the job

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 main anyway

The pipeline should be triggered on any new commit across backend and frontend repos to rebuild the release image

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 release-x.x.x branch and will rebuild the rc-image.

@oksana-grishchenko oksana-grishchenko marked this pull request as ready for review September 19, 2023 08:59
@oksana-grishchenko oksana-grishchenko requested review from a user and gen1us2k September 19, 2023 08:59
@gen1us2k
Copy link
Contributor

Required checks should pass before triggering the job

We can skip this and be sure that pipelines are passing before triggering the job

Copy link
Contributor

@gen1us2k gen1us2k left a 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

@oksana-grishchenko oksana-grishchenko enabled auto-merge (squash) September 20, 2023 21:33
@oksana-grishchenko oksana-grishchenko merged commit 375d6b1 into main Sep 20, 2023
4 checks passed
@oksana-grishchenko oksana-grishchenko deleted the EVEREST-428-rc-pipeline branch September 20, 2023 21:39
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants