Red Hat Bugzilla – Bug 1356037
Serial runPolicy doesn't work for jenkinspipeline strategy
Last modified: 2017-03-08 13:43 EST
Description of problem: When create a jenkinspipeline strategy buildconfig,the default runPolicy is serial. But when trigger multiple jenkinspipeline strategy builds,still using parallel policy actually. Version-Release number of selected component (if applicable): openshift v3.3.0.4 kubernetes v1.3.0+57fb9ac How reproducible: always Steps to Reproduce: 1.Check sample-pipeline bc which using jenkinspipeline strategy 2.Trigger 2 sample-pipeline builds 3. Actual results: step 1: oc get bc sample-pipeline -n xiuwang12 -o yaml spec: output: {} postCommit: {} resources: {} runPolicy: Serial source: secrets: null type: None strategy: jenkinsPipelineStrategy: jenkinsfile: |- node('agent') { stage 'build' openshiftBuild(buildConfig: 'ruby-sample-build', showBuildLogs: 'true') stage 'deploy' openshiftDeploy(deploymentConfig: 'frontend') } type: JenkinsPipeline step 2: sample-pipeline and ruby-sample-build are using parallel policy actually. # oc get builds NAME TYPE FROM STATUS STARTED DURATION ruby-sample-build-1 Source Git@e79d887 Complete 5 minutes ago 4m16s ruby-sample-build-2 Source Git@e79d887 Running 40 seconds ago 35s ruby-sample-build-3 Source Git New sample-pipeline-1 JenkinsPipeline Git@master Running 6 minutes ago 6m0s sample-pipeline-2 JenkinsPipeline Git@master Running 4 minutes ago 4m10s Expected results: Serial policy should work for jenkinspipeline strategy Additional info:
This is also being tracked here: https://github.com/fabric8io/openshift-jenkins-sync-plugin/issues/61
Fixed in https://github.com/jenkinsci/openshift-sync-plugin/pull/17 - will be available in next release.
Available in v0.0.16. @bparees Assigned to @tdawson to get packaged up please. No dependency changes btw.
rpm has been made: jenkins-plugin-openshift-sync-0.0.16-1.el7 images using that rpm have been made: openshift3/jenkins-1-rhel7:1.651.2-30 openshift3/jenkins-2-rhel7:2.7-15
https://github.com/jenkinsci/openshift-sync-plugin/pull/17 has broken things for me - see https://github.com/jenkinsci/openshift-sync-plugin/pull/18. An example which demonstrates the breakage is: oc create -f https://gist.githubusercontent.com/jim-minter/b4285b000b0e68a09c1bfc1db4b669e3/raw/5ec944dc5bf312efca1506f7c468c5e4e025d23d/gistfile1.txt
@jminter Thanks. I'll release a new version soon which will of course need to be packaged. Will assign to @tdawson once release is done.
Released v0.0.17 of sync plugin ready for packaging please @tdawson.
I do not see it https://updates.jenkins-ci.org/download/plugins/openshift-sync/ https://wiki.jenkins-ci.org/display/JENKINS/Openshift+Sync+Plugin
Took longer to sync from https://repo.jenkins-ci.org/releases/io/fabric8/jenkins/plugins/openshift-sync/0.0.17/ to https://updates.jenkins-ci.org/download/plugins/openshift-sync/0.0.17 than I expected, but is available now.
RPM Made: jenkins-plugin-openshift-sync-0.0.17-1.el7 Images made and pushed to registry.ops: openshift3/jenkins-1-rhel7:1.651.2-33 openshift3/jenkins-2-rhel7:2.7-18
Test with brew-pulp.../openshift3/jenkins-2-rhel7 d126876bf60a brew-pulp.../openshift3/jenkins-1-rhel7 dc04c4ed570b openshift-login 0.9 openshift-pipeline 1.0.33 openshift-sync 0.0.17 openshift v3.4.0.26+f7e109e kubernetes v1.4.0+776c994 etcd 3.1.0-rc.0 Actual results: Serial policy works for jenkinspipeline strategy
Assigning back to Ben for documentation.
I've updated the doc text but assigning back to Jimmi to keep ownership/credit where it belongs (Jimmi there shouldn't be anything further needed from you on this).
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-2017:0066