Currently only a single namespace can be specified for the sync plugin to synchronize against. It should be possible to specify any number of namespaces (comma or space separated) and they should all be synced (assuming the jenkins service account has appropriate permissions to access/edit all the namespaces).
This is a tracker bug for https://github.com/fabric8io/openshift-jenkins-sync-plugin/issues/63
*** Bug 1391209 has been marked as a duplicate of this bug. ***
*** Bug 1390294 has been marked as a duplicate of this bug. ***
This is more of a feature than a bug and too risky to include in 3.5 at this point, so moving to upcoming release.
in progress PR is here:
PR has been merged and included in the jenkins centos image, but we haven't put it into the rhel image yet. Will update this bug when we do.
Test with brew-pulp.../openshift3/jenkins-2-rhel7@sha256:19cbf5987b692ea7bea9be30c7e6ad4a149f77a063c563e746ff0f31e9a6bc53
1.$ oc policy add-role-to-user admin system:serviceaccount:dyantest:jenkins -n dyan2
1.Go to "Manage Jenkins" -> "Configure System" -> "OpenShift Jenkins Sync", input namespace name which want to sync in "Namespace" box.
Actual result: could see pipeline build from other namespace sync into jenkins
But there is an issue, if I start a new pipeline build, it will execute action defined in pipeline build twice.
I use https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/pipeline/samplepipeline.yaml to create pipeline build, if I execute
$ oc start-build sample-pipeline , then the build "sample-pipeline-2" will trigger "nodejs-mongodb-example-2" and "nodejs-mongodb-example-3"
# oc get build -n dyan2
NAME TYPE FROM STATUS STARTED DURATION
nodejs-mongodb-example-1 Source Git@e81cacf Complete 5 hours ago 38s
nodejs-mongodb-example-2 Source Git@e81cacf Complete 21 minutes ago 18s
nodejs-mongodb-example-3 Source Git@e81cacf Complete 21 minutes ago 17s
sample-pipeline-1 JenkinsPipeline Complete 5 hours ago
sample-pipeline-2 JenkinsPipeline Complete 21 minutes ago
so is it normal, should I file a bug for it
have reported this https://bugzilla.redhat.com/show_bug.cgi?id=1443009