You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will fail at deployment #1 letting you wait about a minute (because of inability to pull image " ") and then re-deploy as #2 from the ImageStream. @smarterclayton said that someone is working on that [1].
The bigger issue comes if you decide to use "imageChangeParams": { "automatic": false
which is a valid choice if you do not want to re-deploy your Jenkins
master while doing some important tasks.
This way you will end up with failed deployment #1 and you have to
manually deploy #2 but since you are triggering the build manually it
starts from image " " and fails again. You will be stuck in this loop
and never get it deployed this way!
The previous discussion on mailing list is in [1].
Push Deploy in web console to re-deploy Jenkins after deployment #1 fails on inability to pull image " "
Current Result
Always deploys from image " "
Expected Result
Deploys from ImageStream and not from image " "
Does not fail first time (deployment #1)
Additional Information
Using ADB 2.0 with latest origin containers
The text was updated successfully, but these errors were encountered:
tnozicka
changed the title
Deployments from ImageStream does not work for manual deploy
Deployments from ImageStream do not work for manual deploy
May 19, 2016
The way you can specify Deployments to start from an ImageStream instead of an image is to specify image: " " and trigger from ImageChange.
This will fail at deployment
#1
letting you wait about a minute (because of inability to pull image " ") and then re-deploy as#2
from the ImageStream. @smarterclayton said that someone is working on that [1].The bigger issue comes if you decide to use
"imageChangeParams": { "automatic": false
which is a valid choice if you do not want to re-deploy your Jenkins
master while doing some important tasks.
This way you will end up with failed deployment
#1
and you have tomanually deploy
#2
but since you are triggering the build manually itstarts from image " " and fails again. You will be stuck in this loop
and never get it deployed this way!
The previous discussion on mailing list is in [1].
[1] - https://lists.openshift.redhat.com/openshift-archives/dev/2016-May/msg00047.html
Version
$ oc version
oc v1.3.0-alpha.0-588-g665eb4b
kubernetes v1.3.0-alpha.1-331-g0522e63
Steps To Reproduce
#1
fails on inability to pull image " "Current Result
Always deploys from image " "
Expected Result
#1
)Additional Information
Using ADB 2.0 with latest origin containers
The text was updated successfully, but these errors were encountered: