-
Notifications
You must be signed in to change notification settings - Fork 114
che #13813: Pushing rhel images to 'quay.io/openshiftio' and centos images to 'quay.io/eclipse-che' during the CI build #31
Conversation
The only thing I'm not sure about - are we already pushing rhel (not centos) images to |
docker build -t ${IMAGE} -f ${DOCKERFILE} . | ||
|
||
TAG=$(echo "$GIT_COMMIT" | cut -c1-"${DEVSHIFT_TAG_LEN}") | ||
|
||
tag_push "${REGISTRY}/openshiftio/$IMAGE:$TAG" | ||
tag_push "${REGISTRY}/openshiftio/$IMAGE:latest" | ||
echo 'CICO: Image pushed, ready to update deployed app' | ||
echo "CICO: Images pushed to 'quay.io/openshiftio', ready to update deployed app" |
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.
A few suggestions:
- I don't think you should login/push to
quay.io/eclipse-che
if the"$TARGET" == "rhel"
- You don't need to the
docker build
twice - I would avoid tagging the images as
latest
because that should be done when we do the release of Che every 3 weeks (especially for eclipse-che org)
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.
And do we really need to push centos images to both openshiftio and eclipse-che?
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.
I don't think you should login/push to quay.io/eclipse-che if the "$TARGET" == "rhel"
You don't need to the docker build twice
Maybe I'm missing smth but in the issue description there is - Update che-devfile-registry-master CentOS CI job to push rhel images to quay.io/openshiftio and centos images to quay.io/eclipse-che
and my understanding is that master CI job always build 'rhel for now, right?. So, I do not really understand how we can avoid building and pushing images twice if we want CentOS images beeing build as part of the same job
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.
it is actually related to my question in my first question in the PR - #31 (comment)
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 what you are saying was true ($TARGET is always "rhel") the script would build rhel
images only (the script does only one docker build). But we know that this is not the case because we see that centos images are pushed to the registry right?
So I think that this script is called twice: once with not specific $TARGET and once with TARGET=rhel. And we should double check with SD team but I suspect that we (you and I) do not have the privileges to see the rhel images even if they are pushed in that org.
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.
Another thing I would add in this PR is an update to the README file to use the eclipse-che
org images instead of the openshiftio.
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.
So I think that this script is called twice: once with not specific $TARGET and once with TARGET=rhel
@l0rd looks like this is the case (script is called twice with & without the target), because:
- for now there is only one job for devfile registry - https://github.com/openshiftio/openshiftio-cico-jobs/blob/master/devtools-ci-index.yaml#L4470
- centos images are pushed to https://quay.io/repository/openshiftio/che-devfile-registry?tab=tags
- on dsaas devfile-registry is build against
openshiftio/rhel-che-devfile-registry
images (and yes, we do not have access to https://quay.io/repository/openshiftio/rhel-che-devfile-registry)
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.
Yep.. The script is run twice. Once here:
https://github.com/openshiftio/openshiftio-cico-jobs/blob/master/devtools-ci-index.yaml#L891
And for the second time here (where extra_target=rhel
):
https://github.com/openshiftio/openshiftio-cico-jobs/blob/master/devtools-ci-index.yaml#L902
@l0rd PR has been updated:
I plan to add yet another commit with docs & build instructions but before want to clarify your point around
if brand-new |
why name is rhel-something if it's centos ? |
@benoitf sorry, typo - updated |
just a small note, on dockerhub we had
|
@benoitf |
@ibuziuk then it would mean quay org should the same than github org or that we move to eclipse-che org on github as well (it's possible to have its own 'eclipse' org so it could be a good idea as well so we cleary see only repositories linked to che) |
@benoitf agree, https://quay.io/organization/eclipse would be more logical |
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
I think eclipse organisation makes more sense as well. But didn't knew if we had the time to move to that org. For the change to
But if you want to stay on the safe side (meaning that we want to make sure that the README will always point to the latest build) you should swap 1. and 2. and do that in separate PRs. |
Anyway LGTM for the changes you have made so far |
…s images to 'quay.io/eclipse-che' during the CI build Signed-off-by: Ilya Buziuk <[email protected]>
Indeed looks like we do not have time for moving from one org to anoter and setup ci bots for those
Done @l0rd sounds good, so no docs update in this PR. Could you please approve if you are ok to merge it in the current state. P.S.
checked with SD and indeed |
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
https://quay.io/repository/eclipse-che/che-devfile-registry?tab=tags \o/ |
Signed-off-by: Ihor Okhrimenko <[email protected]>
…plugin Signed-off-by: Oleksandr Garagatyi <[email protected]>
What does this PR do?
Pushing rhel images to 'quay.io/openshiftio' and centos images to 'quay.io/eclipse-che' during the CI build
What issues does this PR fix or reference?
eclipse-che/che#13813
Should be merged only once dedicated cico job pr is merged - openshiftio/openshiftio-cico-jobs#1035