-
Notifications
You must be signed in to change notification settings - Fork 57
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
Using base image from other namespace did not work #179
Comments
I don't see a major reason why the more targeted approach would not work. One reason that the whole thing was updated may be that - IIRC - a |
@henrjk Looking at this again, the issue should ONLY happen if you pass custom |
This happed with the following in Jenkinsfile:
which ultimately stems from here: |
@henrjk Right, this is the default Python Jenkinsfile. For other quickstarters, the issue is not triggered because other quickstarters do not use the buildArgs. Now it makes sense to me why I was sure it was working while you were sure it was not working :D |
… status of the pipeline (opendevstack#179) Co-authored-by: 8vicat <martsec@users.noreply.github.com>
Describe the bug
I experimented with using a base image created in openshift and then referencing this in the buildConfig as follows:
However during the shared library
buildArgs
patch created inods-jenkins-shared-library/vars/stageStartOpenshiftBuild.groovy
Line 106 in a7ff00a
dockerStrategy
and this removes thefrom
information.As a consequence the image was attempted to be loaded from the docker registry instead of the internal registry which failed.
I'd be happy to work on a fix unless there was some known reason that a more targeted patch would not work.
To Reproduce
I don't have something I can share ready. Please ask if clarification is needed.
Expected behavior
The patch should only add build args and leave other pieces of the dockerStrategy alone.
Affected version (please complete the following information):
The text was updated successfully, but these errors were encountered: