Description of problem: Currently jenkins-sync-plugin uses version 5.18 but that doesn't work when you install the jenkins-sync-plugin on a newer jenkins with a newer version of the cloubees-folder plugin, such as version 6.6. What happens is that the synced jobs do not end up in the correct folder which then causes none of the build start and syncing to work. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. install jenkins-sync-plugin in CloudBees 2.x 2. attempt to do pipeline sync 3. pipelines will show up but wont be able to start becasue they wont be nested in the correct folder Actual results: pipelines will show up but wont be able to start becasue they wont be nested in the correct folder Expected results: pipelines should be put in the correct folder Additional info: https://github.com/openshift/jenkins-sync-plugin/pull/275 I couldn't find a component for the jenkins-sync-plugin so just took a stab about where to put this bugzilla.
the jenkins image and sync plugin have been updated to allow this move to 6.6 cloudbees-folders Ian reported that the initial pipeline bc job creation was now going into the folder, but subsequent ones were not. When I circle back to this, if I can reproduce that locally, I'll investigate what additional (probably sync plugin) changes are needed. Otherwise, this possibly is an issue with his custom env.
I've verified the version is updated. Moving to verified directly. I've exchanged some comments with Ian in his PR. We'll open a separate bugzilla for any other issues wrt folders if it relates to the sync plugin.
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-2019:0758