[JENKINS-15293] Can't configure Maven Installations on Jenkins ver. 1.483, 1.484 - Jenkins Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Blocker
Resolution: Fixed
Component/s: maven-plugin
Labels:
None
Environment:
Jenkins 1.483, Ubuntu 12.04 LTS, running Jenkins standalone with Java.
Jenkins 1.484, Ubuntu 10.04 LTS, running Jenkins standalone with Java.

Similar Issues:

Show

Description

After configuring Maven installations (with installer from apache) and clicking save, the Maven installations aren't saved.

Logging on fine doesnt produce any reason about the problem.

Manually copying an older hudson.tasks.Maven.xml works.
Looking at recent bug fixes, I see that ~~JENKINS-14510~~ got integrated in this build.

I will try installing 1.482 and see if it resolves the problem.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

hudson.tasks.Maven.xml
1.0 kB
2012-09-25 07:17

Issue Links

is duplicated by

JENKINS-15312 maven installation settings get lost

Resolved

is related to

JENKINS-14510 NPE at hudson.maven.MavenModuleSet.getMaven(MavenModuleSet.java:982)

Closed

Activity

Ascending order - Click to sort in descending order

Jeroen Ferdinandus created issue - 2012-09-25 07:17

Jeroen Ferdinandus made changes - 2012-09-25 07:19

Field	Original Value	New Value
Environment	Jenkins 1.483, Ubuntu	Jenkins 1.483, Ubuntu 12.04 LTS, running Jenkins standalone with Java.
Summary	Can't configure Maven Installations on Jenkins ver. 1.483 after upgrade from 1.470	Can't configure Maven Installations on Jenkins ver. 1.483 after manual upgrade from 1.470

Jeroen Ferdinandus made changes - 2012-09-25 07:32

Description

After configuring Maven installations (with installer from apache) and clicking save, the Maven installations aren't saved.

Logging on fine doesnt produce any reason about the problem.

Manually copying an older hudson.tasks.Maven.xml does not seem to work either. Looking at recent bug fixes, I see that ~~JENKINS-14510~~ got integrated in this build.

I will try installing 1.482 and see if it resolves the problem.

After configuring Maven installations (with installer from apache) and clicking save, the Maven installations aren't saved.

Logging on fine doesnt produce any reason about the problem.

Manually copying an older hudson.tasks.Maven.xml works.
Looking at recent bug fixes, I see that ~~JENKINS-14510~~ got integrated in this build.

I will try installing 1.482 and see if it resolves the problem.

Jeroen Ferdinandus added a comment - 2012-09-25 07:52 - edited

In 1.482 it is possible to add new Maven installations.

After I upgrade to 1.843 again and try adding a new Maven installation, all previously added Maven installations are removed.

Jeroen Ferdinandus added a comment - 2012-09-25 07:52 - edited In 1.482 it is possible to add new Maven installations. After I upgrade to 1.843 again and try adding a new Maven installation, all previously added Maven installations are removed.

Jeroen Ferdinandus made changes - 2012-09-25 08:01

Priority

Critical [ 2 ]

Blocker [ 1 ]

John Harvey added a comment - 2012-09-25 12:27

Same issue seen on Debian 6.0.5. Jenkins 1.483 has a bug that the config is unable to be saved, resulting in no jobs able to be run. Downgrading to 1.482 also fixed it.

John Harvey added a comment - 2012-09-25 12:27 Same issue seen on Debian 6.0.5. Jenkins 1.483 has a bug that the config is unable to be saved, resulting in no jobs able to be run. Downgrading to 1.482 also fixed it.

Michael Fraefel added a comment - 2012-09-27 07:37

The same on Windows 2003 Server.

Michael Fraefel added a comment - 2012-09-27 07:37 The same on Windows 2003 Server.

Jeroen Ferdinandus added a comment - 2012-09-27 07:44

Updated title to reflect the general problem with 1.483, since it seems it is not related to the upgrade from 1.470.

Jeroen Ferdinandus added a comment - 2012-09-27 07:44 Updated title to reflect the general problem with 1.483, since it seems it is not related to the upgrade from 1.470.

Jeroen Ferdinandus made changes - 2012-09-27 07:44

Summary

Can't configure Maven Installations on Jenkins ver. 1.483 after manual upgrade from 1.470

Can't configure Maven Installations on Jenkins ver. 1.483

Mirko Friedenhagen added a comment - 2012-09-28 09:45

Downgrading to 1.482 fixed this for me as well on Ubuntu 10.04 LTS.

Mirko Friedenhagen added a comment - 2012-09-28 09:45 Downgrading to 1.482 fixed this for me as well on Ubuntu 10.04 LTS.

Larry Shatzer, Jr. made changes - 2012-09-28 20:00

Link

This issue is related to ~~JENKINS-14510~~ [ ~~JENKINS-14510~~ ]

Mirko Friedenhagen added a comment - 2012-10-01 08:08

Still there in 1.484. That's really annoying.

Mirko Friedenhagen added a comment - 2012-10-01 08:08 Still there in 1.484. That's really annoying.

Mirko Friedenhagen made changes - 2012-10-01 08:08

Environment	Jenkins 1.483, Ubuntu 12.04 LTS, running Jenkins standalone with Java.	Jenkins 1.483, Ubuntu 12.04 LTS, running Jenkins standalone with Java. Jenkins 1.484, Ubuntu 10.04 LTS, running Jenkins standalone with Java.
Summary	Can't configure Maven Installations on Jenkins ver. 1.483	Can't configure Maven Installations on Jenkins ver. 1.483, 1.484

Mirko Friedenhagen added a comment - 2012-10-01 08:30

Hello,

I inspected https://github.com/mpapo/jenkins/commit/01482bf3de81f539b7ae4746fd127ca75915a726 and found the problem:

While all Maven installations have a name, those being resolved automatically (e.g. downloaded from Apache directly) do not have a home field set explicitly.
So the for loop just removes these from tmpList and the list is empty in the end.
Maven installations given manually, e.g. you provide a path will stay.

Regards
Mirko

Mirko Friedenhagen added a comment - 2012-10-01 08:30 Hello, I inspected https://github.com/mpapo/jenkins/commit/01482bf3de81f539b7ae4746fd127ca75915a726 and found the problem: While all Maven installations have a name, those being resolved automatically (e.g. downloaded from Apache directly) do not have a home field set explicitly. So the for loop just removes these from tmpList and the list is empty in the end. Maven installations given manually, e.g. you provide a path will stay. Regards Mirko

Jeroen Ferdinandus made changes - 2012-10-01 09:30

Link

This issue is duplicated by ~~JENKINS-15312~~ [ ~~JENKINS-15312~~ ]

Michael Pailloncy made changes - 2012-10-01 10:35

Assignee

Pailloncy Michaël [ mpapo ]

SCM/JIRA link daemon added a comment - 2012-10-01 15:07

Code changed in jenkins
User: Olivier Lamy
Path:
core/src/main/java/hudson/tasks/Maven.java
http://jenkins-ci.org/commit/jenkins/7daa5ef1b245fd7a8887bbc6274be080a52a4d23
Log:
Merge pull request #581 from mpapo/~~JENKINS-15293~~

Fixed ~~JENKINS-15293~~
Thanks

Compare: https://github.com/jenkinsci/jenkins/compare/14098be5db0e...7daa5ef1b245

SCM/JIRA link daemon added a comment - 2012-10-01 15:07 Code changed in jenkins User: Olivier Lamy Path: core/src/main/java/hudson/tasks/Maven.java http://jenkins-ci.org/commit/jenkins/7daa5ef1b245fd7a8887bbc6274be080a52a4d23 Log: Merge pull request #581 from mpapo/ JENKINS-15293 Fixed JENKINS-15293 Thanks Compare: https://github.com/jenkinsci/jenkins/compare/14098be5db0e...7daa5ef1b245

SCM/JIRA link daemon added a comment - 2012-10-01 15:10

Code changed in jenkins
User: Olivier Lamy
Path:
changelog.html
http://jenkins-ci.org/commit/jenkins/c0df15ab38c2fef8592d38451cef0ba68ebc64d0
Log:
changelog entry for ~~JENKINS-15293~~

SCM/JIRA link daemon added a comment - 2012-10-01 15:10 Code changed in jenkins User: Olivier Lamy Path: changelog.html http://jenkins-ci.org/commit/jenkins/c0df15ab38c2fef8592d38451cef0ba68ebc64d0 Log: changelog entry for JENKINS-15293

cowwoc added a comment - 2012-10-01 16:52

Olivier,

Maybe I misunderstood, but shouldn't the OR in the condition be an AND? That is, we only want to remove installations if they have an empty name and an empty home directory. Right?

cowwoc added a comment - 2012-10-01 16:52 Olivier, Maybe I misunderstood, but shouldn't the OR in the condition be an AND? That is, we only want to remove installations if they have an empty name and an empty home directory. Right?

Michael Pailloncy added a comment - 2012-10-01 18:02

The bug https://issues.jenkins-ci.org/browse/JENKINS-14510 is related to a NPE on Maven installation name. So, I think just a check on the maven installation name will be sufficient.

Michael Pailloncy added a comment - 2012-10-01 18:02 The bug https://issues.jenkins-ci.org/browse/JENKINS-14510 is related to a NPE on Maven installation name. So, I think just a check on the maven installation name will be sufficient.

Deepak Mahale added a comment - 2012-10-03 05:20

Hi,
I had a similar problem with ANT, JDK, MSBuild installation configs (all of which were already installed and i had added the proper paths to each) when i upgraded Jenkins. I was also experimenting with the files so even the uninstall and install had stopped working and the Jenkins service stopped altogether.

I followed the the steps mentioned below and it resolved the problem for me:
1. Uninstall Jenkins
2. Restart system
3. Delete the Jenkins Installation directory
4. Manually remove the registry keys using 'regedit'
5. Restart system
6. Install Jenkins
From then on i haven't had problems with updates and configs.

I've never used Maven and do not know if this is a separate issue.
Regards

Deepak Mahale added a comment - 2012-10-03 05:20 Hi, I had a similar problem with ANT, JDK, MSBuild installation configs (all of which were already installed and i had added the proper paths to each) when i upgraded Jenkins. I was also experimenting with the files so even the uninstall and install had stopped working and the Jenkins service stopped altogether. I followed the the steps mentioned below and it resolved the problem for me: 1. Uninstall Jenkins 2. Restart system 3. Delete the Jenkins Installation directory 4. Manually remove the registry keys using 'regedit' 5. Restart system 6. Install Jenkins From then on i haven't had problems with updates and configs. I've never used Maven and do not know if this is a separate issue. Regards

Mirko Friedenhagen added a comment - 2012-10-10 06:33

deepak: I would not know that Jenkins saves it's information about helper programs in the Windows registry. I think you would be better off opening another issue as the Maven bug is clearly gone. You might link to this item (see "More Actions"). And it would be helpful if you stated which registry keys you did delete.

Mirko Friedenhagen added a comment - 2012-10-10 06:33 deepak : I would not know that Jenkins saves it's information about helper programs in the Windows registry. I think you would be better off opening another issue as the Maven bug is clearly gone. You might link to this item (see "More Actions"). And it would be helpful if you stated which registry keys you did delete.

Jeroen Ferdinandus added a comment - 2012-10-10 06:58 - edited

The update to Jenkins 1.485 has resolved this issue.

Jeroen Ferdinandus added a comment - 2012-10-10 06:58 - edited The update to Jenkins 1.485 has resolved this issue.

Jeroen Ferdinandus made changes - 2012-10-10 06:58

Fix Version/s		current [ 10162 ]
Resolution		Fixed [ 1 ]
Status	Open [ 1 ]	Resolved [ 5 ]

Michael Pailloncy added a comment - 2013-01-12 09:16

Bug due to a correction made for https://issues.jenkins-ci.org/browse/JENKINS-14510 -> resolved since 1.485

Michael Pailloncy added a comment - 2013-01-12 09:16 Bug due to a correction made for https://issues.jenkins-ci.org/browse/JENKINS-14510 -> resolved since 1.485

Michael Pailloncy made changes - 2013-01-12 09:16

Status

Resolved [ 5 ]

Closed [ 6 ]

R. Tyler Croy made changes - 2016-07-26 00:00

Workflow

JNJira [ 146016 ]

JNJira + In-Review [ 206173 ]

People

Assignee:: Michael Pailloncy

Reporter:: Jeroen Ferdinandus

Votes:: 9 Vote for this issue

Watchers:: 16 Start watching this issue

Dates

Created:: 2012-09-25 07:17

Updated:: 2013-01-12 09:16

Resolved:: 2012-10-10 06:58