-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
2.0-alpha3
There are a couple sections in the Git SCM configuration that have a red "X" button in them. When you click those red Xs the sections disappear and there is no way to recover them past reloading the page.
Switching the radio buttons around doesn't appear to bring the UI elements back either 
- is related to
-
-
- Closed
-
-
-
- Closed
-
[JENKINS-33564] Sections of "Git" SCM configuration can be X'd out but not restored
gus reiber
added a comment - yup.
I think it will need to wait for the merge traffic jam. But yup. Top of the list.
gus reiber
added a comment - yup.
I think it will need to wait for the merge traffic jam. But yup. Top of the list. gus reiber
added a comment - I agree that this is a critical issue, and although I haven't seen it, likely blocks 2.0.
Don't think much can be done about it until 31162 is merged.
...so critical, yes. Blocking, probability, but I think it is work that has to be serialized and it isn't quite first.
gus reiber
added a comment - I agree that this is a critical issue, and although I haven't seen it, likely blocks 2.0.
Don't think much can be done about it until 31162 is merged.
...so critical, yes. Blocking, probability, but I think it is work that has to be serialized and it isn't quite first. gus reiber
added a comment - So this is a bug with the git plugin not the new UI: http://jenkins.beedemo.net/api-team/job/sandbox/job/FreeGit/configure
gus reiber
added a comment - So this is a bug with the git plugin not the new UI: http://jenkins.beedemo.net/api-team/job/sandbox/job/FreeGit/configure gus reiber
added a comment - this behavior is wrong, but it is the plugin behavior. gusreiber the link you cite is behind an authentication wall, so I'm not entirely sure what you're attempting to show there.
I've attached a screenshot from 1.652 and it appears that my confusion in the new UI was that the "Delete Repository" and "Delete Branch" become new "{x]" buttons.
I agree with gusreiber's assessment that this isn't a bug with the new job configuration UI, but I disagree in that I still believe this to be a bug. for the Git plugin. I've updated the ticket accordingly.
Please roll your git plugin version back to 2.4.2. There is a bug reported in 2.4.3 that certain configurations are not preserved. It appears that my attempt to fix findbugs warnings in 2.4.3 had a very bad side effect of damaging the configuration load / store process. Refer to JENKINS-33695 for more information on the specific issue that was visible in 2.4.3 and not visible in 2.4.2.
gusreiber PTAL at this.