Red Hat Bugzilla – Bug 1304892
jenkins "perform builds" module constantly resets buildconfig name to "frontend"
Last modified: 2016-02-05 10:59:39 EST
I'm not sure if this is a UI thing or an actual data thing, but every time I hit "SAVE" in Jenkins and come back to configure the project, the buildconfig name in the "perform builds" module is reset to "frontend" docker.io/openshift/jenkins-1-centos7 latest 066a52bb8fa4 2 days ago 652.3 MB
pretty sure that's been reported and fixed. not sure why the fix wouldn't be in your image given that it looks current.
this was reported with https://github.com/openshift/jenkins-plugin/issues/10 and fixed in version 1.0.5 of the plugin. I just pulled down this image (066a52bb8fa4) myself and tried it and the build config name is *NOT* reset to frontend after I changed and saved it. It stays at what I changed it to. We could go down a couple of different paths to see what is different. Let's start with verifying the plugin version, in the off chance we are not dealing wiht . Bring up the image you are seeing this with, and from the main dashboard go to "Manage Jenkins", then "Manage Plugins", then go to the installed tab (the uri in the browser should be "pluginManager/installed"). Confirm the OpenShift Pipeline plugin is at V1.0.7. If so, we'll start worrying about browser differences, exact steps you performed, etc.
the output from docker ps -a and a docker inspect <container id> of the jenkins image that was run could also be quick ways to verify / confirm some things.
Today it doesn't appear to be doing it... so... I dunno.
As an FYI, both upstream and QA reported this previously and were able to verify the fix. Suspect the bug occurred using an image other than 066a52bb8fa4, but we'll see if it shows up again as Erik continues to experiment with the plugin, go from there.