Description of problem: If a JenkinsPipeline strategy build is created via `oc new-app` or `oc new-build`, it can take several minutes for Jenkins to run the build when using v1.0.47 of the sync plugin. This is a regression from v1.0.46, when new builds are picked up instantly by the sync plugin Version-Release number of selected component (if applicable): v1.0.47 How reproducible: Always Steps to Reproduce: 1. Install Jenkins on OCP via the provided template (ephemeral OK) 2. Update the sync plugin to v1.0.47 in the Jenkins console 3. Create a Jenkins Pipeline build via oc new-app: $ oc new-app https://github.com/gabemontero/test-jenkins-bc-env-var-override.git --strategy=pipeline --build-env=FOO1=BAR1 Actual results: Jenkins takes several minutes to pick up the build and start the pipeline Expected results: Jenkins starts the pipeline in less than 1 minute with a cluster under low load. Additional info: See https://github.com/openshift/jenkins/pull/1297#issuecomment-877387292
As this bug is specific to v1.0.47 of the sync plugin, and that version will never be incorporated into any OCP release (and we don't do errata for upstream releases of plugins), marking this no doc. Also, will immediately verify when the PR merges. Jitender can handle verification with 1925524
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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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/RHSA-2021:3759