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

[Usman Ismail]

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 "AAAAAAAAA\bbbbbbbbb" -P *********** opened //XXXXXXXXX/XXXXXX/XXXXXX-XXXXXXX/...
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 "AAAAAAAAA\bbbbbbbbb" -P *********** opened //XXXXXXXXX/XXXXXX/XXXXXX-XXXXXXX/...
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 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:98)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:64)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)

[James Nord (jnord)]

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

 

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Usman Ismail]

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

[Usman Ismail]

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

[Daniel B]

Did you ever resolve this? I'm seeing the same problem on a CentOS box.

Thanks

[Usman Ismail]

No idea if this is the canonical solution but I resolved the issue but adding the following line to to the Script Content field in the Inject environment variables setting. This way a ticket file is created on the Jenkins Slave before every build. See attached screen-cap.

echo ${P4PASSWD} | p4 login -a

--Usman

> --
> You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/dMTw_FrSLcU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.