Description of problem: sample-pipeline builds disappered in openshift client after edit or just check configure page of sample-pipeline project in jenkins webconsole. Builds exist in jenkins webconsole. 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.After jenkins pod deploy, trigger some sample-pipeline build from openshift cli and jenkins webcosnole 3.Edit pipeline scripts field in sample-pipeline project configure page,then save. 4.Check builds in openshift cli Actual results: Old sample-pipeline builds disappered Expected results: Builds shouldn't disapper Additional info:
Jimmi, does the fix you just dropped for build deletion also address this scenario?
Spoke with Jimmi on IRC and confirmed this should also be fixed by: https://github.com/jenkinsci/openshift-sync-plugin/pull/7 we'll do a release shortly and get this to QE.
The change is in jenkins-plugin-openshift-sync-0.0.12-1.el7, which is in openshift3/jenkins-1-rhel7-1.651.2-14 or newer.
Test with image brew.../openshift3/jenkins-1-rhel7 1.651.2 24f906abd158 3 days ago 592.4 MB brew.../openshift3/jenkins-1-rhel7 1.651.2-14 24f906abd158 3 days ago 592.4 MB brew.../openshift3/jenkins-1-rhel7 latest 24f906abd158 3 days ago 592.4 MB still can reproduce this issue
@Troy the pulp image is still showing sync plugin v0.11 instead of v0.12.
Fixed this time for sure, I've even checked the image manually. Use image: openshift3/jenkins-1-rhel7:1.651.2-16 This is in pulp, as well as registry.qe and registry.ops
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
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