Re: Failed to connect to repository
Hi, Which versions of jenkins, git and git client plugin are you using? There have been some problems reported with the latest versions of git and git client. Try downgrading git plugin to 1.5.0 and git client to 1.4.0. That's what worked for me, but I was looking for a combination of https access, and gerrit integration working. Maybe downgrading only the git plugin is enough, maybe not. Cheers, Ricardo On 10/31/2013 09:44 PM, slouie.at.w...@gmail.com wrote: Thanks for the reply. Yeah, I don't want to use ssh. I want to use https. On Thursday, October 31, 2013 1:24:40 PM UTC-7, Maneesh M P wrote: if you want to use git clone over ssh, keep your key at /var/lib/jenkins/.ssh then git clone will work just like how it works in your command line. Thanks, Maneesh On Thursday, October 31, 2013 1:15:12 PM UTC-7, slouie@gmail.comwrote: If I can add, in my initial post, I was running Jenkins as a service account user (we'll call jenkins). I also installed a local Jenkins just to debug. If I ran Jenkins as myself and for the repository URL, i typed ssh:// first.l...@blah.com:8443/blah.git, this worked fine so I'm not sure what's wrong with my git or Jenkins config. Running git frmo command line works for both ssh and https. Jenkins works for ssh when Jenkins is run as myself. Jenkins doesn't work on ssh and https when it's not run by me. On Thursday, October 31, 2013 1:07:37 PM UTC-7, slouie@gmail.comwrote: Hi, I'm a noob to Jenkins so please forgive me if this is a dumb question. I'm trying to use Jenkins to pull down our code from git to make a build. Someone told me to use anonymous read-only access via https in Jenkins so we can pull down our code w/o public keys or what not. In my project, I click on Configure. Under Source Code ManagementGitRepository URL, I type in our repo url. https://blah.com:8443/blah.git Jenkins returns this message below. Failed to connect to repository : Failed to connect to https://blah.com:8443/blah.git The funny thing is when I'm on the command line, I can type this and git works fine: git clone https://blah.com:8443/blah.git I also tried this on the cmd line too, which also worked, provided, I have my public keys in place. git clone ssh://first.l...@blah.com:8443/blah.git What do I need to do in Jenkins so that it pulls my code down w/o problems, just like the command line examples? Do I need to do something on the git repo to get this to work with Jenkins? Thanks in advance for your help. -- Ricardo -- 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: Failed to connect to repository
Also, unless you really need any missing features it might be wiser to go with the LTS releases [1] as you'll for sure bump into less issues. I've been bitten several times in the past few weeks by issues with upgrades in the weekly releases of both Jenkins and plugins. [1] https://wiki.jenkins-ci.org/display/JENKINS/LTS+Release+Line On 11/01/2013 07:33 AM, Ricardo Silva wrote: Hi, Which versions of jenkins, git and git client plugin are you using? There have been some problems reported with the latest versions of git and git client. Try downgrading git plugin to 1.5.0 and git client to 1.4.0. That's what worked for me, but I was looking for a combination of https access, and gerrit integration working. Maybe downgrading only the git plugin is enough, maybe not. Cheers, Ricardo On 10/31/2013 09:44 PM, slouie.at.w...@gmail.com wrote: Thanks for the reply. Yeah, I don't want to use ssh. I want to use https. On Thursday, October 31, 2013 1:24:40 PM UTC-7, Maneesh M P wrote: if you want to use git clone over ssh, keep your key at /var/lib/jenkins/.ssh then git clone will work just like how it works in your command line. Thanks, Maneesh On Thursday, October 31, 2013 1:15:12 PM UTC-7, slouie@gmail.comwrote: If I can add, in my initial post, I was running Jenkins as a service account user (we'll call jenkins). I also installed a local Jenkins just to debug. If I ran Jenkins as myself and for the repository URL, i typed ssh:// first.l...@blah.com:8443/blah.git, this worked fine so I'm not sure what's wrong with my git or Jenkins config. Running git frmo command line works for both ssh and https. Jenkins works for ssh when Jenkins is run as myself. Jenkins doesn't work on ssh and https when it's not run by me. On Thursday, October 31, 2013 1:07:37 PM UTC-7, slouie@gmail.comwrote: Hi, I'm a noob to Jenkins so please forgive me if this is a dumb question. I'm trying to use Jenkins to pull down our code from git to make a build. Someone told me to use anonymous read-only access via https in Jenkins so we can pull down our code w/o public keys or what not. In my project, I click on Configure. Under Source Code ManagementGitRepository URL, I type in our repo url. https://blah.com:8443/blah.git Jenkins returns this message below. Failed to connect to repository : Failed to connect to https://blah.com:8443/blah.git The funny thing is when I'm on the command line, I can type this and git works fine: git clone https://blah.com:8443/blah.git I also tried this on the cmd line too, which also worked, provided, I have my public keys in place. git clone ssh://first.l...@blah.com:8443/blah.git What do I need to do in Jenkins so that it pulls my code down w/o problems, just like the command line examples? Do I need to do something on the git repo to get this to work with Jenkins? Thanks in advance for your help. -- Ricardo -- 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.
Multyjob build hanging everytime
Hi all! I setup a multyjob project and i have created a few steps. When starting a build the first step gets started but the entire build hangs on the first job (even if i see that it has ended when opening the job itself). Is there a way to fix that? Is this a known issue? Jenkins ver. 1.485 Multyjob plugin 1.9 -- 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: Slow dashboard loading for jobs with many compiler warnings
Hi Ullrich, Thank you for your fast answer! On Wednesday, October 30, 2013 6:47:33 PM UTC+1, Ullrich Hafner wrote: This seems to be the problem! The build.xml file should be as small as possible since these files are always read (and are always kept in memory). Seems that these plug-ins do not use an additional file to store the data: this is a bug (or at least a bad design). Can you please file a new bug report for both plug-ins? I found 2 earlier bug reports, and added to them cppcheck JENKINS-17363 https://issues.jenkins-ci.org/browse/JENKINS-17363 Ludicrously slow load time [with lazyloading]https://issues.jenkins-ci.org/browse/JENKINS-17363 sloccount JENKINS-4769 https://issues.jenkins-ci.org/browse/JENKINS-4769 Memory consumption is huge https://issues.jenkins-ci.org/browse/JENKINS-4769 Is the performance better if you disable the cppcheck and sloccount plugins? What other warnings are you aggregating in the analysis.xml file? Are these produced by the warnings plugin? I removed the sloccount data and trimmed the cppcheck data as it was too valuable to toss away, but won't be checking for style errors there anymore. The build.xml files now only max out at 300K instead of 13MB. After reloading Jenkins I saw that the heap was reduced from ~700MB to ~300MB and the All view is fast again. As you suggested, the compiler warning with it's separate analysis.xml is not the culprit and follows the right approach. I suggested in those two issues that these plugins also follow that strategy. Best Regards, Ruben -- 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: Jenkins 1.537 and git 2.0 code error reported when cloning git repo
Thank you, I will look deeper into what is happening within the Maven project. From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mark Waite Sent: Thursday, October 31, 2013 8:53 PM To: jenkinsci-users@googlegroups.com Subject: Re: Jenkins 1.537 and git 2.0 code error reported when cloning git repo That stack trace seems unrelated to the git plugin and seems to happen after the clone has completed. It appears the Jenkins maven module is trying to execute, and is failing. I suspect that happens after the clone is complete. I created a maven project and had it clone the git-client-plugin from https://github.com/jenkinsci/git-client-plugin.git . That worked on both Debian Wheezy and Debian Jessie using Maven 3 as delivered with those operating systems. On Thu, Oct 31, 2013 at 3:40 PM, John Kerr john.k...@thinktank.netmailto:john.k...@thinktank.net wrote: Verified that a freestyle project performs a clone without issue. Seems to be related to the Maven project. On Thursday, October 31, 2013 3:06:11 PM UTC-6, John Kerr wrote: I am creating a new installation of Jenkins (1.537) on Ubuntu using the git plugin (2.0) and on a maven 2/3 project cloning from a remote git repo as the first thing the job does I get the following ominous error: Building in workspace /var/lib/jenkins/workspace/project Fetching changes from the remote Git repository Fetching upstream changes from ssh://g...@git.com:/project.githttp://g...@git.com:/project.git using GIT_SSH to set credentials Git access Checking out Revision f03c2a56f862b3b10013c1e9b0265cb917046a7d (origin/master) ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com java.lang.NullPointerExceptionhttp://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerException at java.io.File.init(File.java:251)http://stacktrace.jenkins-ci.org/search/?query=java.io.File.%3Cinit%3Eentity=method at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58)http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenVersionCallable.callentity=method at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41)http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenVersionCallable.callentity=method at hudson.FilePath.act(FilePath.java:1004)http://stacktrace.jenkins-ci.org/search/?query=hudson.FilePath.actentity=method at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:607)http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRunentity=method at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562)http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.runentity=method at hudson.model.Run.execute(Run.java:1665)http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.executeentity=method at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509)http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild.runentity=method at hudson.model.ResourceController.execute(ResourceController.java:88)http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.executeentity=method at hudson.model.Executor.run(Executor.java:230)http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.runentity=method project=hudson.maven.MavenModuleSet@6d133151[projectmailto:project=hudson.maven.MavenModuleSet@6d133151[project] project.getModules()=[] project.getRootModule()=null FATAL: null java.lang.NullPointerExceptionhttp://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerException at java.io.File.init(File.java:251)http://stacktrace.jenkins-ci.org/search/?query=java.io.File.%3Cinit%3Eentity=method at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58)http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenVersionCallable.callentity=method at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41)http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenVersionCallable.callentity=method at hudson.FilePath.act(FilePath.java:1004)http://stacktrace.jenkins-ci.org/search/?query=hudson.FilePath.actentity=method at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:607)http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRunentity=method at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562)http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.runentity=method at
Re: Jenkins 1.537 and git 2.0 code error reported when cloning git repo
It appears you're not the only one encountering the problem. https://groups.google.com/d/msg/jenkinsci-users/QDkVHmHnI-U/6cnw4RAvNQIJ seems to be another example of a similar stack trace Unfortunately, I have no hint as to the root of the problem. Mark Waite On Fri, Nov 1, 2013 at 8:25 AM, John Kerr john.k...@thinktank.net wrote: No, this was the first job on a new install that was only clone-ing the git repository and then calling the maven pom. ** ** *From:* jenkinsci-users@googlegroups.com [mailto: jenkinsci-users@googlegroups.com] *On Behalf Of *Jeff *Sent:* Thursday, October 31, 2013 9:12 PM *To:* jenkinsci-users@googlegroups.com *Subject:* Re: Jenkins 1.537 and git 2.0 code error reported when cloning git repo ** ** By chance, are you trying to use a custom Groovy (or similar) script to read the maven version and store it in a variable? ** ** On Thu, Oct 31, 2013 at 8:52 PM, Mark Waite mark.earl.wa...@gmail.com wrote: That stack trace seems unrelated to the git plugin and seems to happen after the clone has completed. It appears the Jenkins maven module is trying to execute, and is failing. I suspect that happens after the clone is complete. ** ** I created a maven project and had it clone the git-client-plugin from https://github.com/jenkinsci/git-client-plugin.git . That worked on both Debian Wheezy and Debian Jessie using Maven 3 as delivered with those operating systems. ** ** On Thu, Oct 31, 2013 at 3:40 PM, John Kerr john.k...@thinktank.net wrote: Verified that a freestyle project performs a clone without issue. Seems to be related to the Maven project. On Thursday, October 31, 2013 3:06:11 PM UTC-6, John Kerr wrote: I am creating a new installation of Jenkins (1.537) on Ubuntu using the git plugin (2.0) and on a maven 2/3 project cloning from a remote git repo as the first thing the job does I get the following ominous error: ** ** Building in workspace /var/lib/jenkins/workspace/project Fetching changes from the remote Git repository Fetching upstream changes from ssh://g...@git.com:/project.git using GIT_SSH to set credentials Git access Checking out Revision f03c2a56f862b3b10013c1e9b0265cb917046a7d (origin/master) ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-users@googlegroups.com java.lang.NullPointerException http://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerException at java.io.File.init(File.java:251) http://stacktrace.jenkins-ci.org/search/?query=java.io.File.%3Cinit%3Eentity=method at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenVersionCallable.callentity=method at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenVersionCallable.callentity=method at hudson.FilePath.act(FilePath.java:1004) http://stacktrace.jenkins-ci.org/search/?query=hudson.FilePath.actentity=method at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:607) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRunentity=method at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.runentity=method at hudson.model.Run.execute(Run.java:1665) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.executeentity=method at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild.runentity=method at hudson.model.ResourceController.execute(ResourceController.java:88) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.executeentity=method at hudson.model.Executor.run(Executor.java:230) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.runentity=method project=hudson.maven.MavenModuleSet@6d133151[project] project.getModules()=[] project.getRootModule()=null FATAL: null java.lang.NullPointerException http://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerException at java.io.File.init(File.java:251) http://stacktrace.jenkins-ci.org/search/?query=java.io.File.%3Cinit%3Eentity=method at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenVersionCallable.callentity=method at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41)
Re: build failed due to bug in code
John Kerr recently reported a similar stack trace. https://groups.google.com/d/msg/jenkinsci-users/QDkVHmHnI-U/6cnw4RAvNQIJ Unfortunately, I have no idea on either of the cases. Mark Waite On Friday, November 1, 2013 8:10:04 AM UTC-6, William Pughe wrote: A Jenkins build of code that builds from the command line and in other Jenkins instances produced: Checking out Revision 3f7b2aebae0b87940b806423bb5d55e634e93a3b (origin/master) First time build. Skipping changelog. ERROR: Processing failed due to a bug in the code. Please report this to jenkins...@googlegroups.com javascript:java.lang.NullPointerException http://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerException at java.io.File.init(File.java:277) http://stacktrace.jenkins-ci.org/search/?query=java.io.File.%3Cinit%3Eentity=method at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenVersionCallable.callentity=method at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenVersionCallable.callentity=method at hudson.FilePath.act(FilePath.java:1004) http://stacktrace.jenkins-ci.org/search/?query=hudson.FilePath.actentity=method at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:605) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRunentity=method at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.runentity=method at hudson.model.Run.execute(Run.java:1665) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.executeentity=method at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:507) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild.runentity=method at hudson.model.ResourceController.execute(ResourceController.java:88) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.executeentity=method at hudson.model.Executor.run(Executor.java:230) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.runentity=method project=hudson.maven.MavenModuleSet@66f11134[first] project.getModules()=[] project.getRootModule()=null FATAL: nulljava.lang.NullPointerException http://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerException at java.io.File.init(File.java:277) http://stacktrace.jenkins-ci.org/search/?query=java.io.File.%3Cinit%3Eentity=method at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenVersionCallable.callentity=method at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenVersionCallable.callentity=method at hudson.FilePath.act(FilePath.java:1004) http://stacktrace.jenkins-ci.org/search/?query=hudson.FilePath.actentity=method at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:605) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRunentity=method at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.runentity=method at hudson.model.Run.execute(Run.java:1665) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.executeentity=method at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:507) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild.runentity=method at hudson.model.ResourceController.execute(ResourceController.java:88) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.executeentity=method at hudson.model.Executor.run(Executor.java:230) 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/groups/opt_out.
Re: Jenkins 1.537 and git 2.0 code error reported when cloning git repo
On 01/11/2013 14:28, Mark Waite wrote: It appears you're not the only one encountering the problem. https://groups.google.com/d/msg/jenkinsci-users/QDkVHmHnI-U/6cnw4RAvNQIJ seems to be another example of a similar stack trace Unfortunately, I have no hint as to the root of the problem. I too do not know what the root of the problem is but looking at the source corresponding to the stack trace it looks like the maven installation home directory is coming out as null. line 58 MavenVersionCallable.java File home = new File(mavenHome); line 608 MavenModuleSetBuild MavenInformation mavenInformation = getModuleRoot().act( new MavenVersionCallable( mvn.getHome() )); It might be worth checking the global maven configuration to see if there is anything amiss there. Regards Richard Mark Waite On Fri, Nov 1, 2013 at 8:25 AM, John Kerr john.k...@thinktank.net mailto:john.k...@thinktank.net wrote: No, this was the first job on a new install that was only clone-ing the git repository and then calling the maven pom. __ __ *From:*jenkinsci-users@googlegroups.com mailto:jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com mailto:jenkinsci-users@googlegroups.com] *On Behalf Of *Jeff *Sent:* Thursday, October 31, 2013 9:12 PM *To:* jenkinsci-users@googlegroups.com mailto:jenkinsci-users@googlegroups.com *Subject:* Re: Jenkins 1.537 and git 2.0 code error reported when cloning git repo __ __ By chance, are you trying to use a custom Groovy (or similar) script to read the maven version and store it in a variable? __ __ On Thu, Oct 31, 2013 at 8:52 PM, Mark Waite mark.earl.wa...@gmail.com mailto:mark.earl.wa...@gmail.com wrote: That stack trace seems unrelated to the git plugin and seems to happen after the clone has completed. It appears the Jenkins maven module is trying to execute, and is failing. I suspect that happens after the clone is complete. __ __ I created a maven project and had it clone the git-client-plugin from https://github.com/jenkinsci/git-client-plugin.git . That worked on both Debian Wheezy and Debian Jessie using Maven 3 as delivered with those operating systems. __ __ On Thu, Oct 31, 2013 at 3:40 PM, John Kerr john.k...@thinktank.net mailto:john.k...@thinktank.net wrote: Verified that a freestyle project performs a clone without issue. Seems to be related to the Maven project. On Thursday, October 31, 2013 3:06:11 PM UTC-6, John Kerr wrote: I am creating a new installation of Jenkins (1.537) on Ubuntu using the git plugin (2.0) and on a maven 2/3 project cloning from a remote git repo as the first thing the job does I get the following ominous error: __ __ Building in workspace /var/lib/jenkins/workspace/project Fetching changes from the remote Git repository Fetching upstream changes from ssh://g...@git.com:/project.git http://g...@git.com:/project.git using GIT_SSH to set credentials Git access Checking out Revision f03c2a56f862b3b10013c1e9b0265cb917046a7d (origin/master) ERROR: Processing failed due to a bug in the code. Please report this tojenkinsci-us...@googlegroups.com mailto:jenkinsci-users@googlegroups.com java.lang.NullPointerException http://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerException atjava.io.File.init(File.java:251) http://stacktrace.jenkins-ci.org/search/?query=java.io.File.%3Cinit%3Eentity=method athudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenVersionCallable.callentity=method athudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenVersionCallable.callentity=method athudson.FilePath.act(FilePath.java:1004) http://stacktrace.jenkins-ci.org/search/?query=hudson.FilePath.actentity=method athudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:607) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRunentity=method athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.runentity=method athudson.model.Run.execute(Run.java:1665) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.executeentity=method athudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509)
Aw: build failed due to bug in code
What is your Jenkins and your maven-plugin versions? From the error it looks like theres a problem with the configured maven installation to use for this job (Maven home seems to be empty). Can you check that configuration? Gesendet:Freitag, 01. November 2013 um 15:10 Uhr Von:William Pughe willpu...@gmail.com An:jenkinsci-users@googlegroups.com Betreff:build failed due to bug in code A Jenkins build of code that builds from the command line and in other Jenkins instances produced: Checking out Revision 3f7b2aebae0b87940b806423bb5d55e634e93a3b (origin/master) First time build. Skipping changelog. ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-users@googlegroups.com java.lang.NullPointerException at java.io.File.init(File.java:277) at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58) at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41) at hudson.FilePath.act(FilePath.java:1004) at hudson.maven.MavenModuleSetBuildMavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:605) at hudson.model.AbstractBuildAbstractBuildExecution.run(AbstractBuild.java:562) at hudson.model.Run.execute(Run.java:1665) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:507) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) project=hudson.maven.MavenModuleSet@66f11134[first] project.getModules()=[] project.getRootModule()=null FATAL: null java.lang.NullPointerException at java.io.File.init(File.java:277) at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58) at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41) at hudson.FilePath.act(FilePath.java:1004) at hudson.maven.MavenModuleSetBuildMavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:605) at hudson.model.AbstractBuildAbstractBuildExecution.run(AbstractBuild.java:562) at hudson.model.Run.execute(Run.java:1665) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:507) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) -- 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: build failed due to bug in code
This can be trivially reproduced: Create a Maven installation, remove the auto-installer, and leave the path empty. Configure it to be used in a Maven job, and run it. On 01.11.2013, at 15:30, Mark Waite mark.earl.wa...@gmail.com wrote: John Kerr recently reported a similar stack trace. https://groups.google.com/d/msg/jenkinsci-users/QDkVHmHnI-U/6cnw4RAvNQIJ Unfortunately, I have no idea on either of the cases. Mark Waite On Friday, November 1, 2013 8:10:04 AM UTC-6, William Pughe wrote: A Jenkins build of code that builds from the command line and in other Jenkins instances produced: Checking out Revision 3f7b2aebae0b87940b806423bb5d55 e634e93a3b (origin/master) First time build. Skipping changelog. ERROR: Processing failed due to a bug in the code. Please report this to jenkins...@googlegroups.com java.lang.NullPointerException at java.io.File.init(File.java:277) at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58) at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41) at hudson.FilePath.act(FilePath.java:1004) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:605) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562) at hudson.model.Run.execute(Run.java:1665) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:507) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) project=hudson.maven. MavenModuleSet@66f11134[first] project.getModules()=[] project.getRootModule()=null FATAL: null java.lang.NullPointerException at java.io.File.init(File.java:277) at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58) at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41) at hudson.FilePath.act(FilePath.java:1004) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:605) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562) at hudson.model.Run.execute(Run.java:1665) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:507) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) -- 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: build failed due to bug in code
That was it, empty maven_home. All set now, thanks for the help. On Fri, Nov 1, 2013 at 11:46 AM, Christoph Kutzinski ku...@gmx.de wrote: What is your Jenkins and your maven-plugin versions? From the error it looks like there's a problem with the configured maven installation to use for this job (Maven home seems to be empty). Can you check that configuration? *Gesendet:* Freitag, 01. November 2013 um 15:10 Uhr *Von:* William Pughe willpu...@gmail.com *An:* jenkinsci-users@googlegroups.com *Betreff:* build failed due to bug in code A Jenkins build of code that builds from the command line and in other Jenkins instances produced: Checking out Revision 3f7b2aebae0b87940b806423bb5d55e634e93a3b (origin/master) First time build. Skipping changelog. ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-users@googlegroups.com java.lang.NullPointerException http://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerException at java.io.File.init(File.java:277) http://stacktrace.jenkins-ci.org/search/?query=java.io.File.%3Cinit%3Eentity=method at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenVersionCallable.callentity=method at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenVersionCallable.callentity=method at hudson.FilePath.act(FilePath.java:1004) http://stacktrace.jenkins-ci.org/search/?query=hudson.FilePath.actentity=method at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:605) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRunentity=method at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.runentity=method at hudson.model.Run.execute(Run.java:1665) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.executeentity=method at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:507) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild.runentity=method at hudson.model.ResourceController.execute(ResourceController.java:88) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.executeentity=method at hudson.model.Executor.run(Executor.java:230) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.runentity=method project=hudson.maven.MavenModuleSet@66f11134[first] project.getModules()=[] project.getRootModule()=null FATAL: nulljava.lang.NullPointerException http://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerException at java.io.File.init(File.java:277) http://stacktrace.jenkins-ci.org/search/?query=java.io.File.%3Cinit%3Eentity=method at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenVersionCallable.callentity=method at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenVersionCallable.callentity=method at hudson.FilePath.act(FilePath.java:1004) http://stacktrace.jenkins-ci.org/search/?query=hudson.FilePath.actentity=method at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:605) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRunentity=method at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.runentity=method at hudson.model.Run.execute(Run.java:1665) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.executeentity=method at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:507) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild.runentity=method at hudson.model.ResourceController.execute(ResourceController.java:88) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.executeentity=method at hudson.model.Executor.run(Executor.java:230) 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/groups/opt_out. -- You received this message because you are subscribed to a
Aw: Re: build failed due to bug in code
Nice :) Could you create a JIRA issue for this, so we can produce a better error message the next time someone hits this problem? Gesendet:Freitag, 01. November 2013 um 16:53 Uhr Von:William Pughe willpu...@gmail.com An:jenkinsci-users@googlegroups.com Betreff:Re: build failed due to bug in code That was it, empty maven_home. All set now, thanks for the help. On Fri, Nov 1, 2013 at 11:46 AM, Christoph Kutzinski ku...@gmx.de wrote: What is your Jenkins and your maven-plugin versions? From the error it looks like theres a problem with the configured maven installation to use for this job (Maven home seems to be empty). Can you check that configuration? Gesendet:Freitag, 01. November 2013 um 15:10 Uhr Von:William Pughe willpu...@gmail.com An:jenkinsci-users@googlegroups.com Betreff:build failed due to bug in code A Jenkins build of code that builds from the command line and in other Jenkins instances produced: Checking out Revision 3f7b2aebae0b87940b806423bb5d55e634e93a3b (origin/master) First time build. Skipping changelog. ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-users@googlegroups.com java.lang.NullPointerException at java.io.File.init(File.java:277) at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58) at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41) at hudson.FilePath.act(FilePath.java:1004) at hudson.maven.MavenModuleSetBuildMavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:605) at hudson.model.AbstractBuildAbstractBuildExecution.run(AbstractBuild.java:562) at hudson.model.Run.execute(Run.java:1665) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:507) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) project=hudson.maven.MavenModuleSet@66f11134[first] project.getModules()=[] project.getRootModule()=null FATAL: null java.lang.NullPointerException at java.io.File.init(File.java:277) at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58) at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41) at hudson.FilePath.act(FilePath.java:1004) at hudson.maven.MavenModuleSetBuildMavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:605) at hudson.model.AbstractBuildAbstractBuildExecution.run(AbstractBuild.java:562) at hudson.model.Run.execute(Run.java:1665) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:507) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) -- 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/2711nDJxK6A/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. -- 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.
Aw: Re: Re: build failed due to bug in code
maven2 Gesendet:Freitag, 01. November 2013 um 17:24 Uhr Von:William Pughe willpu...@gmail.com An:jenkinsci-users@googlegroups.com Betreff:Re: Re: build failed due to bug in code Sure, what component would this be for? On Fri, Nov 1, 2013 at 12:08 PM, Christoph Kutzinski ku...@gmx.de wrote: Nice :) Could you create a JIRA issue for this, so we can produce a better error message the next time someone hits this problem? Gesendet:Freitag, 01. November 2013 um 16:53 Uhr Von:William Pughe willpu...@gmail.com An:jenkinsci-users@googlegroups.com Betreff:Re: build failed due to bug in code That was it, empty maven_home. All set now, thanks for the help. On Fri, Nov 1, 2013 at 11:46 AM, Christoph Kutzinski ku...@gmx.de wrote: What is your Jenkins and your maven-plugin versions? From the error it looks like theres a problem with the configured maven installation to use for this job (Maven home seems to be empty). Can you check that configuration? Gesendet:Freitag, 01. November 2013 um 15:10 Uhr Von:William Pughe willpu...@gmail.com An:jenkinsci-users@googlegroups.com Betreff:build failed due to bug in code A Jenkins build of code that builds from the command line and in other Jenkins instances produced: Checking out Revision 3f7b2aebae0b87940b806423bb5d55e634e93a3b (origin/master) First time build. Skipping changelog. ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-users@googlegroups.com java.lang.NullPointerException at java.io.File.init(File.java:277) at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58) at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41) at hudson.FilePath.act(FilePath.java:1004) at hudson.maven.MavenModuleSetBuildMavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:605) at hudson.model.AbstractBuildAbstractBuildExecution.run(AbstractBuild.java:562) at hudson.model.Run.execute(Run.java:1665) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:507) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) project=hudson.maven.MavenModuleSet@66f11134[first] project.getModules()=[] project.getRootModule()=null FATAL: null java.lang.NullPointerException at java.io.File.init(File.java:277) at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58) at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41) at hudson.FilePath.act(FilePath.java:1004) at hudson.maven.MavenModuleSetBuildMavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:605) at hudson.model.AbstractBuildAbstractBuildExecution.run(AbstractBuild.java:562) at hudson.model.Run.execute(Run.java:1665) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:507) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) -- 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/2711nDJxK6A/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. -- 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/2711nDJxK6A/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. -- 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: Using variables within the Jenkins email subject lines ?
Check this http://automatethebox.blogspot.in/2013/10/use-environment-variable-in-jenkins.html On Wednesday, September 26, 2012 3:01:23 AM UTC+5:30, Tom80112 wrote: I would like to use variables within Jenkins email subject lines. I am using the editable email notification plugin. Instead of having a set-in-stone email subject line, I would like define the subject line using a variable that I define based upon the job's execution. Anyone have any ideas? -- View this message in context: http://jenkins.361315.n4.nabble.com/Using-variables-within-the-Jenkins-email-subject-lines-tp4641373.html Sent from the Jenkins users mailing list archive at Nabble.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: Jenkins Fails on Create Job
I found the solution. I move .jenkins to backup (ie. .jenkins.bak), restarted jenkins and let it recreate a new .jenkins directory. I recreated a new job, without errors, and move the .jenkins.bak back to .jenkins. This old .jenkins may be corrupt for some reason. Hope this helps anyone. -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Jenkins-Fails-on-Create-Job-tp4668551p4679528.html Sent from the Jenkins users mailing list archive at Nabble.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: Using variables within the Jenkins email subject lines ?
Check this http://automatethebox.blogspot.com/2013/10/use-environment-variable-in-jenkins.html -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Using-variables-within-the-Jenkins-email-subject-lines-tp4641373p4679736.html Sent from the Jenkins users mailing list archive at Nabble.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: Jenkins Fails on Create Job
Hi I've installed with Jetty 9.0.6 with Jenkins 1.511 and I got this error as well. Has anyone found the cause and a solution to this error? Thanks. -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Jenkins-Fails-on-Create-Job-tp4668551p4679518.html Sent from the Jenkins users mailing list archive at Nabble.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.
Mylyn Build Connector - accessing build jobs in folders?
At the moment I'm only able to connect to build jobs and folders at the top level of my build server; which is inconvenient to say the least as we organise our inventory by service per folder, with the build jobs associated with each service. Which effectively puts the build jobs https://Jenkins/job/service 1 folder/job/service 1 job https://Jenkins/job/service 2 folder/job/service 2 job https://Jenkins/job/a build job https://Jenkins/job/another build job currently all I am able to see in eclipse builds is build server connection service 1 folder service 2 folder a build job another build job Which seems a bit poor, expecting all the build jobs to be available at the top level. Changing the server URL to include anything other than https://jenkins , such as a full path to https://Jenkins/job/service 1 folder/ doesn't work, as the connector Does anyone have an experiences of using Jenkins and mylyn in this way; or is this just the way it is? Thanks dD This e-mail and any attachments are confidential and intended solely for the addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the addressee, or have received this e-mail in error, please notify the sender immediately, delete it from your system and do not copy, disclose or otherwise act upon any part of this e-mail or its attachments. Internet communications are not guaranteed to be secure or virus-free. The Barclays Group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any Internet communications by any third party, or from the transmission of any viruses. Replies to this e-mail may be monitored by the Barclays Group for operational or business reasons. Any opinion or other information in this e-mail or its attachments that does not relate to the business of the Barclays Group is personal to the sender and is not given or endorsed by the Barclays Group. Barclays Bank PLC. Registered in England and Wales (registered no. 1026167). Registered Office: 1 Churchill Place, London, E14 5HP, United Kingdom. Barclays Bank PLC is authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority (Financial Services Register No. 122702). -- 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: Jenkins 1.537 and git 2.0 code error reported when cloning git repo
This issue was resolved by specifying the Maven version to use in the Jenkins configuration using the Install automatically option from Apache instead of using the already installed version of Maven on the system. -Original Message- From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Richard Mortimer Sent: Friday, November 01, 2013 8:51 AM To: jenkinsci-users@googlegroups.com Subject: Re: Jenkins 1.537 and git 2.0 code error reported when cloning git repo On 01/11/2013 14:28, Mark Waite wrote: It appears you're not the only one encountering the problem. https://groups.google.com/d/msg/jenkinsci-users/QDkVHmHnI-U/6cnw4RAvNQ IJ seems to be another example of a similar stack trace Unfortunately, I have no hint as to the root of the problem. I too do not know what the root of the problem is but looking at the source corresponding to the stack trace it looks like the maven installation home directory is coming out as null. line 58 MavenVersionCallable.java File home = new File(mavenHome); line 608 MavenModuleSetBuild MavenInformation mavenInformation = getModuleRoot().act( new MavenVersionCallable( mvn.getHome() )); It might be worth checking the global maven configuration to see if there is anything amiss there. Regards Richard Mark Waite On Fri, Nov 1, 2013 at 8:25 AM, John Kerr john.k...@thinktank.net mailto:john.k...@thinktank.net wrote: No, this was the first job on a new install that was only clone-ing the git repository and then calling the maven pom. __ __ *From:*jenkinsci-users@googlegroups.com mailto:jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com mailto:jenkinsci-users@googlegroups.com] *On Behalf Of *Jeff *Sent:* Thursday, October 31, 2013 9:12 PM *To:* jenkinsci-users@googlegroups.com mailto:jenkinsci-users@googlegroups.com *Subject:* Re: Jenkins 1.537 and git 2.0 code error reported when cloning git repo __ __ By chance, are you trying to use a custom Groovy (or similar) script to read the maven version and store it in a variable? __ __ On Thu, Oct 31, 2013 at 8:52 PM, Mark Waite mark.earl.wa...@gmail.com mailto:mark.earl.wa...@gmail.com wrote: That stack trace seems unrelated to the git plugin and seems to happen after the clone has completed. It appears the Jenkins maven module is trying to execute, and is failing. I suspect that happens after the clone is complete. __ __ I created a maven project and had it clone the git-client-plugin from https://github.com/jenkinsci/git-client-plugin.git . That worked on both Debian Wheezy and Debian Jessie using Maven 3 as delivered with those operating systems. __ __ On Thu, Oct 31, 2013 at 3:40 PM, John Kerr john.k...@thinktank.net mailto:john.k...@thinktank.net wrote: Verified that a freestyle project performs a clone without issue. Seems to be related to the Maven project. On Thursday, October 31, 2013 3:06:11 PM UTC-6, John Kerr wrote: I am creating a new installation of Jenkins (1.537) on Ubuntu using the git plugin (2.0) and on a maven 2/3 project cloning from a remote git repo as the first thing the job does I get the following ominous error: __ __ Building in workspace /var/lib/jenkins/workspace/project Fetching changes from the remote Git repository Fetching upstream changes from ssh://g...@git.com:/project.git http://g...@git.com:/project.git using GIT_SSH to set credentials Git access Checking out Revision f03c2a56f862b3b10013c1e9b0265cb917046a7d (origin/master) ERROR: Processing failed due to a bug in the code. Please report this tojenkinsci-us...@googlegroups.com mailto:jenkinsci-users@googlegroups.com java.lang.NullPointerException http://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerEx ception atjava.io.File.init(File.java:251) http://stacktrace.jenkins-ci.org/search/?query=java.io.File.%3Cinit%3 Eentity=method athudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenVers ionCallable.callentity=method athudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenVers ionCallable.callentity=method athudson.FilePath.act(FilePath.java:1004) http://stacktrace.jenkins-ci.org/search/?query=hudson.FilePath.acten tity=method athudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun( MavenModuleSetBuild.java:607)
questions about svn checkout performance and upgrade from hudson
I have a couple of questions We are using Hudson 3.0, we recently upgraded after a need to upgrade our subversion from 1.6 to 1.7 which created a real problem. Checkout/Update performance is very very slow on Hudson with this version and svn 1.7. There is a report that the db that svn uses is being opened/locked on every file, rather than once per checkout. Is this something that has been resolved with Jenkins? Does anyone have any answers to this problem. We were originally on an older version of Hudson 1.3.5 and upgraded to 3.0. How hard is it to migrate to jenkins given that we have had 3.0 running. Does anyone know of any migration scripts? -- 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.
