Re: Double checkstyle/pmd/findbugs warnings in a jenkins maven multimodule job
I am using Jenkins only to aggregate. the problem is that in the scenario I highlighted, Jenkins aggregate plugin is showing double the actual number of warnings. On Fri, Feb 21, 2014 at 2:06 AM, Ullrich Hafner ullrich.haf...@gmail.comwrote: You do not need to aggregate in Maven, the Jenkins plugin does that for you. Am Donnerstag, 20. Februar 2014 schrieb pa7751 : I have a jenkins maven job with an aggregator pom and a bunch of submodules. When jenkins displays the aggregated checkstyle/pmd/findbugs warnings it does it like so: - submodule 1: 10 warnings - submodule 2: 10 warnings - Aggregator module: 20 warnings - Total: 40 warnings In other words, the aggregator (rightfully?) aggregates the warnings found in the submodules. Hence the aggregate displays double the actual count Does any one know what the problem is? Thanks! -- 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/groups/opt_out. -- 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/mXc0N_-trak/unsubscribe. To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out.
cvs checkout fails when running jenkins under Tomcat
I get the following output Started by user anonymous Building in workspace http://gmastst-app1.cadm.harvard.edu:8915/jenkins/job/gmas_autobuild/ws/ cvs update -d -P -r GMAS_1_37 GMAS_1_37 cvs update: Updating GMAS_1_37 cvs update: failed to create lock directory for `/u02/app/cvs/projects/GMAS' (/u02/app/cvs/projects/GMAS/#cvs.lock): Permission denied cvs update: failed to obtain dir lock in repository `/u02/app/cvs/projects/GMAS' cvs [update aborted]: read lock failed - giving up Trying with users other than anonymous doesn't seem to work, either, even though I configured any user to to anything. I start Tomcat from a linux login, jenkins, that can do cvs checkouts from the bash shell with no problems. How can I figure out which linux account tomcat/jenkins uses to run cvs commands? -- 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/groups/opt_out.
Re: Double checkstyle/pmd/findbugs warnings in a jenkins maven multimodule job
Can please create a new bug report and describe in more detail where the wrong number of warnings are shown (which link did you select?). Maybe an example project that exposes the bug would also help. Am Freitag, 21. Februar 2014 schrieb pa7751 : I am using Jenkins only to aggregate. the problem is that in the scenario I highlighted, Jenkins aggregate plugin is showing double the actual number of warnings. On Fri, Feb 21, 2014 at 2:06 AM, Ullrich Hafner ullrich.haf...@gmail.comjavascript:_e(%7B%7D,'cvml','ullrich.haf...@gmail.com'); wrote: You do not need to aggregate in Maven, the Jenkins plugin does that for you. Am Donnerstag, 20. Februar 2014 schrieb pa7751 : I have a jenkins maven job with an aggregator pom and a bunch of submodules. When jenkins displays the aggregated checkstyle/pmd/findbugs warnings it does it like so: - submodule 1: 10 warnings - submodule 2: 10 warnings - Aggregator module: 20 warnings - Total: 40 warnings In other words, the aggregator (rightfully?) aggregates the warnings found in the submodules. Hence the aggregate displays double the actual count Does any one know what the problem is? Thanks! -- 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/groups/opt_out. -- 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/mXc0N_-trak/unsubscribe . To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.comjavascript:_e(%7B%7D,'cvml','jenkinsci-users%2bunsubscr...@googlegroups.com'); . For more options, visit https://groups.google.com/groups/opt_out. -- 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.comjavascript:_e(%7B%7D,'cvml','jenkinsci-users%2bunsubscr...@googlegroups.com'); . For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out.
Re: best approach to automate/manage jenkins jobs?
I called the command line to extract the job definition, then stored that definition in source control. I could replay it at any time. That did not update job definitions when they changed. It did not detect changes (other than through the version control system diff mechanism). It was not attempting to code Jenkins job definitions in a DRY fashion. It was simple to maintain and helped me reconstruct environments more readily on those rare times when I needed to reconstruct them. Mark Waite On Fri, Feb 21, 2014 at 8:14 AM, phil swenson phil.swen...@gmail.comwrote: Hi, we have a large number of jenkins jobs and would like to automate and version control their configuration. From what I can tell, most people just manually config their jobs via the UI. Unless there are only a few very simple jobs, this leads to an unmanageable mess. I think the jobs should be coded in a DRY fashion, version controlled, and deployed via a scripted system. Here are the approaches I am aware of: 1) scripting via command line (jenkins cli) 2) scripting via the rest web services 3) chef cookbook http://community.opscode.com/cookbooks/jenkins What are most people doing? Any recommendations? thanks phil -- 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/groups/opt_out. -- Thanks! Mark Waite -- 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/groups/opt_out.
RE: best approach to automate/manage jenkins jobs?
I use an ant task that generates my jobs based off a template job it pulls down. For me, the CLI tends to be really flaky though, when re-generating ~1500 jobs 10-20 will usually fail. -Andrew From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mark Waite Sent: Friday, February 21, 2014 10:21 AM To: jenkinsci-users@googlegroups.com Subject: Re: best approach to automate/manage jenkins jobs? I called the command line to extract the job definition, then stored that definition in source control. I could replay it at any time. That did not update job definitions when they changed. It did not detect changes (other than through the version control system diff mechanism). It was not attempting to code Jenkins job definitions in a DRY fashion. It was simple to maintain and helped me reconstruct environments more readily on those rare times when I needed to reconstruct them. Mark Waite On Fri, Feb 21, 2014 at 8:14 AM, phil swenson phil.swen...@gmail.com wrote: Hi, we have a large number of jenkins jobs and would like to automate and version control their configuration. From what I can tell, most people just manually config their jobs via the UI. Unless there are only a few very simple jobs, this leads to an unmanageable mess. I think the jobs should be coded in a DRY fashion, version controlled, and deployed via a scripted system. Here are the approaches I am aware of: 1) scripting via command line (jenkins cli) 2) scripting via the rest web services 3) chef cookbook http://community.opscode.com/cookbooks/jenkins What are most people doing? Any recommendations? thanks phil -- 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 mailto:jenkinsci-users%2bunsubscr...@googlegroups.com . For more options, visit https://groups.google.com/groups/opt_out. -- Thanks! Mark Waite -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: best approach to automate/manage jenkins jobs?
https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin Am 21.02.2014 16:21, schrieb Mark Waite: I called the command line to extract the job definition, then stored that definition in source control. I could replay it at any time. That did not update job definitions when they changed. It did not detect changes (other than through the version control system diff mechanism). It was not attempting to code Jenkins job definitions in a DRY fashion. It was simple to maintain and helped me reconstruct environments more readily on those rare times when I needed to reconstruct them. Mark Waite On Fri, Feb 21, 2014 at 8:14 AM, phil swenson phil.swen...@gmail.com mailto:phil.swen...@gmail.com wrote: Hi, we have a large number of jenkins jobs and would like to automate and version control their configuration. From what I can tell, most people just manually config their jobs via the UI. Unless there are only a few very simple jobs, this leads to an unmanageable mess. I think the jobs should be coded in a DRY fashion, version controlled, and deployed via a scripted system. Here are the approaches I am aware of: 1) scripting via command line (jenkins cli) 2) scripting via the rest web services 3) chef cookbook http://community.opscode.com/cookbooks/jenkins What are most people doing? Any recommendations? thanks phil -- 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 mailto:jenkinsci-users%2bunsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Thanks! Mark Waite -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: best approach to automate/manage jenkins jobs?
This sounds similar to the technique described in this post: http://www.blackpepper.co.uk/generating-new-jenkins-jobs-from-templates-and-parameterised-builds/ I've used this technique where I need to have lots of different build which are mostly similar and need to be able to run in parallel. Ben On Fri, Feb 21, 2014 at 7:49 AM, Andrew Kujtan akuj...@evertz.com wrote: I use an ant task that generates my jobs based off a template job it pulls down. For me, the CLI tends to be really flaky though, when re-generating ~1500 jobs 10-20 will usually fail. -Andrew From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mark Waite Sent: Friday, February 21, 2014 10:21 AM To: jenkinsci-users@googlegroups.com Subject: Re: best approach to automate/manage jenkins jobs? I called the command line to extract the job definition, then stored that definition in source control. I could replay it at any time. That did not update job definitions when they changed. It did not detect changes (other than through the version control system diff mechanism). It was not attempting to code Jenkins job definitions in a DRY fashion. It was simple to maintain and helped me reconstruct environments more readily on those rare times when I needed to reconstruct them. Mark Waite On Fri, Feb 21, 2014 at 8:14 AM, phil swenson phil.swen...@gmail.com wrote: Hi, we have a large number of jenkins jobs and would like to automate and version control their configuration. From what I can tell, most people just manually config their jobs via the UI. Unless there are only a few very simple jobs, this leads to an unmanageable mess. I think the jobs should be coded in a DRY fashion, version controlled, and deployed via a scripted system. Here are the approaches I am aware of: 1) scripting via command line (jenkins cli) 2) scripting via the rest web services 3) chef cookbook http://community.opscode.com/cookbooks/jenkins What are most people doing? Any recommendations? thanks phil -- 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/groups/opt_out. -- Thanks! Mark Waite -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out.
Is a central/shared local Maven Repo still Not safe for Jenkins master and many slaves?
Greetings - It seems there is an outstanding maven issue Concurrent-safe access to local Maven repository http://jira.codehaus.org/browse/MNG-2802 which would advise against setting up all Jenkins servers to use a shared (e.g NFS mount) maven local repo - Can anyone confirm or share experience on how unsafe this would be? The issue with having different repo is managing the cleaning up for each and also not optimized when running same job in different slaves, all maven artifacts have to be republished etc...(this is for a setup of 1000s of jobs across 10 slaves) Any suggestions/advise would be helpful. Thanks, --Seena -- 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/groups/opt_out.
Re: best approach to automate/manage jenkins jobs?
On Fri, Feb 21, 2014 at 9:14 AM, phil swenson phil.swen...@gmail.com wrote: Hi, we have a large number of jenkins jobs and would like to automate and version control their configuration. From what I can tell, most people just manually config their jobs via the UI. Unless there are only a few very simple jobs, this leads to an unmanageable mess. I think the jobs should be coded in a DRY fashion, version controlled, and deployed via a scripted system. Here are the approaches I am aware of: 1) scripting via command line (jenkins cli) 2) scripting via the rest web services 3) chef cookbook http://community.opscode.com/cookbooks/jenkins What are most people doing? Any recommendations? Our jobs usually amount to polling an SCM location and running a build or ant script found there and archiving the results from some standard locations, so there's not much complexity in the jenkins job itself. So, we just do nightly backups of the jenkins master with a program called backuppc which has efficient on-line storage and a nice interface to access any individual files or directories, and new jobs are created in the GUI as copies of existing similar jobs and editing the SCM target. -- Les Mikesell lesmikes...@gmail.com -- 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/groups/opt_out.
RE: best approach to automate/manage jenkins jobs?
Hi Phil, There is also the Job DSL plugin[1] and Cloudbees Templates[2]. The DSL plugin (not used it) can store the DSL in source control - you can add the Cloudbees templates (done it) to an SCM like git and commit push them after you make any changes. /James From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of phil swenson Sent: 21 February 2014 15:15 To: jenkinsci-users Subject: best approach to automate/manage jenkins jobs? Hi, we have a large number of jenkins jobs and would like to automate and version control their configuration. From what I can tell, most people just manually config their jobs via the UI. Unless there are only a few very simple jobs, this leads to an unmanageable mess. I think the jobs should be coded in a DRY fashion, version controlled, and deployed via a scripted system. Here are the approaches I am aware of: 1) scripting via command line (jenkins cli) 2) scripting via the rest web services 3) chef cookbook http://community.opscode.com/cookbooks/jenkins What are most people doing? Any recommendations? thanks phil -- 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.commailto:jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out.
Re: Major Problems after upgrading to 1.532.2 LTS Release
Don't use the Active Directory plugin. You likely can configure the LDAP plugin[1] to do the same job. 1: https://wiki.jenkins-ci.org/display/JENKINS/LDAP+Plugin On 21.02.2014, at 00:47, Andrew Sumner andrew.sum...@customs.govt.nz wrote: Nearly everything I do gives this error - any assistance will be greatefully accepted! -- 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/groups/opt_out.
Re: How can I see all builds in a job via api/json ?
Hacky solution:
curl -d 'script=println Jenkins.instance.getItem(jobName).builds.each{
println ${it.number}:${it.startTimeInMillis}:${it.duration}:${it.result}
};' http://localhost:8080/scriptText
On Thursday, February 20, 2014 5:35:19 PM UTC-8, Christian Goetze wrote:
WHen I run url/job/jobname/api/json?tree=builds[url], then I get a
list of some builds, but not all the builds I can retrieve via the UI?
What's the magic to get all builds?
--
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/groups/opt_out.
Re: How can I see all builds in a job via api/json ?
tree=builds will only retrieve the newest 100 builds since 1.485. Use tree=allBuilds to get everything. It's hidden by default and only shows up with depth=3 or higher (when querying a job). On 21.02.2014, at 02:35, Christian Goetze christian.goe...@appdynamics.com wrote: WHen I run url/job/jobname/api/json?tree=builds[url], then I get a list of some builds, but not all the builds I can retrieve via the UI? What's the magic to get all builds? -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: CVS Authentication failed!
I have the same problem. I just installed jenkins for the first time and want to do a very simple build that requires a cvs checkout. I have tried everything I could think of short of actually creating and setting up ssh public/private key authentication for the jenkins user (too scary) Here the email I get from jenkins: Started by timer Building in workspace http://ws-rcrick-l:8080/job/jenkins-test-build-perl/ws/ Using globally configured password for connection to ':ext:iman-repo.example.com:22/usr/local/cvsroot' with username 'rcrick' cvs checkout -P -N -D 21 Feb 2014 17:15:23 -0500 platform/perl ERROR: CVS Authentication failed: null org.netbeans.lib.cvsclient.connection.AuthenticationException: SSH connection failed. at org.netbeans.lib.cvsclient.connection.SSHConnection.open(SSHConnection.java:141) at org.netbeans.lib.cvsclient.Client$1.run(Client.java:374) at java.lang.Thread.run(Thread.java:736) Caused by: com.jcraft.jsch.JSchException: java.io.FileNotFoundException: /var/lib/jenkins/.ssh/id_rsa (No such file or directory) at com.jcraft.jsch.KeyPair.load(KeyPair.java:524) at com.jcraft.jsch.IdentityFile.newInstance(IdentityFile.java:40) at com.jcraft.jsch.JSch.addIdentity(JSch.java:389) at com.jcraft.jsch.JSch.addIdentity(JSch.java:370) at org.netbeans.lib.cvsclient.connection.SSHConnection.open(SSHConnection.java:135) ... 2 more Caused by: java.io.FileNotFoundException: /var/lib/jenkins/.ssh/id_rsa (No such file or directory) at java.io.FileInputStream.init(FileInputStream.java:123) at java.io.FileInputStream.init(FileInputStream.java:83) at com.jcraft.jsch.Util.fromFile(Util.java:492) at com.jcraft.jsch.KeyPair.load(KeyPair.java:521) ... 6 more ERROR: Cvs task failed On Thursday, July 11, 2013 2:57:22 PM UTC-7, Sameh Tawfik wrote: Hi, I'm using Jenkins ver. 1.522 Under Manage Jenkins\Configure System\CVS\ Authentication , I setup CVS Root, Username, and Password, but under same CVS section there are these fields: Private Key Location, Private Key Password, Known Hosts Location which I'm not using or need, because instead I'm using the values under the Authentication. Everytime, I remove the values specified for Private Key Location, Private Key Password, Known Hosts Location fields and save, when I go back Jenkins is populating these values again with the same default values? The problem everytime, Jenkins runs a build it fails with the following message: ERROR: CVS Authentication failed: null Caused by: *com.jcraft.jsch.JSchException*http://stacktrace.jenkins-ci.org/search?query=com.jcraft.jsch.JSchException: java.io.FileNotFoundException: /var/lib/jenkins/.ssh/id_dsa (No such file or directory) So, how to instruct Jenkins to not to use the Private Key Location, Private Key Password, Known Hosts Location fields and use instead the user and password supplied? -- 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/groups/opt_out.
Polling job is not queued even manually started job is already running
It seems that polling job is not queued when manually started job is already running. Instead polling job is trying to run at the same time. I have a Jenkins configured to Mac mini for iOS projects. Let's say I have two jobs: - Job A is scheduled periodically or started manually. This job runs functional tests on simulator. - Job B is triggered by poll every 15 minutes. This job runs unit tests on simulator. The problem is that when I start job A and it will run 40 minutes, the job B will start meanwhile and it tries to run at the same time with job A. Queuing is working fine with several scheduled jobs but not with polling job. Why job B is not queued? Any thoughts? -- 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/groups/opt_out.
Re: CVS Authentication failed!
I could add the ssh public/private key authentication, but what if I do not the access to create the user jenkins on the server that is hosting my cvs repo? On Thursday, July 11, 2013 2:57:22 PM UTC-7, Sameh Tawfik wrote: Hi, I'm using Jenkins ver. 1.522 Under Manage Jenkins\Configure System\CVS\ Authentication , I setup CVS Root, Username, and Password, but under same CVS section there are these fields: Private Key Location, Private Key Password, Known Hosts Location which I'm not using or need, because instead I'm using the values under the Authentication. Everytime, I remove the values specified for Private Key Location, Private Key Password, Known Hosts Location fields and save, when I go back Jenkins is populating these values again with the same default values? The problem everytime, Jenkins runs a build it fails with the following message: ERROR: CVS Authentication failed: null Caused by: *com.jcraft.jsch.JSchException*http://stacktrace.jenkins-ci.org/search?query=com.jcraft.jsch.JSchException: java.io.FileNotFoundException: /var/lib/jenkins/.ssh/id_dsa (No such file or directory) So, how to instruct Jenkins to not to use the Private Key Location, Private Key Password, Known Hosts Location fields and use instead the user and password supplied? -- 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/groups/opt_out.
