Improve the state of the CI on the release branches #12163
Labels
area/ci-cd
kind/improvement
Improvement on an existing feature
triage/accepted
The issue was reviewed and is complete enough to start working on it
Comments
bartsmykla
added
area/ci-cd
triage/accepted
This was referenced Dec 11, 2024
bartsmykla
added a commit
that referenced
this issue
Dec 11, 2024
…istribute-workflow-on-workflow-dispatch-release-2-8 ## Motivation We don’t know how stable our CI is on release branches because we don’t make changes to them often. This means we don’t get enough feedback about their status. ## Implementation information This is a part of the effort to run tests on CI for release branches on schedule. As GitHub doesn't allow to run workflows on schedule from branches other than default (master in our case), the best solution I could find is to allow to run `build-test-distribute` workflow on `workflow_dispatch` event and then in master on schedule send a REST call to manually trigger these workflows on wanted release branches. ## Supporting documentation <!-- Is there a MADR? An Issue? A related PR? --> Part of: - #12164 - #12163 <!-- > Changelog: skip --> <!-- Uncomment the above section to explicitly set a [`> Changelog:` entry here](https://github.com/kumahq/kuma/blob/master/CONTRIBUTING.md#submitting-a-patch)? --> Signed-off-by: Bart Smykla <[email protected]>
bartsmykla
added a commit
that referenced
this issue
Dec 11, 2024
…istribute-workflow-on-workflow-dispatch-master ## Motivation We don’t know how stable our CI is on release branches because we don’t make changes to them often. This means we don’t get enough feedback about their status. ## Implementation information This is a part of the effort to run tests on CI for release branches on schedule. As GitHub doesn't allow to run workflows on schedule from branches other than default (master in our case), the best solution I could find is to allow to run `build-test-distribute` workflow on `workflow_dispatch` event and then in master on schedule send a REST call to manually trigger these workflows on wanted release branches. ## Supporting documentation <!-- Is there a MADR? An Issue? A related PR? --> Part of: - #12164 - #12163 <!-- > Changelog: skip --> <!-- Uncomment the above section to explicitly set a [`> Changelog:` entry here](https://github.com/kumahq/kuma/blob/master/CONTRIBUTING.md#submitting-a-patch)? --> Signed-off-by: Bart Smykla <[email protected]>
bartsmykla
added a commit
that referenced
this issue
Dec 11, 2024
…istribute-workflow-on-workflow-dispatch-release-2-6 ## Motivation We don’t know how stable our CI is on release branches because we don’t make changes to them often. This means we don’t get enough feedback about their status. ## Implementation information This is a part of the effort to run tests on CI for release branches on schedule. As GitHub doesn't allow to run workflows on schedule from branches other than default (master in our case), the best solution I could find is to allow to run `build-test-distribute` workflow on `workflow_dispatch` event and then in master on schedule send a REST call to manually trigger these workflows on wanted release branches. ## Supporting documentation <!-- Is there a MADR? An Issue? A related PR? --> Part of: - #12164 - #12163 <!-- > Changelog: skip --> <!-- Uncomment the above section to explicitly set a [`> Changelog:` entry here](https://github.com/kumahq/kuma/blob/master/CONTRIBUTING.md#submitting-a-patch)? --> Signed-off-by: Bart Smykla <[email protected]>
lukidzi
added a commit
that referenced
this issue
Dec 11, 2024
…istribute-workflow-on-workflow-dispatch-release-2-7 ## Motivation We don’t know how stable our CI is on release branches because we don’t make changes to them often. This means we don’t get enough feedback about their status. ## Implementation information This is a part of the effort to run tests on CI for release branches on schedule. As GitHub doesn't allow to run workflows on schedule from branches other than default (master in our case), the best solution I could find is to allow to run `build-test-distribute` workflow on `workflow_dispatch` event and then in master on schedule send a REST call to manually trigger these workflows on wanted release branches. ## Supporting documentation <!-- Is there a MADR? An Issue? A related PR? --> Part of: - #12164 - #12163 <!-- > Changelog: skip --> <!-- Uncomment the above section to explicitly set a [`> Changelog:` entry here](https://github.com/kumahq/kuma/blob/master/CONTRIBUTING.md#submitting-a-patch)? --> Signed-off-by: Bart Smykla <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
We don’t have a clear picture of how stable our CI is on release branches because we don’t make changes to them often. As a result, we don’t get enough feedback about their status. This issue will track efforts to assess the current state of the CI on release branches and identify any improvements needed.
Tasks:
build-test-distributeonworkflow_dispatch#12149 (release-2.9)build-test-distributeonworkflow_dispatch#12231 (release-2.8)build-test-distributeonworkflow_dispatch#12232 (release-2.7)build-test-distributeonworkflow_dispatch#12233 (release-2.6)The text was updated successfully, but these errors were encountered: