Design yamls with podman and docker to run as separate jobs #13524
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
b10n1k
force-pushed
the
refactor_yamls_containers
branch
from
1cdcc65
to
1b8ba73
Compare
b10n1k
force-pushed
the
refactor_yamls_containers
branch
4 times, most recently
from
7b11d27
to
ecad51b
Compare
We need to split the jobs which get scheduled with both container engines together, to run separately. Redesign the yamls schedules which fit those conditions to be able to do so. This follows the latest trend in the qa-c. The need cames from another task which tries to merge podman_image and docker_image in one side and podman__3rd_party_images and docker_3rd_party_images. Make the change in scheduling only for jeos for now to easy the followup work Signed-off-by: Ioannis Bonatakis <ybonatakis@suse.com>
b10n1k
force-pushed
the
refactor_yamls_containers
branch
from
ecad51b
to
fcbbd03
Compare
jlausuch
reviewed
Nov 5, 2021
pdostal
approved these changes
Nov 5, 2021
|
not valid anymore |
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 need to split the jobs which get scheduled with both container engines together, to run separately.
Redesign the yamls schedules which fit those conditions to be able to do so.
This follows the latest trend in the qa-c.
The need cames from another task which tries to merge podman_image and docker_image in one side and
podman__3rd_party_images and docker_3rd_party_images.
Those apparently touch pubcloud jobs and jeos and it wouldnt necessity if they were scheduled by main.pm.
make the change only for jeos for now.
This comes with https://gitlab.suse.de/qac/qac-openqa-yaml/-/merge_requests/482
Signed-off-by: Ioannis Bonatakis ybonatakis@suse.com