Re: Unable to release project from a specific jenkins box using m2 release plugin and perforce SCM

2013-09-24 Thread Daniel B
Did you ever resolve this? I'm seeing the same problem on a CentOS box.

Thanks

On Monday, 8 July 2013 12:22:01 UTC-4, Usman Ismail wrote:

 Both the job failing and succeeding are running on OSX boxes.

 On Monday, July 8, 2013 9:21:30 AM UTC-7, Usman Ismail wrote:

 The password is simple its just the user name that has the slash.
 Its running on an OSX box.

 On Monday, July 8, 2013 1:20:42 AM UTC-7, James Nord (jnord) wrote:

  Passwords with any shell special characters aren’t handled properly 
 (there is an open JIRA).

  

 So ‘\’ on Unix like OSs will want some escaping – try your password with 
 \\ instead of a single backslash – or put quotes around it.

  

 Is your other box which can perform releases a windows box?  That’s the 
 only reason I can think of that it works on one and not on another.

  

 /James

  

  
   
 *From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] 
 *On Behalf Of *Usman Ismail
 *Sent:* 06 July 2013 01:15
 *To:* jenkins...@googlegroups.com
 *Subject:* Unable to release project from a specific jenkins box using 
 m2 release plugin and perforce SCM
  
  

 I am using the maven release plungin using the jenkins m2release plugin 
 and keep getting the error shouwn below.

 The username and password is correct as I have tested it on other 
 machines and also to get source from this jenkins box. The password only 
 fails on release and not at any other point.

 The only weird thing I can think off is that the user name has a '\' in 
 it but this does seem to the phase my other jenkins box which works 
 correctly.

 Is there anything I can do get a more detailed error message or debug 
 whats going on?

 [INFO] 
 [INFO] --- maven-release-plugin:2.4:prepare (default-cli) @ 
 cascade-proto ---
 [INFO] Verifying that there are no local modifications...
 [INFO]   ignoring changes on: **/pom.xml.backup, **/release.properties, 
 **/pom.xml.branch, **/pom.xml.next, **/pom.xml.releaseBackup, **/pom.xml.tag
 [ERROR] CommandLineException Exit code: 1 - Perforce password (P4PASSWD) 
 invalid or unset.

 Command line was:p4 -d /opt/hudson_workspace01/jobs/JOB-NAME/workspace 
 -p perforceserver.com:1666 -u A\b -P *** 
 opened //X/XX/XX-XXX/...
 org.codehaus.plexus.util.cli.CommandLineException: Exit code: 1 - 
 Perforce password (P4PASSWD) invalid or unset.

 Command line was:p4 -d /opt/hudson_workspace01/jobs/JOB-NAME/workspace 
 -p perforceserver.com:1666 -u A\b -P *** 
 opened //X/XX/XX-XXX/...
 at 
 org.apache.maven.scm.provider.perforce.command.status.PerforceStatusCommand.readOpened(PerforceStatusCommand.java:116)
 at 
 org.apache.maven.scm.provider.perforce.command.status.PerforceStatusCommand.executeStatusCommand(PerforceStatusCommand.java:59)
 at 
 org.apache.maven.scm.command.status.AbstractStatusCommand.executeCommand(AbstractStatusCommand.java:44)
 at 
 org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
 at 
 org.apache.maven.scm.provider.perforce.PerforceScmProvider.status(PerforceScmProvider.java:226)
 at 
 org.apache.maven.scm.provider.AbstractScmProvider.status(AbstractScmProvider.java:793)
 at 
 org.apache.maven.shared.release.phase.ScmCheckModificationsPhase.execute(ScmCheckModificationsPhase.java:126)
 at 
 org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:234)
 at 
 org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:169)
 at 
 org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:146)
 at 
 org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:107)
 at 
 org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:277)
 at 
 org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:232)
 at 
 org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
 at 
 org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
 at 
 org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
 at 
 org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 

Re: M2 Release Plugin + SVN

2012-06-06 Thread Daniel B
Does anyone know how to pass the jenkins saved credentials to the M2
release plugin, rather than specifying the username and password  in
the build parameters?

Thanks

Dan

On May 21, 11:27 am, Nord, James jn...@nds.com wrote:
 Add -Dusername=releaseuser to the command line (if different from the user 
 that runs Jenkins)

 Authenticate against SVN server using the svn command line tools on the slave
 (this updates ~jenkinsuser/.subversion/auth/)
 Copy that around all your slaves.

 Jenkins also has the ability somewhere to store the credentials it uses to 
 checkout in the auth cache.

 YMMV.

 /James

  -Original Message-
  From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
  us...@googlegroups.com] On Behalf Of BusyByte
  Sent: 21 May 2012 16:23
  To: Jenkins Users
  Subject: M2 Release Plugin + SVN

  How do I pass my credentials for maven to do the SCM plugin stuff for the
  Maven Release.
  I don't want each job to have to enter the process id username/ password.
  I tried to put it in my settings.xml by the base host name for svn server.
  EGhttps://myhost/mysvnpathI put a server entry with: idmyshostid

 *** 
 ***
 This message is confidential and intended only for the addressee. If you have 
 received this message in error, please immediately notify the 
 postmas...@nds.com and delete it from your system as well as any copies. The 
 content of e-mails as well as traffic data may be monitored by NDS for 
 employment and security purposes. To protect the environment please do not 
 print this e-mail unless necessary.

 NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 
 4EX, United Kingdom. A company registered in England and Wales. Registered 
 no. 3080780. VAT no. GB 603 8808 40-00
 *** 
 ***