Description of problem: Could trigger sample-pipeline build successfully before jenkins master pod is ready.Build disappear after the jenkins pod ready, but bc is marked build version to 1. Version-Release number of selected component (if applicable): jenkins-1-rhel7 (91cc89832f5f) How reproducible: always Steps to Reproduce: 1.Create a jenkinspipeline app oc new-app -f https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/pipeline/samplepipeline.json 2.Trigger sample-pipeline build before jenkins master is ready 3. Actual results: Trigger build successfully, but disappers after jenkins master ready. Expected results: Should prompt warning info. Additional info:
The real issue here is that the build is disappearing, that should not happen, it should be run correctly. This issue was also reported here: https://github.com/openshift/jenkins/issues/139
Fixed in https://github.com/jenkinsci/openshift-sync-plugin/pull/7. Releasing community version,
Test with openshift3/jenkins-1-rhel7 1.651.2-16 19bc08e9d803 2 days ago 626.7 MB openshift3/jenkins-1-rhel7 latest 19bc08e9d803 this bug is fixed, openshift sync plugin is 0.0.12
The fix is in jenkins-plugin-openshift-sync-0.0.12-1.el7, which is in openshift3/jenkins-1-rhel7:1.651.2-21 or later.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1933