-
Notifications
You must be signed in to change notification settings - Fork 55
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
release: allow pushing container images to multipes repositories #1091
Conversation
6a88c81
to
f46e326
Compare
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.
Some comments, but approach LGTM overall!
This changes the schema, so we'll need to make sure to have the changes for the RHCOS pipecfg as well lined up so they merge at the same time.
jobs/release.Jenkinsfile
Outdated
@@ -259,26 +259,28 @@ lock(resource: "release-${params.STREAM}", extra: locks) { | |||
if (push_containers) { | |||
stage("Push Containers") { | |||
parallel push_containers.collectEntries{configname, val -> [configname, { | |||
if (!registry_repos?."${configname}"?.'repo') { | |||
if (!registry_repos?."${configname}"?.isEmpty()) { |
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.
Does isEmpty()
work if the $configname
key is missing?
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.
if I understand correctly, if $configname
is missing the ?
will short circuit the expression
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.
Did some testing and haven't had issues. However I see what you mean : it would not exit and fail afterwards I suppose.
WDYT of if (!registry_repos?."${configname}") {
as empty collections evaluate to false.
I tested that and it works as expected (see below comment)
f46e326
to
ac12015
Compare
Thanks @dustymabe @jlebon for the review comments. I addressed those.
Yep, The PR over there is ready. I added the hold label just in case. |
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.
LGTM
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.
This is now blocked on https://issues.redhat.com/browse/DPTP-4328.
Is it ? The RHCOS change is, yes, but we can test this change before adding the extra repository in the RHCOS config |
Yes, that's fine assuming we remove that part of the pipecfg PR. |
b31a48d
to
fe95c57
Compare
In RHCOS we need to publish the oscontainer image to the release repo and also the CI repo. Changing the registry_repo object to be an array instead of a map to allow multiple entries.
fe95c57
to
8de05b1
Compare
Allright, I did some testing on the staging FCOS pipeline to iron out the small details :) With the following patch, this is the result :
Result:
Using the following config :
|
8de05b1
to
2035d97
Compare
9db798a
to
2035d97
Compare
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.
LGTM! Will merge when ready to merge the pipecfg one.
In RHCOS we need to publish the oscontainer image to the release repo and also the CI repo. Changing the registry_repo object to be an array instead of a map to allow multiple entries.
Patch best reviwed without whitespace changes