[JIRA] (JENKINS-12877) Problem to configure perforce plugin and maven release plugin
Hugo Lassiège commented on JENKINS-12877 Problem to configure perforce plugin and maven release plugin I have more time to investigate on that this week ^^ So, the problem is that every P4 variables are not exported to the environment for post build actions. All variables declared in the perforce section are not exposed in the environment when the maven command is runned. So we end up with several errors due to P4CHARSET, P4CLIENT, P4USER not known. It fails even if I add a pre build step to set this variable through a shell script. I guess the pre build script is not runned on the same environnement and so my EXPORT commands are useless for post build actions. So the question is, is it possible for the jenkins perforce plugin to expose these variables to the build when maven is invoked ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12877) Problem to configure perforce plugin and maven release plugin
Hugo Lassiège created JENKINS-12877:
---
Summary: Problem to configure perforce plugin and maven release
plugin
Key: JENKINS-12877
URL: https://issues.jenkins-ci.org/browse/JENKINS-12877
Project: Jenkins
Issue Type: Bug
Components: perforce, release
Affects Versions: current
Environment: unix (centos)
jenkins 1.447
perforce plugin 1.3.7
jenkins maven release plugin 0.9.0
Reporter: Hugo Lassiège
Assignee: Peter Hayes
Hi,
I try to use jenkins maven release plugin on Jenkins with a perforce SCM.
However, I have a weird error. In debug mode I see the following messages :
[DEBUG] SCM path in pom: //depot/AirTravelServer/main/
[DEBUG] Executing: /bin/sh -c p4 -p srvpar5p4p01:1992 where
/home/www-data/.jenkins/jobs/ATS-TRUNK-RELEASE/workspace/pom.xml
[DEBUG] p4 can not support a wide charset unless
and the stacktrace :
{code}
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of
range: -2
at java.lang.String.substring(String.java:1937)
at
org.apache.maven.scm.provider.perforce.command.PerforceWhereCommand.getDepotLocation(PerforceWhereCommand.java:117)
at
org.apache.maven.scm.provider.perforce.command.PerforceWhereCommand.getDepotLocation(PerforceWhereCommand.java:61)
at
org.apache.maven.scm.provider.perforce.PerforceScmProvider.getRepoPath(PerforceScmProvider.java:466)
at
org.apache.maven.scm.provider.perforce.command.status.PerforceStatusCommand.executeStatusCommand(PerforceStatusCommand.java:57)
at
org.apache.maven.scm.command.status.AbstractStatusCommand.executeCommand(AbstractStatusCommand.java:44)
at
org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
{code}
The problem is due to : p4 can not support a wide charset unless
I've configured P4CHARSET to utf16le-bom and I've tried several different
charsets for P4COMMANDCHARSET : winansi, utf8, none
The problem exists only for maven release plugin. I don't have this error with
mvn install.
Do you know what is the right configuration to make it works ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12877) Problem to configure perforce plugin and maven release plugin
[
https://issues.jenkins-ci.org/browse/JENKINS-12877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Petti updated JENKINS-12877:
Component/s: (was: perforce)
This is unrelated to the perforce plugin, and in fact may be unrelated to
Jenkins at all... It's looks purely like a maven error to me.
Problem to configure perforce plugin and maven release plugin
-
Key: JENKINS-12877
URL: https://issues.jenkins-ci.org/browse/JENKINS-12877
Project: Jenkins
Issue Type: Bug
Components: release
Affects Versions: current
Environment: unix (centos)
jenkins 1.447
perforce plugin 1.3.7
jenkins maven release plugin 0.9.0
Reporter: Hugo Lassiège
Assignee: Peter Hayes
Labels: perforce
Hi,
I try to use jenkins maven release plugin on Jenkins with a perforce SCM.
However, I have a weird error. In debug mode I see the following messages :
[DEBUG] SCM path in pom: //depot/AirTravelServer/main/
[DEBUG] Executing: /bin/sh -c p4 -p srvpar5p4p01:1992 where
/home/www-data/.jenkins/jobs/ATS-TRUNK-RELEASE/workspace/pom.xml
[DEBUG] p4 can not support a wide charset unless
and the stacktrace :
{code}
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of
range: -2
at java.lang.String.substring(String.java:1937)
at
org.apache.maven.scm.provider.perforce.command.PerforceWhereCommand.getDepotLocation(PerforceWhereCommand.java:117)
at
org.apache.maven.scm.provider.perforce.command.PerforceWhereCommand.getDepotLocation(PerforceWhereCommand.java:61)
at
org.apache.maven.scm.provider.perforce.PerforceScmProvider.getRepoPath(PerforceScmProvider.java:466)
at
org.apache.maven.scm.provider.perforce.command.status.PerforceStatusCommand.executeStatusCommand(PerforceStatusCommand.java:57)
at
org.apache.maven.scm.command.status.AbstractStatusCommand.executeCommand(AbstractStatusCommand.java:44)
at
org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
{code}
The problem is due to : p4 can not support a wide charset unless
I've configured P4CHARSET to utf16le-bom and I've tried several different
charsets for P4COMMANDCHARSET : winansi, utf8, none
The problem exists only for maven release plugin. I don't have this error
with mvn install.
Do you know what is the right configuration to make it works ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
