-
Couldn't load subscription status.
- Fork 6
ci: Add options to run VLAB/HLAB tests on manual dispatch #936
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
Conversation
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.
Pull Request Overview
This PR enhances the manual dispatch interface for the dev.yml workflow by adding three boolean input options that allow users to enable VLAB tests, HLAB tests, and release tests when triggering the workflow manually. Previously, these test types could only be enabled through Pull Request labels, which are unavailable in manual workflow dispatches.
Key changes:
- Added three boolean workflow dispatch inputs:
run_vlab_tests,run_hlab_tests, andenable_release_tests - Updated the
skiplogic to check both the new inputs and existing PR labels using OR conditions - Modified the
releasetestparameter to consider the newrun_release_testsinput alongside the existing label check
65c816d to
638de30
Compare
When we manually trigger the dev.yml workflow to run tests, we don't have Pull Request labels in the context, and can't turn VLAB or HLAB tests on. Add options to enable these tests (and the "release" tests) via the dispatch interface. Signed-off-by: Quentin Monnet <[email protected]>
638de30 to
1b16d22
Compare
|
Fredi reported that VLAB tests are currently failing, this is not related to this PR. |
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.
Looks good to me @qmonnet , thanks!
We should document somewhere what options do we have wrt to ci pipelines/workflows etc. I see a lot of workflow files but have to admit that have very little idea of what they do.
This adds comprehensive documentation for all GitHub workflows in the repository, including triggers, main steps, and available options for manual dispatch and PR labels. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Prompt: Look at all GitHub workflow files under .github/workflows/, and produce a file .github/workflows/README.md that summarizes the different workflows, what they do, the main steps, and on what triggers. You may mention the main elements from the job matrix if any, but don't go super deep into the details. For the dev.yaml, mention the main "options" that users can use via labels (when running the workflow on a Pull Request) or via dispatch options. The objective is to help contributors not familiar with CI understand what workflows we have in this repository. Quentin: I did a second pass, changed the formatting, cleaned up and trimmed or completed some pieces of information. Suggested-by: Fredi Raspall <[email protected]> Co-Authored-By: Claude <[email protected]> Signed-off-by: Quentin Monnet <[email protected]>
dbbef94 to
becb0f8
Compare
|
@Fredi-raspall True. I added a commit with an overview of the workflows, please take a look. |
When we manually trigger the dev.yml workflow to run tests, we don't have Pull Request labels in the context, and can't turn VLAB or HLAB tests on. Add options to enable these tests (and the "release" tests) via the dispatch interface.