-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
v1.13: ci: use Ariane to trigger workflows #26580
Conversation
20d4534
to
9a2e1fd
Compare
/ariane-test-backport-1.13 |
9a2e1fd
to
8f60f4f
Compare
@@ -0,0 +1,15 @@ | |||
# List of test cases for conformance-gke with helm installation options |
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.
Copy paste? )
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.
@viktor-kurchenko That's just how the file is in main
, it was probably a copy-paste issue there. If you want to fix it, let's fix in main
:p
8f60f4f
to
b42b1ce
Compare
[ upstream commit 4a9ee81 ] This is a custom backport, please see upstream commit for full details. Ariane is a new GitHub App intended to trigger Cilium CI workflows based on trigger phrases commented in pull requests, in order to replace the existing `issue_comment`-based workflows and simplify our CI stack. This commit adds a configuration setting up triggers such that existing 1.13 workflows can be triggered with the usual `/test-backport-1.13`, and based on the same PR changelist match / ignore rules. Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
[ upstream commit 9949c5a ] This is a custom backport, please see upstream commit for full details. In this commit, we move stable workflows from the `main` branch back into the 1.13 stable branch now that workflows are triggered via `workflow_dispatch` events in the appropriate context. Since these new workflows were previously living in `main`, we also need to backport dependencies on `.github/actions` configuration files. We take the opportunity to adjust the configuration files as appropriate, notably in terms of K8s version coverage, to ensure that we only test K8s versions officially supported by the stable branch. Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
b42b1ce
to
b1ad7b3
Compare
Please see the main PR at #26237 for full context and discussions.