• Type: Bug
• Resolution: Won't Fix
• Priority: Major
• Component/s: m2release-plugin
• Labels:

  None
• Environment:

  Linux gentoo

[JENKINS-5167] M2 release plugin does not take care of CVS configuration in admin panel

Collapse comment: Dominik Bartholdi added a comment - 2011-12-20 18:14

Dominik Bartholdi added a comment - 2011-12-20 18:14

all this plugin does, is trigger maven with the correct command line arguments.
So its not the m2release plugin looking for the .cvspass in "/home/tomcat/.cvspass" but maven. The reason for this is most probably, because this "/home/tomcat/" is the home directory of the user you'r running jenkins with.

Expand comment: Dominik Bartholdi added a comment - 2011-12-20 18:14

Dominik Bartholdi added a comment - 2011-12-20 18:14 all this plugin does, is trigger maven with the correct command line arguments. So its not the m2release plugin looking for the .cvspass in "/home/tomcat/.cvspass" but maven. The reason for this is most probably, because this "/home/tomcat/" is the home directory of the user you'r running jenkins with.

Collapse comment: Michael Clarke added a comment - 2012-01-29 09:43

Michael Clarke added a comment - 2012-01-29 09:43

The .cvspass file config option was for the cvs plugin and, as of version 2.0 of this plugin, is no longer available (.cvspass is unsecure and we don't want to force users to use it).

There's also no way for us to tell Maven where the cvspass file is location - it assumes that it's in user.home by default - so even if we did read the cvsplugin configiration, we'd have no way of using the value.

Given these issues, I'm closing this as wont fix. Consider running the 'cvs login' command under the user account you have running Tomcat/Jenkins is you still need Maven to login to CVS.

Expand comment: Michael Clarke added a comment - 2012-01-29 09:43

Michael Clarke added a comment - 2012-01-29 09:43 The .cvspass file config option was for the cvs plugin and, as of version 2.0 of this plugin, is no longer available (.cvspass is unsecure and we don't want to force users to use it). There's also no way for us to tell Maven where the cvspass file is location - it assumes that it's in user.home by default - so even if we did read the cvsplugin configiration, we'd have no way of using the value. Given these issues, I'm closing this as wont fix. Consider running the 'cvs login' command under the user account you have running Tomcat/Jenkins is you still need Maven to login to CVS.