Re: Configure SCM in the Coverity Plugin
yes. Perforce does not have that user but it is just the system user
builder doing the builds. Why is the Plugin getting this user anyways?
On Tuesday, July 28, 2015 at 5:10:05 PM UTC+5:30, rginga wrote:
I don’t use that option, but it looks like maybe Perforce does not have
a user named Builder?
*From:* Shobha Dashottar [mailto:shobha.d...@gmail.com javascript:]
*Sent:* Tuesday, July 28, 2015 7:07 AM
*To:* Jenkins Users
*Cc:* Ginga, Dick
*Subject:* Re: Configure SCM in the Coverity Plugin
Thanks .
I have now added p4 to the blacklist and it went ahead. But it fails
further down the line on every single file.
*MAKE SUCCESSFUL 13:28:48 + exit 0 13:28:48 [WARNING] 1313 C/C++
compilation units (85%) are ready for analysis 13:28:48 For more details,
please look at: 13:28:48
/home/builder/COV_TEMP/idirs/project_name/build-log.txt 13:28:48
[Coverity] cmd so far is:
[/home/builder/cov-analysis-linux64-7.5.0/bin/cov-import-scm, --dir,
/home/builder/COV_TEMP/idirs/project_name, --scm, perforce] 13:28:48 $
/home/builder/cov-analysis-linux64-7.5.0/bin/cov-import-scm --dir
/home/builder/COV_TEMP/idirs/project_name --scm perforce 13:28:49
Extracting SCM data for 4431 files... 13:28:50 User builder doesn't exist.
13:28:51 [WARNING] An error occurred while executing command at
'/home/builder/jenkins/workspace/project_name/subdir..': 13:28:51
COMMAND: '/usr/bin/p4 filelog -t -i -h somesourcefile.c' failed. Error code
1. Proceeding...*
This error is thrown for every single file. On executing the p4 filelog
command locally, I get the correct results. Looks like the cov-import-scm
command needs some more commandline arguments which I can give using the
optional scm-tools or commands arguments but not sure what it wants :)
Thanks
Shobha
On Wednesday, June 24, 2015 at 5:01:09 PM UTC+5:30, rginga wrote:
I have found that you need to add P4 to the “cov-build blacklist”. This
tells Coverity to no wrap these calls.
*From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] *On
Behalf Of *Shobha Dashottar
*Sent:* Tuesday, June 23, 2015 11:22 PM
*To:* jenkins...@googlegroups.com
*Subject:* Configure SCM in the Coverity Plugin
Hi Team,
I have configured the Coverity plugin for our build. The cov commands
are issues from the build script itself. Coverity itself runs fine but I
wanted to enhance further and selected the Source Control (SCM) option. I
selected the perforce option and entered the P4PORT.
But, looks it needs something more. The build run throws this error
java.lang.NullPointerException
http://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerException
*08:13:29* at
jenkins.plugins.coverity.ScmOptionBlock.checkScmConfig(ScmOptionBlock.java:73)
http://stacktrace.jenkins-ci.org/search/?query=jenkins.plugins.coverity.ScmOptionBlock.checkScmConfigentity=method
*08:13:29* at
jenkins.plugins.coverity.CoverityLauncherDecorator.decorate(CoverityLauncherDecorator.java:104)
http://stacktrace.jenkins-ci.org/search/?query=jenkins.plugins.coverity.CoverityLauncherDecorator.decorateentity=method
*08:13:29* at hudson.Launcher.decorateFor(Launcher.java:695)
http://stacktrace.jenkins-ci.org/search/?query=hudson.Launcher.decorateForentity=method
*08:13:29* at hudson.model.Slave.createLauncher(Slave.java:374)
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Slave.createLauncherentity=method
*08:13:29* at
hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:564)
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.createLauncherentity=method
*08:13:29* at
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:495)
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.runentity=method
*08:13:29* at hudson.model.Run.execute(Run.java:1744)
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.executeentity=method
*08:13:29* at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.FreeStyleBuild.runentity=method
*08:13:29* at
hudson.model.ResourceController.execute(ResourceController.java:98)
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.executeentity=method
*08:13:29* at hudson.model.Executor.run(Executor.java:374)
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.runentity=method
Jenkins version : 1.612
Coverity Plugin version : 1.5.0
Coverity version 7.5.0
SCM : Perforce
I checked the line 73 in ScmOptionBlock.java of Coverity Plugin. It says
*if(!version.compareToAnalysis(new CoverityVersion(7, 5, 0))
this.scmSystem.equals(perforce2009)){*
Any idea what is going wrong? I mainly wanted
Re: Configure SCM in the Coverity Plugin
Thanks .
I have now added p4 to the blacklist and it went ahead. But it fails
further down the line on every single file.
*MAKE SUCCESSFUL13:28:48 + exit 013:28:48 [WARNING] 1313 C/C++ compilation
units (85%) are ready for analysis13:28:48 For more details, please look
at: 13:28:48
/home/builder/COV_TEMP/idirs/project_name/build-log.txt13:28:48
[Coverity] cmd so far is:
[/home/builder/cov-analysis-linux64-7.5.0/bin/cov-import-scm, --dir,
/home/builder/COV_TEMP/idirs/project_name, --scm, perforce]13:28:48 $
/home/builder/cov-analysis-linux64-7.5.0/bin/cov-import-scm --dir
/home/builder/COV_TEMP/idirs/project_name --scm perforce13:28:49
Extracting SCM data for 4431 files...13:28:50 User builder doesn't
exist.13:28:51 [WARNING] An error occurred while executing command at
'/home/builder/jenkins/workspace/project_name/subdir..':13:28:51
COMMAND: '/usr/bin/p4 filelog -t -i -h somesourcefile.c' failed. Error code
1. Proceeding...*
This error is thrown for every single file. On executing the p4 filelog
command locally, I get the correct results. Looks like the cov-import-scm
command needs some more commandline arguments which I can give using the
optional scm-tools or commands arguments but not sure what it wants :)
Thanks
Shobha
On Wednesday, June 24, 2015 at 5:01:09 PM UTC+5:30, rginga wrote:
I have found that you need to add P4 to the “cov-build blacklist”. This
tells Coverity to no wrap these calls.
*From:* jenkins...@googlegroups.com javascript: [mailto:
jenkins...@googlegroups.com javascript:] *On Behalf Of *Shobha Dashottar
*Sent:* Tuesday, June 23, 2015 11:22 PM
*To:* jenkins...@googlegroups.com javascript:
*Subject:* Configure SCM in the Coverity Plugin
Hi Team,
I have configured the Coverity plugin for our build. The cov commands
are issues from the build script itself. Coverity itself runs fine but I
wanted to enhance further and selected the Source Control (SCM) option. I
selected the perforce option and entered the P4PORT.
But, looks it needs something more. The build run throws this error
java.lang.NullPointerException
http://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerException
*08:13:29* at
jenkins.plugins.coverity.ScmOptionBlock.checkScmConfig(ScmOptionBlock.java:73)
http://stacktrace.jenkins-ci.org/search/?query=jenkins.plugins.coverity.ScmOptionBlock.checkScmConfigentity=method
*08:13:29* at
jenkins.plugins.coverity.CoverityLauncherDecorator.decorate(CoverityLauncherDecorator.java:104)
http://stacktrace.jenkins-ci.org/search/?query=jenkins.plugins.coverity.CoverityLauncherDecorator.decorateentity=method
*08:13:29* at hudson.Launcher.decorateFor(Launcher.java:695)
http://stacktrace.jenkins-ci.org/search/?query=hudson.Launcher.decorateForentity=method
*08:13:29* at hudson.model.Slave.createLauncher(Slave.java:374)
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Slave.createLauncherentity=method
*08:13:29* at
hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:564)
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.createLauncherentity=method
*08:13:29* at
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:495)
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.runentity=method
*08:13:29* at hudson.model.Run.execute(Run.java:1744)
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.executeentity=method
*08:13:29* at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.FreeStyleBuild.runentity=method
*08:13:29* at
hudson.model.ResourceController.execute(ResourceController.java:98)
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.executeentity=method
*08:13:29* at hudson.model.Executor.run(Executor.java:374)
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.runentity=method
Jenkins version : 1.612
Coverity Plugin version : 1.5.0
Coverity version 7.5.0
SCM : Perforce
I checked the line 73 in ScmOptionBlock.java of Coverity Plugin. It says
*if**(!version.compareToAnalysis(new CoverityVersion(7, 5, 0))
this.scmSystem.equals(perforce2009)){*
Any idea what is going wrong? I mainly wanted to see the defect trend on the
job's main page.
Thanks
Shobha
--
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 javascript:.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/e42dd99a-8792-427d-a141-0148eaab1d17%40googlegroups.com
https://groups.google.com/d/msgid/jenkinsci-users
Configure SCM in the Coverity Plugin
Hi Team,
I have configured the Coverity plugin for our build. The cov commands
are issues from the build script itself. Coverity itself runs fine but I
wanted to enhance further and selected the Source Control (SCM) option. I
selected the perforce option and entered the P4PORT.
But, looks it needs something more. The build run throws this error
java.lang.NullPointerException
http://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerException*08:13:29*
at
jenkins.plugins.coverity.ScmOptionBlock.checkScmConfig(ScmOptionBlock.java:73)
http://stacktrace.jenkins-ci.org/search/?query=jenkins.plugins.coverity.ScmOptionBlock.checkScmConfigentity=method*08:13:29*
at
jenkins.plugins.coverity.CoverityLauncherDecorator.decorate(CoverityLauncherDecorator.java:104)
http://stacktrace.jenkins-ci.org/search/?query=jenkins.plugins.coverity.CoverityLauncherDecorator.decorateentity=method*08:13:29*
at hudson.Launcher.decorateFor(Launcher.java:695)
http://stacktrace.jenkins-ci.org/search/?query=hudson.Launcher.decorateForentity=method*08:13:29*
at hudson.model.Slave.createLauncher(Slave.java:374)
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Slave.createLauncherentity=method*08:13:29*
at
hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:564)
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.createLauncherentity=method*08:13:29*
at
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:495)
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.runentity=method*08:13:29*
at hudson.model.Run.execute(Run.java:1744)
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.executeentity=method*08:13:29*
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.FreeStyleBuild.runentity=method*08:13:29*
at hudson.model.ResourceController.execute(ResourceController.java:98)
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.executeentity=method*08:13:29*
at hudson.model.Executor.run(Executor.java:374)
http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.runentity=method
Jenkins version : 1.612
Coverity Plugin version : 1.5.0
Coverity version 7.5.0
SCM : Perforce
I checked the line 73 in ScmOptionBlock.java of Coverity Plugin. It says
*if(!version.compareToAnalysis(new CoverityVersion(7, 5, 0))
this.scmSystem.equals(perforce2009)){*
Any idea what is going wrong? I mainly wanted to see the defect trend on the
job's main page.
Thanks
Shobha
--
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/e42dd99a-8792-427d-a141-0148eaab1d17%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Credentials Plugin : escape characters don't work?
Yep. I had to give 4$'s for one so a total of 8 $'s :) . Thanks Shobha -- 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-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/09920630-d3a3-4e0f-95b8-8cb8dd643144%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Credentials Plugin : escape characters don't work?
I am using the Credentials Plugin username:password. I get the credentials using the use secrets option into the environment but the special characters are getting messed up. It appears the Plugin is not recognizing the backslash as a special character. I have a $$ in my password string and that somehow gets translated to $. Is there a separate set of escape characters it understands. \$\$ translates to \$\$ but \$$ translates to \$ Thanks Shobha. -- 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-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ae94bdce-9a40-4918-b1a2-b5dd61d8dee8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Using Coverity plugin
Awesome !! This worked. Thanks a lot On Friday, November 7, 2014 6:34:26 PM UTC+5:30, rginga wrote: Yup, you need to add P4 to the cov-build blacklist field. The Coverity pluging wraps everything and it does not like null responses. *From:* jenkins...@googlegroups.com javascript: [mailto: jenkins...@googlegroups.com javascript:] *On Behalf Of *Shobha Dashottar *Sent:* Thursday, November 06, 2014 11:38 PM *To:* jenkins...@googlegroups.com javascript: *Subject:* Using Coverity plugin Hi, I have the Coverity setup created and installed the client on a linux slave machine. Using Coverity UI I can created the xml and run coverity analysis just fine. In my Jenkins job, I have configured Coverity and that build just fails with the below error: The build job was running fine prior to Coverity . In the job config, I have given the details of the Integrity Manager and checked the option of Perform Coverity build, analysis and commit and nothing else. What am I missing? Thanks Shobha Saving modified client Dev_RHEL5_x86--274771558 *06:52:21* [Dev_RHEL5_x86] $ /home/builder/cov-analysis-linux-7.5.0/bin/cov-build --dir /home/builder/jenkins/coverity/temp-5203856065298512221.tmp /usr/bin/p4 -P 827C6449450B2A55C2F2B48 -s client -i *06:52:23* Last build changeset: 18067994 *06:52:23* [Dev_RHEL5_x86] $ /home/builder/cov-analysis-linux-7.5.0/bin/cov-build --dir /home/builder/jenkins/coverity/temp-5203856065298512221.tmp /usr/bin/p4 -P 827C6449450B2A55C2F2B48 changes -s submitted -m 1 //Dev_RHEL5_x86--274771558/... *06:52:25* FATAL: null *06:52:25* java.util.NoSuchElementException http://stacktrace.jenkins-ci.org/search?query=java.util.NoSuchElementException *06:52:25* at java.util.StringTokenizer.nextToken(StringTokenizer.java:349) http://stacktrace.jenkins-ci.org/search/?query=java.util.StringTokenizer.nextTokenentity=method *06:52:25* at com.tek42.perforce.parse.AbstractPerforceTemplate.parseList(AbstractPerforceTemplate.java:112) http://stacktrace.jenkins-ci.org/search/?query=com.tek42.perforce.parse.AbstractPerforceTemplate.parseListentity=method *06:52:25* at com.tek42.perforce.parse.Changes.getChangeNumbers(Changes.java:186) http://stacktrace.jenkins-ci.org/search/?query=com.tek42.perforce.parse.Changes.getChangeNumbersentity=method *06:52:25* at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:996) http://stacktrace.jenkins-ci.org/search/?query=hudson.plugins.perforce.PerforceSCM.checkoutentity=method ... ... -- 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 javascript:. For more options, visit https://groups.google.com/d/optout. -- 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-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Using Coverity plugin
Hi, I have the Coverity setup created and installed the client on a linux slave machine. Using Coverity UI I can created the xml and run coverity analysis just fine. In my Jenkins job, I have configured Coverity and that build just fails with the below error: The build job was running fine prior to Coverity . In the job config, I have given the details of the Integrity Manager and checked the option of Perform Coverity build, analysis and commit and nothing else. What am I missing? Thanks Shobha Saving modified client Dev_RHEL5_x86--274771558*06:52:21* [Dev_RHEL5_x86] $ /home/builder/cov-analysis-linux-7.5.0/bin/cov-build --dir /home/builder/jenkins/coverity/temp-5203856065298512221.tmp /usr/bin/p4 -P 827C6449450B2A55C2F2B48 -s client -i*06:52:23* Last build changeset: 18067994*06:52:23* [Dev_RHEL5_x86] $ /home/builder/cov-analysis-linux-7.5.0/bin/cov-build --dir /home/builder/jenkins/coverity/temp-5203856065298512221.tmp /usr/bin/p4 -P 827C6449450B2A55C2F2B48 changes -s submitted -m 1 //Dev_RHEL5_x86--274771558/...*06:52:25* FATAL: null*06:52:25* java.util.NoSuchElementException http://stacktrace.jenkins-ci.org/search?query=java.util.NoSuchElementException *06:52:25* at java.util.StringTokenizer.nextToken(StringTokenizer.java:349) http://stacktrace.jenkins-ci.org/search/?query=java.util.StringTokenizer.nextTokenentity=method*06:52:25* at com.tek42.perforce.parse.AbstractPerforceTemplate.parseList(AbstractPerforceTemplate.java:112) http://stacktrace.jenkins-ci.org/search/?query=com.tek42.perforce.parse.AbstractPerforceTemplate.parseListentity=method*06:52:25* at com.tek42.perforce.parse.Changes.getChangeNumbers(Changes.java:186) http://stacktrace.jenkins-ci.org/search/?query=com.tek42.perforce.parse.Changes.getChangeNumbersentity=method*06:52:25* at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:996) http://stacktrace.jenkins-ci.org/search/?query=hudson.plugins.perforce.PerforceSCM.checkoutentity=method ... ... http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.runentity=method -- 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-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
certutil -importPFX fails from Jenkins
Hi, Usually my signing scripts works fine from Jenkins but this time when I am using certutil to import the pfx and then do the signing. certutil.exe -user -f -P somepassword -importPFX C:\path to pfx from within a script , I am getting this error CertUtil: -importPFX command FAILED: 0x800704c7 (WIN32: 1223) The script is working fine from the build machine though. Googled the error code but didn't find anything helpful. Has anyone come across this issue before? Thanks Shobha -- 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-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: P4 Plugin throws Error occurred during the SSL handshake: invalid SSL session Error
I ran that test code and earlier it gave 128 . So, made a few more changes
like reinstalling jdk, setting the java paths in a few more files for
Jenkins to get the path during slave launch itself and then finally copying
the UnlimitedJCEPolicy jar files even though they existed in the security
folder.
Looks like something was messed up in my java environment as after I ran
the test code it gave me the value 2147483647. the SSL handshake error has
gone away too.
Thanks Dan for your help on this. Much Appreciated.
On Friday, September 26, 2014 9:30:58 PM UTC+5:30, Dan Tran wrote:
Also note, that p4jenkins uses the startup JRE to talk to perforce ( not
the one configure in the job)
-D
On Thursday, September 25, 2014 7:11:13 PM UTC-7, Dan Tran wrote:
run a java test with your JRE?
private boolean isUnlimitedCryptoSupported() throws
NoSuchAlgorithmException {
int bits = Cipher.getMaxAllowedKeyLength(AES);
this.getLog().info(Current encryption strength is: + bits);
return bits == 2147483647;
}
On Thursday, September 25, 2014 10:15:01 AM UTC-7, Shobha Dashottar wrote:
I have now removed all the older jre versions from the systems leaving
jre only in one place. I even have the JRE home in the PATH variable.
I have setup some Windows VMs now but those are too giving the same
error. They already have the JCE jars in their installation folders.
Is there some other requirement for this to work ?
Thanks
Shobha
On Thursday, September 25, 2014 9:32:35 PM UTC+5:30, Dan Tran wrote:
Very likely, you patch the wrong JRE
-D
On Thursday, September 25, 2014 8:46:01 AM UTC-7, Shobha Dashottar
wrote:
I am setting up a new Jenkins server. I have been using the Perforce
Plugin so far but this time I have switched to the P4 Plugin as has a
good
integration with the Credential Plugin to connect to the perforce server.
For most of the VMs that I am connecting to it goes ahead with P4
command execution without issue. So far one VM is giving issue and
throwing
exception while even trying to communicate with the perforce server.
P4: Unable to connect: com.perforce.p4java.exception.ConnectionException:
Error occurred during the SSL handshake: invalid SSL session
P4: Unable to use Workspace: java.lang.NullPointerException
P4: Unable to close Perforce connection: java.lang.NullPointerException
ERROR: Unable to update workspace: java.lang.NullPointerException
After following some articles, I have added the jars from JCE for Java 7
inside the slave VMs jre/lib/security folder.
But still the error keeps popping up.
Does anyone know what is going on or is missing on that VM?
Thanks
Shobha
--
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-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Errors while using Credential manager to store P4 password
This is solved. I had to edit the /etc/hosts file and make an entry for the hostname of the slave VM On Thursday, September 25, 2014 11:23:11 AM UTC+5:30, Shobha Dashottar wrote: I used the Credential manager plugin to store the perforce credentials. I have filled in the details as required on the Jenkins - Credentials - Global Credentials page like the p4 port, ssl connection, fingerprint , username and password. but on clicking on test Connection I get the following error Unable to connect to: p4javassl://perforce.xxx.com:1666 Unable to determine client host name: Jenkinshostname: Jenkinshostname Where Jenkinshostname is the hostname of the Linux machine( RHEL 6 x64) with Jenkins installed. Am I missing something? Thanks Shobha -- 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-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
P4 Plugin throws Error occurred during the SSL handshake: invalid SSL session Error
I am setting up a new Jenkins server. I have been using the Perforce Plugin so far but this time I have switched to the P4 Plugin as has a good integration with the Credential Plugin to connect to the perforce server. For most of the VMs that I am connecting to it goes ahead with P4 command execution without issue. So far one VM is giving issue and throwing exception while even trying to communicate with the perforce server. P4: Unable to connect: com.perforce.p4java.exception.ConnectionException: Error occurred during the SSL handshake: invalid SSL session P4: Unable to use Workspace: java.lang.NullPointerException P4: Unable to close Perforce connection: java.lang.NullPointerException ERROR: Unable to update workspace: java.lang.NullPointerException After following some articles, I have added the jars from JCE for Java 7 inside the slave VMs jre/lib/security folder. But still the error keeps popping up. Does anyone know what is going on or is missing on that VM? Thanks Shobha -- 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-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: P4 Plugin throws Error occurred during the SSL handshake: invalid SSL session Error
I have now removed all the older jre versions from the systems leaving jre only in one place. I even have the JRE home in the PATH variable. I have setup some Windows VMs now but those are too giving the same error. They already have the JCE jars in their installation folders. Is there some other requirement for this to work ? Thanks Shobha On Thursday, September 25, 2014 9:32:35 PM UTC+5:30, Dan Tran wrote: Very likely, you patch the wrong JRE -D On Thursday, September 25, 2014 8:46:01 AM UTC-7, Shobha Dashottar wrote: I am setting up a new Jenkins server. I have been using the Perforce Plugin so far but this time I have switched to the P4 Plugin as has a good integration with the Credential Plugin to connect to the perforce server. For most of the VMs that I am connecting to it goes ahead with P4 command execution without issue. So far one VM is giving issue and throwing exception while even trying to communicate with the perforce server. P4: Unable to connect: com.perforce.p4java.exception.ConnectionException: Error occurred during the SSL handshake: invalid SSL session P4: Unable to use Workspace: java.lang.NullPointerException P4: Unable to close Perforce connection: java.lang.NullPointerException ERROR: Unable to update workspace: java.lang.NullPointerException After following some articles, I have added the jars from JCE for Java 7 inside the slave VMs jre/lib/security folder. But still the error keeps popping up. Does anyone know what is going on or is missing on that VM? Thanks Shobha -- 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-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Errors while using Credential manager to store P4 password
I used the Credential manager plugin to store the perforce credentials. I have filled in the details as required on the Jenkins - Credentials - Global Credentials page like the p4 port, ssl connection, fingerprint , username and password. but on clicking on test Connection I get the following error Unable to connect to: p4javassl://perforce.xxx.com:1666 Unable to determine client host name: Jenkinshostname: Jenkinshostname Where Jenkinshostname is the hostname of the Linux machine( RHEL 6 x64) with Jenkins installed. Am I missing something? Thanks Shobha -- 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-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
