-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🌱 Run release workflow periodically #235
🌱 Run release workflow periodically #235
Conversation
94aba8e
to
d5f72d2
Compare
This looks good. Will do final review after #232 has merged and this rebased. |
f516c19
to
1be331d
Compare
This is now updated to use the latest version of #232 |
492f6a5
to
b85484f
Compare
Now aligned with #232 latest improvements. |
+1 |
#232 has noe been merged. @salasberryfin - any chance you'd be able to rebase? |
bcf94dc
to
2de8c32
Compare
2de8c32
to
7308d3e
Compare
Signed-off-by: Carlos Salas <carlos.salas@suse.com>
7308d3e
to
c0cb4ad
Compare
Last update includes the multiarch job from #251. |
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, as the improvements could be added later.
What this PR does / why we need it:
Based on @Danil-Grigorev's work on refactoring the release process to make jobs reusable here, this PR adds a nightly workflow (frequency can be modified if nightly is considered too often) that validates these reusable workflows by following the release process and avoiding pushing images to the production registry and publishing helm charts.
The testing workflow is based on creating a fake tag
t9.9.9-fake
(this naming is used to avoid triggering the real release action and is similar to the approach used in upstream CAPI). The workflow then follows the build/sign/release process:The images are only pushed to GitHub Container Registry and Helm charts are created but not published.
When the action finishes, no matter the result, the testing tag is deleted so that it can be used in the next execution of the test.
If any of the steps fail to run, a notification will be sent to the Slack channel we use for nightly E2E testing alerts.
Which issue(s) this PR fixes:
Fixes #214
Special notes for your reviewer:
### This PR depends on #232.Checklist: