[JIRA] (JENKINS-13790) Subversion externals fail
[ https://issues.jenkins-ci.org/browse/JENKINS-13790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162816#comment-162816 ] tapiomtr commented on JENKINS-13790: We also noticed same AssertionError when Jenkins subversion pluging is upgraded from 1.39 to 1.40 version. Subversion externals fail - Key: JENKINS-13790 URL: https://issues.jenkins-ci.org/browse/JENKINS-13790 Project: Jenkins Issue Type: Bug Components: subversion Affects Versions: current Environment: Windows XP SP3 Reporter: chikigai Updates on a repository with svn:externals property set fail with the following: AssertionError: appears to be using unpatched svnkit at jar:xxx/SVNEvent.class The issue is present with the latest 1.40 release. The issue is not preset with the 1.39 release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9509) Cannot choose Editable Email as action for promotion
[ https://issues.jenkins-ci.org/browse/JENKINS-9509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162790#comment-162790 ] Juan Manuel Barroso edited comment on JENKINS-9509 at 5/16/12 6:33 AM: --- I'm having the same error in version 2.20 and Jenkins 1.4.63. Is it possible? EDIT: I found the issue https://issues.jenkins-ci.org/browse/JENKINS-13737 was (Author: jmbarroso): I'm having the same error in version 2.20 and Jenkins 1.4.63. Is it possible? Cannot choose Editable Email as action for promotion --- Key: JENKINS-9509 URL: https://issues.jenkins-ci.org/browse/JENKINS-9509 Project: Jenkins Issue Type: Bug Components: email-ext, promoted-builds Reporter: Sagar Khushalani Assignee: b2jrock Fix For: current Attachments: button.JPG This used to work before. However, now if I try to select Editable Email Notification as an action of a promotion, it does nothing. Not sure if there is any log I can check, but I didn't see anything in the main Jenkins Log. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13791) naginator plugin NullPointerException on successful build
[
https://issues.jenkins-ci.org/browse/JENKINS-13791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162817#comment-162817
]
SCM/JIRA link daemon commented on JENKINS-13791:
Code changed in jenkins
User: Jesse Farinacci
Path:
.classpath
.gitignore
src/main/java/com/chikli/hudson/plugin/naginator/NaginatorListener.java
http://jenkins-ci.org/commit/naginator-plugin/506f067d5fa3f1814951ff59c509a638314c3978
Log:
[FIXED JENKINS-13791] naginator plugin NullPointerException on successful
build
naginator plugin NullPointerException on successful build
-
Key: JENKINS-13791
URL: https://issues.jenkins-ci.org/browse/JENKINS-13791
Project: Jenkins
Issue Type: Bug
Components: naginator
Reporter: jieryn
Assignee: Nayan Hajratwala
Jenkins v1.447.1
Naginator Plugin v1.6.1
{code}[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 24:13.510s
[INFO] Finished at: Tue May 15 22:27:18 EDT 2012
[INFO] Final Memory: 38M/2048M
[INFO]
ERROR: Processing failed due to a bug in the code. Please report this to
jenkinsci-us...@googlegroups.com
java.lang.NullPointerException
at
com.chikli.hudson.plugin.naginator.NaginatorListener.onCompleted(NaginatorListener.java:32)
at
com.chikli.hudson.plugin.naginator.NaginatorListener.onCompleted(NaginatorListener.java:20)
at
hudson.model.listeners.RunListener.fireCompleted(RunListener.java:178)
at hudson.model.Run.run(Run.java:1454)
at hudson.maven.MavenBuild.access$600(MavenBuild.java:83)
at hudson.maven.MavenBuild$ProxyImpl2.close(MavenBuild.java:546)
at
hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:106)
at
hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:795)
at
hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:467)
at hudson.model.Run.run(Run.java:1404)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)
project=hudson.maven.MavenModuleSet@6b006b0[release_com.acme.project]
project.getModules()=[hudson.maven.MavenModule@3ba73ba7[release_com.acme.project/com.acme:project][release_com.acme.project/com.acme:project][relativePath:],
hudson.maven.MavenModule@64856485[release_com.acme.project/com.acme.project:cim][release_com.acme.project/com.acme.project:cim][relativePath:cim],
hudson.maven.MavenModule@b100b10[release_com.acme.project/com.acme.project:dao][release_com.acme.project/com.acme.project:dao][relativePath:dao],
hudson.maven.MavenModule@1e001e[release_com.acme.project/com.acme.project:domain][release_com.acme.project/com.acme.project:domain][relativePath:domain],
hudson.maven.MavenModule@1e271e27[release_com.acme.project/com.acme.project:gwt][release_com.acme.project/com.acme.project:gwt][relativePath:gwt],
hudson.maven.MavenModule@7a0b7a0b[release_com.acme.project/com.acme.project:mock][release_com.acme.project/com.acme.project:mock][relativePath:mock],
hudson.maven.MavenModule@4ac34ac3[release_com.acme.project/com.acme.project:service][release_com.acme.project/com.acme.project:service][relativePath:service],
hudson.maven.MavenModule@3b173b17[release_com.acme.project/com.acme.project:war][release_com.acme.project/com.acme.project:war][relativePath:war],
hudson.maven.MavenModule@e030e03[release_com.acme.project/com.acme.project:ws][release_com.acme.project/com.acme.project:ws][relativePath:ws],
hudson.maven.MavenModule@474c474c[release_com.acme.project/com.acme.project.ws:domain][release_com.acme.project/com.acme.project.ws:domain][relativePath:ws/domain],
hudson.maven.MavenModule@18041804[release_com.acme.project/com.acme.project.ws:rs][release_com.acme.project/com.acme.project.ws:rs][relativePath:ws/rs],
hudson.maven.MavenModule@26132613[release_com.acme.project/com.acme.project.ws:war][release_com.acme.project/com.acme.project.ws:war][relativePath:ws/war]]
project.getRootModule()=hudson.maven.MavenModule@3ba73ba7[release_com.acme.project/com.acme:project][release_com.acme.project/com.acme:project][relativePath:]
FATAL: null
java.lang.NullPointerException
at
com.chikli.hudson.plugin.naginator.NaginatorListener.onCompleted(NaginatorListener.java:32)
at
com.chikli.hudson.plugin.naginator.NaginatorListener.onCompleted(NaginatorListener.java:20)
at
hudson.model.listeners.RunListener.fireCompleted(RunListener.java:178)
at hudson.model.Run.run(Run.java:1454)
at
[JIRA] (JENKINS-13791) naginator plugin NullPointerException on successful build
[
https://issues.jenkins-ci.org/browse/JENKINS-13791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162818#comment-162818
]
SCM/JIRA link daemon commented on JENKINS-13791:
Code changed in jenkins
User: Nicolas De loof
Path:
.classpath
.gitignore
src/main/java/com/chikli/hudson/plugin/naginator/NaginatorListener.java
http://jenkins-ci.org/commit/naginator-plugin/d0d065b69c14b1ecb3f6409c2f57b1a8e67428e3
Log:
Merge pull request #2 from jieryn/master
[FIXED JENKINS-13791] naginator plugin NullPointerException on successful build
Compare: https://github.com/jenkinsci/naginator-plugin/compare/e3719cc...d0d065b
naginator plugin NullPointerException on successful build
-
Key: JENKINS-13791
URL: https://issues.jenkins-ci.org/browse/JENKINS-13791
Project: Jenkins
Issue Type: Bug
Components: naginator
Reporter: jieryn
Assignee: Nayan Hajratwala
Jenkins v1.447.1
Naginator Plugin v1.6.1
{code}[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 24:13.510s
[INFO] Finished at: Tue May 15 22:27:18 EDT 2012
[INFO] Final Memory: 38M/2048M
[INFO]
ERROR: Processing failed due to a bug in the code. Please report this to
jenkinsci-us...@googlegroups.com
java.lang.NullPointerException
at
com.chikli.hudson.plugin.naginator.NaginatorListener.onCompleted(NaginatorListener.java:32)
at
com.chikli.hudson.plugin.naginator.NaginatorListener.onCompleted(NaginatorListener.java:20)
at
hudson.model.listeners.RunListener.fireCompleted(RunListener.java:178)
at hudson.model.Run.run(Run.java:1454)
at hudson.maven.MavenBuild.access$600(MavenBuild.java:83)
at hudson.maven.MavenBuild$ProxyImpl2.close(MavenBuild.java:546)
at
hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:106)
at
hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:795)
at
hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:467)
at hudson.model.Run.run(Run.java:1404)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)
project=hudson.maven.MavenModuleSet@6b006b0[release_com.acme.project]
project.getModules()=[hudson.maven.MavenModule@3ba73ba7[release_com.acme.project/com.acme:project][release_com.acme.project/com.acme:project][relativePath:],
hudson.maven.MavenModule@64856485[release_com.acme.project/com.acme.project:cim][release_com.acme.project/com.acme.project:cim][relativePath:cim],
hudson.maven.MavenModule@b100b10[release_com.acme.project/com.acme.project:dao][release_com.acme.project/com.acme.project:dao][relativePath:dao],
hudson.maven.MavenModule@1e001e[release_com.acme.project/com.acme.project:domain][release_com.acme.project/com.acme.project:domain][relativePath:domain],
hudson.maven.MavenModule@1e271e27[release_com.acme.project/com.acme.project:gwt][release_com.acme.project/com.acme.project:gwt][relativePath:gwt],
hudson.maven.MavenModule@7a0b7a0b[release_com.acme.project/com.acme.project:mock][release_com.acme.project/com.acme.project:mock][relativePath:mock],
hudson.maven.MavenModule@4ac34ac3[release_com.acme.project/com.acme.project:service][release_com.acme.project/com.acme.project:service][relativePath:service],
hudson.maven.MavenModule@3b173b17[release_com.acme.project/com.acme.project:war][release_com.acme.project/com.acme.project:war][relativePath:war],
hudson.maven.MavenModule@e030e03[release_com.acme.project/com.acme.project:ws][release_com.acme.project/com.acme.project:ws][relativePath:ws],
hudson.maven.MavenModule@474c474c[release_com.acme.project/com.acme.project.ws:domain][release_com.acme.project/com.acme.project.ws:domain][relativePath:ws/domain],
hudson.maven.MavenModule@18041804[release_com.acme.project/com.acme.project.ws:rs][release_com.acme.project/com.acme.project.ws:rs][relativePath:ws/rs],
hudson.maven.MavenModule@26132613[release_com.acme.project/com.acme.project.ws:war][release_com.acme.project/com.acme.project.ws:war][relativePath:ws/war]]
project.getRootModule()=hudson.maven.MavenModule@3ba73ba7[release_com.acme.project/com.acme:project][release_com.acme.project/com.acme:project][relativePath:]
FATAL: null
java.lang.NullPointerException
at
com.chikli.hudson.plugin.naginator.NaginatorListener.onCompleted(NaginatorListener.java:32)
at
com.chikli.hudson.plugin.naginator.NaginatorListener.onCompleted(NaginatorListener.java:20)
at
[JIRA] (JENKINS-13791) naginator plugin NullPointerException on successful build
[
https://issues.jenkins-ci.org/browse/JENKINS-13791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
SCM/JIRA link daemon resolved JENKINS-13791.
Resolution: Fixed
naginator plugin NullPointerException on successful build
-
Key: JENKINS-13791
URL: https://issues.jenkins-ci.org/browse/JENKINS-13791
Project: Jenkins
Issue Type: Bug
Components: naginator
Reporter: jieryn
Assignee: Nayan Hajratwala
Jenkins v1.447.1
Naginator Plugin v1.6.1
{code}[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 24:13.510s
[INFO] Finished at: Tue May 15 22:27:18 EDT 2012
[INFO] Final Memory: 38M/2048M
[INFO]
ERROR: Processing failed due to a bug in the code. Please report this to
jenkinsci-us...@googlegroups.com
java.lang.NullPointerException
at
com.chikli.hudson.plugin.naginator.NaginatorListener.onCompleted(NaginatorListener.java:32)
at
com.chikli.hudson.plugin.naginator.NaginatorListener.onCompleted(NaginatorListener.java:20)
at
hudson.model.listeners.RunListener.fireCompleted(RunListener.java:178)
at hudson.model.Run.run(Run.java:1454)
at hudson.maven.MavenBuild.access$600(MavenBuild.java:83)
at hudson.maven.MavenBuild$ProxyImpl2.close(MavenBuild.java:546)
at
hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:106)
at
hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:795)
at
hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:467)
at hudson.model.Run.run(Run.java:1404)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)
project=hudson.maven.MavenModuleSet@6b006b0[release_com.acme.project]
project.getModules()=[hudson.maven.MavenModule@3ba73ba7[release_com.acme.project/com.acme:project][release_com.acme.project/com.acme:project][relativePath:],
hudson.maven.MavenModule@64856485[release_com.acme.project/com.acme.project:cim][release_com.acme.project/com.acme.project:cim][relativePath:cim],
hudson.maven.MavenModule@b100b10[release_com.acme.project/com.acme.project:dao][release_com.acme.project/com.acme.project:dao][relativePath:dao],
hudson.maven.MavenModule@1e001e[release_com.acme.project/com.acme.project:domain][release_com.acme.project/com.acme.project:domain][relativePath:domain],
hudson.maven.MavenModule@1e271e27[release_com.acme.project/com.acme.project:gwt][release_com.acme.project/com.acme.project:gwt][relativePath:gwt],
hudson.maven.MavenModule@7a0b7a0b[release_com.acme.project/com.acme.project:mock][release_com.acme.project/com.acme.project:mock][relativePath:mock],
hudson.maven.MavenModule@4ac34ac3[release_com.acme.project/com.acme.project:service][release_com.acme.project/com.acme.project:service][relativePath:service],
hudson.maven.MavenModule@3b173b17[release_com.acme.project/com.acme.project:war][release_com.acme.project/com.acme.project:war][relativePath:war],
hudson.maven.MavenModule@e030e03[release_com.acme.project/com.acme.project:ws][release_com.acme.project/com.acme.project:ws][relativePath:ws],
hudson.maven.MavenModule@474c474c[release_com.acme.project/com.acme.project.ws:domain][release_com.acme.project/com.acme.project.ws:domain][relativePath:ws/domain],
hudson.maven.MavenModule@18041804[release_com.acme.project/com.acme.project.ws:rs][release_com.acme.project/com.acme.project.ws:rs][relativePath:ws/rs],
hudson.maven.MavenModule@26132613[release_com.acme.project/com.acme.project.ws:war][release_com.acme.project/com.acme.project.ws:war][relativePath:ws/war]]
project.getRootModule()=hudson.maven.MavenModule@3ba73ba7[release_com.acme.project/com.acme:project][release_com.acme.project/com.acme:project][relativePath:]
FATAL: null
java.lang.NullPointerException
at
com.chikli.hudson.plugin.naginator.NaginatorListener.onCompleted(NaginatorListener.java:32)
at
com.chikli.hudson.plugin.naginator.NaginatorListener.onCompleted(NaginatorListener.java:20)
at
hudson.model.listeners.RunListener.fireCompleted(RunListener.java:178)
at hudson.model.Run.run(Run.java:1454)
at hudson.maven.MavenBuild.access$600(MavenBuild.java:83)
at hudson.maven.MavenBuild$ProxyImpl2.close(MavenBuild.java:546)
at
hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:106)
at
hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:795)
at
hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:467)
[JIRA] (JENKINS-13791) naginator plugin NullPointerException on successful build
[
https://issues.jenkins-ci.org/browse/JENKINS-13791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162819#comment-162819
]
dogfood commented on JENKINS-13791:
---
Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png!
[plugins_naginator #14|http://ci.jenkins-ci.org/job/plugins_naginator/14/]
[FIXED JENKINS-13791] naginator plugin NullPointerException on successful
build (Revision 506f067d5fa3f1814951ff59c509a638314c3978)
Result = SUCCESS
Jesse Farinacci :
Files :
* .gitignore
* .classpath
* src/main/java/com/chikli/hudson/plugin/naginator/NaginatorListener.java
naginator plugin NullPointerException on successful build
-
Key: JENKINS-13791
URL: https://issues.jenkins-ci.org/browse/JENKINS-13791
Project: Jenkins
Issue Type: Bug
Components: naginator
Reporter: jieryn
Assignee: Nayan Hajratwala
Jenkins v1.447.1
Naginator Plugin v1.6.1
{code}[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 24:13.510s
[INFO] Finished at: Tue May 15 22:27:18 EDT 2012
[INFO] Final Memory: 38M/2048M
[INFO]
ERROR: Processing failed due to a bug in the code. Please report this to
jenkinsci-us...@googlegroups.com
java.lang.NullPointerException
at
com.chikli.hudson.plugin.naginator.NaginatorListener.onCompleted(NaginatorListener.java:32)
at
com.chikli.hudson.plugin.naginator.NaginatorListener.onCompleted(NaginatorListener.java:20)
at
hudson.model.listeners.RunListener.fireCompleted(RunListener.java:178)
at hudson.model.Run.run(Run.java:1454)
at hudson.maven.MavenBuild.access$600(MavenBuild.java:83)
at hudson.maven.MavenBuild$ProxyImpl2.close(MavenBuild.java:546)
at
hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:106)
at
hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:795)
at
hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:467)
at hudson.model.Run.run(Run.java:1404)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)
project=hudson.maven.MavenModuleSet@6b006b0[release_com.acme.project]
project.getModules()=[hudson.maven.MavenModule@3ba73ba7[release_com.acme.project/com.acme:project][release_com.acme.project/com.acme:project][relativePath:],
hudson.maven.MavenModule@64856485[release_com.acme.project/com.acme.project:cim][release_com.acme.project/com.acme.project:cim][relativePath:cim],
hudson.maven.MavenModule@b100b10[release_com.acme.project/com.acme.project:dao][release_com.acme.project/com.acme.project:dao][relativePath:dao],
hudson.maven.MavenModule@1e001e[release_com.acme.project/com.acme.project:domain][release_com.acme.project/com.acme.project:domain][relativePath:domain],
hudson.maven.MavenModule@1e271e27[release_com.acme.project/com.acme.project:gwt][release_com.acme.project/com.acme.project:gwt][relativePath:gwt],
hudson.maven.MavenModule@7a0b7a0b[release_com.acme.project/com.acme.project:mock][release_com.acme.project/com.acme.project:mock][relativePath:mock],
hudson.maven.MavenModule@4ac34ac3[release_com.acme.project/com.acme.project:service][release_com.acme.project/com.acme.project:service][relativePath:service],
hudson.maven.MavenModule@3b173b17[release_com.acme.project/com.acme.project:war][release_com.acme.project/com.acme.project:war][relativePath:war],
hudson.maven.MavenModule@e030e03[release_com.acme.project/com.acme.project:ws][release_com.acme.project/com.acme.project:ws][relativePath:ws],
hudson.maven.MavenModule@474c474c[release_com.acme.project/com.acme.project.ws:domain][release_com.acme.project/com.acme.project.ws:domain][relativePath:ws/domain],
hudson.maven.MavenModule@18041804[release_com.acme.project/com.acme.project.ws:rs][release_com.acme.project/com.acme.project.ws:rs][relativePath:ws/rs],
hudson.maven.MavenModule@26132613[release_com.acme.project/com.acme.project.ws:war][release_com.acme.project/com.acme.project.ws:war][relativePath:ws/war]]
project.getRootModule()=hudson.maven.MavenModule@3ba73ba7[release_com.acme.project/com.acme:project][release_com.acme.project/com.acme:project][relativePath:]
FATAL: null
java.lang.NullPointerException
at
com.chikli.hudson.plugin.naginator.NaginatorListener.onCompleted(NaginatorListener.java:32)
at
com.chikli.hudson.plugin.naginator.NaginatorListener.onCompleted(NaginatorListener.java:20)
at
hudson.model.listeners.RunListener.fireCompleted(RunListener.java:178)
[JIRA] (JENKINS-13792) Support for conditional post-build actions
Carsten Pfeiffer created JENKINS-13792: -- Summary: Support for conditional post-build actions Key: JENKINS-13792 URL: https://issues.jenkins-ci.org/browse/JENKINS-13792 Project: Jenkins Issue Type: Improvement Components: conditional-buildstep Affects Versions: current Reporter: Carsten Pfeiffer Assignee: domi Priority: Minor It would be great if the plugin could also be used for *post*-build actions. Our use case is that we have a parameterized build, and, depending on the input parameters of a build, we would like to tag the workspace, or not. So we would add a run-condition for the Tag post-build action checking whether a specific input parameter was set. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13735) Jenkins starts wrong slave for job restricted to specific one
[ https://issues.jenkins-ci.org/browse/JENKINS-13735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13735 started by Kohsuke Kawaguchi. Jenkins starts wrong slave for job restricted to specific one - Key: JENKINS-13735 URL: https://issues.jenkins-ci.org/browse/JENKINS-13735 Project: Jenkins Issue Type: Bug Components: slave-setup, vsphere-cloud Affects Versions: current Environment: Jenkins 1.463 under Tomcat6 on Linux (SLES 11), Windows XP slave VMs controlled via vSphere Cloud plugin Reporter: Marco Lehnort Assignee: Kohsuke Kawaguchi Labels: slave I'm using the following setup: - WinXP slaves A,B,C - jobs jA, jB, jC, tied to slaves A,B,C respectively using Restrict where this job can run Assume all slaves are disconnected and powered off, no builds are queued. When starting a build manually, say jC, the following will happen: - job jC will be scheduled and also displayed accordingly in the build queue - tooltip will say it's waiting because slave C is offline - next, slave A is powered on by Jenkins and connection is established - jC will not be started, Jenkins seems to honor the restriction correctly - after some idle time, Jenkins realizes the slave is idle and causes shut down - then, same procedure happens with slave B - on occasion, next one is slave A again - finally (on good luck?) slave C happens to be started - jC is executed It is possible that jC is waiting for hours (indefinitely?), because the required slave is not powered on. I also observed this behaviour using a time-trigger instead of manual trigger, so I assume it is independent of the type of trigger. Occasionally it also happens that the correct slave is powered up right away, but that seems to happen by chance. The concrete pattern is not obvious to me. Note that the component selection above is just my best guess. Cheers, Marco -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13735) Jenkins starts wrong slave for job restricted to specific one
[ https://issues.jenkins-ci.org/browse/JENKINS-13735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13735 stopped by Marco Lehnort. Jenkins starts wrong slave for job restricted to specific one - Key: JENKINS-13735 URL: https://issues.jenkins-ci.org/browse/JENKINS-13735 Project: Jenkins Issue Type: Bug Components: slave-setup, vsphere-cloud Affects Versions: current Environment: Jenkins 1.463 under Tomcat6 on Linux (SLES 11), Windows XP slave VMs controlled via vSphere Cloud plugin Reporter: Marco Lehnort Assignee: Kohsuke Kawaguchi Labels: slave I'm using the following setup: - WinXP slaves A,B,C - jobs jA, jB, jC, tied to slaves A,B,C respectively using Restrict where this job can run Assume all slaves are disconnected and powered off, no builds are queued. When starting a build manually, say jC, the following will happen: - job jC will be scheduled and also displayed accordingly in the build queue - tooltip will say it's waiting because slave C is offline - next, slave A is powered on by Jenkins and connection is established - jC will not be started, Jenkins seems to honor the restriction correctly - after some idle time, Jenkins realizes the slave is idle and causes shut down - then, same procedure happens with slave B - on occasion, next one is slave A again - finally (on good luck?) slave C happens to be started - jC is executed It is possible that jC is waiting for hours (indefinitely?), because the required slave is not powered on. I also observed this behaviour using a time-trigger instead of manual trigger, so I assume it is independent of the type of trigger. Occasionally it also happens that the correct slave is powered up right away, but that seems to happen by chance. The concrete pattern is not obvious to me. Note that the component selection above is just my best guess. Cheers, Marco -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13775) String index out of range
[
https://issues.jenkins-ci.org/browse/JENKINS-13775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162820#comment-162820
]
Cyril Picat commented on JENKINS-13775:
---
I have the same issue on a iOS project.
I think this might be due to filenames with a '+' inside, like all the
categories we create in Objective-C.
For example, Profile+Additions.h
String index out of range
-
Key: JENKINS-13775
URL: https://issues.jenkins-ci.org/browse/JENKINS-13775
Project: Jenkins
Issue Type: Bug
Components: sloccount
Affects Versions: current
Environment: Linux:redhat9
jenkins:1.463
Reporter: wang y
Assignee: npiguet
Labels: plugin
console output:
{quote}
ERROR: Publisher hudson.plugins.sloccount.SloccountPublisher aborted due to
exception
java.lang.StringIndexOutOfBoundsException: String index out of range: -5
at java.lang.String.substring(String.java:1937)
at java.lang.String.substring(String.java:1904)
at hudson.plugins.sloccount.model.Folder.simplifyName(Folder.java:22)
at
hudson.plugins.sloccount.model.SloccountReport.simplifyNames(SloccountReport.java:175)
at
hudson.plugins.sloccount.model.SloccountParser.invoke(SloccountParser.java:42)
at
hudson.plugins.sloccount.model.SloccountParser.invoke(SloccountParser.java:17)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2154)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{quote}
sloccount file:
{quote}
Have a non-directory at the top, so creating directory top_dir
Adding /g2m_builder_test/railway-svn-code/support/cppcheck-check-Make to
top_dir
Adding /g2m_builder_test/railway-svn-code/support/cppcheck_reports.xml to
top_dir
Adding /g2m_builder_test/railway-svn-code/support/cppcheck-suppress to top_dir
Creating filelist for driver
Adding /g2m_builder_test/railway-svn-code/support/sloccount.sc to top_dir
Creating filelist for test
Categorizing files.
Computing results.
43ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/GhtDspDisp.c
197 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/GhtDspEnc.c
268 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/GhtDspCap.c
179 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/GhtDspDec.c
87ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/Convert.c
636 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/dm648api.c
387 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/GhtDspApi.c
173 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/include/dm648api.h
27ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/include/GhtDspCommon.h
173 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/include/GhtDspApi.h
5 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/Convert.h
6 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/SdkVersion.h
240 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/ShareStruct.h
37makefiletest
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/Makefile
174 cpp test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/dialog/iconDecodeArea.cpp
236 cpp test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/dialog/iconPreviewArea.cpp
223 cpp test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/dialog/mainWindow.cpp
12cpp test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/main.cpp
39cpp test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/public/sunday.cpp
220 cpp test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/public/yuv.cpp
143 cpp test
[JIRA] (JENKINS-13735) Jenkins starts wrong slave for job restricted to specific one
[ https://issues.jenkins-ci.org/browse/JENKINS-13735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Lehnort updated JENKINS-13735: Component/s: master-slave Jenkins starts wrong slave for job restricted to specific one - Key: JENKINS-13735 URL: https://issues.jenkins-ci.org/browse/JENKINS-13735 Project: Jenkins Issue Type: Bug Components: master-slave, slave-setup, vsphere-cloud Affects Versions: current Environment: Jenkins 1.463 under Tomcat6 on Linux (SLES 11), Windows XP slave VMs controlled via vSphere Cloud plugin Reporter: Marco Lehnort Assignee: Kohsuke Kawaguchi Labels: slave I'm using the following setup: - WinXP slaves A,B,C - jobs jA, jB, jC, tied to slaves A,B,C respectively using Restrict where this job can run Assume all slaves are disconnected and powered off, no builds are queued. When starting a build manually, say jC, the following will happen: - job jC will be scheduled and also displayed accordingly in the build queue - tooltip will say it's waiting because slave C is offline - next, slave A is powered on by Jenkins and connection is established - jC will not be started, Jenkins seems to honor the restriction correctly - after some idle time, Jenkins realizes the slave is idle and causes shut down - then, same procedure happens with slave B - on occasion, next one is slave A again - finally (on good luck?) slave C happens to be started - jC is executed It is possible that jC is waiting for hours (indefinitely?), because the required slave is not powered on. I also observed this behaviour using a time-trigger instead of manual trigger, so I assume it is independent of the type of trigger. Occasionally it also happens that the correct slave is powered up right away, but that seems to happen by chance. The concrete pattern is not obvious to me. Note that the component selection above is just my best guess. Cheers, Marco -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13775) String index out of range
[
https://issues.jenkins-ci.org/browse/JENKINS-13775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162821#comment-162821
]
Cyril Picat commented on JENKINS-13775:
---
After more investigation, this is not due to the '+' but to the directory tree.
In some cases, sloc seems to create a fake top_dir at the top and it makes the
plugin fail.
In those cases, you get the following message at the top of the sloccount.sc
file:
'Have a non-directory at the top, so creating directory top_dir'
and entries like:
15 objctop_dir /Users/udd/Jenkins/Workspace/jobs/MyProject
dev/workspace/MyProject/main.m
I simply prune those entries and it works again.
So my full shell build step in Jenkins is the following:
# Compute basic code metrics
sloccount --duplicates --wide --details MyProject | grep -v 'top_dir'
build/sloccount.sc
String index out of range
-
Key: JENKINS-13775
URL: https://issues.jenkins-ci.org/browse/JENKINS-13775
Project: Jenkins
Issue Type: Bug
Components: sloccount
Affects Versions: current
Environment: Linux:redhat9
jenkins:1.463
Reporter: wang y
Assignee: npiguet
Labels: plugin
console output:
{quote}
ERROR: Publisher hudson.plugins.sloccount.SloccountPublisher aborted due to
exception
java.lang.StringIndexOutOfBoundsException: String index out of range: -5
at java.lang.String.substring(String.java:1937)
at java.lang.String.substring(String.java:1904)
at hudson.plugins.sloccount.model.Folder.simplifyName(Folder.java:22)
at
hudson.plugins.sloccount.model.SloccountReport.simplifyNames(SloccountReport.java:175)
at
hudson.plugins.sloccount.model.SloccountParser.invoke(SloccountParser.java:42)
at
hudson.plugins.sloccount.model.SloccountParser.invoke(SloccountParser.java:17)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2154)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{quote}
sloccount file:
{quote}
Have a non-directory at the top, so creating directory top_dir
Adding /g2m_builder_test/railway-svn-code/support/cppcheck-check-Make to
top_dir
Adding /g2m_builder_test/railway-svn-code/support/cppcheck_reports.xml to
top_dir
Adding /g2m_builder_test/railway-svn-code/support/cppcheck-suppress to top_dir
Creating filelist for driver
Adding /g2m_builder_test/railway-svn-code/support/sloccount.sc to top_dir
Creating filelist for test
Categorizing files.
Computing results.
43ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/GhtDspDisp.c
197 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/GhtDspEnc.c
268 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/GhtDspCap.c
179 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/GhtDspDec.c
87ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/Convert.c
636 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/dm648api.c
387 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/GhtDspApi.c
173 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/include/dm648api.h
27ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/include/GhtDspCommon.h
173 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/include/GhtDspApi.h
5 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/Convert.h
6 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/SdkVersion.h
240 ansic test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/ShareStruct.h
37makefiletest
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/GhtDspApi/Makefile
174 cpp test
/g2m_builder_test/railway-svn-code/support/test/viSdkDialog/dialog/iconDecodeArea.cpp
236 cpp test
[JIRA] (JENKINS-13357) Autoinstall JDK from download.oracle.com no longer works
[
https://issues.jenkins-ci.org/browse/JENKINS-13357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162822#comment-162822
]
chanti vlad commented on JENKINS-13357:
---
JENKINS-13435 fix in 1.464 did not help with this issue.
Autoinstall JDK from download.oracle.com no longer works
Key: JENKINS-13357
URL: https://issues.jenkins-ci.org/browse/JENKINS-13357
Project: Jenkins
Issue Type: Bug
Components: core
Affects Versions: current
Reporter: andreasmandel
Assignee: Kohsuke Kawaguchi
Priority: Critical
Just noticed that the autoinstallation of JDK from download.oracle.com
stopped working recently. I tried various Jenkins instances running here and
they all have the same problem; versions 1.458 on Linux Windows
The downloaded 'jdk.exe' or 'jdh.sh' just contains a html page with the note
'Sorry! In order to download products from Oracle Technology
Network you must agree to the OTN license terms.'
The error on Windows build is then:
{code}
Installing JDK jdk-7-oth-JPR
Downloading JDK from
http://download.oracle.com/otn/java/jdk/7/jdk-7-windows-i586.exe
Downloading 5307bytes
[jdk_1.7.0] $ C:\tools\jenkins\tools\jdk_1.7.0\jdk.exe /s /v /qn /L
\C:\tools\jenkins\tools\jdk_1.7.0\jdk.exe.install.log\
REBOOT=ReallySuppress INSTALLDIR=\C:\tools\jenkins\tools\jdk_1.7.0\
The image file %1 is valid, but is for a machine type other than the current
machine
FATAL: Befehlsausführung fehlgeschlagen
java.io.IOException: Cannot run program
C:\tools\jenkins\tools\jdk_1.7.0\jdk.exe (in directory
C:\tools\jenkins\tools\jdk_1.7.0): CreateProcess error=216, This version of
%1 is not compatible with the version of Windows you're running. Check your
computer's system information to see whether you need a x86 (32-bit) or x64
(64-bit) version of the program, and then contact the software publisher
...
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9635) git clone --progress not supported with older git binaries
[ https://issues.jenkins-ci.org/browse/JENKINS-9635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] evernat resolved JENKINS-9635. -- Resolution: Fixed As it can be seen in the commit linked above, the Git version is checked before adding the --progress argument. So this issue seems to be fixed. git clone --progress not supported with older git binaries -- Key: JENKINS-9635 URL: https://issues.jenkins-ci.org/browse/JENKINS-9635 Project: Jenkins Issue Type: Bug Components: git Reporter: Nico Halpern Assignee: abayer Priority: Minor Jenkins-9168 adds the '--progress' option to git-clone. This flag was introduced to git sometime after git v1.5.5.6. The sensible workaround for people running older versions (ie, anyone using EPEL) is to update git to a newer version. There should be a minimum required version of git listed somewhere in the release notes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13357) Autoinstall JDK from download.oracle.com no longer works
[
https://issues.jenkins-ci.org/browse/JENKINS-13357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chanti vlad reopened JENKINS-13357:
---
JENKINS-13435 is marked as a duplicate and is supposed to be fixed in 1.464.
I updated my Jenkins installation to 1.464 but JENKINS-13357 still occurs when
trying to launch a slave as a service on windows 2008 x64.
{{{
Connecting to my.host.name
Checking if Java exists
'java' is not recognized as an internal or external command,
operable program or batch file.
No Java found. Downloading JDK
Installing JDK
Installing C:\tmp2\jenkins_slave\service\jdk.exe
[jdk] $ C:\tmp2\jenkins_slave\service\jdk.exe /s /v /qn /L
\C:\tmp2\jenkins_slave\service\jdk.exe.install.log\ REBOOT=ReallySuppress
INSTALLDIR=\C:\tmp2\jenkins_slave\service\jdk\
This version of C:\tmp2\jenkins_slave\service\jdk.exe is not compatible with
the version of Windows you're running. Check your computer's system information
to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program,
and then contact the software publisher.
Failed to install JDK. Exit code=1
ERROR: Failed to prepare Java
jcifs.smb.SmbException: The system cannot find the file specified.
at jcifs.smb.SmbTransport.checkStatus(SmbTransport.java:545)
at jcifs.smb.SmbTransport.send(SmbTransport.java:646)
at jcifs.smb.SmbSession.send(SmbSession.java:244)
at jcifs.smb.SmbTree.send(SmbTree.java:119)
at jcifs.smb.SmbFile.send(SmbFile.java:770)
at jcifs.smb.SmbFile.open0(SmbFile.java:982)
at jcifs.smb.SmbFile.open(SmbFile.java:999)
at jcifs.smb.SmbFileInputStream.init(SmbFileInputStream.java:74)
at jcifs.smb.SmbFileInputStream.init(SmbFileInputStream.java:66)
at jcifs.smb.SmbFile.getInputStream(SmbFile.java:2833)
at
hudson.os.windows.WindowsRemoteFileSystem.read(WindowsRemoteFileSystem.java:41)
at hudson.tools.JDKInstaller.install(JDKInstaller.java:242)
at
hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:251)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Copying jenkins-slave.xml
Copying slave.jar
Starting the service
* NOT DOING ANYTHING AFTER THAT *
}}}
Autoinstall JDK from download.oracle.com no longer works
Key: JENKINS-13357
URL: https://issues.jenkins-ci.org/browse/JENKINS-13357
Project: Jenkins
Issue Type: Bug
Components: core
Affects Versions: current
Reporter: andreasmandel
Assignee: Kohsuke Kawaguchi
Priority: Critical
Just noticed that the autoinstallation of JDK from download.oracle.com
stopped working recently. I tried various Jenkins instances running here and
they all have the same problem; versions 1.458 on Linux Windows
The downloaded 'jdk.exe' or 'jdh.sh' just contains a html page with the note
'Sorry! In order to download products from Oracle Technology
Network you must agree to the OTN license terms.'
The error on Windows build is then:
{code}
Installing JDK jdk-7-oth-JPR
Downloading JDK from
http://download.oracle.com/otn/java/jdk/7/jdk-7-windows-i586.exe
Downloading 5307bytes
[jdk_1.7.0] $ C:\tools\jenkins\tools\jdk_1.7.0\jdk.exe /s /v /qn /L
\C:\tools\jenkins\tools\jdk_1.7.0\jdk.exe.install.log\
REBOOT=ReallySuppress INSTALLDIR=\C:\tools\jenkins\tools\jdk_1.7.0\
The image file %1 is valid, but is for a machine type other than the current
machine
FATAL: Befehlsausführung fehlgeschlagen
java.io.IOException: Cannot run program
C:\tools\jenkins\tools\jdk_1.7.0\jdk.exe (in directory
C:\tools\jenkins\tools\jdk_1.7.0): CreateProcess error=216, This version of
%1 is not compatible with the version of Windows you're running. Check your
computer's system information to see whether you need a x86 (32-bit) or x64
(64-bit) version of the program, and then contact the software publisher
...
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13357) Autoinstall JDK from download.oracle.com no longer works
[
https://issues.jenkins-ci.org/browse/JENKINS-13357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162824#comment-162824
]
chanti vlad edited comment on JENKINS-13357 at 5/16/12 8:42 AM:
JENKINS-13435 is marked as a duplicate and is supposed to be fixed in 1.464.
I updated my Jenkins installation to 1.464 but JENKINS-13357 still occurs when
trying to launch a slave as a service on windows 2008 x64.
{{
Connecting to my.host.name
Checking if Java exists
'java' is not recognized as an internal or external command,
operable program or batch file.
No Java found. Downloading JDK
Installing JDK
Installing C:\tmp2\jenkins_slave\service\jdk.exe
[jdk] $ C:\tmp2\jenkins_slave\service\jdk.exe /s /v /qn /L
\C:\tmp2\jenkins_slave\service\jdk.exe.install.log\ REBOOT=ReallySuppress
INSTALLDIR=\C:\tmp2\jenkins_slave\service\jdk\
This version of C:\tmp2\jenkins_slave\service\jdk.exe is not compatible with
the version of Windows you're running. Check your computer's system information
to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program,
and then contact the software publisher.
Failed to install JDK. Exit code=1
ERROR: Failed to prepare Java
jcifs.smb.SmbException: The system cannot find the file specified.
at jcifs.smb.SmbTransport.checkStatus(SmbTransport.java:545)
at jcifs.smb.SmbTransport.send(SmbTransport.java:646)
at jcifs.smb.SmbSession.send(SmbSession.java:244)
at jcifs.smb.SmbTree.send(SmbTree.java:119)
at jcifs.smb.SmbFile.send(SmbFile.java:770)
at jcifs.smb.SmbFile.open0(SmbFile.java:982)
at jcifs.smb.SmbFile.open(SmbFile.java:999)
at jcifs.smb.SmbFileInputStream.init(SmbFileInputStream.java:74)
at jcifs.smb.SmbFileInputStream.init(SmbFileInputStream.java:66)
at jcifs.smb.SmbFile.getInputStream(SmbFile.java:2833)
at
hudson.os.windows.WindowsRemoteFileSystem.read(WindowsRemoteFileSystem.java:41)
at hudson.tools.JDKInstaller.install(JDKInstaller.java:242)
at
hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:251)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Copying jenkins-slave.xml
Copying slave.jar
Starting the service
* NOT DOING ANYTHING AFTER THAT *
}}
was (Author: chantivlad):
JENKINS-13435 is marked as a duplicate and is supposed to be fixed in 1.464.
I updated my Jenkins installation to 1.464 but JENKINS-13357 still occurs when
trying to launch a slave as a service on windows 2008 x64.
{{{
Connecting to my.host.name
Checking if Java exists
'java' is not recognized as an internal or external command,
operable program or batch file.
No Java found. Downloading JDK
Installing JDK
Installing C:\tmp2\jenkins_slave\service\jdk.exe
[jdk] $ C:\tmp2\jenkins_slave\service\jdk.exe /s /v /qn /L
\C:\tmp2\jenkins_slave\service\jdk.exe.install.log\ REBOOT=ReallySuppress
INSTALLDIR=\C:\tmp2\jenkins_slave\service\jdk\
This version of C:\tmp2\jenkins_slave\service\jdk.exe is not compatible with
the version of Windows you're running. Check your computer's system information
to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program,
and then contact the software publisher.
Failed to install JDK. Exit code=1
ERROR: Failed to prepare Java
jcifs.smb.SmbException: The system cannot find the file specified.
at jcifs.smb.SmbTransport.checkStatus(SmbTransport.java:545)
at jcifs.smb.SmbTransport.send(SmbTransport.java:646)
at jcifs.smb.SmbSession.send(SmbSession.java:244)
at jcifs.smb.SmbTree.send(SmbTree.java:119)
at jcifs.smb.SmbFile.send(SmbFile.java:770)
at jcifs.smb.SmbFile.open0(SmbFile.java:982)
at jcifs.smb.SmbFile.open(SmbFile.java:999)
at jcifs.smb.SmbFileInputStream.init(SmbFileInputStream.java:74)
at jcifs.smb.SmbFileInputStream.init(SmbFileInputStream.java:66)
at jcifs.smb.SmbFile.getInputStream(SmbFile.java:2833)
at
hudson.os.windows.WindowsRemoteFileSystem.read(WindowsRemoteFileSystem.java:41)
at hudson.tools.JDKInstaller.install(JDKInstaller.java:242)
at
hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:251)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
[JIRA] (JENKINS-13357) Autoinstall JDK from download.oracle.com no longer works
[
https://issues.jenkins-ci.org/browse/JENKINS-13357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162824#comment-162824
]
chanti vlad edited comment on JENKINS-13357 at 5/16/12 8:49 AM:
JENKINS-13435 is marked as a duplicate and is supposed to be fixed in 1.464.
I updated my Jenkins installation to 1.464 but JENKINS-13357 still occurs when
trying to launch a slave as a service on windows 2008 x64.
{{Connecting to my.host.name
Checking if Java exists
'java' is not recognized as an internal or external command,
operable program or batch file.
No Java found. Downloading JDK
Installing JDK
Installing C:\tmp2\jenkins_slave\service\jdk.exe
[jdk] $ C:\tmp2\jenkins_slave\service\jdk.exe /s /v /qn /L
\C:\tmp2\jenkins_slave\service\jdk.exe.install.log\ REBOOT=ReallySuppress
INSTALLDIR=\C:\tmp2\jenkins_slave\service\jdk\
This version of C:\tmp2\jenkins_slave\service\jdk.exe is not compatible with
the version of Windows you're running. Check your computer's system information
to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program,
and then contact the software publisher.
Failed to install JDK. Exit code=1
ERROR: Failed to prepare Java
jcifs.smb.SmbException: The system cannot find the file specified.
at jcifs.smb.SmbTransport.checkStatus(SmbTransport.java:545)
at jcifs.smb.SmbTransport.send(SmbTransport.java:646)
at jcifs.smb.SmbSession.send(SmbSession.java:244)
at jcifs.smb.SmbTree.send(SmbTree.java:119)
at jcifs.smb.SmbFile.send(SmbFile.java:770)
at jcifs.smb.SmbFile.open0(SmbFile.java:982)
at jcifs.smb.SmbFile.open(SmbFile.java:999)
at jcifs.smb.SmbFileInputStream.init(SmbFileInputStream.java:74)
at jcifs.smb.SmbFileInputStream.init(SmbFileInputStream.java:66)
at jcifs.smb.SmbFile.getInputStream(SmbFile.java:2833)
at
hudson.os.windows.WindowsRemoteFileSystem.read(WindowsRemoteFileSystem.java:41)
at hudson.tools.JDKInstaller.install(JDKInstaller.java:242)
at
hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:251)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Copying jenkins-slave.xml
Copying slave.jar
Starting the service
* NOT DOING ANYTHING AFTER THAT *}}
was (Author: chantivlad):
JENKINS-13435 is marked as a duplicate and is supposed to be fixed in 1.464.
I updated my Jenkins installation to 1.464 but JENKINS-13357 still occurs when
trying to launch a slave as a service on windows 2008 x64.
{{
Connecting to my.host.name
Checking if Java exists
'java' is not recognized as an internal or external command,
operable program or batch file.
No Java found. Downloading JDK
Installing JDK
Installing C:\tmp2\jenkins_slave\service\jdk.exe
[jdk] $ C:\tmp2\jenkins_slave\service\jdk.exe /s /v /qn /L
\C:\tmp2\jenkins_slave\service\jdk.exe.install.log\ REBOOT=ReallySuppress
INSTALLDIR=\C:\tmp2\jenkins_slave\service\jdk\
This version of C:\tmp2\jenkins_slave\service\jdk.exe is not compatible with
the version of Windows you're running. Check your computer's system information
to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program,
and then contact the software publisher.
Failed to install JDK. Exit code=1
ERROR: Failed to prepare Java
jcifs.smb.SmbException: The system cannot find the file specified.
at jcifs.smb.SmbTransport.checkStatus(SmbTransport.java:545)
at jcifs.smb.SmbTransport.send(SmbTransport.java:646)
at jcifs.smb.SmbSession.send(SmbSession.java:244)
at jcifs.smb.SmbTree.send(SmbTree.java:119)
at jcifs.smb.SmbFile.send(SmbFile.java:770)
at jcifs.smb.SmbFile.open0(SmbFile.java:982)
at jcifs.smb.SmbFile.open(SmbFile.java:999)
at jcifs.smb.SmbFileInputStream.init(SmbFileInputStream.java:74)
at jcifs.smb.SmbFileInputStream.init(SmbFileInputStream.java:66)
at jcifs.smb.SmbFile.getInputStream(SmbFile.java:2833)
at
hudson.os.windows.WindowsRemoteFileSystem.read(WindowsRemoteFileSystem.java:41)
at hudson.tools.JDKInstaller.install(JDKInstaller.java:242)
at
hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:251)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
[JIRA] (JENKINS-13745) Valgrind Plugin: Any Configuration of the publish valgrind results part triggers exception
[ https://issues.jenkins-ci.org/browse/JENKINS-13745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Georg Hofmann closed JENKINS-13745. --- I have tested version 0.8 with jenkins 1.464. Configuration and execution is now working fine. Nice plugin, thanks. Valgrind Plugin: Any Configuration of the publish valgrind results part triggers exception Key: JENKINS-13745 URL: https://issues.jenkins-ci.org/browse/JENKINS-13745 Project: Jenkins Issue Type: Bug Components: valgrind Affects Versions: current Environment: Ubuntu 12.04 Jenkins 1.463 Reporter: Georg Hofmann Assignee: Johannes Ohlemacher Labels: exception, plugin Fix For: current Attachments: hudson_valgrind_plugin_excpetion.txt I have tested the Valgrind plugin, but I cannot configure it. The build configuration part is working find, but when I try to configure the publish valgrind results part, I get the exception in the attached file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13793) Build isn't triggered after reboot
Alan Birtles created JENKINS-13793: -- Summary: Build isn't triggered after reboot Key: JENKINS-13793 URL: https://issues.jenkins-ci.org/browse/JENKINS-13793 Project: Jenkins Issue Type: Bug Components: buildresult-trigger Environment: Mac OS X Jenkins 1.463 buildresult-trigger 0.6 Reporter: Alan Birtles Priority: Minor After rebooting jenkins the buildresult-trigger won't trigger a build. In our setup we use the buildresult-trigger to run a nightly test suite only after a build has happened during the day. If the server is rebooted then builds will not be triggered on the first night and will only be triggered on the second night if another build has happened during the second day. The polling log on the first night says that the monitored build didn't exist before. I guess this is because the plugin has no persistance? This means that after installing updates or new plugins our tests wont run for at least a day. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13792) Support for conditional post-build actions
[ https://issues.jenkins-ci.org/browse/JENKINS-13792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162826#comment-162826 ] Carsten Pfeiffer commented on JENKINS-13792: I found out that one can use the [Flexible Publish Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Flexible+Publish+Plugin] to conditionally execute post-build actions, but unfortunately the Perform CVS Tagging action is not available then. Support for conditional post-build actions -- Key: JENKINS-13792 URL: https://issues.jenkins-ci.org/browse/JENKINS-13792 Project: Jenkins Issue Type: Improvement Components: conditional-buildstep Affects Versions: current Reporter: Carsten Pfeiffer Assignee: domi Priority: Minor It would be great if the plugin could also be used for *post*-build actions. Our use case is that we have a parameterized build, and, depending on the input parameters of a build, we would like to tag the workspace, or not. So we would add a run-condition for the Tag post-build action checking whether a specific input parameter was set. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13794) Expose Sauce OnDemand credentials entered into plugin as environment variables
Ross Rowe created JENKINS-13794: --- Summary: Expose Sauce OnDemand credentials entered into plugin as environment variables Key: JENKINS-13794 URL: https://issues.jenkins-ci.org/browse/JENKINS-13794 Project: Jenkins Issue Type: Improvement Components: sauce-ondemand Reporter: Ross Rowe Assignee: Ross Rowe Currently, the Sauce OnDemand Jenkins plugin does not expose the Sauce OnDemand username and api key as environment variables, so tests being invoked using the plugin don't have an easy way of obtaining the credentials. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13795) NPE with Flexible Publisher job
Carsten Pfeiffer created JENKINS-13795:
--
Summary: NPE with Flexible Publisher job
Key: JENKINS-13795
URL: https://issues.jenkins-ci.org/browse/JENKINS-13795
Project: Jenkins
Issue Type: Bug
Components: conditional-buildstep
Affects Versions: current
Reporter: Carsten Pfeiffer
Assignee: domi
Priority: Minor
I created a new job test-conditional that basically did nothing. I added a
Flexible Publish post-build action and added a boolean condition. The
combobox that should show the available actions to execute was empty.
I the log I found the following exception. When leaving and reopening the
configuration page of the job, the list of actions to execute was available.
{code}
SCHWERWIEGEND: Error while serving
http://trend-test:8080/job/test-conditional/configSubmit
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)
at
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488)
at org.kohsuke.stapler.Stapler.service(Stapler.java:162)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
at
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at
hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
at
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at
hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:74)
at
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:331)
at
winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215)
at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.NullPointerException
at
[JIRA] (JENKINS-13796) Expose selected browser/os/version information as environment variables
Ross Rowe created JENKINS-13796: --- Summary: Expose selected browser/os/version information as environment variables Key: JENKINS-13796 URL: https://issues.jenkins-ci.org/browse/JENKINS-13796 Project: Jenkins Issue Type: Improvement Components: sauce-ondemand Reporter: Ross Rowe Assignee: Ross Rowe Currently, the selected browser information is exposed via the SELENIUM_DRIVER and SAUCE_ONDEMAND_BROWSERS variables. If a single browser combination is selected, this information should be exposed via specific environment variables. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13797) Unstable or failure reason is not printed in build summary
Ulli Hafner created JENKINS-13797: - Summary: Unstable or failure reason is not printed in build summary Key: JENKINS-13797 URL: https://issues.jenkins-ci.org/browse/JENKINS-13797 Project: Jenkins Issue Type: Bug Components: warnings Reporter: Ulli Hafner Assignee: Ulli Hafner Priority: Minor The build summary view does not show the reason and status of the plug-in. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13798) Plugin should read System.out of Job to parse Session Ids
Ross Rowe created JENKINS-13798: --- Summary: Plugin should read System.out of Job to parse Session Ids Key: JENKINS-13798 URL: https://issues.jenkins-ci.org/browse/JENKINS-13798 Project: Jenkins Issue Type: Improvement Components: sauce-ondemand Reporter: Ross Rowe Assignee: Ross Rowe Currently, the plugin parses the JUnit output to find Session ID information. The plugin should be updated to also parse the System output of a job, as not all jobs will be producing JUnit reports -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13799) Job name sensitive
David Voillemin created JENKINS-13799: - Summary: Job name sensitive Key: JENKINS-13799 URL: https://issues.jenkins-ci.org/browse/JENKINS-13799 Project: Jenkins Issue Type: Bug Components: nodelabelparameter Affects Versions: current Reporter: David Voillemin Assignee: domi Fix For: current If job name has special characters (like '-', '_', '.', etc), that's does not work! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13800) Subversion Plugin deletes private Maven repository when using Always checkout a fresh copy, Emulate clean checkout by first... or Use svn update... with 'svn revert' before
Sebastien Arod created JENKINS-13800: Summary: Subversion Plugin deletes private Maven repository when using Always checkout a fresh copy, Emulate clean checkout by first... or Use svn update... with 'svn revert' before update Key: JENKINS-13800 URL: https://issues.jenkins-ci.org/browse/JENKINS-13800 Project: Jenkins Issue Type: Bug Components: subversion Affects Versions: current Reporter: Sebastien Arod Priority: Minor Subversion Plugin deletes private Maven repository when using Always checkout a fresh copy, Emulate clean checkout by first... or Use svn update... with 'svn revert' before update as Check-out Strategy. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6450) post-commit hook does no handle svn:externals
[ https://issues.jenkins-ci.org/browse/JENKINS-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162828#comment-162828 ] Deniz Bahadir commented on JENKINS-6450: I can confirm the exact same behavior with Jenkins 1.463 and Subversion plugin 1.39. @Leander Hasty: I would recommend, you vote for this issue to be fixed. (I did.) By doing this the developers might become aware of this bug and that (hopefully) many people want it to be fixed. :-) post-commit hook does no handle svn:externals - Key: JENKINS-6450 URL: https://issues.jenkins-ci.org/browse/JENKINS-6450 Project: Jenkins Issue Type: Bug Components: subversion Affects Versions: current Environment: Windows, Hudson V1.356, Subversion Plug-in V1.17, Poll SCM enabled and left empty Reporter: Axel Heider I've set up a post-commit hook that send a post request with the changed files (http://%HUDSON%/hudson/subversion/%UUID%/notifyCommit?rev=%REV%). It works fine except for changes in directories or files referenced via svn:externals. If something changes there, the project is no rebuild. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13777) Minor spelling errors.
[ https://issues.jenkins-ci.org/browse/JENKINS-13777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mads Nielsen resolved JENKINS-13777. Fix Version/s: current Resolution: Fixed Fixed in 1.0.2 Minor spelling errors. -- Key: JENKINS-13777 URL: https://issues.jenkins-ci.org/browse/JENKINS-13777 Project: Jenkins Issue Type: Bug Components: prqa Affects Versions: current Environment: Windows, Unix Reporter: Mads Nielsen Assignee: Mads Nielsen Priority: Trivial Fix For: current There are a few spelling errors in the plugin. These include that 'atleast' must be in two words. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13778) Icon file with low resolution - needs to be replaced
[ https://issues.jenkins-ci.org/browse/JENKINS-13778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mads Nielsen resolved JENKINS-13778. Fix Version/s: current Resolution: Fixed Fixed in 1.0.2 Icon file with low resolution - needs to be replaced Key: JENKINS-13778 URL: https://issues.jenkins-ci.org/browse/JENKINS-13778 Project: Jenkins Issue Type: Bug Components: prqa Affects Versions: current Reporter: Mads Nielsen Assignee: Mads Nielsen Priority: Trivial Fix For: current The current icon has too low resolution, add a better icon image. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10025) Calling rebuildDependencyGraph() in cycle
[ https://issues.jenkins-ci.org/browse/JENKINS-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162833#comment-162833 ] eguess74 commented on JENKINS-10025: It has become critical as the workaround doesn't work anymore. Jenkins 1.460 same error Calling rebuildDependencyGraph() in cycle - Key: JENKINS-10025 URL: https://issues.jenkins-ci.org/browse/JENKINS-10025 Project: Jenkins Issue Type: Bug Components: ivy Reporter: vjuranek Assignee: Timothy Bingaman There probably possible cycle call of rebuildDependencyGraph(), Ivy calls Hudson.getInstance().rebuildDependencyGraph(); which starts following cycle: getModuleDescriptor() - recomputeModuleDescriptor() - setModuleDescriptor() - hudson.model.Hudson.rebuildDependencyGraph() which results into StackOverflowError, for whole exception, see http://groups.google.com/group/jenkinsci-users/browse_thread/thread/3c6b67b448c98379# -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13761) PRAQ plugin disconnects slaves on Linux when tools aren't installed correctly
[ https://issues.jenkins-ci.org/browse/JENKINS-13761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mads Nielsen resolved JENKINS-13761. Fix Version/s: current Resolution: Fixed Fixed in 1.0.2 PRAQ plugin disconnects slaves on Linux when tools aren't installed correctly - Key: JENKINS-13761 URL: https://issues.jenkins-ci.org/browse/JENKINS-13761 Project: Jenkins Issue Type: Improvement Components: prqa Environment: Linux (Seen and reproduced on Fedora 16 - 64bit) - but probably affects all Linux version Reporter: Lars Kruse Assignee: Lars Kruse Labels: Praqma Fix For: current This issue is reported during beta test (on version PRQA plugin version 1.0.1), and reported by the tester like this: Quote begin We have done some tests on Linux - using the plugin causes Jenkins to crash! We don't quite understand this - there was no information in the build log files. However, we were able to run the command to analyse and generate the report as a normal build step as a shell command. We used exactly the same command as the for Windows: - Obviously we used forward slashes in the path to the project - I was wrong about qaw being called qaw.pl - it is called qaw on Linux - qar is called qar.pl on Linux - but we added a symbolic link 'qar-qar.pl' in the qar binary directory. This seems the easiest solution (and perhaps we might include this link in future versions of war) quote end -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10025) Calling rebuildDependencyGraph() in cycle
[ https://issues.jenkins-ci.org/browse/JENKINS-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eguess74 updated JENKINS-10025: --- Priority: Blocker (was: Major) Calling rebuildDependencyGraph() in cycle - Key: JENKINS-10025 URL: https://issues.jenkins-ci.org/browse/JENKINS-10025 Project: Jenkins Issue Type: Bug Components: ivy Reporter: vjuranek Assignee: Timothy Bingaman Priority: Blocker There probably possible cycle call of rebuildDependencyGraph(), Ivy calls Hudson.getInstance().rebuildDependencyGraph(); which starts following cycle: getModuleDescriptor() - recomputeModuleDescriptor() - setModuleDescriptor() - hudson.model.Hudson.rebuildDependencyGraph() which results into StackOverflowError, for whole exception, see http://groups.google.com/group/jenkinsci-users/browse_thread/thread/3c6b67b448c98379# -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6450) post-commit hook does no handle svn:externals
[ https://issues.jenkins-ci.org/browse/JENKINS-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162834#comment-162834 ] Leander Hasty commented on JENKINS-6450: Odd, I thought I had. Vote placed. At the moment we had to revert to polling every so hour or so to supplement the push notifications, and that's still less than ideal. Since a patch might make this all go faster, I'll see what I can put together, but no promises -- the studio is quite busy at the moment. post-commit hook does no handle svn:externals - Key: JENKINS-6450 URL: https://issues.jenkins-ci.org/browse/JENKINS-6450 Project: Jenkins Issue Type: Bug Components: subversion Affects Versions: current Environment: Windows, Hudson V1.356, Subversion Plug-in V1.17, Poll SCM enabled and left empty Reporter: Axel Heider I've set up a post-commit hook that send a post request with the changed files (http://%HUDSON%/hudson/subversion/%UUID%/notifyCommit?rev=%REV%). It works fine except for changes in directories or files referenced via svn:externals. If something changes there, the project is no rebuild. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13801) Allow label/node passthrough for job chaining
Costin Caraivan created JENKINS-13801: - Summary: Allow label/node passthrough for job chaining Key: JENKINS-13801 URL: https://issues.jenkins-ci.org/browse/JENKINS-13801 Project: Jenkins Issue Type: Improvement Components: nodelabelparameter Affects Versions: current Environment: Ubuntu 12.04 64 bit, Java 6 64 bit Reporter: Costin Caraivan Assignee: domi We have a setup with several levels of job chaining. We would like to have some completely configurable jobs: parameters, nodes on which they are launched, etc. The Node Label Parameter plugins gets us very close to this but it has 1 downside, when chaining jobs. Currently it is not possible to have a top level job with a string parameter (for example) containing the label on which to execute the downstream projects. We would like to have an orchestrator job which would set the label on which to execute the downstream jobs. This label would then be passed downstream. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13802) Downstream promotion should be prohibited/impossible when upstream promotion is outstanding
Thomas Lehmann created JENKINS-13802: Summary: Downstream promotion should be prohibited/impossible when upstream promotion is outstanding Key: JENKINS-13802 URL: https://issues.jenkins-ci.org/browse/JENKINS-13802 Project: Jenkins Issue Type: Improvement Components: promoted-builds Environment: Fedora 15 OpenJDK 1.6.0_22 on x86-64 + Jenkins 1.462 + Promoted Builds Plugin 2.5 Reporter: Thomas Lehmann The view where one can click Approve should disable the button as long as the upstream promotion is not successful done. Situation: I have three promotions configured which should only happen in this order: Deploy to Staging (refered as A) - QA OK (refered as B) - Deploy to live (refered as C) Obviously the QA should not be able to mark the build OK before it has been deployed. The Promotions are configured with these upstream criterias: - A: manual - B: manual, when A is promoted - C: manual, when B is promoted Current: B can be approved even if A has never been approved. Same for C vs. B or A. Desired: B's Approve should be disabled until A is successful approved. Same for C vs. B or A -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13611) Misleading error leads to slave disconnecting from master
[ https://issues.jenkins-ci.org/browse/JENKINS-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162835#comment-162835 ] Julian Requejo commented on JENKINS-13611: -- I can confirm that with version 1.0.2, the issue has been solved. Thanks very much for the quick response time Misleading error leads to slave disconnecting from master - Key: JENKINS-13611 URL: https://issues.jenkins-ci.org/browse/JENKINS-13611 Project: Jenkins Issue Type: Bug Components: prqa Affects Versions: current Environment: Jenkins 1.441, Windows 7, QAC-7.2F Reporter: Julian Requejo Assignee: Mads Nielsen I'm having some issues running the PQRA Plugin. The [documentation|https://wiki.jenkins-ci.org/display/JENKINS/PRQA+Plugin] is a bit strange. To start with, the screenshot shows a report type quality, even though it says that currently only compliance is available. Then it also says that a tool qaw must be installed, which I don't have anywhere in my installation files. In any case, here is the problem: the plugin seems to not find this qaw tool, and it produces an error that disconnects my slave agent from the master. Started by user X X, xx.xx...@xxx.xx Building remotely on Legoland Updating https://xxx/ At revision 1292 Updating https://xxx/ At revision 1292 Updating https://xxx/ At revision 1292 no change for Updating https://xxx/ since the previous build no change for Updating https://xxx/ since the previous build no change for Updating https://xxx/ since the previous build This job will try to create a report with the following selected parameters: QAR selected project file:Sources//QAC.prj QAR selected product: QAC QAR selected report type: Compliance Beginning report generation with the following command: qaw QAC Sources//QAC.prj -maseq qar %Q %P+ %L+ -po qar::report_type=Compliance\ Report -po qar::project_name=%J -po qar::output_path=c:\_dev\jenkins-int\workspace\x\ QAC -po qar::viewing_program=dummy -po qar::report_format=xhtml ERROR: Publisher net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier aborted due to exception hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.Request.call(Request.java:149) at hudson.remoting.Channel.call(Channel.java:681) at hudson.FilePath.act(FilePath.java:772) at hudson.FilePath.act(FilePath.java:765) at net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier.perform(PRQANotifier.java:203) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:667) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:645) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:614) at hudson.model.Run.run(Run.java:1429) 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: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.Request.abort(Request.java:273) at hudson.remoting.Channel.terminate(Channel.java:732) at hudson.remoting.Channel$ReaderThread.run(Channel.java:1139) Caused by: java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:168) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2249) at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2542) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2552) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1297) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at hudson.remoting.Channel$ReaderThread.run(Channel.java:1109) Notifying upstream projects of job completion Finished: FAILURE After this, my slave gets disconnected from the master. So my questions: - Where do I find this qaw tool? It is
[JIRA] (JENKINS-13611) Misleading error leads to slave disconnecting from master
[ https://issues.jenkins-ci.org/browse/JENKINS-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Requejo resolved JENKINS-13611. -- Resolution: Fixed Misleading error leads to slave disconnecting from master - Key: JENKINS-13611 URL: https://issues.jenkins-ci.org/browse/JENKINS-13611 Project: Jenkins Issue Type: Bug Components: prqa Affects Versions: current Environment: Jenkins 1.441, Windows 7, QAC-7.2F Reporter: Julian Requejo Assignee: Mads Nielsen I'm having some issues running the PQRA Plugin. The [documentation|https://wiki.jenkins-ci.org/display/JENKINS/PRQA+Plugin] is a bit strange. To start with, the screenshot shows a report type quality, even though it says that currently only compliance is available. Then it also says that a tool qaw must be installed, which I don't have anywhere in my installation files. In any case, here is the problem: the plugin seems to not find this qaw tool, and it produces an error that disconnects my slave agent from the master. Started by user X X, xx.xx...@xxx.xx Building remotely on Legoland Updating https://xxx/ At revision 1292 Updating https://xxx/ At revision 1292 Updating https://xxx/ At revision 1292 no change for Updating https://xxx/ since the previous build no change for Updating https://xxx/ since the previous build no change for Updating https://xxx/ since the previous build This job will try to create a report with the following selected parameters: QAR selected project file:Sources//QAC.prj QAR selected product: QAC QAR selected report type: Compliance Beginning report generation with the following command: qaw QAC Sources//QAC.prj -maseq qar %Q %P+ %L+ -po qar::report_type=Compliance\ Report -po qar::project_name=%J -po qar::output_path=c:\_dev\jenkins-int\workspace\x\ QAC -po qar::viewing_program=dummy -po qar::report_format=xhtml ERROR: Publisher net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier aborted due to exception hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.Request.call(Request.java:149) at hudson.remoting.Channel.call(Channel.java:681) at hudson.FilePath.act(FilePath.java:772) at hudson.FilePath.act(FilePath.java:765) at net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier.perform(PRQANotifier.java:203) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:667) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:645) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:614) at hudson.model.Run.run(Run.java:1429) 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: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.Request.abort(Request.java:273) at hudson.remoting.Channel.terminate(Channel.java:732) at hudson.remoting.Channel$ReaderThread.run(Channel.java:1139) Caused by: java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:168) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2249) at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2542) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2552) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1297) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at hudson.remoting.Channel$ReaderThread.run(Channel.java:1109) Notifying upstream projects of job completion Finished: FAILURE After this, my slave gets disconnected from the master. So my questions: - Where do I find this qaw tool? It is not installed with QAC-7.2F - Why does the absence of such tool end up in such a brutal way? Thanks -- This message is automatically generated by
[JIRA] (JENKINS-13611) Misleading error leads to slave disconnecting from master
[ https://issues.jenkins-ci.org/browse/JENKINS-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Requejo closed JENKINS-13611. Misleading error leads to slave disconnecting from master - Key: JENKINS-13611 URL: https://issues.jenkins-ci.org/browse/JENKINS-13611 Project: Jenkins Issue Type: Bug Components: prqa Affects Versions: current Environment: Jenkins 1.441, Windows 7, QAC-7.2F Reporter: Julian Requejo Assignee: Mads Nielsen I'm having some issues running the PQRA Plugin. The [documentation|https://wiki.jenkins-ci.org/display/JENKINS/PRQA+Plugin] is a bit strange. To start with, the screenshot shows a report type quality, even though it says that currently only compliance is available. Then it also says that a tool qaw must be installed, which I don't have anywhere in my installation files. In any case, here is the problem: the plugin seems to not find this qaw tool, and it produces an error that disconnects my slave agent from the master. Started by user X X, xx.xx...@xxx.xx Building remotely on Legoland Updating https://xxx/ At revision 1292 Updating https://xxx/ At revision 1292 Updating https://xxx/ At revision 1292 no change for Updating https://xxx/ since the previous build no change for Updating https://xxx/ since the previous build no change for Updating https://xxx/ since the previous build This job will try to create a report with the following selected parameters: QAR selected project file:Sources//QAC.prj QAR selected product: QAC QAR selected report type: Compliance Beginning report generation with the following command: qaw QAC Sources//QAC.prj -maseq qar %Q %P+ %L+ -po qar::report_type=Compliance\ Report -po qar::project_name=%J -po qar::output_path=c:\_dev\jenkins-int\workspace\x\ QAC -po qar::viewing_program=dummy -po qar::report_format=xhtml ERROR: Publisher net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier aborted due to exception hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.Request.call(Request.java:149) at hudson.remoting.Channel.call(Channel.java:681) at hudson.FilePath.act(FilePath.java:772) at hudson.FilePath.act(FilePath.java:765) at net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier.perform(PRQANotifier.java:203) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:667) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:645) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:614) at hudson.model.Run.run(Run.java:1429) 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: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.Request.abort(Request.java:273) at hudson.remoting.Channel.terminate(Channel.java:732) at hudson.remoting.Channel$ReaderThread.run(Channel.java:1139) Caused by: java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:168) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2249) at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2542) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2552) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1297) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at hudson.remoting.Channel$ReaderThread.run(Channel.java:1109) Notifying upstream projects of job completion Finished: FAILURE After this, my slave gets disconnected from the master. So my questions: - Where do I find this qaw tool? It is not installed with QAC-7.2F - Why does the absence of such tool end up in such a brutal way? Thanks -- This message is automatically generated by JIRA. If you think it was
[JIRA] (JENKINS-13803) PRQA Plugin fails during the publishing phase with NULL pointer exception
Julian Requejo created JENKINS-13803:
Summary: PRQA Plugin fails during the publishing phase with NULL
pointer exception
Key: JENKINS-13803
URL: https://issues.jenkins-ci.org/browse/JENKINS-13803
Project: Jenkins
Issue Type: Bug
Components: prqa
Environment: Master: linux
Slave: Windows 7
Jenkins 1.441
Reporter: Julian Requejo
Assignee: Lars Kruse
PRQA plugin generates reports correctly, but fails during publishing phase.
{noformat}
At revision 1572
no change for https://xx/xx since the previous build
This job will create a report with the following selected parameters:
QAR selected project file: Sources\QAC\xx\xx.prj
QAR selected product: QAC
QAR selected report type: Compliance
Beginning report generation with the following command:
qaw QAC Sources\QAC\xx\xx.prj -maseq qar %Q %P+ %L+ -po
qar::report_type=Compliance\ Report -po qar::project_name=%J -po
qar::output_path=c:\_dev\jenkins-int\workspace\xx_QAC -po
qar::viewing_program=dummy -po qar::report_format=xhtml
Viewer dummy not available, result will not be rendered.
Generating - Please wait...
Writing c:\_dev\jenkins-int\workspace\xx_QAC\Compliance Report.xml
Writing c:\_dev\jenkins-int\workspace\xx_QAC\Compliance Report.xhtml
Writing c:\_dev\jenkins-int\workspace\xx_QAC\Compliance Report-Main.xhtml
Finished remote reporting.
Found report. Attempting to copy Compliance Report.xhtml to artifacts
directory: /home/xx/.jenkins/jobs/xx_QAC/builds/2012-05-16_17-11-12/archive
Attempting to copy report to following target: Compliance Report.xhtml
Succesfully copied report
ERROR: Publisher net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier aborted
due to exception
java.lang.NullPointerException
at
net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier.perform(PRQANotifier.java:240)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:667)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:645)
at hudson.model.Build$RunnerImpl.post2(Build.java:162)
at
hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:614)
at hudson.model.Run.run(Run.java:1429)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)
Notifying upstream projects of job completion
Finished: FAILURE
{noformat}
I have tested this using three configurations, all with Jenkins 1.441
- Single Jenkins web app running on my local machine (Windows 7): it works
- Master-slave configuration, *both* on my local machine (Windows 7), slave as
a user process: it works
- Master-slave configuration, master on a Linux box, slave on my local Windows
7 machine (Windows 7), slave as a user process: it does *not* work and triggers
the error above.
I could try upgrading to a newer Jenkins, but I'd strongly prefer not to unless
shown to be essential.
I'll be happy to provide further logs. Thanks
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13804) radioBlocks contained in repeatable are not shown correctly anymore / affects plot plugin
Jens Schiebel created JENKINS-13804: --- Summary: radioBlocks contained in repeatable are not shown correctly anymore / affects plot plugin Key: JENKINS-13804 URL: https://issues.jenkins-ci.org/browse/JENKINS-13804 Project: Jenkins Issue Type: Bug Components: plot, plugin Affects Versions: current Reporter: Jens Schiebel Assignee: nidaley Attachments: radioBlock-fail.png When activating the plot plugin in a jenkins job configuration and adding 2 or more data series files and saving this job configuration and then going back into the config page, only the last data series file radioblock field will be shown correctly, all the others will not show the input fields on the selected radio buttons... This bug appears whenever you use radioblocks inside a repeatable structure. Jenkins 1.411 + Plot Plugin 1.5 work well and don't show this bug. Jenkins 1.464 + Plot Plugin 1.5 do show this bug. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13737) Javascript error when selecting Editable Email Notification
[ https://issues.jenkins-ci.org/browse/JENKINS-13737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162836#comment-162836 ] Kelly Schoenhofen commented on JENKINS-13737: - Let us know when you have something, we're affected by the same issue. What is the xml so we can manually enable this in a job's config file? Javascript error when selecting Editable Email Notification - Key: JENKINS-13737 URL: https://issues.jenkins-ci.org/browse/JENKINS-13737 Project: Jenkins Issue Type: Bug Components: email-ext Affects Versions: current Environment: Windows, IE8, Jenkins 1.463, Jenkins Email Extension Plugin 2.20 Reporter: Noel Bernardez Assignee: Slide-O-Mix Labels: email-ext, jenkins In Jenkins ver. 1.463, when selecting Editable Email Notification in the Add post-build action, getting the following Javascript error Message: 'emailExtInit' is undefined Line: 480 Char: 17 Code: 0 URI: http://myserver:8080/static/f11a6618/scripts/hudson-behavior.js -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13787) Error when job is running on slave
[ https://issues.jenkins-ci.org/browse/JENKINS-13787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Kruse resolved JENKINS-13787. -- Resolution: Duplicate Duplicate of https://issues.jenkins-ci.org/browse/JENKINS-13803 Error when job is running on slave -- Key: JENKINS-13787 URL: https://issues.jenkins-ci.org/browse/JENKINS-13787 Project: Jenkins Issue Type: Bug Components: prqa Reporter: Lars Kruse Assignee: Lars Kruse Labels: Praqma If I set up the PRQA plugin on a Jenkins running on my machine (just install the official 1.441 war file and start it via java -jar jenkins.war, everything works fine. Now if I setup my machine to run as a slave and let the job be triggered by the master somewhere else (also version 1.441), I get the following error: This job will try to create a report with the following selected parameters: QAR selected project file:Sources\QAC\LibFusion\LibFusion.prj QAR selected product: QAC QAR selected report type: Compliance Beginning report generation with the following command: qaw QAC Sources\QAC\LibFusion\LibFusion.prj -maseq qar %Q %P+ %L+ -po qar::report_type=Compliance\ Report -po qar::project_name=%J -po qar::output_path=c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC -po qar::viewing_program=dummy -po qar::report_format=xhtml Viewer dummy not available, result will not be rendered. Generating - Please wait... Writing c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC\Compliance Report.xml Writing c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC\Compliance Report.xhtml Writing c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC\Compliance Report-Main.xhtml Finished remote reporting. Found report. Attempting to copy Compliance Report.xhtml to artifacts directory: /home/qqmthk1/.jenkins/jobs/OFRF_LibFusion_QAC/builds/2012-05-11_17-32-05/archive Attempting to copy report to following target: Compliance Report.xhtml Succesfully copied report ERROR: Publisher net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier aborted due to exception java.lang.NullPointerException at net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier.perform(PRQANotifier.java:240) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:667) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:645) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:614) at hudson.model.Run.run(Run.java:1429) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Notifying upstream projects of job completion Finished: FAILURE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13789) 'cvs update' replaces the Tag file which has the branch name in it with a Tag with time and date which effectively corresponds back to the Head
[ https://issues.jenkins-ci.org/browse/JENKINS-13789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162838#comment-162838 ] Amir Isfy commented on JENKINS-13789: - Downgraded to version 2.0 and this problem is still there. 'cvs update' replaces the Tag file which has the branch name in it with a Tag with time and date which effectively corresponds back to the Head --- Key: JENKINS-13789 URL: https://issues.jenkins-ci.org/browse/JENKINS-13789 Project: Jenkins Issue Type: Bug Components: cvs, cvs-tag Reporter: Amir Isfy I am building a Module that comes from a CVS branch. 'cvs checkout' correctly keeps the branch name in the Tag file. Now after a clean checkout if the 'Use Update' is checked under 'Source Code Management' then the command looks like: cvs update -d -P -r branch_name -D 15 May 2012 13:12:24 -0600 module_name After this the Tag file will have 'D2012.05.15.19.12.24' in it which basically corresponds to the Head now. This could be related to this. Help please. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13803) PRQA Plugin fails during the publishing phase with NULL pointer exception
[
https://issues.jenkins-ci.org/browse/JENKINS-13803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162839#comment-162839
]
Lars Kruse commented on JENKINS-13803:
--
Hi Julian
We actually got this error report from you via Jason, PRQA. I filed it as
https://issues.jenkins-ci.org/browse/JENKINS-13787 but I will close that as a
duplicate.
We tried to get this fix into 1.0.2 as well but we could not reproduce it in
our lab. Even when the master was on Linux and the slave was on windows -
started with the java web start (which essentially is a user process).
Hmmm - I'm not suspecting the 1.441 version to really be the issue.
Actually the stack trace you have given us is helpful, But I believe in this
case, we would welcome any relevant logs you can produce.
Please attach them to a mail and send them to supp...@praqma.net.
Cheers
PRQA Plugin fails during the publishing phase with NULL pointer exception
-
Key: JENKINS-13803
URL: https://issues.jenkins-ci.org/browse/JENKINS-13803
Project: Jenkins
Issue Type: Bug
Components: prqa
Environment: Master: linux
Slave: Windows 7
Jenkins 1.441
Reporter: Julian Requejo
Assignee: Lars Kruse
PRQA plugin generates reports correctly, but fails during publishing phase.
{noformat}
At revision 1572
no change for https://xx/xx since the previous build
This job will create a report with the following selected parameters:
QAR selected project file:Sources\QAC\xx\xx.prj
QAR selected product: QAC
QAR selected report type: Compliance
Beginning report generation with the following command:
qaw QAC Sources\QAC\xx\xx.prj -maseq qar %Q %P+ %L+ -po
qar::report_type=Compliance\ Report -po qar::project_name=%J -po
qar::output_path=c:\_dev\jenkins-int\workspace\xx_QAC -po
qar::viewing_program=dummy -po qar::report_format=xhtml
Viewer dummy not available, result will not be rendered.
Generating - Please wait...
Writing c:\_dev\jenkins-int\workspace\xx_QAC\Compliance Report.xml
Writing c:\_dev\jenkins-int\workspace\xx_QAC\Compliance Report.xhtml
Writing c:\_dev\jenkins-int\workspace\xx_QAC\Compliance Report-Main.xhtml
Finished remote reporting.
Found report. Attempting to copy Compliance Report.xhtml to artifacts
directory: /home/xx/.jenkins/jobs/xx_QAC/builds/2012-05-16_17-11-12/archive
Attempting to copy report to following target: Compliance Report.xhtml
Succesfully copied report
ERROR: Publisher net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier aborted
due to exception
java.lang.NullPointerException
at
net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier.perform(PRQANotifier.java:240)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:667)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:645)
at hudson.model.Build$RunnerImpl.post2(Build.java:162)
at
hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:614)
at hudson.model.Run.run(Run.java:1429)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)
Notifying upstream projects of job completion
Finished: FAILURE
{noformat}
I have tested this using three configurations, all with Jenkins 1.441
- Single Jenkins web app running on my local machine (Windows 7): it works
- Master-slave configuration, *both* on my local machine (Windows 7), slave
as a user process: it works
- Master-slave configuration, master on a Linux box, slave on my local
Windows 7 machine (Windows 7), slave as a user process: it does *not* work
and triggers the error above.
I could try upgrading to a newer Jenkins, but I'd strongly prefer not to
unless shown to be essential.
I'll be happy to provide further logs. Thanks
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13787) Error when job is running on slave
[ https://issues.jenkins-ci.org/browse/JENKINS-13787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Kruse updated JENKINS-13787: - Description: If I set up the PRQA plugin on a Jenkins running on my machine (just install the official 1.441 war file and start it via java -jar jenkins.war, everything works fine. Now if I setup my machine to run as a slave and let the job be triggered by the master somewhere else (also version 1.441), I get the following error: This job will try to create a report with the following selected parameters: QAR selected project file:Sources\QAC\LibFusion\LibFusion.prj QAR selected product: QAC QAR selected report type: Compliance Beginning report generation with the following command: qaw QAC Sources\QAC\xx\yy.prj -maseq qar %Q %P+ %L+ -po qar::report_type=Compliance\ Report -po qar::project_name=%J -po qar::output_path=c:\_dev\jenkins-int\workspace\xx_QAC -po qar::viewing_program=dummy -po qar::report_format=xhtml Viewer dummy not available, result will not be rendered. Generating - Please wait... Writing c:\_dev\jenkins-int\workspace\xx_QAC\Compliance Report.xml Writing c:\_dev\jenkins-int\workspace\xx_QAC\Compliance Report.xhtml Writing c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC\Compliance Report-Main.xhtml Finished remote reporting. Found report. Attempting to copy Compliance Report.xhtml to artifacts directory: /home/qqmthk1/.jenkins/jobs/xx_QAC/builds/2012-05-11_17-32-05/archive Attempting to copy report to following target: Compliance Report.xhtml Succesfully copied report ERROR: Publisher net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier aborted due to exception java.lang.NullPointerException at net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier.perform(PRQANotifier.java:240) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:667) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:645) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:614) at hudson.model.Run.run(Run.java:1429) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Notifying upstream projects of job completion Finished: FAILURE was: If I set up the PRQA plugin on a Jenkins running on my machine (just install the official 1.441 war file and start it via java -jar jenkins.war, everything works fine. Now if I setup my machine to run as a slave and let the job be triggered by the master somewhere else (also version 1.441), I get the following error: This job will try to create a report with the following selected parameters: QAR selected project file:Sources\QAC\LibFusion\LibFusion.prj QAR selected product: QAC QAR selected report type: Compliance Beginning report generation with the following command: qaw QAC Sources\QAC\LibFusion\LibFusion.prj -maseq qar %Q %P+ %L+ -po qar::report_type=Compliance\ Report -po qar::project_name=%J -po qar::output_path=c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC -po qar::viewing_program=dummy -po qar::report_format=xhtml Viewer dummy not available, result will not be rendered. Generating - Please wait... Writing c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC\Compliance Report.xml Writing c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC\Compliance Report.xhtml Writing c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC\Compliance Report-Main.xhtml Finished remote reporting. Found report. Attempting to copy Compliance Report.xhtml to artifacts directory: /home/qqmthk1/.jenkins/jobs/OFRF_LibFusion_QAC/builds/2012-05-11_17-32-05/archive Attempting to copy report to following target: Compliance Report.xhtml Succesfully copied report ERROR: Publisher net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier aborted due to exception java.lang.NullPointerException at net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier.perform(PRQANotifier.java:240) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:667) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:645) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:614) at hudson.model.Run.run(Run.java:1429) at
[JIRA] (JENKINS-13114) dropdown views taskbar: error when saving jenkins config page
[
https://issues.jenkins-ci.org/browse/JENKINS-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162840#comment-162840
]
Steve Roth commented on JENKINS-13114:
--
This is preventing our sites (which have many views) from upgrading to a
Jenkins version newer than 1.454. I presume others with many views may be in
the same situation.
dropdown views taskbar: error when saving jenkins config page
-
Key: JENKINS-13114
URL: https://issues.jenkins-ci.org/browse/JENKINS-13114
Project: Jenkins
Issue Type: Bug
Components: dropdown-viewstabbar
Affects Versions: current
Reporter: Steve Roth
Assignee: jieryn
I have the dropdown views tabbar enabled, and am usign Jenkins 1.455 When I
go to save the main Jenkins config page, I see this CNF exception in the
browser:
exception
javax.servlet.ServletException: java.lang.IllegalArgumentException: Failed to
instantiate class hudson.views.ViewsTabBar from
{showJobCount:false,stapler-class:[hudson.views.DefaultViewsTabBar,hudson.views.tabbar.DropDownViewsTabBar]}
org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:605)
org.kohsuke.stapler.Stapler.invoke(Stapler.java:648)
org.kohsuke.stapler.Stapler.invoke(Stapler.java:477)
org.kohsuke.stapler.Stapler.service(Stapler.java:159)
javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:185)
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:159)
net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
oracle.boulderlabs.jenkins.validatorkiller.ValidatorKiller.doFilter(ValidatorKiller.java:63)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:61)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
root cause
java.lang.IllegalArgumentException: Failed to instantiate class
hudson.views.ViewsTabBar from
{showJobCount:false,stapler-class:[hudson.views.DefaultViewsTabBar,hudson.views.tabbar.DropDownViewsTabBar]}
org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:633)
org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:377)
[JIRA] (JENKINS-13805) email-ext plugin cannot see env variables set as part of build config
kalpesh soni created JENKINS-13805:
--
Summary: email-ext plugin cannot see env variables set as part of
build config
Key: JENKINS-13805
URL: https://issues.jenkins-ci.org/browse/JENKINS-13805
Project: Jenkins
Issue Type: Bug
Components: email-ext
Environment: 2.18
Reporter: kalpesh soni
I have tried to use env variable DEFAULT_RECIPIENTS as part of build, and not
as part of global env variables
I need DEFAULT_RECIPIENTS value to be different for each job
I try to set it as part of build step
but the value is NOT available when email ext tries to send email
I get
===
{
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
Sending email to: $team.acids
ERROR: Could not send email as a part of the post-build publishers.
com.sun.mail.smtp.SMTPSendFailedException: 250 2.6.0
26943585.5.1337190669479.JavaMail.CAUDSWAP41$@CAUDSWAP41 Queued mail for
delivery
;
nested exception is:
com.sun.mail.smtp.SMTPAddressFailedException: 550 5.1.1 User unknown
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1112)
at javax.mail.Transport.send0(Transport.java:195)
at javax.mail.Transport.send(Transport.java:124)
at
hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:263)
at
hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:247)
at
hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:207)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
at
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:678)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:656)
at hudson.model.Build$RunnerImpl.cleanUp(Build.java:171)
at hudson.model.Run.run(Run.java:1454)
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: com.sun.mail.smtp.SMTPAddressFailedException: 550 5.1.1 User unknown
at com.sun.mail.smtp.SMTPTransport.rcptTo(SMTPTransport.java:1686)
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1098)
... 14 more
Notifying upstream projects of job completion
Finished: SUCCESS
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13805) email-ext plugin cannot see env variables set as part of build config
[
https://issues.jenkins-ci.org/browse/JENKINS-13805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kalpesh soni updated JENKINS-13805:
---
Description:
I have tried to use env variable DEFAULT_RECIPIENTS as part of build, and not
as part of global env variables
I need DEFAULT_RECIPIENTS value to be different for each job
I try to set it as part of build step
but the value is NOT available when email ext tries to send email
I get
===
{quote}
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
Sending email to: $team.acids
ERROR: Could not send email as a part of the post-build publishers.
com.sun.mail.smtp.SMTPSendFailedException: 250 2.6.0
26943585.5.1337190669479.JavaMail.CAUDSWAP41$@CAUDSWAP41 Queued mail for
delivery
;
nested exception is:
com.sun.mail.smtp.SMTPAddressFailedException: 550 5.1.1 User unknown
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1112)
at javax.mail.Transport.send0(Transport.java:195)
at javax.mail.Transport.send(Transport.java:124)
at
hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:263)
at
hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:247)
at
hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:207)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
at
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:678)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:656)
at hudson.model.Build$RunnerImpl.cleanUp(Build.java:171)
at hudson.model.Run.run(Run.java:1454)
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: com.sun.mail.smtp.SMTPAddressFailedException: 550 5.1.1 User unknown
at com.sun.mail.smtp.SMTPTransport.rcptTo(SMTPTransport.java:1686)
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1098)
... 14 more
Notifying upstream projects of job completion
Finished: SUCCESS
{quote}
was:
I have tried to use env variable DEFAULT_RECIPIENTS as part of build, and not
as part of global env variables
I need DEFAULT_RECIPIENTS value to be different for each job
I try to set it as part of build step
but the value is NOT available when email ext tries to send email
I get
===
{
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
Sending email to: $team.acids
ERROR: Could not send email as a part of the post-build publishers.
com.sun.mail.smtp.SMTPSendFailedException: 250 2.6.0
26943585.5.1337190669479.JavaMail.CAUDSWAP41$@CAUDSWAP41 Queued mail for
delivery
;
nested exception is:
com.sun.mail.smtp.SMTPAddressFailedException: 550 5.1.1 User unknown
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1112)
at javax.mail.Transport.send0(Transport.java:195)
at javax.mail.Transport.send(Transport.java:124)
at
hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:263)
at
hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:247)
at
hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:207)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
at
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:678)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:656)
at hudson.model.Build$RunnerImpl.cleanUp(Build.java:171)
at hudson.model.Run.run(Run.java:1454)
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: com.sun.mail.smtp.SMTPAddressFailedException: 550 5.1.1 User unknown
at com.sun.mail.smtp.SMTPTransport.rcptTo(SMTPTransport.java:1686)
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1098)
... 14 more
Notifying upstream projects of job completion
Finished: SUCCESS
}
email-ext plugin cannot see env variables set as part of build config
-
Key: JENKINS-13805
URL: https://issues.jenkins-ci.org/browse/JENKINS-13805
Project: Jenkins
Issue Type: Bug
[JIRA] (JENKINS-13114) dropdown views taskbar: error when saving jenkins config page
[
https://issues.jenkins-ci.org/browse/JENKINS-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162842#comment-162842
]
Jim Searle commented on JENKINS-13114:
--
Yes, we had the same issue, but discovered that it works in Internet Explorer...
dropdown views taskbar: error when saving jenkins config page
-
Key: JENKINS-13114
URL: https://issues.jenkins-ci.org/browse/JENKINS-13114
Project: Jenkins
Issue Type: Bug
Components: dropdown-viewstabbar
Affects Versions: current
Reporter: Steve Roth
Assignee: jieryn
I have the dropdown views tabbar enabled, and am usign Jenkins 1.455 When I
go to save the main Jenkins config page, I see this CNF exception in the
browser:
exception
javax.servlet.ServletException: java.lang.IllegalArgumentException: Failed to
instantiate class hudson.views.ViewsTabBar from
{showJobCount:false,stapler-class:[hudson.views.DefaultViewsTabBar,hudson.views.tabbar.DropDownViewsTabBar]}
org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:605)
org.kohsuke.stapler.Stapler.invoke(Stapler.java:648)
org.kohsuke.stapler.Stapler.invoke(Stapler.java:477)
org.kohsuke.stapler.Stapler.service(Stapler.java:159)
javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:185)
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:159)
net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
oracle.boulderlabs.jenkins.validatorkiller.ValidatorKiller.doFilter(ValidatorKiller.java:63)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:61)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
root cause
java.lang.IllegalArgumentException: Failed to instantiate class
hudson.views.ViewsTabBar from
{showJobCount:false,stapler-class:[hudson.views.DefaultViewsTabBar,hudson.views.tabbar.DropDownViewsTabBar]}
org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:633)
org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:377)
org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:373)
[JIRA] (JENKINS-13222) Allow job selection with fixed job names to contain variables without requiring job permissions for authenticated users
[
https://issues.jenkins-ci.org/browse/JENKINS-13222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Beck updated JENKINS-13222:
--
Attachment: fix.diff
Something like the attached patch might work for this. I've been using a
patched 1.21 or so for a while successfully.
Allow job selection with fixed job names to contain variables without
requiring job permissions for authenticated users
---
Key: JENKINS-13222
URL: https://issues.jenkins-ci.org/browse/JENKINS-13222
Project: Jenkins
Issue Type: Improvement
Components: copyartifact
Environment: Any
Reporter: Daniel Beck
Assignee: Alan Harder
Labels: artifact, parameter, permissions
Attachments: fix.diff
Copy Artifacts plugin prevents copying from jobs when the job specifier
(project name) changes by evaluating variables contained in it.
This should be changed to check whether the job name part of the expression
is fixed, and only the filter dynamic, thereby making it possible to e.g.
select a build with a same parameter as the current build
({{SourceJob/param=$param}}) without requiring permission on that project for
all authenticated users.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13789) 'cvs update' replaces the Tag file which has the branch name in it with a Tag with time and date which effectively corresponds back to the Head
[ https://issues.jenkins-ci.org/browse/JENKINS-13789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amir Isfy updated JENKINS-13789: Component/s: (was: cvs-tag) 'cvs update' replaces the Tag file which has the branch name in it with a Tag with time and date which effectively corresponds back to the Head --- Key: JENKINS-13789 URL: https://issues.jenkins-ci.org/browse/JENKINS-13789 Project: Jenkins Issue Type: Bug Components: cvs Reporter: Amir Isfy I am building a Module that comes from a CVS branch. 'cvs checkout' correctly keeps the branch name in the Tag file. Now after a clean checkout if the 'Use Update' is checked under 'Source Code Management' then the command looks like: cvs update -d -P -r branch_name -D 15 May 2012 13:12:24 -0600 module_name After this the Tag file will have 'D2012.05.15.19.12.24' in it which basically corresponds to the Head now. This could be related to this. Help please. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10313) Fails to copy artifacts from one multi-configuration build to another
[
https://issues.jenkins-ci.org/browse/JENKINS-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Murrell reopened JENKINS-10313:
-
How can this be Resolved/Not A Defect? I'm going to Reopen for further
discussion.
Requiring any project that will be the source of a Copy Artifacts action to
have to be readable even by all authenticated users eliminates any use one can
get out of individual or group ACLs and reduces the effective security model to
only two groups of people, authenticated and non-authenticated.
i.e. I cannot create a project that is readable by only some authenticated
users.
The solution, it seems to me (a layperson in terms of any knowledge of the
architecture of Jenkins) is that this plugin should be represented by a
particular authenticated user that one can assign read permission to in one's
ACLs.
Fails to copy artifacts from one multi-configuration build to another
-
Key: JENKINS-10313
URL: https://issues.jenkins-ci.org/browse/JENKINS-10313
Project: Jenkins
Issue Type: Bug
Components: copyartifact
Affects Versions: current
Environment: Mac OS X 10.6.8 client running Jenkins Master
Ubuntu 10.04 running Jenkins slave
Copy Artifact Plugin v1.16
Jenkins v1.420
Reporter: snrkiwi71
Assignee: Alan Harder
[can't find anything on this in the issues tracker, nor the 'net]
Project A (ztest1) is a multi-configuration job that produces artifacts for
Ubuntu and Mac OS X (axes values = macosx64, ubuntuLynx32), for two fake
branches (axes values = x, y). Project B (ztest2) wants access to the
appropriate artifacts from A, given the OS/branch combination.
Using ztest1/label=macosx64,branch=x as the Project name for copy
artifacts works, for all B combinations, but this obviously copies the
artifacts for macosx64/x into all B combinations.
Using ztest1/label=$label,branch=x instead produces the following error.
{{Unable to find project for artifact copy: ztest1/label=macosx64,branch=x
This may be due to incorrect project name or permission settings; see help
for project name in job configuration.
Build step 'Copy artifacts from another project' marked build as failure}}
The actual project name, including the parameters, is correct, but it fails.
The same happens if you use ...,branch=$branch also.
The copy artifacts help instructs
{{To copy artifacts from one matrix project to another, use a parameter to
select the matching configuration in the source project. Example:
OtherMatrixJob/jdk=$jdk}}
so I believe that the above syntax is correct.
The Hudson log for failed B build shows only
{{Jul 12, 2011 12:16:43 PM hudson.model.Run run
INFO: ztest2 #12 main build action completed: FAILURE
Jul 12, 2011 12:16:42 PM hudson.model.Run run
INFO: ztest2 » x,macosx64 #12 main build action completed: FAILURE
Jul 12, 2011 12:16:33 PM hudson.model.Run run
INFO: ztest2 #11 main build action completed: FAILURE
Jul 12, 2011 12:16:32 PM hudson.model.Run run
INFO: ztest2 » x,macosx64 #11 main build action completed: FAILURE
Jul 12, 2011 12:13:06 PM hudson.model.Run run
INFO: ztest2 #10 main build action completed: FAILURE}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10313) Fails to copy artifacts from one multi-configuration build to another
[
https://issues.jenkins-ci.org/browse/JENKINS-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162844#comment-162844
]
Brian Murrell edited comment on JENKINS-10313 at 5/16/12 7:36 PM:
--
How can this be Resolved/Not A Defect? I'm going to Reopen for further
discussion.
Requiring any project that will be the source of a Copy Artifacts action to
have to be readable even by all authenticated users eliminates any use one can
get out of individual or group ACLs and reduces the effective security model to
only two groups of people, authenticated and non-authenticated.
i.e. I cannot create a project that is readable by only some authenticated
users.
The solution, it seems to me (a layperson in terms of any knowledge of the
architecture of Jenkins) is that this plugin should be run with the permissions
of the user initiating the job that the plugin is being used in thus one can
assign read permission to people expected to be able to read the artifacts in
one's ACLs.
was (Author: brian):
How can this be Resolved/Not A Defect? I'm going to Reopen for further
discussion.
Requiring any project that will be the source of a Copy Artifacts action to
have to be readable even by all authenticated users eliminates any use one can
get out of individual or group ACLs and reduces the effective security model to
only two groups of people, authenticated and non-authenticated.
i.e. I cannot create a project that is readable by only some authenticated
users.
The solution, it seems to me (a layperson in terms of any knowledge of the
architecture of Jenkins) is that this plugin should be represented by a
particular authenticated user that one can assign read permission to in one's
ACLs.
Fails to copy artifacts from one multi-configuration build to another
-
Key: JENKINS-10313
URL: https://issues.jenkins-ci.org/browse/JENKINS-10313
Project: Jenkins
Issue Type: Bug
Components: copyartifact
Affects Versions: current
Environment: Mac OS X 10.6.8 client running Jenkins Master
Ubuntu 10.04 running Jenkins slave
Copy Artifact Plugin v1.16
Jenkins v1.420
Reporter: snrkiwi71
Assignee: Alan Harder
[can't find anything on this in the issues tracker, nor the 'net]
Project A (ztest1) is a multi-configuration job that produces artifacts for
Ubuntu and Mac OS X (axes values = macosx64, ubuntuLynx32), for two fake
branches (axes values = x, y). Project B (ztest2) wants access to the
appropriate artifacts from A, given the OS/branch combination.
Using ztest1/label=macosx64,branch=x as the Project name for copy
artifacts works, for all B combinations, but this obviously copies the
artifacts for macosx64/x into all B combinations.
Using ztest1/label=$label,branch=x instead produces the following error.
{{Unable to find project for artifact copy: ztest1/label=macosx64,branch=x
This may be due to incorrect project name or permission settings; see help
for project name in job configuration.
Build step 'Copy artifacts from another project' marked build as failure}}
The actual project name, including the parameters, is correct, but it fails.
The same happens if you use ...,branch=$branch also.
The copy artifacts help instructs
{{To copy artifacts from one matrix project to another, use a parameter to
select the matching configuration in the source project. Example:
OtherMatrixJob/jdk=$jdk}}
so I believe that the above syntax is correct.
The Hudson log for failed B build shows only
{{Jul 12, 2011 12:16:43 PM hudson.model.Run run
INFO: ztest2 #12 main build action completed: FAILURE
Jul 12, 2011 12:16:42 PM hudson.model.Run run
INFO: ztest2 » x,macosx64 #12 main build action completed: FAILURE
Jul 12, 2011 12:16:33 PM hudson.model.Run run
INFO: ztest2 #11 main build action completed: FAILURE
Jul 12, 2011 12:16:32 PM hudson.model.Run run
INFO: ztest2 » x,macosx64 #11 main build action completed: FAILURE
Jul 12, 2011 12:13:06 PM hudson.model.Run run
INFO: ztest2 #10 main build action completed: FAILURE}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13735) Jenkins starts wrong slave for job restricted to specific one
[ https://issues.jenkins-ci.org/browse/JENKINS-13735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162845#comment-162845 ] Jason Swager commented on JENKINS-13735: I've been encountering the same problem. I thought it was in the code of the vSphere Plugin, but it turns out that it's not. Jenkins is issuing a connect() call on slaves that have no reason to be starting up due to the queued jobs that I can see. Part of the problem IS the vSphere Plugin itself. Originally, when a job was fired up, any slave that was down that could the job would be started by the vSphere Plugin because the connect() method would get called on all those slaves, which resulted in a large number of VMs being powered on for a single job. I added code to the plugin to throttle that behavior. Unfortunately, the throttling is causing this problem to get worse. Where as originally, jA, jB, and jC might have been started up, jC now MIGHT get started up due to the vSphere plugin throttling the VM startups. Initial investigation seems to indicate that the Slave.canTake() function might not be functioning as expected. If I find anything further during my investigation, I'll post here. Jenkins starts wrong slave for job restricted to specific one - Key: JENKINS-13735 URL: https://issues.jenkins-ci.org/browse/JENKINS-13735 Project: Jenkins Issue Type: Bug Components: master-slave, slave-setup, vsphere-cloud Affects Versions: current Environment: Jenkins 1.463 under Tomcat6 on Linux (SLES 11), Windows XP slave VMs controlled via vSphere Cloud plugin Reporter: Marco Lehnort Assignee: Kohsuke Kawaguchi Labels: slave I'm using the following setup: - WinXP slaves A,B,C - jobs jA, jB, jC, tied to slaves A,B,C respectively using Restrict where this job can run Assume all slaves are disconnected and powered off, no builds are queued. When starting a build manually, say jC, the following will happen: - job jC will be scheduled and also displayed accordingly in the build queue - tooltip will say it's waiting because slave C is offline - next, slave A is powered on by Jenkins and connection is established - jC will not be started, Jenkins seems to honor the restriction correctly - after some idle time, Jenkins realizes the slave is idle and causes shut down - then, same procedure happens with slave B - on occasion, next one is slave A again - finally (on good luck?) slave C happens to be started - jC is executed It is possible that jC is waiting for hours (indefinitely?), because the required slave is not powered on. I also observed this behaviour using a time-trigger instead of manual trigger, so I assume it is independent of the type of trigger. Occasionally it also happens that the correct slave is powered up right away, but that seems to happen by chance. The concrete pattern is not obvious to me. Note that the component selection above is just my best guess. Cheers, Marco -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13789) 'cvs update' replaces the Tag file which has the branch name in it with a Tag with time and date which effectively corresponds back to the Head
[ https://issues.jenkins-ci.org/browse/JENKINS-13789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162846#comment-162846 ] Amir Isfy commented on JENKINS-13789: - Now when I introduce another option to this command like -f which makes the command look like: cvs update -d -P -f -r branch_name -D 15 May 2012 13:12:24 -0600 module_name then the Tag file does not get touched. It just doesn't like the way these arguments are lined up. 'cvs update' replaces the Tag file which has the branch name in it with a Tag with time and date which effectively corresponds back to the Head --- Key: JENKINS-13789 URL: https://issues.jenkins-ci.org/browse/JENKINS-13789 Project: Jenkins Issue Type: Bug Components: cvs Reporter: Amir Isfy I am building a Module that comes from a CVS branch. 'cvs checkout' correctly keeps the branch name in the Tag file. Now after a clean checkout if the 'Use Update' is checked under 'Source Code Management' then the command looks like: cvs update -d -P -r branch_name -D 15 May 2012 13:12:24 -0600 module_name After this the Tag file will have 'D2012.05.15.19.12.24' in it which basically corresponds to the Head now. This could be related to this. Help please. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13737) Javascript error when selecting Editable Email Notification
[ https://issues.jenkins-ci.org/browse/JENKINS-13737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162847#comment-162847 ] SCM/JIRA link daemon commented on JENKINS-13737: Code changed in jenkins User: slide Path: src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/config.jelly http://jenkins-ci.org/commit/email-ext-plugin/ee715fbd1bd81e83cb9501c311fd04f309431a2c Log: FIX JENKINS-13737 - Workaround issue with eval'd jscript code by making the variable window level (global) Javascript error when selecting Editable Email Notification - Key: JENKINS-13737 URL: https://issues.jenkins-ci.org/browse/JENKINS-13737 Project: Jenkins Issue Type: Bug Components: email-ext Affects Versions: current Environment: Windows, IE8, Jenkins 1.463, Jenkins Email Extension Plugin 2.20 Reporter: Noel Bernardez Assignee: Slide-O-Mix Labels: email-ext, jenkins In Jenkins ver. 1.463, when selecting Editable Email Notification in the Add post-build action, getting the following Javascript error Message: 'emailExtInit' is undefined Line: 480 Char: 17 Code: 0 URI: http://myserver:8080/static/f11a6618/scripts/hudson-behavior.js -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13805) email-ext plugin cannot see env variables set as part of build config
[
https://issues.jenkins-ci.org/browse/JENKINS-13805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162848#comment-162848
]
Slide-O-Mix commented on JENKINS-13805:
---
DEFAULT_RECIPIENTS is not an environment variable, it is a token that is
replaced. If you want to use an environment variable use the ENV token (see the
Content Token Reference info in the help section of the plugin).
email-ext plugin cannot see env variables set as part of build config
-
Key: JENKINS-13805
URL: https://issues.jenkins-ci.org/browse/JENKINS-13805
Project: Jenkins
Issue Type: Bug
Components: email-ext
Environment: 2.18
Reporter: kalpesh soni
Labels: email-ext, environment-variables, plugin
I have tried to use env variable DEFAULT_RECIPIENTS as part of build, and not
as part of global env variables
I need DEFAULT_RECIPIENTS value to be different for each job
I try to set it as part of build step
but the value is NOT available when email ext tries to send email
I get
===
{quote}
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
Sending email to: $team.acids
ERROR: Could not send email as a part of the post-build publishers.
com.sun.mail.smtp.SMTPSendFailedException: 250 2.6.0
26943585.5.1337190669479.JavaMail.CAUDSWAP41$@CAUDSWAP41 Queued mail for
delivery
;
nested exception is:
com.sun.mail.smtp.SMTPAddressFailedException: 550 5.1.1 User unknown
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1112)
at javax.mail.Transport.send0(Transport.java:195)
at javax.mail.Transport.send(Transport.java:124)
at
hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:263)
at
hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:247)
at
hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:207)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
at
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:678)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:656)
at hudson.model.Build$RunnerImpl.cleanUp(Build.java:171)
at hudson.model.Run.run(Run.java:1454)
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: com.sun.mail.smtp.SMTPAddressFailedException: 550 5.1.1 User
unknown
at com.sun.mail.smtp.SMTPTransport.rcptTo(SMTPTransport.java:1686)
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1098)
... 14 more
Notifying upstream projects of job completion
Finished: SUCCESS
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13805) email-ext plugin cannot see env variables set as part of build config
[
https://issues.jenkins-ci.org/browse/JENKINS-13805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slide-O-Mix closed JENKINS-13805.
-
Assignee: Slide-O-Mix
Resolution: Not A Defect
This is not a bug, DEFAULT_RECIPIENTS is not an environment variable. Use the
ENV content token in the recipients field to use an environment variable.
email-ext plugin cannot see env variables set as part of build config
-
Key: JENKINS-13805
URL: https://issues.jenkins-ci.org/browse/JENKINS-13805
Project: Jenkins
Issue Type: Bug
Components: email-ext
Environment: 2.18
Reporter: kalpesh soni
Assignee: Slide-O-Mix
Labels: email-ext, environment-variables, plugin
I have tried to use env variable DEFAULT_RECIPIENTS as part of build, and not
as part of global env variables
I need DEFAULT_RECIPIENTS value to be different for each job
I try to set it as part of build step
but the value is NOT available when email ext tries to send email
I get
===
{quote}
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
Sending email to: $team.acids
ERROR: Could not send email as a part of the post-build publishers.
com.sun.mail.smtp.SMTPSendFailedException: 250 2.6.0
26943585.5.1337190669479.JavaMail.CAUDSWAP41$@CAUDSWAP41 Queued mail for
delivery
;
nested exception is:
com.sun.mail.smtp.SMTPAddressFailedException: 550 5.1.1 User unknown
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1112)
at javax.mail.Transport.send0(Transport.java:195)
at javax.mail.Transport.send(Transport.java:124)
at
hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:263)
at
hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:247)
at
hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:207)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
at
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:678)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:656)
at hudson.model.Build$RunnerImpl.cleanUp(Build.java:171)
at hudson.model.Run.run(Run.java:1454)
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: com.sun.mail.smtp.SMTPAddressFailedException: 550 5.1.1 User
unknown
at com.sun.mail.smtp.SMTPTransport.rcptTo(SMTPTransport.java:1686)
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1098)
... 14 more
Notifying upstream projects of job completion
Finished: SUCCESS
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13359) Blank email (subject+body) for Failure emails only
[ https://issues.jenkins-ci.org/browse/JENKINS-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slide-O-Mix reassigned JENKINS-13359: - Assignee: Slide-O-Mix Blank email (subject+body) for Failure emails only -- Key: JENKINS-13359 URL: https://issues.jenkins-ci.org/browse/JENKINS-13359 Project: Jenkins Issue Type: Bug Components: email-ext Affects Versions: current Environment: Windows Server 2008 with silverlight c# project built with MSBuild Reporter: Alex Assignee: Slide-O-Mix All emails apart from Failure working great using default html.jelly template (ie success, still failing, unstable etc.) However the first failure email (ie matching the failure trigger) sends as a blank subject and body with nothing printed in the jenkins.err.log Same if i dont use the jelly template but a simple text context Any ideas? Thanks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13302) save html file in build before sending
[ https://issues.jenkins-ci.org/browse/JENKINS-13302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slide-O-Mix reassigned JENKINS-13302: - Assignee: Slide-O-Mix save html file in build before sending -- Key: JENKINS-13302 URL: https://issues.jenkins-ci.org/browse/JENKINS-13302 Project: Jenkins Issue Type: New Feature Components: email-ext Reporter: Larry Cai Assignee: Slide-O-Mix Priority: Minor Labels: artifact, email, email-ext, plugin before the email (html/txt) is sent out, the file could be saved in current build directory if needed. there are two use usage for this - check purpose, it could be checked whether the file sent out is correct or not, especially during debug the format (groovy template like), it can avoid wait for the real email in mailbox - archive for access in web, mostly newsletter had the statement view in the browser, then when email is send out, there is a link to view it in web. Thank to consider this, not code yet -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13700) Build hangs during while Sending email
[ https://issues.jenkins-ci.org/browse/JENKINS-13700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162851#comment-162851 ] Slide-O-Mix commented on JENKINS-13700: --- What do the other jobs use? Build hangs during while Sending email Key: JENKINS-13700 URL: https://issues.jenkins-ci.org/browse/JENKINS-13700 Project: Jenkins Issue Type: Bug Components: core, email-ext Environment: OS: Master: Ubuntu 10.04 Slaves: OSX 1.7.3, Win2K8 Server, Win XP, Win2K3 Server Jenkins: 1.424.1 Plugins: Email-ext plugin: 2.14.1 Configuration Slicing plugin: 1.28.1 Jenkins GIT plugin: 1.1.18 Perforce Plugin: 1.3.9 Reporter: crwong When building on the OSX slave, the build will get to the point where the console says that it is sending email, and it stays there. If you look at the list of executors, the progress bar shows that the build is still on progress. If you look at the job's status page, it looks like the job has completed, and it is no longer running. Clicking on the Stop build button next to the job in the Build Executors Status section, does nothing. The only way to clear the executor is to restart Jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13583) Error about sending to an empty list of recipients
[ https://issues.jenkins-ci.org/browse/JENKINS-13583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jpschewe updated JENKINS-13583: --- Attachment: success-expanded.jpg screenshot of success expanded Error about sending to an empty list of recipients -- Key: JENKINS-13583 URL: https://issues.jenkins-ci.org/browse/JENKINS-13583 Project: Jenkins Issue Type: Bug Components: email-ext, git Environment: Jenkins version 1.460, git plugin: 1.1.17, email-ext: 2.20 Reporter: jpschewe Assignee: Nicolas De Loof Attachments: fll-build.log, fll-email-ext-config.jpg, fll-git-config-0.jpg, fll-git-config-1.jpg, success-expanded.jpg Sometimes my jobs won't send emails and I will see the message An attempt to send an e-mail to empty list of recipients, ignored. You can see an email of this at http://mtu.net:8042/job/fll-release/20/. I have this job setup to send only to the recipient list ($DEFAULT_RECIPIENTS) for all actions. I've received this error on jobs setup to use the committers list as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13781) NPE in UserRelevanceView when no user is logged on
[ https://issues.jenkins-ci.org/browse/JENKINS-13781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jacob_robertson resolved JENKINS-13781. --- Resolution: Fixed Look for this fix in version 1.20 of the plugin, to be released soon. NPE in UserRelevanceView when no user is logged on -- Key: JENKINS-13781 URL: https://issues.jenkins-ci.org/browse/JENKINS-13781 Project: Jenkins Issue Type: Bug Components: view-job-filters Reporter: Michael Glauche Assignee: jacob_robertson Priority: Blocker I'm getting a NPE when i try to use the view-job-filters plugin with a recent Jenkins install (did try with 1463,1464): /.jenkins/war/WEB-INF/lib/jenkins-core-1.464.jar!/lib/hudson/projectView.jelly:60:22: d:invokeBody java.lang.NullPointerException at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:716) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:282) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.kohsuke.stapler.jelly.CompressTag.doTag(CompressTag.java:44) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:107) ... 53 more Caused by: java.lang.RuntimeException: org.apache.commons.jelly.JellyTagException: jar:file://.jenkins/war/WEB-INF/lib/jenkins-core-1.464.jar!/lib/hudson/projectView.jelly:60:22: d:invokeBody java.lang.NullPointerException at org.kohsuke.stapler.jelly.groovy.JellyBuilder.doInvokeMethod(JellyBuilder.java:287) at org.kohsuke.stapler.jelly.groovy.Namespace$ProxyImpl.invoke(Namespace.java:92) at $Proxy25.projectView(Unknown Source) at lib.JenkinsTagLib$projectView.call(Unknown Source) at hudson.model.View.main.run(main.groovy:14) at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:66) at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:59) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) ... 84 more Caused by: org.apache.commons.jelly.JellyTagException:
[JIRA] (JENKINS-13737) Javascript error when selecting Editable Email Notification
[ https://issues.jenkins-ci.org/browse/JENKINS-13737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162855#comment-162855 ] Leo Dolan commented on JENKINS-13737: - I have made the changes locally as specified in the link above (deleted three lines and added three lines), and validated that it does work now for me. Note, the path to the file on my systems (OEL5.8) was: /var/lib/jenkins/plugins/email-ext/WEB-INF/classes/hudson/plugins/emailext/ExtendedEmailPublisher/config.jelly Javascript error when selecting Editable Email Notification - Key: JENKINS-13737 URL: https://issues.jenkins-ci.org/browse/JENKINS-13737 Project: Jenkins Issue Type: Bug Components: email-ext Affects Versions: current Environment: Windows, IE8, Jenkins 1.463, Jenkins Email Extension Plugin 2.20 Reporter: Noel Bernardez Assignee: Slide-O-Mix Labels: email-ext, jenkins In Jenkins ver. 1.463, when selecting Editable Email Notification in the Add post-build action, getting the following Javascript error Message: 'emailExtInit' is undefined Line: 480 Char: 17 Code: 0 URI: http://myserver:8080/static/f11a6618/scripts/hudson-behavior.js -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13737) Javascript error when selecting Editable Email Notification
[ https://issues.jenkins-ci.org/browse/JENKINS-13737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162855#comment-162855 ] Leo Dolan edited comment on JENKINS-13737 at 5/16/12 9:20 PM: -- I have made the changes locally as specified in the link above (deleted three lines and added three lines), and validated that it does work now for me. Note, the path to the file on my system (OEL5.5) was: /var/lib/jenkins/plugins/email-ext/WEB-INF/classes/hudson/plugins/emailext/ExtendedEmailPublisher/config.jelly was (Author: ldolan): I have made the changes locally as specified in the link above (deleted three lines and added three lines), and validated that it does work now for me. Note, the path to the file on my systems (OEL5.8) was: /var/lib/jenkins/plugins/email-ext/WEB-INF/classes/hudson/plugins/emailext/ExtendedEmailPublisher/config.jelly Javascript error when selecting Editable Email Notification - Key: JENKINS-13737 URL: https://issues.jenkins-ci.org/browse/JENKINS-13737 Project: Jenkins Issue Type: Bug Components: email-ext Affects Versions: current Environment: Windows, IE8, Jenkins 1.463, Jenkins Email Extension Plugin 2.20 Reporter: Noel Bernardez Assignee: Slide-O-Mix Labels: email-ext, jenkins In Jenkins ver. 1.463, when selecting Editable Email Notification in the Add post-build action, getting the following Javascript error Message: 'emailExtInit' is undefined Line: 480 Char: 17 Code: 0 URI: http://myserver:8080/static/f11a6618/scripts/hudson-behavior.js -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13295) Jenkins hangs for ~1 hour after posting 'Sending Email'
[ https://issues.jenkins-ci.org/browse/JENKINS-13295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162856#comment-162856 ] Slide-O-Mix commented on JENKINS-13295: --- I think this is probably related to JENKINS-13102 Jenkins hangs for ~1 hour after posting 'Sending Email' --- Key: JENKINS-13295 URL: https://issues.jenkins-ci.org/browse/JENKINS-13295 Project: Jenkins Issue Type: Bug Components: email-ext Reporter: Devin Barbieri Priority: Critical -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13700) Build hangs during while Sending email
[ https://issues.jenkins-ci.org/browse/JENKINS-13700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162857#comment-162857 ] Slide-O-Mix commented on JENKINS-13700: --- I bet this is related to JENKINS-13102 Build hangs during while Sending email Key: JENKINS-13700 URL: https://issues.jenkins-ci.org/browse/JENKINS-13700 Project: Jenkins Issue Type: Bug Components: core, email-ext Environment: OS: Master: Ubuntu 10.04 Slaves: OSX 1.7.3, Win2K8 Server, Win XP, Win2K3 Server Jenkins: 1.424.1 Plugins: Email-ext plugin: 2.14.1 Configuration Slicing plugin: 1.28.1 Jenkins GIT plugin: 1.1.18 Perforce Plugin: 1.3.9 Reporter: crwong When building on the OSX slave, the build will get to the point where the console says that it is sending email, and it stays there. If you look at the list of executors, the progress bar shows that the build is still on progress. If you look at the job's status page, it looks like the job has completed, and it is no longer running. Clicking on the Stop build button next to the job in the Build Executors Status section, does nothing. The only way to clear the executor is to restart Jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12577) Email notification hangs due to NullPointerException
[ https://issues.jenkins-ci.org/browse/JENKINS-12577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162858#comment-162858 ] Slide-O-Mix commented on JENKINS-12577: --- Probably similar to JENKINS-13102 Email notification hangs due to NullPointerException Key: JENKINS-12577 URL: https://issues.jenkins-ci.org/browse/JENKINS-12577 Project: Jenkins Issue Type: Bug Components: email-ext Affects Versions: current Environment: Windows 2008 Server x64, Java 1.6.0_25 Reporter: Costin Caraivan Priority: Blocker Attachments: template.jelly We have an email notification which uses a Jelly template. So far it worked ok, but recently we started getting these: Jan 25, 2012 2:11:23 PM hudson.plugins.emailext.ExtendedEmailPublisher sendMail WARNING: Could not send email. java.lang.NullPointerException at hudson.model.Slave.createLauncher(Slave.java:311) at hudson.plugins.perforce.PerforceMailResolver.findMailAddressFor(PerforceMailResolver.java:60) at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:100) at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:488) at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:331) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:251) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:243) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:203) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:694) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:669) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:647) at hudson.model.Build$RunnerImpl.cleanUp(Build.java:171) at hudson.model.Run.run(Run.java:1448) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7997) Changelog read from JellyScript
[ https://issues.jenkins-ci.org/browse/JENKINS-7997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162859#comment-162859 ] Slide-O-Mix commented on JENKINS-7997: -- You should be able to set the content-type of the email in the global config. Please try this and see if it helps. Changelog read from JellyScript --- Key: JENKINS-7997 URL: https://issues.jenkins-ci.org/browse/JENKINS-7997 Project: Jenkins Issue Type: Bug Components: email-ext Affects Versions: current Environment: WindowsXP Reporter: ttaqt Priority: Critical Use the Jelly Script Template from version 2.9. I found that if SVN Checkin log has Chinese. It will show the Chinese as (鏇挎崲鍐欏箍鎾姛鑳藉尯鐨勮创鍥惧苟淇敼鍔ㄧ敾鐨勫疄鐜� . Is it the Jelly Script doesn`t support UTF-8? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7859) Email-ext trigger for the transition from success to failure
[
https://issues.jenkins-ci.org/browse/JENKINS-7859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162860#comment-162860
]
Slide-O-Mix commented on JENKINS-7859:
--
Please clone the git repo, make the change and issue a pull request.
Email-ext trigger for the transition from success to failure
Key: JENKINS-7859
URL: https://issues.jenkins-ci.org/browse/JENKINS-7859
Project: Jenkins
Issue Type: New Feature
Components: email-ext
Affects Versions: current
Reporter: branso
Continuation from JENKINS-7858. Wasn't able to add a comment for some reason.
Email-ext currently does not have a trigger for when a build goes from
success to failure. The failure triggers on every failed build however the
patch the I'm suggesting will only trigger on the transition.
To add this feature change/add the following files
* hudson/plugins/emailext/EmailExtensionPlugin.java add the lines indicated
{code:java}
/*
* The MIT License
*
* Copyright (c) 2010, kyle.swee...@valtech.com, Stellar Science Ltd Co, K.
R. Walker
*
* Permission is hereby granted, free of charge, to any person obtaining a
copy
* of this software and associated documentation files (the Software), to
deal
* in the Software without restriction, including without limitation the
rights
* to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
* copies of the Software, and to permit persons to whom the Software is
* furnished to do so, subject to the following conditions:
*
* The above copyright notice and this permission notice shall be included in
* all copies or substantial portions of the Software.
*
* THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
* AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM,
* OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
* THE SOFTWARE.
*/
package hudson.plugins.emailext;
import hudson.Plugin;
import hudson.plugins.emailext.plugins.ContentBuilder;
import hudson.plugins.emailext.plugins.EmailContent;
import hudson.plugins.emailext.plugins.EmailTriggerDescriptor;
import hudson.plugins.emailext.plugins.content.*;
import hudson.plugins.emailext.plugins.trigger.*;
import hudson.plugins.emailext.plugins.trigger.FirstFailureTrigger; //add
line
/**
* Entry point of a plugin.
*
* p
* There must be one {@link Plugin} class in each plugin.
* See javadoc of {@link Plugin} for more about what can be done on this
class.
*
* @author kyle.swee...@valtech.com
*/
public class EmailExtensionPlugin extends Plugin {
@Override
public void start() throws Exception {
//We are adding different Content plugins to the list of
content types.
addEmailContentPlugin(new BuildLogContent());
addEmailContentPlugin(new BuildLogRegexContent());
addEmailContentPlugin(new BuildNumberContent());
addEmailContentPlugin(new BuildStatusContent());
addEmailContentPlugin(new BuildURLContent());
addEmailContentPlugin(new ChangesSinceLastBuildContent());
addEmailContentPlugin(new
ChangesSinceLastSuccessfulBuildContent());
addEmailContentPlugin(new
ChangesSinceLastUnstableBuildContent());
addEmailContentPlugin(new EnvContent());
addEmailContentPlugin(new FailedTestsContent());
addEmailContentPlugin(new HudsonURLContent());
addEmailContentPlugin(new ProjectNameContent());
addEmailContentPlugin(new ProjectURLContent());
addEmailContentPlugin(new SVNRevisionContent());
addEmailContentPlugin(new CauseContent());
addEmailContentPlugin(new JellyScriptContent());
addEmailTriggerPlugin(PreBuildTrigger.DESCRIPTOR);
addEmailTriggerPlugin(FailureTrigger.DESCRIPTOR);
addEmailTriggerPlugin(StillFailingTrigger.DESCRIPTOR);
addEmailTriggerPlugin(UnstableTrigger.DESCRIPTOR);
addEmailTriggerPlugin(StillUnstableTrigger.DESCRIPTOR);
addEmailTriggerPlugin(SuccessTrigger.DESCRIPTOR);
addEmailTriggerPlugin(FixedTrigger.DESCRIPTOR);
addEmailTriggerPlugin(FirstFailureTrigger.DESCRIPTOR);//add
line
}
private void addEmailContentPlugin(EmailContent content) {
try {
ContentBuilder.addEmailContentType(content);
[JIRA] (JENKINS-13806) View update deadlock freezes the UI for all users
garethbowles created JENKINS-13806: -- Summary: View update deadlock freezes the UI for all users Key: JENKINS-13806 URL: https://issues.jenkins-ci.org/browse/JENKINS-13806 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: Jenkins 1.462 on Red Hat Linux, JDK1.6.0_27 64-bit Reporter: garethbowles Attachments: jenkins-stackdump-051512-1700.zip See the attached stack dump. It looks as if one user was updating a view, then another user tried to access that view resulting in a deadlock on hudson.models.Hudson. Builds continued to run after the deadlock, but the UI was inaccessible for all users. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6703) Allow for selection of Cc:, Bcc: fields for email recipients on global recipient list
[ https://issues.jenkins-ci.org/browse/JENKINS-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162862#comment-162862 ] Slide-O-Mix commented on JENKINS-6703: -- I'm not sure Bcc is such a good idea, but Cc would probably be fine. Allow for selection of Cc:, Bcc: fields for email recipients on global recipient list - Key: JENKINS-6703 URL: https://issues.jenkins-ci.org/browse/JENKINS-6703 Project: Jenkins Issue Type: Improvement Components: email-ext Affects Versions: current Reporter: arostfx Hello, a common use case for this plugin is that the the global recipient list contains addresses of people who are not actually involved in breaking or fixing a build, but who still would like to get informed about breaks and fixes. It would be very useful to have those people addressed in the CC: field of emails, instead of adding them to the To: field. This will also increase the awareness of the real breakers when a build fails. Such a distinction (To vs Cc/Bcc) will only be needed for the global recipient list, which could greatly simplify the implementation of this feature. I figure that support for some prefix in the list, like CC:recipi...@foobar.com, could be sufficient. Thanks a lot for this really powerful and extremely useful plugin! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8385) In the text.jelly and html.jelly templates, it would be nice to show all changes since last successful build.
[ https://issues.jenkins-ci.org/browse/JENKINS-8385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slide-O-Mix closed JENKINS-8385. Resolution: Won't Fix You can create your own templates that do this. Please see the wiki for more information. In the text.jelly and html.jelly templates, it would be nice to show all changes since last successful build. - Key: JENKINS-8385 URL: https://issues.jenkins-ci.org/browse/JENKINS-8385 Project: Jenkins Issue Type: Improvement Components: email-ext Affects Versions: current Reporter: rmohn Priority: Minor In the text.jelly and html.jelly templates, it would be nice to show all changes since the last successful build, rather than just the changes since last build. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7358) Better way to configure users to nofify after a build
[ https://issues.jenkins-ci.org/browse/JENKINS-7358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162864#comment-162864 ] Slide-O-Mix commented on JENKINS-7358: -- I wonder if this could be done using an auto-complete instead of checkboxes. Better way to configure users to nofify after a build - Key: JENKINS-7358 URL: https://issues.jenkins-ci.org/browse/JENKINS-7358 Project: Jenkins Issue Type: Improvement Components: email-ext Affects Versions: current Reporter: rlagoue Since Hudson has a module for user management (that can connected to crowd). It would be great, when configuring a job to just select the users from the list of those present in the system (via checkboxes for example), who will receive notifications, instead of adding the email address directly. Sure I suppose the users have their email address configured. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-3670) Configure 'DefaultContents' per build status
[ https://issues.jenkins-ci.org/browse/JENKINS-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slide-O-Mix closed JENKINS-3670. Resolution: Won't Fix I think this would be too klunky to define in the global config area. I recommend using the Jelly or Groovy scripting instead and checking the build status in there and changing the output accordingly. Configure 'DefaultContents' per build status Key: JENKINS-3670 URL: https://issues.jenkins-ci.org/browse/JENKINS-3670 Project: Jenkins Issue Type: Improvement Components: email-ext Affects Versions: current Environment: Platform: All, OS: All Reporter: jhm Assignee: markltbaker You could configure the $DEFAULT_CONTENT in the Hudson configuration. But seeing always the same structure is not required - if the build status is success or fixed I dont need the $FAILED_TESTS, $CHANGES or $BUILD_LOG. It would be good to configure multiple 'defaults' so each trigger could use different defaults. Better than configure them for each job. $DEFAULT_CONTENT $DEFAULT_CONTENT_SUCCESS $DEFAULT_CONTENT_FAILURE $DEFAULT_CONTENT_FIXED $DEFAULT_CONTENT_UNSTABLE $DEFAULT_CONTENT_STILL_FAILING $DEFAULT_CONTENT_STILL_UNSTABLE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162866#comment-162866 ] Guillaume Bilodeau commented on JENKINS-13227: -- I've installed the latest plugin and changes are still not picked up. I don't see anything suspicious in the logs. Is there something that could help you in our setup? CVS plugin 2.1 does not detect changes -- Key: JENKINS-13227 URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 Project: Jenkins Issue Type: Bug Components: cvs Reporter: Guillaume Bilodeau Assignee: Michael Clarke Priority: Critical Labels: cvs Attachments: rlog.txt As presented in the user group: https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS repository for a few weeks now, without any problems. The CVS plugin (v1.6) was using the local cvsnt install. We've since upgraded the CVS plugin to version 2.1 (by manually pinning the plugin) and since then, CVS changes are not detected. The CVS polling log is triggered properly, tons of cvs rlog instructions are sent, but at the end No changes is displayed. Using CVS plugin 1.6 the cvs polling command looked like this (executed at 5:26:21 PM EDT): cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D Thursday, March 22, 2012 9:26:21 PM UTC Using CVS plugin 2.1, the last cvs checkout command looked like this (executed at 11:56:16 AM EDT): cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 11:56:16 EDT -d portailInt portailInt We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13700) Build hangs during while Sending email
[ https://issues.jenkins-ci.org/browse/JENKINS-13700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162867#comment-162867 ] crwong commented on JENKINS-13700: -- The other jobs are running perforce. Could have something to do with the email addresses that it is attempting to send to? Not all of the users have email address information enter correctly. Also, I don't see the same errors in my logs as the person who entered bug JENKINS-13102 Build hangs during while Sending email Key: JENKINS-13700 URL: https://issues.jenkins-ci.org/browse/JENKINS-13700 Project: Jenkins Issue Type: Bug Components: core, email-ext Environment: OS: Master: Ubuntu 10.04 Slaves: OSX 1.7.3, Win2K8 Server, Win XP, Win2K3 Server Jenkins: 1.424.1 Plugins: Email-ext plugin: 2.14.1 Configuration Slicing plugin: 1.28.1 Jenkins GIT plugin: 1.1.18 Perforce Plugin: 1.3.9 Reporter: crwong When building on the OSX slave, the build will get to the point where the console says that it is sending email, and it stays there. If you look at the list of executors, the progress bar shows that the build is still on progress. If you look at the job's status page, it looks like the job has completed, and it is no longer running. Clicking on the Stop build button next to the job in the Build Executors Status section, does nothing. The only way to clear the executor is to restart Jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13737) Javascript error when selecting Editable Email Notification
[ https://issues.jenkins-ci.org/browse/JENKINS-13737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slide-O-Mix resolved JENKINS-13737. --- Resolution: Fixed Put in place a workaround to have the custom JS object made a global. Javascript error when selecting Editable Email Notification - Key: JENKINS-13737 URL: https://issues.jenkins-ci.org/browse/JENKINS-13737 Project: Jenkins Issue Type: Bug Components: email-ext Affects Versions: current Environment: Windows, IE8, Jenkins 1.463, Jenkins Email Extension Plugin 2.20 Reporter: Noel Bernardez Assignee: Slide-O-Mix Labels: email-ext, jenkins In Jenkins ver. 1.463, when selecting Editable Email Notification in the Add post-build action, getting the following Javascript error Message: 'emailExtInit' is undefined Line: 480 Char: 17 Code: 0 URI: http://myserver:8080/static/f11a6618/scripts/hudson-behavior.js -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13607) certain projects can't send email: javax.mail.MessagingException: Could not connect to SMTP host: mail.recondotech.com, port: 25, response: 421
[ https://issues.jenkins-ci.org/browse/JENKINS-13607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slide-O-Mix closed JENKINS-13607. - Resolution: Cannot Reproduce certain projects can't send email: javax.mail.MessagingException: Could not connect to SMTP host: mail.recondotech.com, port: 25, response: 421 --- Key: JENKINS-13607 URL: https://issues.jenkins-ci.org/browse/JENKINS-13607 Project: Jenkins Issue Type: Bug Components: email-ext Affects Versions: current Environment: CentOS 5.6 64 bit, Java Hotspot 1.6.0.26 /usr/lib/jvm/java-1.6.0/bin/java -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -DJENKINS_HOME=/var/lib/jenkins -jar /usr/lib/jenkins/jenkins.war -XX:PermSize=512M --logfile=/var/log/jenkins/jenkins.log --webroot=/var/cache/jenkins/war --daemon --httpPort=8080 --ajp13Port=8009 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20 Reporter: Adam Sloan Labels: email, jenkins Loss of functionality: emails aren't getting sent out Build Console Output: Build step 'Execute shell' marked build as failure Emma: looking for coverage reports in the provided path: target/site/emma/coverage.xml Sending e-mails to: aslo...@gmail.com ERROR: Could not connect to SMTP host: mail.recondotech.com, port: 25, response: 421 javax.mail.MessagingException: Could not connect to SMTP host: mail.recondotech.com, port: 25, response: 421 at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1922) at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:638) at javax.mail.Service.connect(Service.java:295) at javax.mail.Service.connect(Service.java:176) at javax.mail.Service.connect(Service.java:125) at javax.mail.Transport.send0(Transport.java:194) at javax.mail.Transport.send(Transport.java:124) at hudson.tasks.MailSender.execute(MailSender.java:114) at hudson.maven.MavenModuleSetBuild$RunnerImpl.cleanUp(MavenModuleSetBuild.java:1012) at hudson.model.Run.run(Run.java:1465) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Notifying upstream projects of job completion Finished: FAILURE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13563) Attachment filepath does not support token reference
[
https://issues.jenkins-ci.org/browse/JENKINS-13563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slide-O-Mix reassigned JENKINS-13563:
-
Assignee: Slide-O-Mix
Attachment filepath does not support token reference
Key: JENKINS-13563
URL: https://issues.jenkins-ci.org/browse/JENKINS-13563
Project: Jenkins
Issue Type: Improvement
Components: email-ext
Reporter: Sam He
Assignee: Slide-O-Mix
I defined an string parameter named env.
email content can retrieve it with token ${ENV, var=env}.
However, attachment field cannot solve the filepath with the tocken:
attachment: logs/${ENV, var=env}.log
Is there any suggestion on this behavior ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12421) Add pre-send step to email-ext that can modify the mail message object
[ https://issues.jenkins-ci.org/browse/JENKINS-12421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162869#comment-162869 ] Slide-O-Mix commented on JENKINS-12421: --- Would you want this only at the project level? Add pre-send step to email-ext that can modify the mail message object -- Key: JENKINS-12421 URL: https://issues.jenkins-ci.org/browse/JENKINS-12421 Project: Jenkins Issue Type: New Feature Components: claim, email-ext Affects Versions: current Environment: All Reporter: terryl westerhold Assignee: Slide-O-Mix Labels: claim, email-ext, feature, groovy, jenkins, plugin, script When the Email-Ext plugin is used in conjunction with the Claim plugin there is no way to configure a project's email options to only send to the one who has claimed it. This results in every person on a team receiving emails for a build they did not break, turning Jenkins emails into something annoying instead of something useful. For someone who knew the code this would be a pretty easy feature to add. And while this would be a good feature, I think a more elaborate solution that would allow Email-ext plugin users to access/modify all parts of the email message (including who the message is being sent to) would be more useful in the long run. Giving users access to all parts of the email message and the option to run a Groovy script after the email has been built, but before the email has been sent would satisfy this feature request and would make the Email-Ext plugin much more versatile. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13805) email-ext plugin cannot see env variables set as part of build config
[
https://issues.jenkins-ci.org/browse/JENKINS-13805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162870#comment-162870
]
kalpesh soni commented on JENKINS-13805:
what syntax do i use? its not documented anywhere
email-ext plugin cannot see env variables set as part of build config
-
Key: JENKINS-13805
URL: https://issues.jenkins-ci.org/browse/JENKINS-13805
Project: Jenkins
Issue Type: Bug
Components: email-ext
Environment: 2.18
Reporter: kalpesh soni
Assignee: Slide-O-Mix
Labels: email-ext, environment-variables, plugin
I have tried to use env variable DEFAULT_RECIPIENTS as part of build, and not
as part of global env variables
I need DEFAULT_RECIPIENTS value to be different for each job
I try to set it as part of build step
but the value is NOT available when email ext tries to send email
I get
===
{quote}
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
Sending email to: $team.acids
ERROR: Could not send email as a part of the post-build publishers.
com.sun.mail.smtp.SMTPSendFailedException: 250 2.6.0
26943585.5.1337190669479.JavaMail.CAUDSWAP41$@CAUDSWAP41 Queued mail for
delivery
;
nested exception is:
com.sun.mail.smtp.SMTPAddressFailedException: 550 5.1.1 User unknown
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1112)
at javax.mail.Transport.send0(Transport.java:195)
at javax.mail.Transport.send(Transport.java:124)
at
hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:263)
at
hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:247)
at
hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:207)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
at
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:678)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:656)
at hudson.model.Build$RunnerImpl.cleanUp(Build.java:171)
at hudson.model.Run.run(Run.java:1454)
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: com.sun.mail.smtp.SMTPAddressFailedException: 550 5.1.1 User
unknown
at com.sun.mail.smtp.SMTPTransport.rcptTo(SMTPTransport.java:1686)
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1098)
... 14 more
Notifying upstream projects of job completion
Finished: SUCCESS
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13803) PRQA Plugin fails during the publishing phase with NULL pointer exception
[
https://issues.jenkins-ci.org/browse/JENKINS-13803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162871#comment-162871
]
Mads Nielsen commented on JENKINS-13803:
Hi Julian,
First of all thanks for trying out our plugin!
I have another question regarding this issue, were you by any chance selecting
'Improvement' for any of the available metrics? And did the job have any prior
failed builds?
Regards,
Mads
PRQA Plugin fails during the publishing phase with NULL pointer exception
-
Key: JENKINS-13803
URL: https://issues.jenkins-ci.org/browse/JENKINS-13803
Project: Jenkins
Issue Type: Bug
Components: prqa
Environment: Master: linux
Slave: Windows 7
Jenkins 1.441
Reporter: Julian Requejo
Assignee: Lars Kruse
PRQA plugin generates reports correctly, but fails during publishing phase.
{noformat}
At revision 1572
no change for https://xx/xx since the previous build
This job will create a report with the following selected parameters:
QAR selected project file:Sources\QAC\xx\xx.prj
QAR selected product: QAC
QAR selected report type: Compliance
Beginning report generation with the following command:
qaw QAC Sources\QAC\xx\xx.prj -maseq qar %Q %P+ %L+ -po
qar::report_type=Compliance\ Report -po qar::project_name=%J -po
qar::output_path=c:\_dev\jenkins-int\workspace\xx_QAC -po
qar::viewing_program=dummy -po qar::report_format=xhtml
Viewer dummy not available, result will not be rendered.
Generating - Please wait...
Writing c:\_dev\jenkins-int\workspace\xx_QAC\Compliance Report.xml
Writing c:\_dev\jenkins-int\workspace\xx_QAC\Compliance Report.xhtml
Writing c:\_dev\jenkins-int\workspace\xx_QAC\Compliance Report-Main.xhtml
Finished remote reporting.
Found report. Attempting to copy Compliance Report.xhtml to artifacts
directory: /home/xx/.jenkins/jobs/xx_QAC/builds/2012-05-16_17-11-12/archive
Attempting to copy report to following target: Compliance Report.xhtml
Succesfully copied report
ERROR: Publisher net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier aborted
due to exception
java.lang.NullPointerException
at
net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier.perform(PRQANotifier.java:240)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:667)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:645)
at hudson.model.Build$RunnerImpl.post2(Build.java:162)
at
hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:614)
at hudson.model.Run.run(Run.java:1429)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)
Notifying upstream projects of job completion
Finished: FAILURE
{noformat}
I have tested this using three configurations, all with Jenkins 1.441
- Single Jenkins web app running on my local machine (Windows 7): it works
- Master-slave configuration, *both* on my local machine (Windows 7), slave
as a user process: it works
- Master-slave configuration, master on a Linux box, slave on my local
Windows 7 machine (Windows 7), slave as a user process: it does *not* work
and triggers the error above.
I could try upgrading to a newer Jenkins, but I'd strongly prefer not to
unless shown to be essential.
I'll be happy to provide further logs. Thanks
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13746) Buildresult trigger plugin does not support hierachical folders
[ https://issues.jenkins-ci.org/browse/JENKINS-13746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162872#comment-162872 ] SCM/JIRA link daemon commented on JENKINS-13746: Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/buildresulttrigger/BuildResultTrigger.java src/main/resources/org/jenkinsci/plugins/buildresulttrigger/BuildResultTrigger/config.jelly http://jenkins-ci.org/commit/buildresult-trigger-plugin/f91e697fc1e36eee1c969cab320e7e582afd Log: Merge pull request #2 from ndeloof/master support hierarchical model (Fix JENKINS-13746) Compare: https://github.com/jenkinsci/buildresult-trigger-plugin/compare/3d39035...f91e6aa Buildresult trigger plugin does not support hierachical folders --- Key: JENKINS-13746 URL: https://issues.jenkins-ci.org/browse/JENKINS-13746 Project: Jenkins Issue Type: Bug Components: buildresult-trigger, buildresulttrigger Reporter: mwebber Assignee: Gregory Boissinot According to http://wiki.cloudbees.com/bin/view/Jenkins+Enterprise/CloudBees+Free+and+Open+Source+Jenkins+Plugins, the Build Result trigger plugin does not correctly support hierarchical projects (see the bottom of the page for this assertion). This means that I cannot use the very useful looking Cloudbees Folders plugin, since we use the Build Result trigger plugin heavily. Can the Build Result trigger plugin be updated to support hierarchical projects, using the [instructions|https://wiki.jenkins-ci.org/display/JENKINS/Hierarchical+projects+support]? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13805) email-ext plugin cannot see env variables set as part of build config
[
https://issues.jenkins-ci.org/browse/JENKINS-13805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162873#comment-162873
]
Slide-O-Mix commented on JENKINS-13805:
---
Yes, it is documented in the content macro reference when configuring the
plugin.
email-ext plugin cannot see env variables set as part of build config
-
Key: JENKINS-13805
URL: https://issues.jenkins-ci.org/browse/JENKINS-13805
Project: Jenkins
Issue Type: Bug
Components: email-ext
Environment: 2.18
Reporter: kalpesh soni
Assignee: Slide-O-Mix
Labels: email-ext, environment-variables, plugin
I have tried to use env variable DEFAULT_RECIPIENTS as part of build, and not
as part of global env variables
I need DEFAULT_RECIPIENTS value to be different for each job
I try to set it as part of build step
but the value is NOT available when email ext tries to send email
I get
===
{quote}
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
Sending email to: $team.acids
ERROR: Could not send email as a part of the post-build publishers.
com.sun.mail.smtp.SMTPSendFailedException: 250 2.6.0
26943585.5.1337190669479.JavaMail.CAUDSWAP41$@CAUDSWAP41 Queued mail for
delivery
;
nested exception is:
com.sun.mail.smtp.SMTPAddressFailedException: 550 5.1.1 User unknown
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1112)
at javax.mail.Transport.send0(Transport.java:195)
at javax.mail.Transport.send(Transport.java:124)
at
hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:263)
at
hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:247)
at
hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:207)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
at
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:678)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:656)
at hudson.model.Build$RunnerImpl.cleanUp(Build.java:171)
at hudson.model.Run.run(Run.java:1454)
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: com.sun.mail.smtp.SMTPAddressFailedException: 550 5.1.1 User
unknown
at com.sun.mail.smtp.SMTPTransport.rcptTo(SMTPTransport.java:1686)
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1098)
... 14 more
Notifying upstream projects of job completion
Finished: SUCCESS
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13807) Email-ext Plugin Does Not work
Jared Griffith created JENKINS-13807: Summary: Email-ext Plugin Does Not work Key: JENKINS-13807 URL: https://issues.jenkins-ci.org/browse/JENKINS-13807 Project: Jenkins Issue Type: Bug Components: email-ext Affects Versions: current Environment: CentOS 6.2, Sun JDK 6.0.31, Jenkins ver. 1.464 installed from yum repo Reporter: Jared Griffith I have installed and tried to activate the email-ext plugin, but when I try to enable the extension for a particular job, it does not work. I am getting the following error with the Firefox Javascript debugger: Timestamp: 05/16/2012 06:16:42 PM Error: emailExtInit is not defined Source File: http://jenkins.picsauditing.com/static/5f664cc9/scripts/hudson-behavior.js Line: 480 Please help. The latest version of the plug in is installed and was installed from the Jenkins Plugin UI. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13776) Slave is unable to checkout svn due to missing resources
[
https://issues.jenkins-ci.org/browse/JENKINS-13776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162874#comment-162874
]
Stephen Morrison edited comment on JENKINS-13776 at 5/17/12 1:23 AM:
-
Doesn't appear to be related to the subversion plugin. It has now started
happening for jobs that don't do any checkout, and on a different environment
from the where the original problem was reported. No changes have been made to
the instance or the environment since the original report. I'm happy to
provide any further information that will help to track this down, it prevents
us using these environments with Jenkins. Bouncing the Jenkins instance and
bouncing the slave machine doesn't seem to help.
{code}
Started
Building remotely on PPP VX.00 CT5 in workspace
/ppp/home/pppx00c3/jenkins/workspace/ReplicateBuild
No emails were triggered.
FATAL: command execution failed
java.io.IOException: Remote call on PPP VX.00 CT5 failed
at hudson.remoting.Channel.call(Channel.java:655)
at hudson.Launcher$RemoteLauncher.launch(Launcher.java:798)
at hudson.Launcher$ProcStarter.start(Launcher.java:338)
at hudson.Launcher$ProcStarter.join(Launcher.java:345)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:82)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:58)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710)
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:480)
at hudson.model.Run.run(Run.java:1434)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:239)
Caused by: java.lang.Error: Unable to load resource
hudson/model/Messages.properties
at
hudson.remoting.RemoteClassLoader.findResource(RemoteClassLoader.java:202)
at java.lang.ClassLoader.getResource(ClassLoader.java:978)
at java.lang.Class.getResource(Class.java:2074)
at
org.jvnet.localizer.ResourceBundleHolder.get(ResourceBundleHolder.java:83)
at
org.jvnet.localizer.ResourceBundleHolder.get(ResourceBundleHolder.java:102)
at
org.jvnet.localizer.ResourceBundleHolder.get(ResourceBundleHolder.java:102)
at
org.jvnet.localizer.ResourceBundleHolder.format(ResourceBundleHolder.java:139)
at hudson.model.Messages.Node_Mode_NORMAL(Messages.java:1733)
at hudson.model.Node$Mode.clinit(Node.java:432)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at java.lang.Class.getEnumConstantsShared(Class.java:2942)
at java.lang.Class.getEnumConstants(Class.java:2920)
at jenkins.model.Jenkins.clinit(Jenkins.java:3845)
at hudson.model.Computer.clinit(Computer.java:1208)
at hudson.Launcher$LocalLauncher.init(Launcher.java:691)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:927)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:901)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.io.FileNotFoundException:
/tmp/hudson-remoting8447610959433617636/hudson/model/Messages.properties (No
such file or directory)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.init(FileOutputStream.java:179)
at java.io.FileOutputStream.init(FileOutputStream.java:131)
at
hudson.remoting.RemoteClassLoader.makeResource(RemoteClassLoader.java:270)
at
hudson.remoting.RemoteClassLoader.findResource(RemoteClassLoader.java:198)
... 28 more
Build step 'Execute shell' marked build as failure
{code}
was (Author: smorriso):
Doesn't appear to be related to the
[JIRA] (JENKINS-13776) Slave is unable to checkout svn due to missing resources
[ https://issues.jenkins-ci.org/browse/JENKINS-13776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Morrison updated JENKINS-13776: --- Priority: Minor (was: Blocker) Lowering priority right down. Can be closed if reporting the real problem is java's fault rather than Jenkins. Slave is unable to checkout svn due to missing resources Key: JENKINS-13776 URL: https://issues.jenkins-ci.org/browse/JENKINS-13776 Project: Jenkins Issue Type: Bug Components: ssh-slaves Affects Versions: current Environment: Linux x86_64 Java 1.6.0_16 Jenkins 1.464 ant 1.1 javadoc 1.0 offlineonfailure-plugin 1.0 groovy-postbuild 1.7 distfork 1.3 nested-view 1.7 PrioritySorter1.3 maven-plugin 1.464 subversion1.40 cvs 1.6 build-pipeline-plugin 1.2 parameterized-trigger 2.14 copyartifact 1.22 join 1.15 global-build-stats1.0 build-timeout 1.8 matrixtieparent 1.1 email-ext 2.16 view-job-filters 1.17.2 nodelabelparameter1.1.3 groovy1.12 rebuild 1.10 translation 1.8 ssh-slaves0.21 Reporter: Stephen Morrison Assignee: Kohsuke Kawaguchi Priority: Minor I get the following exception from one of my matrix jobs when the ssh slave connects and attempts to checkout the svn repo. hudson.util.IOException2: remote file operation failed: /ct/home/ct085/jenkins_parent/workspace/master_build at hudson.remoting.Channel@581ec7bf:Main_Stream_CT at hudson.FilePath.act(FilePath.java:835) at hudson.FilePath.act(FilePath.java:821) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:743) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:685) at hudson.model.AbstractProject.checkout(AbstractProject.java:1218) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:586) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:475) at hudson.model.Run.run(Run.java:1434) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:248) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66) Caused by: java.io.IOException: Remote call on Main_Stream_CT failed at hudson.remoting.Channel.call(Channel.java:655) at hudson.FilePath.act(FilePath.java:828) ... 11 more Caused by: java.lang.Error: Unable to load resource javax/servlet/http/LocalStrings.properties at hudson.remoting.RemoteClassLoader.findResource(RemoteClassLoader.java:202) at java.lang.ClassLoader.getResource(ClassLoader.java:978) at java.lang.ClassLoader.getResourceAsStream(ClassLoader.java:1168) at java.util.ResourceBundle$Control$1.run(ResourceBundle.java:2418) at java.util.ResourceBundle$Control$1.run(ResourceBundle.java:2403) at java.security.AccessController.doPrivileged(Native Method) at java.util.ResourceBundle$Control.newBundle(ResourceBundle.java:2402) at java.util.ResourceBundle.loadBundle(ResourceBundle.java:1406) at java.util.ResourceBundle.findBundle(ResourceBundle.java:1365) at java.util.ResourceBundle.findBundle(ResourceBundle.java:1292) at java.util.ResourceBundle.findBundle(ResourceBundle.java:1292) at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1234) at java.util.ResourceBundle.getBundle(ResourceBundle.java:715) at javax.servlet.http.HttpServlet.clinit(HttpServlet.java:93) at hudson.model.Node$Mode.clinit(Node.java:450) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at java.lang.Class.getEnumConstantsShared(Class.java:2942) at java.lang.Class.getEnumConstants(Class.java:2920) at jenkins.model.Jenkins.clinit(Jenkins.java:3845) at hudson.scm.SubversionSCM.createDefaultSVNOptions(SubversionSCM.java:844) at hudson.scm.SubversionSCM.createClientManager(SubversionSCM.java:834) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:766) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2161) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48)
Jenkins (Windows7) - Execute shell (gitbash)
Hi, I have jenkins 1.464 install on a Windows7 x64 machine. I have Git 1.7.10 installed on the same machine I create a basic free style project I have configured Jenkins to Shell executable with C:\bin\sh.exe I have run the sh.exe on the DOS prompt and it works sh.exe is a copy of the executable from the Git 1.7.0 distribution I added a build step in the jenkins job and chose the Execute shell option When I click Build Now, I get the error Started by useranonymous http://localhost:8080/user/null Building in workspace C:\Program Files (x86)\Jenkins\workspace\ShellTest [ShellTest] $ C:\bin\sh.exe -xe C:\Windows\TEMP\hudson7189706247470481416.sh Build step 'Execute shell' marked build as failure Finished: FAILURE I am trying to debug the problem by creating the above as simple as possible. Is there a way to examine the temporary hudson*.sh file before it gets deleted? The content of the Command window in the jenkins job configuration page is empty so there is nothing in there that should trigger any errors. I don't understand why this simple test would fail. Regards -- Nicholas Yue Graphics - RenderMan, Visualization, OpenGL, HDF5 Custom Dev - C++ porting, OSX, Linux, Windows Management - Recruitment, career management http://www.proceduralinsight.com/ http://au.linkedin.com/in/nicholasyue
[JIRA] (JENKINS-13549) Duplicate test results are shown for grails projectsgr
[ https://issues.jenkins-ci.org/browse/JENKINS-13549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162875#comment-162875 ] kiy0taka edited comment on JENKINS-13549 at 5/17/12 5:49 AM: - If you set 'target/test-reports/\*.xml' in 'Publish JUnit test report' configuration, please change to 'target/test-reports/TEST-*.xml'. was (Author: kiy0taka): If you set 'target/test-reports/*.xml' in 'Publish JUnit test report' configuration, please change to 'target/test-reports/TEST-*.xml'. Duplicate test results are shown for grails projectsgr -- Key: JENKINS-13549 URL: https://issues.jenkins-ci.org/browse/JENKINS-13549 Project: Jenkins Issue Type: Bug Components: core, grails Reporter: Ravi Teja Lokineni Assignee: jeffg2one Labels: grails Attachments: dup_tests.png, dup_tests_1.png, dup_tests_1.png This started happening recently. PFA the attached screenshots. Each failed testcase is printed twice. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
