This was fixed with the plugin about a month ago, per the cloned bug. I'm guessing that this was attempted with the RHEL jenkins image, and that the version used was downlevel and did not have a version of the jenkins plugin with the fix. This could be confirmed a few ways. The easiest perhaps would be to log into the jenkins image used, and go to Manage Jenkins, then Manage Plugins, and then clicking the installed tab. Then see which version of the openshift pipeline plugin is installed. If I'm correct, then we would simple need to upgrade the version of the Jenkins RHEL image.
So online is pulling the jenkins image from registry.access.redhat.com/openshift3/jenkins-1-rhel7:latest I verified that that image is a bit older ... and it only has version 1.0.4 of the openshift-pipeline plugin @bparees @tdawson @sdodson - can you all confirm for me what the schedule is for pushing out the latest jenkins rhel image to registry.access.redhat.com ... will it not occur until 3.2 ships? thanks, gabe
I believe that's correct (that it won't be updated until 3.2 ships). Troy will need to confirm though.
We currently have no bugzilla/errata scheduled that would update the released jenkins image for OpenShift 3.1. So Ben is correct. It will not be updated until 3.2 ships.
Created attachment 1138402 [details] UI of build part
The names of the steps were changed as part of a documentation / usability review. "Get latest openshift build status" is now "Verify OpenShift Build". I pulled down the image you referenced and the fix for this bug is there.
Created attachment 1138859 [details] verify Openshift build UI
It's just my opinion:> of course ,it's good for us to understand the meaning of the options