Hide Forgot
Description of problem: JenkinsPipeline strategy is not allowed in online env Version-Release number of selected component (if applicable): dev-preview-int OpenShift Master: v3.3.0.26+74ac228-dirty Kubernetes Master: v1.3.0+507d3a7 How reproducible: Always Steps to Reproduce: 1.Create a project, create a JenkinsPipeline strategy build $ oc new-app https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/pipeline/samplepipeline.json 2. 3. Actual results: --> Creating resources with label app=jenkins-pipeline-example ... error: buildconfigs "sample-pipeline" is forbidden: build strategy JenkinsPipeline is not allowed service "frontend" created route "frontend" created imagestream "origin-ruby-sample" created buildconfig "ruby-sample-build" created deploymentconfig "frontend" created service "database" created deploymentconfig "database" created --> Failed Expected results: Could create jenkinspipeline strategy build successfully Additional info:
This is working as designed. By default, pipeline builds are not allowed in the current version of OpenShift online. However, it should be enabled when we upgrade to v3.3.
We already have upgraded to v3.3.0.28 in dev-preview-int
@Vu Dinh, Don't know if you are the right person for this, but do you or someone else know if JenkinsPipeline strategy should be enabled or not in online 3.3? thanks!
Hi Bing, This question is better suit for Ben Parees. Thanks, Vu
Since the online ops registry is using the latest jenkins image from pulp, we can go ahead and enable pipeline strategy builds in any online environment that is at 3.3 and above.
Pipeline build strategy is also NOT allowed in dev-preview-stg
Hi, Vu Dinh, as Ben said , we should enable the pipeline strategy on online env, how do you think ?
We are still in progress to enable this feature on Online cluster. Will keep you posted :). Thanks, Vu
PR: https://github.com/openshift/online/pull/572 Release ticket for Online: https://github.com/openshift/online/issues/573
This is now configured in devpreview INT
JenkinsPipeline build can be successfully triggered in INT: $ oc new-app https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/pipeline/samplepipeline.json $ oc start-build sample-pipeline build "sample-pipeline-1" started $ oc get pod NAME READY STATUS RESTARTS AGE jenkins-1-m4rlk 1/1 Running 0 7m mongodb-1-kmtoj 1/1 Running 0 7m nodejs-mongodb-example-1-build 0/1 Completed 0 2m nodejs-mongodb-example-1-t1k8u 1/1 Running 0 50s $ oc get build NAME TYPE FROM STATUS STARTED DURATION nodejs-mongodb-example-1 Source Git@fb4415c Complete 3 minutes ago 1m19s sample-pipeline-1 JenkinsPipeline Complete 6 minutes ago 4m34s Move to verified.