Allow overriding the project on OBS to install openQA from #215
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
This allows to test packages from a fixed snapshot more easily (without overriding the whole `OPENQA_REPO_URL`). Related ticket: https://progress.opensuse.org/issues/167395
|
Looks like For now we can just have a look at the overview page on openQA: https://openqa.opensuse.org/tests/overview?version=Tumbleweed&distri=openqa&build=Martchus%3Aos-autoinst-distri-openQA%23project-override |
perlpunk
approved these changes
Nov 14, 2024
kalikiana
approved these changes
Nov 15, 2024
Martchus
added a commit
to Martchus/scripts
that referenced
this pull request
Nov 15, 2024
The packages on `devel:openQA` might change while openQA-in-openQA tests are executing. So far we submit packages directly from `devel:openQA` after openQA-in-openQA have passed. This means we don't neccassarily submit the version of the packages we have actually tested. With this change we "release" a snapshot of `devel:openQA` to the staging repository `devel:openQA:testing` when triggering tests and use that within openQA-in-openQA tests (see os-autoinst/os-autoinst-distri-openQA#215). We then only submit from this staging repository when tests have passed. This way we only submit what we've tested despite changes on `devel:openQA`. Packages in the staging repository are cleaned up when openQA-in-openQA tests fail or after packages have been submitted. This trigger script will only release a new version into the staging project if it has been cleaned up ensuring its contents stay the same while tests/submissions are pending. This commit also adds the new script `cleanup-obs-project`. It conveniently deletes all packages in an OBS project without deleting the project itself. We might want to add it on Jenkins as post-failure action for monitoring and submissions to avoid leftovers. (It is also useful to test the deletion code on its own.) Related ticket: https://progress.opensuse.org/issues/167395
Martchus
added a commit
to Martchus/scripts
that referenced
this pull request
Nov 15, 2024
The packages on `devel:openQA` might change while openQA-in-openQA tests are executing. So far we submit packages directly from `devel:openQA` after openQA-in-openQA have passed. This means we don't neccassarily submit the version of the packages we have actually tested. With this change we "release" a snapshot of `devel:openQA` to the staging repository `devel:openQA:testing` when triggering tests and use that within openQA-in-openQA tests (see os-autoinst/os-autoinst-distri-openQA#215). We then only submit from this staging repository when tests have passed. This way we only submit what we've tested despite changes on `devel:openQA`. Packages in the staging repository are cleaned up when openQA-in-openQA tests fail or after packages have been submitted. This trigger script will only release a new version into the staging project if it has been cleaned up ensuring its contents stay the same while tests/submissions are pending. This commit also adds the new script `cleanup-obs-project`. It conveniently deletes all packages in an OBS project without deleting the project itself. We might want to add it on Jenkins as post-failure action for monitoring and submissions to avoid leftovers. (It is also useful to test the deletion code on its own.) Related ticket: https://progress.opensuse.org/issues/167395
Martchus
added a commit
to Martchus/scripts
that referenced
this pull request
Nov 15, 2024
The packages on `devel:openQA` might change while openQA-in-openQA tests are executing. So far we submit packages directly from `devel:openQA` after openQA-in-openQA have passed. This means we don't neccassarily submit the version of the packages we have actually tested. With this change we "release" a snapshot of `devel:openQA` to the staging repository `devel:openQA:testing` when triggering tests and use that within openQA-in-openQA tests (see os-autoinst/os-autoinst-distri-openQA#215). We then only submit from this staging repository when tests have passed. This way we only submit what we've tested despite changes on `devel:openQA`. Packages in the staging repository are cleaned up when openQA-in-openQA tests fail or after packages have been submitted. This trigger script will only release a new version into the staging project if it has been cleaned up ensuring its contents stay the same while tests/submissions are pending. This commit also adds the new script `cleanup-obs-project`. It conveniently deletes all packages in an OBS project without deleting the project itself. We might want to add it on Jenkins as post-failure action for monitoring and submissions to avoid leftovers. (It is also useful to test the deletion code on its own.) Related ticket: https://progress.opensuse.org/issues/167395
Martchus
added a commit
to Martchus/scripts
that referenced
this pull request
Nov 15, 2024
The packages on `devel:openQA` might change while openQA-in-openQA tests are executing. So far we submit packages directly from `devel:openQA` after openQA-in-openQA have passed. This means we don't neccassarily submit the version of the packages we have actually tested. With this change we "release" a snapshot of `devel:openQA` to the staging repository `devel:openQA:testing` when triggering tests and use that within openQA-in-openQA tests (see os-autoinst/os-autoinst-distri-openQA#215). We then only submit from this staging repository when tests have passed. This way we only submit what we've tested despite changes on `devel:openQA`. Packages in the staging repository are cleaned up when openQA-in-openQA tests fail or after packages have been submitted. This trigger script will only release a new version into the staging project if it has been cleaned up ensuring its contents stay the same while tests/submissions are pending. This commit also adds the new script `cleanup-obs-project`. It conveniently deletes all packages in an OBS project without deleting the project itself. We might want to add it on Jenkins as post-failure action for monitoring and submissions to avoid leftovers. (It is also useful to test the deletion code on its own.) Related ticket: https://progress.opensuse.org/issues/167395
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.
This allows to test packages from a fixed snapshot more easily (without overriding the whole
OPENQA_REPO_URL).Related ticket: https://progress.opensuse.org/issues/167395