No, P$CHARSET is not set, but the password contains only US-ASCII
characters. Also, I have verified there is no typo.
On Monday, September 22, 2014 12:16:47 PM UTC+3, Jan Seidel wrote:
>
> Is P4CHARSET set to winansi?
> Maybe you should write the P4PAASWD into a text file and inject it with
> en
Hi Dan,
Thanks, I will check if I can take this plugin
David
On Monday, September 22, 2014 7:40:40 AM UTC+3, Dan Tran wrote:
>
>
> The combination of new P4Jenkins[1] and P4Maven[2] works well with
> maven-release-plugin. you will need cut an internal release of p4maven
>
> -D
>
>
>
> [1] http
Is P4CHARSET set to winansi?
Maybe you should write the P4PAASWD into a text file and inject it with
env_inject.
This would make the testing a bit easier.
You can then find whitespace characters and have no encoding trouble with
the password.
If this works is your problem probably a matter of en
The combination of new P4Jenkins[1] and P4Maven[2] works well with
maven-release-plugin. you will need cut an internal release of p4maven
-D
[1] https://wiki.jenkins-ci.org/display/JENKINS/P4+Plugin
[2] https://swarm.workshop.perforce.com/files/guest/dantran/p4maven .
p4maven has not offic
I'm using Jenkins with Perforce to build a maven project, and I need to use
the maven-release plugin. I have configured my project and the build is
going well, until I have tried to use the maven release plugin using the
relevant Jenkins plugin. With dry run everything went well, but when tryi
