problems with collabnet plug-in
We are using Collabnet to upload the builds. Here is the info of the environment - Jenkins version / 1.457 CollabNet Plugin/1.1.6 /usr/lib/jvm/java-1.6. 0-openjdk-1.6.0.0.x86_64 All the way, at the end of the build while trying to upload the build, it throws the following exception. Thus Jenkins sets the build status to unstable. Has anyone seen this exception ? If so, I would appreciate any suggestions. channel stopped CollabNet FileRelease: Critical Error: login to https://collabnet.xyz.abc failed. Setting build status to UNSTABLE (or worse). ERROR: Publisher hudson.plugins.collabnet.filerelease.CNFileRelease aborted due to exception java.lang.NullPointerException at hudson.plugins.collabnet.filerelease.CNFileRelease.createAction(CNFileRe lease.java:195) at hudson.plugins.collabnet.filerelease.CNFileRelease.perform(CNFileRelease .java:169) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703 ) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractB uild.java:678) at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.ja va:998) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:625) at hudson.model.Run.run(Run.java:1435) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Sending e-mails to: z...@abc.com Email was triggered for: Failure Sending email for trigger: Failure thanks
RE: problems with collabnet plug-in
That is correct. It does have the appropriate URL and is a working one. Thanks From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Darryl Bowler Sent: Tuesday, May 22, 2012 12:54 PM To: jenkinsci-users@googlegroups.com Subject: Re: problems with collabnet plug-in CollabNet FileRelease: Critical Error: login to https://collabnet.xyz.abc failed I assume you have replaced https://collabnet.xyz.abc; with the URL to a functional Teamforge server? Regards On May 22, 2012, at 2:35 PM, sampath.rajago...@vce.com wrote: We are using Collabnet to upload the builds. Here is the info of the environment - Jenkins version / 1.457 CollabNet Plugin/1.1.6 /usr/lib/jvm/java-1.6. 0-openjdk-1.6.0.0.x86_64 All the way, at the end of the build while trying to upload the build, it throws the following exception. Thus Jenkins sets the build status to unstable. Has anyone seen this exception ? If so, I would appreciate any suggestions. channel stopped CollabNet FileRelease: Critical Error: login to https://collabnet.xyz.abc failed. Setting build status to UNSTABLE (or worse). ERROR: Publisher hudson.plugins.collabnet.filerelease.CNFileRelease aborted due to exception java.lang.NullPointerException at hudson.plugins.collabnet.filerelease.CNFileRelease.createAction(CNFileRe lease.java:195) at hudson.plugins.collabnet.filerelease.CNFileRelease.perform(CNFileRelease .java:169) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703 ) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractB uild.java:678) at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.ja va:998) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:625) at hudson.model.Run.run(Run.java:1435) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Sending e-mails to: z...@abc.com Email was triggered for: Failure Sending email for trigger: Failure thanks
RE: problems with collabnet plug-in
After much of woes, found out that domainname\username is not acceptable within Jenkins environment. Just use username for Collabnet configuration within Jenkins. Thanks Darryl. Regards From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Darryl Bowler Sent: Tuesday, May 22, 2012 2:17 PM To: jenkinsci-users@googlegroups.com Subject: Re: problems with collabnet plug-in Can you confirm that credentials used to access the Teamforge server (1) Can log into the UI (2) Make sure the account used has a sufficient role(RBAC) to access the file release in the project Regarding (2) you could use a site admin access to test. Regards On May 22, 2012, at 4:01 PM, sampath.rajago...@vce.com wrote: That is correct. It does have the appropriate URL and is a working one. Thanks From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Darryl Bowler Sent: Tuesday, May 22, 2012 12:54 PM To: jenkinsci-users@googlegroups.com Subject: Re: problems with collabnet plug-in CollabNet FileRelease: Critical Error: login to https://collabnet.xyz.abc failed I assume you have replaced https://collabnet.xyz.abc; with the URL to a functional Teamforge server? Regards On May 22, 2012, at 2:35 PM, sampath.rajago...@vce.com wrote: We are using Collabnet to upload the builds. Here is the info of the environment - Jenkins version / 1.457 CollabNet Plugin/1.1.6 /usr/lib/jvm/java-1.6. 0-openjdk-1.6.0.0.x86_64 All the way, at the end of the build while trying to upload the build, it throws the following exception. Thus Jenkins sets the build status to unstable. Has anyone seen this exception ? If so, I would appreciate any suggestions. channel stopped CollabNet FileRelease: Critical Error: login to https://collabnet.xyz.abc failed. Setting build status to UNSTABLE (or worse). ERROR: Publisher hudson.plugins.collabnet.filerelease.CNFileRelease aborted due to exception java.lang.NullPointerException at hudson.plugins.collabnet.filerelease.CNFileRelease.createAction(CNFileRe lease.java:195) at hudson.plugins.collabnet.filerelease.CNFileRelease.perform(CNFileRelease .java:169) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703 ) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractB uild.java:678) at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.ja va:998) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:625) at hudson.model.Run.run(Run.java:1435) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Sending e-mails to: z...@abc.com Email was triggered for: Failure Sending email for trigger: Failure thanks
RE: After disk upgrade, jenkins build stopped working
Referring to https://issues.jenkins-ci.org/browse/JENKINS-11398, I see the updates posted by Seiji Sogabe (user name:dogfood) and plugins_cobertura#70 is part of 1.463-SNAPSHOT release (http://ci.jenkins-ci.org/job/plugins_cobertura/70/). I would like to know when this fix will be available from jenkins download center (http://updates.jenkins-ci.org/download) Essentially fix to src/main/java/hudson/plugins/cobertura/dashboard/CoverageTablePortlet.java I would like to be prompted for downloading a release containing this fix, to move ahead as the CI environment is not functional as of now. I would guess this will be available as part of 1.463 ? Please advise. thanks From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mark Waite Sent: Sunday, May 06, 2012 1:45 PM To: jenkinsci-users@googlegroups.com Subject: Re: After disk upgrade, jenkins build stopped working I would guess (looking at the classpath mentioned in the trace) that the cobertura plugin is the first plugin to attempt the steps. A google search hints that there may be a bug that was just recently fixed in the Cobertura and Emma plugins which has that stack trace. You might review https://issues.jenkins-ci.org/browse/JENKINS-11398 to see if it matches your situation. Mark Waite From: sampath.rajago...@vce.com sampath.rajago...@vce.com To: jenkinsci-users@googlegroups.com Sent: Sunday, May 6, 2012 3:14 PM Subject: RE: After disk upgrade, jenkins build stopped working Thanks Mark for that note. Just curious – what are the plugins that correspond to the following exceptions (as well as dependency plugins if any) – Failed to load hudson.plugins.cobertura.dashboard.CoverageTablePortlet$DescriptorImpl java.lang.LinkageError: Failed to resolve class hudson.plugins.cobertura.dashboard.CoverageTablePortlet$DescriptorImpl Caused by java.lang.TypeNotPresentException: Type hudson.plugins.view.dashboard.DashboardPortlet not present Caused by java.lang.ClassNotFoundException: hudson.plugins.view.dashboard.DashboardPortlet In particular for dashboard.DashboardPortlet. Thanks From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mark Waite Sent: Sunday, May 06, 2012 1:06 PM To: jenkinsci-users@googlegroups.com Subject: Re: After disk upgrade, jenkins build stopped working I doubt the addition of the disc space is the cause of the problem. Did the disc become full during previous operation? If so, then attempts to write to the disc may have failed at that time. If the writes failed, then it is possible that the plugin you're trying to reference is not completely installed, or is installed and not completely configured. You might try attempting to reconfigure the plugin. If the issue is not resolved after you reconfigure the plugin, you could try disabling the plugin, restarting Jenkins, then enabling the plugin again. If disable and enable does not repair it, then you could try removing the plugin completely, restarting Jenkins and installing the plugin again. Mark Waite To: jenkinsci-users@googlegroups.com Sent: Sunday, May 6, 2012 2:51 PM Subject: After disk upgrade, jenkins build stopped working Not sure if any one else has run into this issue. After disk space addition, the builds stopped working. ‘build now’ link is not doing anything. Appreicate your input. Is there a best practice that one should be following while doing such a maintenance work ? The VM where Jenkins CI is running, was reaching to a point of disk space being full. Our Admin decided to increase the disk space. After that the builds stopped working. Both “Build Now” link as well as scheduled builds do not work anymore. Here is the exception details in the log – Failed to load hudson.plugins.cobertura.dashboard.CoverageTablePortlet$DescriptorImpl java.lang.LinkageError: Failed to resolve class hudson.plugins.cobertura.dashboard.CoverageTablePortlet$DescriptorImpl Caused by java.lang.TypeNotPresentException: Type hudson.plugins.view.dashboard.DashboardPortlet not present Caused by java.lang.ClassNotFoundException: hudson.plugins.view.dashboard.DashboardPortlet Looking at the link https://issues.jenkins-ci.org/browse/JENKINS-11398, I installed Dashboard
After disk upgrade, jenkins build stopped working
Not sure if any one else has run into this issue. After disk space addition, the builds stopped working. 'build now' link is not doing anything. Appreicate your input. Is there a best practice that one should be following while doing such a maintenance work ? The VM where Jenkins CI is running, was reaching to a point of disk space being full. Our Admin decided to increase the disk space. After that the builds stopped working. Both Build Now link as well as scheduled builds do not work anymore. Here is the exception details in the log - Failed to load hudson.plugins.cobertura.dashboard.CoverageTablePortlet$DescriptorImpl java.lang.LinkageError: Failed to resolve class hudson.plugins.cobertura.dashboard.CoverageTablePortlet$DescriptorImpl Caused by java.lang.TypeNotPresentException: Type hudson.plugins.view.dashboard.DashboardPortlet not present Caused by java.lang.ClassNotFoundException: hudson.plugins.view.dashboard.DashboardPortlet Looking at the link https://issues.jenkins-ci.org/browse/JENKINS-11398, I installed Dashboard plugin but it still does not help. The environment stopped working. When I go to smart Jenkins page, everything shows up in Blocked state. Never realized that adding extra disk space would lead to this situation. Thanks for any help
RE: After disk upgrade, jenkins build stopped working
Thanks Mark for that note. Just curious – what are the plugins that correspond to the following exceptions (as well as dependency plugins if any) – Failed to load hudson.plugins.cobertura.dashboard.CoverageTablePortlet$DescriptorImpl java.lang.LinkageError: Failed to resolve class hudson.plugins.cobertura.dashboard.CoverageTablePortlet$DescriptorImpl Caused by java.lang.TypeNotPresentException: Type hudson.plugins.view.dashboard.DashboardPortlet not present Caused by java.lang.ClassNotFoundException: hudson.plugins.view.dashboard.DashboardPortlet In particular for dashboard.DashboardPortlet. Thanks From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mark Waite Sent: Sunday, May 06, 2012 1:06 PM To: jenkinsci-users@googlegroups.com Subject: Re: After disk upgrade, jenkins build stopped working I doubt the addition of the disc space is the cause of the problem. Did the disc become full during previous operation? If so, then attempts to write to the disc may have failed at that time. If the writes failed, then it is possible that the plugin you're trying to reference is not completely installed, or is installed and not completely configured. You might try attempting to reconfigure the plugin. If the issue is not resolved after you reconfigure the plugin, you could try disabling the plugin, restarting Jenkins, then enabling the plugin again. If disable and enable does not repair it, then you could try removing the plugin completely, restarting Jenkins and installing the plugin again. Mark Waite To: jenkinsci-users@googlegroups.com Sent: Sunday, May 6, 2012 2:51 PM Subject: After disk upgrade, jenkins build stopped working Not sure if any one else has run into this issue. After disk space addition, the builds stopped working. ‘build now’ link is not doing anything. Appreicate your input. Is there a best practice that one should be following while doing such a maintenance work ? The VM where Jenkins CI is running, was reaching to a point of disk space being full. Our Admin decided to increase the disk space. After that the builds stopped working. Both “Build Now” link as well as scheduled builds do not work anymore. Here is the exception details in the log – Failed to load hudson.plugins.cobertura.dashboard.CoverageTablePortlet$DescriptorImpl java.lang.LinkageError: Failed to resolve class hudson.plugins.cobertura.dashboard.CoverageTablePortlet$DescriptorImpl Caused by java.lang.TypeNotPresentException: Type hudson.plugins.view.dashboard.DashboardPortlet not present Caused by java.lang.ClassNotFoundException: hudson.plugins.view.dashboard.DashboardPortlet Looking at the link https://issues.jenkins-ci.org/browse/JENKINS-11398, I installed Dashboard plugin but it still does not help. The environment stopped working. When I go to “smart Jenkins” page, everything shows up in “Blocked” state. Never realized that adding extra disk space would lead to this situation. Thanks for any help
Builds stopped working - Hudson.plugins.view.dashboard.DashboardPortlet not present
The VM where Jenkins CI is running, was reaching to a point of disk space being full. Our Admin decided to increase the disk space. After that the builds stopped working. Both Build Now link as well as scheduled builds do not work anymore. Here is the exception details in the log - Failed to load hudson.plugins.cobertura.dashboard.CoverageTablePortlet$DescriptorImpl java.lang.LinkageError: Failed to resolve class hudson.plugins.cobertura.dashboard.CoverageTablePortlet$DescriptorImpl Caused by java.lang.TypeNotPresentException: Type hudson.plugins.view.dashboard.DashboardPortlet not present Caused by java.lang.ClassNotFoundException: hudson.plugins.view.dashboard.DashboardPortlet Looking at the link https://issues.jenkins-ci.org/browse/JENKINS-11398, I installed Dashboard plugin but it still does not help. The environment stopped working. When I go to smart Jenkins page, everything shows up in Blocked state. Never realized that adding extra disk space would lead to this situation. Thanks for any help.
problems with 'mvn deploy wagon:upload' when invoked from jenkins
I have ftp configured using vsftp in linux x86_64 (vm) environment,
running
Red Hat Enterprise Linux Server release 6.2 (Santiago)
POM.xml as follows -
distributionManagement
repository
idftp-repository/id
nameRepository/name
urlftp://192.123.456.789/repository//url
/repository
/distributionManagement
groupIdorg.codehaus.mojo/groupId
artifactIdwagon-maven-plugin/artifactId
version1.0-beta-3/version
configuration
fromDir${project.build.directory}/fromDir
includes*.war/includes
urlftp://192.123.456.789//url
toDirrepository/toDir
serverIdftp-repository/serverId
/configuration
My settings.xml has user id, passwd and the server id.
When I do 'mvn deploy wagon:upload' with my user id from the command
line, it works.
When I run the same command from Jenkins, it does not work and ends up
with the following error -
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy (default-deploy)
on project v-a-sample-main: Failed to retrieve remote metadata
v.a.sample.main:v-a-sample-main:1.0-SNAPSHOT/maven-metadata.xml: Could
not transfer metadata
v.a.sample.main:v-a-sample-main:1.0-SNAPSHOT/maven-metadata.xml from/to
a-samples-ftp-repository (ftp://192.123.345.567/repository/):
NullPointerException - [Help 1]
[ERROR]
Why is the 'deploy wagon:upload' command not working from Jenkins gui. ?
any suggestions
RE: problems with 'mvn deploy wagon:upload' when invoked from jenkins
Tim, we are using apache-maven/3.0.3 both within and outside of Jenkins.
Is there a plug-in (of a particular version) that I am missing ? Please advise.
Not sure if anyone has run into this problem - why maven goals (configured for
ftp) don’t work from within Jenkins ?
thanks
-Original Message-
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Tim Pizey
Sent: Monday, April 02, 2012 1:13 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: problems with 'mvn deploy wagon:upload' when invoked from jenkins
Hi Sampath,
There is a possibility that Jenkins is using Maven3 and you are using
maven2 outside of Jenkins.
cheers
Tim
On 2 April 2012 07:50, wrote:
I have ftp configured using vsftp in linux x86_64 (vm) environment, running
Red Hat Enterprise Linux Server release 6.2 (Santiago)
POM.xml as follows –
distributionManagement
repository
idftp-repository/id
nameRepository/name
urlftp://192.123.456.789/repository//url
/repository
/distributionManagement
groupIdorg.codehaus.mojo/groupId
artifactIdwagon-maven-plugin/artifactId
version1.0-beta-3/version
configuration
fromDir${project.build.directory}/fromDir
includes*.war/includes
urlftp://192.123.456.789//url
toDirrepository/toDir
serverIdftp-repository/serverId
/configuration
My settings.xml has user id, passwd and the server id.
When I do ‘mvn deploy wagon:upload’ with my user id from the command line,
it works.
When I run the same command from Jenkins, it does not work and ends up with
the following error –
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy (default-deploy) on
project v-a-sample-main: Failed to retrieve remote metadata
v.a.sample.main:v-a-sample-main:1.0-SNAPSHOT/maven-metadata.xml: Could not
transfer metadata
v.a.sample.main:v-a-sample-main:1.0-SNAPSHOT/maven-metadata.xml from/to
a-samples-ftp-repository (ftp://192.123.345.567/repository/):
NullPointerException - [Help 1]
[ERROR]
Why is the ‘deploy wagon:upload’ command not working from Jenkins gui. ? any
suggestions
--
Tim Pizey - http://pizey.net/~timp
maven build fails when invoked from jenkins
Not sure about this strange error suddenly. Nothing has changed. It was a working system. Now when I submit the build thru Jenkins, it throws up io exception. It checks out everything from svn repo, builds fine but then throws up this IO exception. Don't have any idea as to what is going on. Why would it give FATAL command execution failed msg ? There is no problem from the cmdtool window. This is a VM. Appreciate any clues. thanks [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 5.652s [INFO] Finished at: Wed Mar 07 20:53:30 PST 2012 [INFO] Final Memory: 11M/203M [INFO] [workspace] $ mvn FATAL: command execution failed java.io.IOException: Cannot run program mvn (in directory /var/lib/jenkins/jobs/Ax_Tools/workspace): java.io.IOException: error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:475) at hudson.Proc$LocalProc.init(Proc.java:244) at hudson.Proc$LocalProc.init(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:707) at hudson.Launcher$ProcStarter.start(Launcher.java:338) at hudson.Launcher$ProcStarter.join(Launcher.java:345) at hudson.tasks.Maven.perform(Maven.java:263) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:700 ) at hudson.model.Build$RunnerImpl.build(Build.java:178) at hudson.model.Build$RunnerImpl.doRun(Build.java:139) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:470) at hudson.model.Run.run(Run.java:1409) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Caused by: java.io.IOException: java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.init(UNIXProcess.java:164) at java.lang.ProcessImpl.start(ProcessImpl.java:81) at java.lang.ProcessBuilder.start(ProcessBuilder.java:468) ... 15 more Build step 'Invoke top-level Maven targets' marked build as failure
RE: email coming to everyone instead of build breakers (culprits)
Send to Recipient List is not checked for any trigger. Include Culprits is checked for Failure trigger. In here Recipient List is empty. send to Committers is not checked for any trigger. From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Slide Sent: Wednesday, February 22, 2012 4:27 PM To: jenkinsci-users@googlegroups.com Subject: Re: email coming to everyone instead of build breakers (culprits) Do you also have send to recipients checked? On Feb 22, 2012 4:40 PM, sampath.rajago...@vce.com wrote: Using Jenkins 1.4.51 and mail-ext-plug in / 2.1.8 The build failure notification goes to everyone instead of culprits. The question is - when you enable Include Culprits, should it have Recipient List filled in ? or it can be left blank ?? What should be done to have the mail sent to the breaker only. ? thanks
RE: email coming to everyone instead of build breakers (culprits)
Sounds like https://issues.jenkins-ci.org/browse/JENKINS-12421 From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Slide Sent: Wednesday, February 22, 2012 5:34 PM To: jenkinsci-users@googlegroups.com Subject: RE: email coming to everyone instead of build breakers (culprits) This may be a known bug, I don't have JIRA available right now, but you could check. On Feb 22, 2012 6:03 PM, sampath.rajago...@vce.com wrote: Send to Recipient List is not checked for any trigger. Include Culprits is checked for Failure trigger. In here Recipient List is empty. send to Committers is not checked for any trigger. From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Slide Sent: Wednesday, February 22, 2012 4:27 PM To: jenkinsci-users@googlegroups.com Subject: Re: email coming to everyone instead of build breakers (culprits) Do you also have send to recipients checked? On Feb 22, 2012 4:40 PM, sampath.rajago...@vce.com wrote: Using Jenkins 1.4.51 and mail-ext-plug in / 2.1.8 The build failure notification goes to everyone instead of culprits. The question is - when you enable Include Culprits, should it have Recipient List filled in ? or it can be left blank ?? What should be done to have the mail sent to the breaker only. ? thanks
