-
Bug
-
Resolution: Duplicate
-
Blocker
-
OS: Ubuntu 14.04
Jenkins: 2.27 (installed & updated from official APT repo)
Maven Plugin: 2.14 & 2.13
Since:
I assume it lasts for at least 3 weeks.
Until a recent update (didn't receive the detail from our dev team about the bug right after the update so not sure to which it applies)
I also downgrade to 2.13 with no luck
When:
Both upon job creation and job modification
How to reproduce:
Create a Maven job and fill the fields "Root POM" and "Goals and Options" in Build with random (but valid ...) values
The matching values in the config.xml are not created
How to counterpass this:
Edit the config.xml file via SSH and restart Jenkins so it re-parse the file
- duplicates
-
JENKINS-39078 Config UI in job broken / unusable
-
- Closed
-
- is related to
-
JENKINS-39078 Config UI in job broken / unusable
-
- Closed
-
[JENKINS-39214] "Goals and Options" and "Root POM" not written to config.xml
Rank | New: Ranked higher |
Description |
Original:
Since: I assume it lasts for at least 3 weeks. Until a recent update (didn't receive the detail from our dev team about the bug right after the update so not sure to which it applies) When: Both upon job creation and job modification How to reproduce: Create a job and fill the fields "Root POM" and "Goals and Options" in Build with random (but valid ...) values The matching values in the config.xml are not created How to counterpass this: Edit the config.xml file via SSH and restart Jenkins so it re-parse the file |
New:
Since: I assume it lasts for at least 3 weeks. Until a recent update (didn't receive the detail from our dev team about the bug right after the update so not sure to which it applies) When: Both upon job creation and job modification How to reproduce: Create a Maven job and fill the fields "Root POM" and "Goals and Options" in Build with random (but valid ...) values The matching values in the config.xml are not created How to counterpass this: Edit the config.xml file via SSH and restart Jenkins so it re-parse the file |
Description |
Original:
Since: I assume it lasts for at least 3 weeks. Until a recent update (didn't receive the detail from our dev team about the bug right after the update so not sure to which it applies) When: Both upon job creation and job modification How to reproduce: Create a Maven job and fill the fields "Root POM" and "Goals and Options" in Build with random (but valid ...) values The matching values in the config.xml are not created How to counterpass this: Edit the config.xml file via SSH and restart Jenkins so it re-parse the file |
New:
Since: I assume it lasts for at least 3 weeks. Until a recent update (didn't receive the detail from our dev team about the bug right after the update so not sure to which it applies) I also downgrade to 2.13 with no luck When: Both upon job creation and job modification How to reproduce: Create a Maven job and fill the fields "Root POM" and "Goals and Options" in Build with random (but valid ...) values The matching values in the config.xml are not created How to counterpass this: Edit the config.xml file via SSH and restart Jenkins so it re-parse the file |
Environment |
Original:
OS: Ubuntu 14.04 Jenkins: 2.27 (installed & updated from official APT repo) Maven Plugin: 2.14 |
New:
OS: Ubuntu 14.04 Jenkins: 2.27 (installed & updated from official APT repo) Maven Plugin: 2.14 & 2.13 |
Attachment | New: POST.png [ 34492 ] |
Hrrm - I can't reproduce this with a fresh install of Jenkins 2.27 and Maven plugin 2.14 on OS X (just using the war file). Does anything show up in the Jenkins log on the master when you try to save a Maven job with changed goals/root POM?