Bug 1304892 - jenkins "perform builds" module constantly resets buildconfig name to "frontend"
jenkins "perform builds" module constantly resets buildconfig name to "frontend"
Product: OpenShift Origin
Classification: Red Hat
Component: Image (Show other bugs)
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Gabe Montero
Wang Haoran
Depends On:
  Show dependency treegraph
Reported: 2016-02-04 17:35 EST by Erik M Jacobs
Modified: 2016-02-05 10:59 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-02-05 10:49:19 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
gmontero: needinfo+

Attachments (Terms of Use)

  None (edit)
Description Erik M Jacobs 2016-02-04 17:35:14 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
Comment 1 Ben Parees 2016-02-04 18:20:44 EST
pretty sure that's been reported and fixed.  not sure why the fix wouldn't be in your image given that it looks current.
Comment 2 Gabe Montero 2016-02-04 22:49:10 EST
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.
Comment 3 Gabe Montero 2016-02-05 09:26:14 EST
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.
Comment 4 Erik M Jacobs 2016-02-05 10:49:19 EST
Today it doesn't appear to be doing it... so... I dunno.
Comment 5 Gabe Montero 2016-02-05 10:59:39 EST
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.

Note You need to log in before you can comment on or make changes to this bug.