Description of problem:
Opened against https://github.com/openshift/jenkins-sync-plugin/issues/307
I should have the PR up later today
When that merges, I'll cut a new version of the sync plugin which based on the exchanges in
https://github.com/openshift/jenkins-sync-plugin/issues/307 Everett should be able to apply
in the customer env.
The process of cutting new openshift-jenkins images and errata / zstream will start in
parallel once the new version of the sync plugin is cut.
PR https://github.com/openshift/jenkins-sync-plugin/pull/308 contains the proposed fix and is up for review
Updating target release to v4.2.0
@gmontero please clone this BZ if we backport the plugin fix to the 4.1.z and/or 3.11.z Jenkins images.
PR https://github.com/openshift/jenkins/pull/853 to update the image with v1.0.37 of the sync plugin is up
PR https://github.com/openshift/jenkins/pull/855 updates the upstream 3.11 branch to v1.0.37 of the sync plugin
looks like we have new images on brew for this
The created Kubernetes Pod Template using the ConfigMap style will not removed more than a dozen hours.
openshift3/jenkins-2-rhel7:v3.11 (v3.11.117 47da6bb652f4)
with openshift-sync : 1.0.37 installed
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.