Allow triggering openQA-in-openQA tests if submission is pending #358
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We can schedule the tests anyway; we only should not override the staging repo and follow up with a submission. This way we see problems with openQA- in-openQA tests early - even when submissions are pending for a while. To indicate that we should not do a submission, this change creates the file `job_post_skip_submission` in the current working directory which is picked up by e.g. Jenkins as artifact via the glob `job_post_*` and can be used by subsequent jobs. It is important to configure that subsequent jobs use the artifacts from the preceding job that triggered them and *not* the last successful job. Related ticket: https://progress.opensuse.org/issues/167395
okurz
approved these changes
Nov 29, 2024
kalikiana
approved these changes
Nov 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We can schedule the tests anyway; we only should not override the staging repo and follow up with a submission. This way we see problems with openQA- in-openQA tests early - even when submissions are pending for a while.
To indicate that we should not do a submission, this change creates the file
job_post_skip_submissionin the current working directory which is picked up by e.g. Jenkins as artifact via the globjob_post_*and can be used by subsequent jobs. It is important to configure that subsequent jobs use the artifacts from the preceding job that triggered them and not the last successful job.Related ticket: https://progress.opensuse.org/issues/167395