[JIRA] (JENKINS-16877) In Jenkins v1.480.3 encoding problems occur for XML api using a XPath function as leaf
Geoff Cummings commented on JENKINS-16877 In Jenkins v1.480.3 encoding problems occur for XML api using a XPath function as leaf I was able to get the text() functionality back by setting hudson.model.Api.INSECURE=true when starting jenkins Please see the following link: https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-02-16 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16892) Git plugin update breaks builds, if SCM Changes are used in other plugins
Denis Syrokvash commented on JENKINS-16892 Git plugin update breaks builds, if SCM Changes are used in other plugins It's also the "Send To Committers" option enabled in email-ext plugin to cause the issue This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16904) JaCoCo Plugin incorrectly uses POM-configured excludes
Ognjen Bubalo commented on JENKINS-16904 JaCoCo Plugin incorrectly uses POM-configured excludes Hi, To set the excludes, you have to configure it as you said in the job configuration. The JaCoCo Jenkins plugin does not use Maven to generate the coverage report. It uses the JaCoCo API. Cheers, Ogi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16904) JaCoCo Plugin incorrectly uses POM-configured excludes
Ognjen Bubalo closed JENKINS-16904 as Not A Defect JaCoCo Plugin incorrectly uses POM-configured excludes Change By: Ognjen Bubalo (21/Feb/13 8:42 AM) Status: Open Closed Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16904) JaCoCo Plugin incorrectly uses POM-configured excludes
Ognjen Bubalo commented on JENKINS-16904 JaCoCo Plugin incorrectly uses POM-configured excludes If you have more questions, please use the mailing list: http://groups.google.com/group/jenkins-jacoco-plugin-mailing-list This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14447) Clone on Slave Fails
Satpal Chander commented on JENKINS-14447 Clone on Slave Fails I actually misunderstood the comment from Martin Wiklundh, which says: Restarting the slave solved the problem for now. I thought it meant restarting Jenkins The problem actually went away when the machine was rebooted. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16905) java.lang.ClassCastException when triggering build
rere rere created JENKINS-16905 java.lang.ClassCastException when triggering build Issue Type: Bug Assignee: jyrkiput Components: gerrit, gerrit-trigger Created: 21/Feb/13 9:01 AM Description: A build triggered with the gerrit-trigger plugin failed with the following output: FATAL: org.jenkinsci.plugins.gitclient.CliGitAPIImpl cannot be cast to hudson.plugins.git.GitAPI java.lang.ClassCastException: org.jenkinsci.plugins.gitclient.CliGitAPIImpl cannot be cast to hudson.plugins.git.GitAPI at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerBuildChooser.getFirstParent(GerritTriggerBuildChooser.java:107) at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerBuildChooser.prevBuildForChangelog(GerritTriggerBuildChooser.java:79) at hudson.plugins.git.util.BuildChooser.prevBuildForChangelog(BuildChooser.java:114) at hudson.plugins.git.GitSCM.computeChangeLog(GitSCM.java:1286) at hudson.plugins.git.GitSCM.access$1500(GitSCM.java:57) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1234) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1192) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192) at hudson.model.AbstractProject.checkout(AbstractProject.java:1342) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:683) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:588) at hudson.model.Run.execute(Run.java:1568) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Environment: Jenkins ver. 1.502 and Windows Project: Jenkins Priority: Major Reporter: rere rere This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16906) StackOverflowError after build
hugo lassiege created JENKINS-16906 StackOverflowError after build Issue Type: Bug Affects Versions: current Assignee: Sonar Team Components: sonar Created: 21/Feb/13 9:02 AM Description: Hi, I have the following error at the end of the build : [INFO] [17:58:41.251] Executing post-job class org.sonar.plugins.buildbreaker.AlertBreaker [WARN] [17:58:41.252] Rules compliance < 90 [WARN] [17:58:41.252] Coverage < 80 [INFO] [17:58:41.252] Executing post-job class org.sonar.plugins.buildbreaker.ForbiddenConfigurationBreaker [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 2 minutes 12 seconds [INFO] Finished at: Wed Feb 20 17:58:41 CET 2013 [INFO] Final Memory: 60M/495M [INFO] Sonar analysis completed: UNSTABLE FATAL: null java.lang.StackOverflowError at java.io.UnixFileSystem.getBooleanAttributes0(Native Method) at java.io.UnixFileSystem.getBooleanAttributes(UnixFileSystem.java:243) at java.io.File.exists(File.java:750) at hudson.model.User.getOrCreate(User.java:341) at hudson.model.User.get(User.java:331) at hudson.model.User.get(User.java:299) at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:271) at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:325) at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:454) at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1530) at hudson.model.User.getProjects(User.java:448) at hudson.scm.MailAddressResolverImpl.findMailAddressFor(MailAddressResolverImpl.java:19) at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:101) at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:532) at hudson.plugins.git.GitChangeSet.isMailerPropertySet(GitChangeSet.java:291) at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:277) at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:325) at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:454) at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1530) at hudson.model.User.getProjects(User.java:448) at hudson.scm.MailAddressResolverImpl.findMailAddressFor(MailAddressResolverImpl.java:19) at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:101) at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:532) at hudson.plugins.git.GitChangeSet.isMailerPropertySet(GitChangeSet.java:291) at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:277) at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:325) at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:454) at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1530) at hudson.model.User.getProjects(User.java:448) at hudson.scm.MailAddressResolverImpl.findMailAddressFor(MailAddressResolverImpl.java:19) at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:101) at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:532) at hudson.plugins.git.GitChangeSet.isMailerPropertySet(GitChangeSet.java:291) at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:277) at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:325) at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:454) at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1530) at hudson.model.User.getProjects(User.java:448) at hudson.scm.MailAddressResolverImpl.findMailAddressFor(MailAddressResolverImpl.java:19) at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:101) at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:532) Environment: ubuntu Project: Jenkins
[JIRA] (JENKINS-14551) an update which contains added files merged from a branch results in those files having doubled content
sseidel commented on JENKINS-14551 an update which contains added files merged from a branch results in those files having doubled content How to reproduce: Do this on the Jenkins host: cd /tmp mkdir svn ws svnadmin create svn svn mkdir file:///tmp/svn/trunk -m trunk svn mkdir file:///tmp/svn/branch -m branch cd ws svn co file:///tmp/svn/trunk svn co file:///tmp/svn/branch cd branch echo test > singleline svn add singleline svn commit -m added cd ../trunk Now create a Jenkins "freestyle" project with SVN URL file:///tmp/svn/trunk and build it once, then continue in the shell: svn merge -r 2:3 ../branch/ svn commit -m merged Now build the project again. Check the workspace, the file "singleline" will contain 2 lines! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14551) an update which contains added files merged from a branch results in those files having doubled content
sseidel edited a comment on JENKINS-14551 an update which contains added files merged from a branch results in those files having doubled content How to reproduce: Do this on the Jenkins host: cd /tmp mkdir svn ws svnadmin create svn svn mkdir file:///tmp/svn/trunk -m trunk svn mkdir file:///tmp/svn/branch -m branch cd ws svn co file:///tmp/svn/branch cd branch echo test > singleline svn add singleline svn commit -m added Now create a Jenkins "freestyle" project with SVN URL file:///tmp/svn/trunk and build it once, then continue in the shell: cd /tmp/ws svn co file:///tmp/svn/trunk cd trunk svn merge -r 2:3 ../branch/ svn commit -m merged Now build the project again. Check the workspace, the file "singleline" will contain 2 lines! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12188) GIT plug-ins keep lock on workspace file if branch use default insted of master. So unable to clean workspace.
Andrey Upadyshev edited a comment on JENKINS-12188 GIT plug-ins keep lock on workspace file if branch use default insted of master. So unable to clean workspace. Same problem. This is really annoying problem because it's impossible to cleanup a workspace. And after cleanup try, the Git repository became corrupted and all next builds fail until Jenkins slave service is restarted and workspace cleaned. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16877) In Jenkins v1.480.3 encoding problems occur for XML api using a XPath function as leaf
andreas f commented on JENKINS-16877 In Jenkins v1.480.3 encoding problems occur for XML api using a XPath function as leaf Thanks, that did the trick. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13160) Manually triggering a build, which clones a workspace, which is then used by the Multiple SCM Plugin causes job failure
Robert commented on JENKINS-13160 Manually triggering a build, which clones a workspace, which is then used by the Multiple SCM Plugin causes job failure I've added a null check, which helps in our case: https://github.com/Arzie/jenkins-clone-workspace-scm-plugin The plugin can be downloaded from: https://buildhive.cloudbees.com/job/jenkinsci/job/jenkins-clone-workspace-scm-plugin/6/org.jenkins-ci.plugins$clone-workspace-scm/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16877) In Jenkins v1.480.3 encoding problems occur for XML api using a XPath function as leaf
twolfart commented on JENKINS-16877 In Jenkins v1.480.3 encoding problems occur for XML api using a XPath function as leaf I have the same problem: After upgrading to 1.502 (from 1.49x) we can't detect the build status using: /lastBuild/api/xml?xpath=/mavenModuleSetBuild/result/text() It works without the xpath function, but provides the result-tag and not only the content: /lastBuild/api/xml?xpath=/mavenModuleSetBuild/result This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16906) StackOverflowError after build
hugo lassiege updated JENKINS-16906 StackOverflowError after build It is not related to Sonar. The same build without sonar (just a mvn install) give the same stacktrace : [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 1 minute 47 seconds [INFO] Finished at: Thu Feb 21 10:39:53 CET 2013 [INFO] Final Memory: 54M/131M [INFO] channel stopped FATAL: null java.lang.StackOverflowError at sun.nio.cs.UTF_8$Encoder.encodeArrayLoop(UTF_8.java:360) at sun.nio.cs.UTF_8$Encoder.encodeLoop(UTF_8.java:466) at java.nio.charset.CharsetEncoder.encode(CharsetEncoder.java:561) at java.lang.StringCoding$StringEncoder.encode(StringCoding.java:257) at java.lang.StringCoding.encode(StringCoding.java:289) at java.lang.String.getBytes(String.java:954) at java.io.UnixFileSystem.getBooleanAttributes0(Native Method) at java.io.UnixFileSystem.getBooleanAttributes(UnixFileSystem.java:243) at java.io.File.exists(File.java:750) at hudson.model.User.getOrCreate(User.java:341) at hudson.model.User.get(User.java:331) at hudson.model.User.get(User.java:299) at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:271) at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:325) at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:454) at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1530) Change By: hugo lassiege (21/Feb/13 9:43 AM) Component/s: git Component/s: sonar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16906) StackOverflowError after build
kutzi resolved JENKINS-16906 as Duplicate StackOverflowError after build Please search for duplicates before creating new issues. Change By: kutzi (21/Feb/13 9:47 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16849) StackOverflowError involving findMailAddressFor
Eloy Lafuente commented on JENKINS-16849 StackOverflowError involving findMailAddressFor Sorry Nicolas, I did not open a new issue because: 1) Looking for it, I already saw JENKINS-16886 (I forgot to put that piece of information in my early comments, sorry). 2) I ended with that error applying / following your changes here. I'm running right now: 1.2.0 + 1.0.2 and it seems that everything is working (not getting the error in this issue nor in JENKINS-16886 anymore). Ciao This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16886) 500 Error when type the git url during creating new job
Eloy Lafuente commented on JENKINS-16886 500 Error when type the git url during creating new job FYI I commented about a similar error @ JENKINS-16849 and it seems that the 1.2.0 + 1.0.2 combination is working ok here. Ciao This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16849) StackOverflowError involving findMailAddressFor
Eloy Lafuente edited a comment on JENKINS-16849 StackOverflowError involving findMailAddressFor Sorry Nicolas, I did not open a new issue because: 1) Looking for it, I already saw JENKINS-16886 (I forgot to put that piece of information in my early comments, sorry). 2) I ended with that error applying / following your changes here. I'm running right now: 1.2.0 + 1.0.2 and it seems that everything is working (not getting the error in this issue nor in JENKINS-16886 anymore). Ciao Edited: And big thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16278) "Remember me on this computer" does not work, cookie is not accepted in new session
Hendrik Millner commented on JENKINS-16278 "Remember me on this computer" does not work, cookie is not accepted in new session But this date should point to two weeks in the future... Seems to be a problem with long expiryTime = System.currentTimeMillis() + (tokenValiditySeconds * 1000);, for some reason your tokenValiditySeconds seems to be zero (or less). This field is also used as maxCookieAge and is actually never ever touched in Jenkins. It is initialized with protected long tokenValiditySeconds = 1209600; // 14 days and thus should not be zero... Anyone else has an idea on this? I cannot tell anything more without extra debugging information, but since I cannot reproduce the error on my system we would need to do this on your system. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16827) console display wrong build number when triggering a new build
Louis Roché updated JENKINS-16827 console display wrong build number when triggering a new build Change By: Louis Roché (21/Feb/13 10:08 AM) Component/s: all-changes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16903) JaCoCo Plugin marks build as UNSTABLE, but the coverage was sufficient
Ognjen Bubalo closed JENKINS-16903 as Not A Defect JaCoCo Plugin marks build as UNSTABLE, but the coverage was sufficient Change By: Ognjen Bubalo (21/Feb/13 10:20 AM) Status: Open Closed Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16903) JaCoCo Plugin marks build as UNSTABLE, but the coverage was sufficient
Ognjen Bubalo commented on JENKINS-16903 JaCoCo Plugin marks build as UNSTABLE, but the coverage was sufficient Hi, This is not a bug, but it will change with the next release. Check this thread: https://groups.google.com/d/topic/jenkins-jacoco-plugin-mailing-list/pzHm98RJjB8/discussion Cheers, Ogi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16837) Don't change build status
Ognjen Bubalo resolved JENKINS-16837 as Fixed Don't change build status Will be fixed in the next release. Change By: Ognjen Bubalo (21/Feb/13 10:21 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14551) an update which contains added files merged from a branch results in those files having doubled content
sseidel edited a comment on JENKINS-14551 an update which contains added files merged from a branch results in those files having doubled content How to reproduce: Do this on the Jenkins host: cd /tmp mkdir svn ws svnadmin create svn svn mkdir file:///tmp/svn/trunk -m trunk svn mkdir file:///tmp/svn/branch -m branch cd ws svn co file:///tmp/svn/branch cd branch echo test > singleline svn add singleline svn commit -m added Now create a Jenkins "freestyle" project with SVN URL file:///tmp/svn/trunk and build it once, then continue in the shell: cd /tmp/ws svn co file:///tmp/svn/trunk cd trunk svn merge -r 2:3 ../branch/ svn commit -m merged Now build the project again. Check the workspace, the file "singleline" will contain 2 lines! Reproducible with: Jenkins 1.502, Subversion Plugin 1.45, Host SVN 1.6.12 (Debian/CollabNet). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16907) Conflict with standard clover plugin
Alexander Menk created JENKINS-16907 Conflict with standard clover plugin Issue Type: Bug Assignee: sogabe Components: cloverphp-plugin Created: 21/Feb/13 10:29 AM Description: The plugin seems to conflict with the standard plugin. Is there a way so that both can be installed? Exception: java.lang.IllegalArgumentException: CloverPublisher is ambiguous; matches both org.jenkinsci.plugins.cloverphp.CloverPublisher and hudson.plugins.clover.CloverPublisher Stacktrace: javax.servlet.ServletException: java.lang.IllegalArgumentException: CloverPublisher is ambiguous; matches both org.jenkinsci.plugins.cloverphp.CloverPublisher and hudson.plugins.clover.CloverPublisher at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:615) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) 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:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) 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.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) Project: Jenkins Priority: Major Reporter: Alexander Menk This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16908) As a plugin administrator, I want to close Github pull requests whose builds wasn't built successfully
Manuel de la Peña created JENKINS-16908 As a plugin administrator, I want to close Github pull requests whose builds wasn't built successfully Issue Type: Improvement Affects Versions: current Assignee: Honza Brázdil Components: ghprb Created: 21/Feb/13 11:16 AM Description: A plugin administrator could have the ability to automatically close tested pulls if associated build wasn't successfull. Plugin administrator will be able to enable/disable this ability for every build. Fix Versions: current Project: Jenkins Labels: github pull_request Priority: Major Reporter: Manuel de la Peña This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13160) Manually triggering a build, which clones a workspace, which is then used by the Multiple SCM Plugin causes job failure
Robert edited a comment on JENKINS-13160 Manually triggering a build, which clones a workspace, which is then used by the Multiple SCM Plugin causes job failure I've added a null check, which seemed to help in our case: https://github.com/Arzie/jenkins-clone-workspace-scm-plugin Unfortunately, now we get a NPE somewhere upstream . I'm trying to fix it now and will push when it's done. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16579) Lines not counted
Ognjen Bubalo commented on JENKINS-16579 Lines not counted Hi, Have you found a solution? Ogi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16899) jacoco plugin exception java.lang.instrument.IllegalClassFormatException: Error while instrumenting class
Ognjen Bubalo commented on JENKINS-16899 jacoco plugin exception java.lang.instrument.IllegalClassFormatException: Error while instrumenting class Hi, Please ask the question on the mailing list: http://groups.google.com/group/jenkins-jacoco-plugin-mailing-list Thanks, Ogi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16909) SSH Slave + Sonar breaks the build
Michael Pailloncy
created JENKINS-16909
SSH Slave + Sonar breaks the build
Issue Type:
Bug
Affects Versions:
current
Assignee:
Sonar Team
Components:
sonar
Created:
21/Feb/13 11:41 AM
Description:
Hi,
We've recently passed the slaves strategy connection to SSH strategy (previously in JNLP mode).
Everything is well, but Sonar analysis launched in Post Build Action broke the build (mvn no found).
Here is the error :
...
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 14:26.080s
[INFO] Finished at: Thu Feb 21 12:12:04 CET 2013
[INFO] Final Memory: 54M/410M
[INFO]
[myproject] $ mvn -f /path/to/.jenkins/workspace/myproject/pom.xml -e -B sonar:sonar -V -U -Dpmd.failOnViolation=false -Dmaven.repo.local=${WORKSPACE}/.repository -Dgwt.logLevel=ERROR -Dsonar.jdbc.driver=com.mysql.jdbc.Driver -Dsonar.jdbc.url="" -Dsonar.host.url="" href="http://url.sonar:9000">http://url.sonar:9000
FATAL: L'exécution de la commande a échoué.
java.io.IOException: Cannot run program "mvn" (in directory "/path/to/.jenkins/workspace/myproject"): java.io.IOException: error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:460)
at hudson.Proc$LocalProc.(Proc.java:244)
at hudson.Proc$LocalProc.(Proc.java:216)
at hudson.Launcher$LocalLauncher.launch(Launcher.java:763)
at hudson.Launcher$ProcStarter.start(Launcher.java:353)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:988)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:955)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
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 hudson.remoting.Engine$1$1.run(Engine.java:58)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.io.IOException: java.io.IOException: error=2, No such file or directory
at java.lang.UNIXProcess.(UNIXProcess.java:148)
at java.lang.ProcessImpl.start(ProcessImpl.java:65)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:453)
... 16 more 12:12:48 Sonar analysis completed: FAILURE
Build step 'Sonar' changed build result to FAILURE
Build step 'Sonar' marked build as failure
Notifying upstream projects of job completion
Finished: FAILURE
The main build is a maven type build.
If I rollback to JNLP strategy to connect slaves, the build is OK.
This bug seems to be the same as : https://issues.jenkins-ci.org/browse/JENKINS-6718
But the Jenkins version is older than this, and I haven't got any answers to my comment. Anyone has a workaround for this issue ?
Thanks in advance from any help !
Michaël Pailloncy
Environment:
Jenkins 1.502 - Maven 3.0.3 - Sonar plugin 2.0 - JDK 1.6
Project:
Jenkins
Priority:
Major
Reporter:
Michael Pailloncy
This message is automatically generated by JIRA.
If you think it
[JIRA] (JENKINS-16909) SSH Slave + Sonar breaks the build
Michael Pailloncy updated JENKINS-16909 SSH Slave + Sonar breaks the build Change By: Michael Pailloncy (21/Feb/13 11:43 AM) Component/s: ssh-slaves This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14730) Support File & Multi Extended Choice parameters
Roni Licht commented on JENKINS-14730 Support File & Multi Extended Choice parameters Hi Steven, the main target on this issue was to improve the parameters delivery to jobs from the MultiJob phase. This is achieved by our last fix which based on the triggered-parametrized plugin. Regards to your question, I checked it and found that the MultiJob plugin works in harmony with the Conditional BuildStep plugin. So the best way to that, as Devin offered, is to create in your multi job a conditional step that the step to run if the condition is met will be a MultiJob Phase with all the logic you need. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16910) Email Ext-Plugin doesn't work with Jenkins 1.502
Claudia Drabetz created JENKINS-16910 Email Ext-Plugin doesn't work with Jenkins 1.502 Issue Type: Bug Affects Versions: current Assignee: Alex Earl Components: email-ext Created: 21/Feb/13 12:16 PM Description: email ext-plugin: cannot make default settings like System Admin E-mail Address = Status Code 404 (Email adress is real!!!) in the job I get following error message Status Code: 500 Exception: java.lang.NullPointerException Stacktrace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:615) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) 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:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) 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.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) 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 org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) 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:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Caused by: java.lang.NullPointerException at hudson.plugins.emailext.EmailRecipientUtils.convertRecipientString(EmailRecipientUtils.java:32) at hudson.plugins.emailext.EmailRecipientUtils.validateFormRecipientList(EmailRecipientUtils.java:82) at hudson.plugins.emailext.ExtendedEmailPublisherDescriptor.doRecipientListRecipientsCheck(ExtendedEmailPublisherDescriptor.java:430) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.in
[JIRA] (JENKINS-2413) [Email plugin] Read parameters/variables used during build
lloyd roles commented on JENKINS-2413 [Email plugin] Read parameters/variables used during build Why is it that we can't use a build parameter in the recipient field? I've tried similar combo's to those documented above by asalicetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16910) Email Ext-Plugin doesn't work with Jenkins 1.502
Alex Earl commented on JENKINS-16910 Email Ext-Plugin doesn't work with Jenkins 1.502 Do you have Mailer plugin installed and enabled? Just so you know, email-ext is tested only with the latest LTS release (1.480.3 right now). Bugs on versions newer than that will not be given high priority. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10089) Support for 3.7
Lorenzo Bettini assigned JENKINS-10089 to Lorenzo Bettini Support for 3.7 Change By: Lorenzo Bettini (21/Feb/13 12:43 PM) Assignee: jutzig Lorenzo Bettini This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10089) Support for 3.7
Lorenzo Bettini resolved JENKINS-10089 as Fixed Support for 3.7 This is finally fixed I've setup a crawler (https://github.com/jenkinsci/backend-crawler) that periodically generates a json file with also recent releases (including 3.7 and 4.2); the crawled json file is taken from here https://github.com/jenkinsci/buckminster-plugin/blob/master/updates/buckminster.json you can now select also 3.7 and 4.2 versions of Buckminster to install Change By: Lorenzo Bettini (21/Feb/13 12:45 PM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-3265) Reload Configuration from Disk (or POSTing config.xml) loses info on running builds
Patrick Byrne commented on JENKINS-3265 Reload Configuration from Disk (or POSTing config.xml) loses info on running builds Seeing this in 1.492 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16912) CI-Game Plug-in fails: Null-pointer exception
Chris Engler created JENKINS-16912 CI-Game Plug-in fails: Null-pointer exception Issue Type: Bug Assignee: redsolo Components: ci-game Created: 21/Feb/13 1:18 PM Description: After the successful vbuild, the game failes the job. log: [ci-game] evaluating rule: Changed number of compiler warnings ERROR: Publisher hudson.plugins.cigame.GamePublisher aborted due to exception java.lang.NullPointerException at hudson.plugins.cigame.model.ScoreCard.record(ScoreCard.java:42) at hudson.plugins.cigame.model.ScoreCard.record(ScoreCard.java:111) at hudson.plugins.cigame.GamePublisher.perform(GamePublisher.java:60) at hudson.plugins.cigame.GamePublisher.perform(GamePublisher.java:45) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:785) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) at hudson.model.Run.execute(Run.java:1601) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Environment: Windows XP, Jenkins 1.500, CI game v1.18 Project: Jenkins Priority: Major Reporter: Chris Engler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16911) An invalid git reference repository path now causes clone to fail, previously did not fail
markewaite created JENKINS-16911 An invalid git reference repository path now causes clone to fail, previously did not fail Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 21/Feb/13 1:17 PM Description: The git plugin "Advanced" configuration section accepts a "reference" repository path. Previously, if there was a value in that path and if that path existed, then the --reference argument was added to the "git clone" and the clone was able to dramatically reduce the time to clone and the disc space used by that cloned copy of the repository, especially for large repositories. With the plugin version 1.2.0, if a reference value is given, it must exist, otherwise the clone operation fails with a message in the stack trace that the reference repository does not exist. That is very inconvenient for my use case, since some of my slave agents have the reference repository in that location, and others do not. Previously, that meant some of the slaves needed more disc space than others to clone this large repository, but they were still able to clone the repository. With the new implementation, if the reference directory does not exist on all slaves, I must either remove the reference argument or must assure that all slaves have that reference directory available. Stack trace is: ERROR: Error cloning remote repo 'origin' : Could not clone git://mwaite6.ptcnet.ptc.com/git/mwaite/bin.git hudson.plugins.git.GitException: Could not clone git://mwaite6.ptcnet.ptc.com/git/mwaite/bin.git at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.clone(CliGitAPIImpl.java:218) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1002) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:941) at hudson.FilePath.act(FilePath.java:852) at hudson.FilePath.act(FilePath.java:834) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:941) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1113) at hudson.model.AbstractProject.checkout(AbstractProject.java:1256) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:590) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:495) at hudson.model.Run.execute(Run.java:1502) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: hudson.plugins.git.GitException: Reference path does not exist: /var/cache/git/repo-does-not-exist.git at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.clone(CliGitAPIImpl.java:206) ... 14 more Trying next repository ERROR: Could not clone repository FATAL: Could not clone hudson.plugins.git.GitException: Could not clone at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1014) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:941) at hudson.FilePath.act(FilePath.java:852) at hudson.FilePath.act(FilePath.java:834) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:941) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1113) at hudson.model.AbstractProject.checkout(AbstractProject.java:1256) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:590) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:495) at hudson.model.Run.execute(Run.java:1502) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Environment: Linux master server with job tied to execute on master node Project: Jenkins
[JIRA] (JENKINS-16913) Warning use POST method on click to 'Build now' in a context menu
Michael Pailloncy created JENKINS-16913 Warning use POST method on click to 'Build now' in a context menu Issue Type: Bug Assignee: Unassigned Attachments: context-menu-build-now.PNG, warning-use-POST-method.PNG Components: core Created: 21/Feb/13 1:46 PM Description: Hi, A warning is shown when clicking on the 'Build now' link in a context menu (attachment context-menu-build-now.png) of a job (see attachment warning-use-POST-method.png). This message makes sense if the build is triggered externally (by a script or something else), but not when clicking on 'Build now' in Jenkins. Michaël Environment: Jenkins 1.502 Project: Jenkins Priority: Minor Reporter: Michael Pailloncy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15846) Deadlock during Maven builds Parsing POM step
Jesse Glick assigned JENKINS-15846 to Jesse Glick Deadlock during Maven builds Parsing POM step Change By: Jesse Glick (21/Feb/13 2:02 PM) Assignee: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15846) Deadlock during Maven builds Parsing POM step
Jesse Glick commented on JENKINS-15846 Deadlock during Maven builds Parsing POM step Possible workaround being tested: add to slave JVM args: -Dorg.apache.maven.wagon.providers.http.commons.logging.LogFactory.HashtableImpl=java.util.Hashtable This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16914) Specifying multiple git repositories to git plugin causes "git fetch" to fail on all repos after first repo
markewaite created JENKINS-16914 Specifying multiple git repositories to git plugin causes "git fetch" to fail on all repos after first repo Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 21/Feb/13 2:23 PM Description: If I specify multiple git repositories to the git plugin by clicking the "Add" button in the "Repositories" area of the git section of the job configuration screen, then the "git fetch" for each added repository will fail with the message that the remote repository being fetched is invalid. In this example, I assigned the name "origin-mwaite1" to the second repository. ERROR: Problem fetching from origin-mwaite1 / origin-mwaite1 - could be unavailable. Continuing anyway hudson.plugins.git.GitException: Command "git fetch -t origin-mwaite1 +refs/heads/:refs/remotes/origin-mwaite1/" returned status code 128: stdout: stderr: fatal: 'origin-mwaite1' does not appear to be a git repository fatal: The remote end hung up unexpectedly I suspect the plugin has missed the necessary step of defining the remote repository with "git remote add" if the remote is not already defined in the working repository. This is only using the Git plugin, not any other plugin. This is not related to any "multiple SCM" plugin topics, nor to any interaction between other plugins and the Git plugin. Environment: Linux master server using either master node or any Linux slave agent Project: Jenkins Priority: Minor Reporter: markewaite This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13222) Allow job selection with fixed job names to contain variables without requiring job permissions for authenticated users
Daniel Beck updated JENKINS-13222 Allow job selection with fixed job names to contain variables without requiring job permissions for authenticated users Attached a patch for 1.25. Note that there might be parameter values that include forward slashes, so we need to determine where the first parameter starts. This assumes there's no job name with 'equal' character. A proper solution probably uses a configurable separation char, or uses a second text field for parameter filtering altogether, especially since the UI is misleading: Filtering only works for "latest successful build" AFAICT. Change By: Daniel Beck (21/Feb/13 2:41 PM) Attachment: copyartifact-1.25-patch.diff This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16914) Specifying multiple git repositories to git plugin causes "git fetch" to fail on all repos after first repo
Johannes Haseitl commented on JENKINS-16914 Specifying multiple git repositories to git plugin causes "git fetch" to fail on all repos after first repo I'm having the same issue. The repository in the workspace only contains the alphabetically first remote name (I used "gitolite" and "zdc" - only "gitolite" appears). Cloning the remote Git repository Cloning repository ssh://gitolite@XXX/sandbox_derhasi git --version git version 1.7.10.4 Fetching upstream changes from gitolite Fetching upstream changes from zdc ERROR: Problem fetching from zdc / zdc - could be unavailable. Continuing anyway. hudson.plugins.git.GitException: Command "/usr/bin/git fetch -t zdc +refs/heads/master:refs/remotes/zdc/master" returned status code 128: stdout: stderr: fatal: 'zdc' does not appear to be a git repository fatal: The remote end hung up unexpectedly at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:772) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:738) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.fetch(CliGitAPIImpl.java:160) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1023) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:941) at hudson.FilePath.act(FilePath.java:787) at hudson.FilePath.act(FilePath.java:769) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:941) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1113) at hudson.model.AbstractProject.checkout(AbstractProject.java:1195) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:573) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:462) at hudson.model.Run.run(Run.java:1404) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) I tried to find the specific lines of code in github, but as I'm no java guy, I really did not get anything Would be great someone could fix that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12421) Add pre-send step to email-ext that can modify the mail message object
Markus Hjerto commented on JENKINS-12421 Add pre-send step to email-ext that can modify the mail message object Thank you very much, Chris. Your script works perfectly! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16914) Specifying multiple git repositories to git plugin causes "git fetch" to fail on all repos after first repo
markewaite commented on JENKINS-16914 Specifying multiple git repositories to git plugin causes "git fetch" to fail on all repos after first repo I believe the intended workflow for this use of the plugin was that multiple git remotes could contribute changes to a single Jenkins job. That Jenkins job would merge the changes from all the remote repos together, then if the job was successful, it would push the changes to a single central repository. Since only one remote now seems to be added to the Jenkins repository, that workflow won't work until this bug is fixed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16851) Strategy GerritTrigger missing with git plugin 1.1.28
SCM/JIRA link daemon commented on JENKINS-16851 Strategy GerritTrigger missing with git plugin 1.1.28 Code changed in jenkins User: Robert Sandell Path: gerrithudsontrigger/pom.xml gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTriggerBuildChooser.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/155ab6790a33b6f0b229976a40f5ee5f64d1ce22 Log: Removed use of deprecated APIs for git BuildChooser Followup fix for JENKINS-16851 which is fixed in git plugin v. 1.2.0 this commit should remove any use of deprecated APIs after the introduction of gitclient plugin. Change-Id: Ibaa11fe9e06150555af675aae1a32f29cb15aab3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16844) Triggering a build from the context menu produces a warning when security is enabled
Jesse Glick assigned JENKINS-16844 to Jesse Glick Triggering a build from the context menu produces a warning when security is enabled Change By: Jesse Glick (21/Feb/13 3:13 PM) Assignee: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16844) Triggering a build from the context menu produces a warning when security is enabled
Jesse Glick updated JENKINS-16844 Triggering a build from the context menu produces a warning when security is enabled Change By: Jesse Glick (21/Feb/13 3:15 PM) Component/s: gui Component/s: security Component/s: ldap This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16844) Triggering a build from the context menu produces a warning when security is enabled
Jesse Glick commented on JENKINS-16844 Triggering a build from the context menu produces a warning when security is enabled @antwnis: your curl command ought to work since you are passing a token. If not, it is something else. Do not discuss in this issue which is about the context menu. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16659) TriggerBuilder builds based on parameter value should be listed as downstream builds
Benjamin Kemper commented on JENKINS-16659 TriggerBuilder builds based on parameter value should be listed as downstream builds Thanks! I've used the RC and it did the trick. When is it expected to be released? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16659) TriggerBuilder builds based on parameter value should be listed as downstream builds
Benjamin Kemper resolved JENKINS-16659 as Fixed TriggerBuilder builds based on parameter value should be listed as downstream builds Fixed in 2.17-RC. Change By: Benjamin Kemper (21/Feb/13 3:27 PM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16851) Strategy GerritTrigger missing with git plugin 1.1.28
rsandell resolved JENKINS-16851 as Fixed Strategy GerritTrigger missing with git plugin 1.1.28 Released in Git Plugin 1.2.0 Gerrit Trigger Plugin 2.8.0 Change By: rsandell (21/Feb/13 3:31 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13659) Migrating to Jenkins 1.462 : Bad version number in .class file (unable to load class com.google.common.collect.ImmutableSet)
Jesse Glick commented on JENKINS-13659 Migrating to Jenkins 1.462 : Bad version number in .class file (unable to load class com.google.common.collect.ImmutableSet) @brianpreuss: @cmueller: your problem looks quite different (Result → Stapler.CONVERT_UTILS → HttpServlet) and would better be filed separately. Probably specific to running native Maven projects on JDK 5 using Jenkins hosted on Tomcat 7. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Jesse Glick updated JENKINS-16863 After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable Unrelated to JENKINS-16862 I think. Change By: Jesse Glick (21/Feb/13 3:35 PM) Labels: exception job plugin Component/s: groovy-postbuild Component/s: mail Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Jesse Glick assigned JENKINS-16863 to wolfs After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable Change By: Jesse Glick (21/Feb/13 3:35 PM) Assignee: wolfs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14699) hg clone adding "@2" to end of clone destination path
Jesse Glick resolved JENKINS-14699 as Not A Defect hg clone adding "@2" to end of clone destination path You have asked that your job be capable of multiple concurrent builds, so Jenkins is obliging by creating multiple workspaces for it. Change By: Jesse Glick (21/Feb/13 3:38 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14699) hg clone adding "@2" to end of clone destination path
Jesse Glick updated JENKINS-14699 hg clone adding "@2" to end of clone destination path Change By: Jesse Glick (21/Feb/13 3:37 PM) Component/s: core Component/s: mercurial This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16916) Create easier method to use content tokens in groovy templates
Alex Earl created JENKINS-16916 Create easier method to use content tokens in groovy templates Issue Type: Improvement Assignee: Alex Earl Components: email-ext Created: 21/Feb/13 3:41 PM Description: Currently you have to import all the content token plugins you want to use, create an instance and then call the getContent method to use the email-ext tokens in a groovy template. It would be nice to have an easier method to do this, where you could do something like: ENV(var: 'MY_VAR') To use the ENV content token. Project: Jenkins Priority: Minor Reporter: Alex Earl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16917) status 500 when trying to save build configuration
ramzez ramzez created JENKINS-16917 status 500 when trying to save build configuration Issue Type: Bug Assignee: kutzi Components: downstream-ext Created: 21/Feb/13 3:41 PM Description: When trying to use downstream-ext plug job cannot be saved with and the following error is generated: Status Code: 500 Exception: java.lang.ClassCastException: hudson.plugins.downstream_ext.DownstreamTrigger cannot be cast to hudson.tasks.BuildTrigger Stacktrace: javax.servlet.ServletException: java.lang.ClassCastException: hudson.plugins.downstream_ext.DownstreamTrigger cannot be cast to hudson.tasks.BuildTrigger at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:615) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) 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:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) 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.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:36) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:32) 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 org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) 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:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) 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:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:680) Caused by: java.lang.ClassCastException: hudson.plugins.downstream_ext.DownstreamTrigger cannot be
[JIRA] (JENKINS-16877) In Jenkins v1.480.3 encoding problems occur for XML api using a XPath function as leaf
Jesse Glick resolved JENKINS-16877 as Not A Defect In Jenkins v1.480.3 encoding problems occur for XML api using a XPath function as leaf Support for primitive result sets with the xpath query parameter in the REST API has been dropped. Please retrieve a complete XML (or JSON) document and parse out the bits you need. Change By: Jesse Glick (21/Feb/13 3:43 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16893) Cross Site Scripting Version 1.502
Jesse Glick resolved JENKINS-16893 as Incomplete Cross Site Scripting Version 1.502 Please see https://wiki.jenkins-ci.org/display/JENKINS/Security+Advisories and file all potential security vulnerabilities in the SECURITY component rather than the open bug tracker. Thanks! Change By: Jesse Glick (21/Feb/13 3:47 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14699) hg clone adding "@2" to end of clone destination path
mat007 reopened JENKINS-14699 hg clone adding "@2" to end of clone destination path The "Execute concurrent builds if necessary" check box is unchecked and we don't see multiple concurrent builds (not counting axis of the build matrix of course). Change By: mat007 (21/Feb/13 4:03 PM) Resolution: Not A Defect Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14699) hg clone adding "@2" to end of clone destination path
Jesse Glick commented on JENKINS-14699 hg clone adding "@2" to end of clone destination path Then it is probably specific to matrix jobs, and probably not a bug in that case either: you just need multiple workspaces to handle the concurrent (matrix) builds. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14699) hg clone adding "@2" to end of clone destination path
mat007 commented on JENKINS-14699 hg clone adding "@2" to end of clone destination path I really don't think matrix builds need multiple workspaces as all our projects are matrix based and they don't all create @2 workspaces all the time. Most builds re-use the same workspace, our flagship project builds 30+ times a day and triggers the issue only once a week. Plus it hasn't always been like that : the server has been running for a few years and we have only been experiencing this issue for a few months. Also once a project has switched to @2 it doesn't come back to the regular workspace unless we shutdown jenkins, remove the workspaces manually and re-start jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16777) ArrayIndexOutOfBoundsException when trying to publish the Jacoco report
Ognjen Bubalo resolved JENKINS-16777 as Fixed ArrayIndexOutOfBoundsException when trying to publish the Jacoco report New release will fix it Change By: Ognjen Bubalo (21/Feb/13 4:57 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16777) ArrayIndexOutOfBoundsException when trying to publish the Jacoco report
SCM/JIRA link daemon commented on JENKINS-16777 ArrayIndexOutOfBoundsException when trying to publish the Jacoco report Code changed in jenkins User: Ognjen Bubalo Path: src/main/java/hudson/plugins/jacoco/ExecutionFileLoader.java http://jenkins-ci.org/commit/jacoco-plugin/f0843cc3a2ff21d5b2f5676753929192e17cdf61 Log: Fixing JENKINS-16777 ArrayIndexOutOfBoundsException when trying to publish the Jacoco report This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16837) Don't change build status
SCM/JIRA link daemon commented on JENKINS-16837 Don't change build status Code changed in jenkins User: Ognjen Bubalo Path: src/main/java/hudson/plugins/jacoco/JacocoBuildAction.java src/main/java/hudson/plugins/jacoco/JacocoHealthReportThresholds.java src/main/java/hudson/plugins/jacoco/JacocoPublisher.java src/main/java/hudson/plugins/jacoco/report/CoverageReport.java src/main/resources/hudson/plugins/jacoco/JacocoPublisher/config.jelly http://jenkins-ci.org/commit/jacoco-plugin/cb492c16ade3847569bbcb3e72c8bd52024a0077 Log: Fixing JENKINS-16837: Don't change build status Compare: https://github.com/jenkinsci/jacoco-plugin/compare/a1243a6a16bc...cb492c16ade3 – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16300) Dashborad plugin shows 2008R2 / 2012 connected slaves as offline
Marco Ambu commented on JENKINS-16300 Dashborad plugin shows 2008R2 / 2012 connected slaves as offline I have flagged this issue to the person who contributed this portlet. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15466) Fatal Error No Class Definition found for Kernel32
Bruce Rust commented on JENKINS-15466 Fatal Error No Class Definition found for Kernel32 @dogfood - I use 1.480.1 LTS and after upgrading to this version from 1.447.2 some of my nodes starting have the issues but others do not. I have the issue with SVN updates when they do the deleting of files as part of the cleanup. So is the issue related to the plugin or is it part of the core Jenkins? As for the fix above, when will that be integrated into the LTS versions because this is killing us. The only good work around I have found so far is to remove the workspace files for the problem build and then build again. The removal is a manual process. Setting SVN to do a fresh checkout does not seem to work either. Anyone else have options? If we reverted, what version should we downgrade to? Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16528) Jenkins master node crashes often when viewing console logs of builds on slaves
Geoff Rowell commented on JENKINS-16528 Jenkins master node crashes often when viewing console logs of builds on slaves Since I disabled the timestamper plugin, we've not seen the problem. That, and the consistent mention of the same plugin in the JVM dumps, seems to indicate a flaw in the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12858) With Maven3 when build fails does not show exceptions
evernat resolved JENKINS-12858 as Not A Defect With Maven3 when build fails does not show exceptions If it can probably be closed, then resolving as "not a defect" Change By: evernat (21/Feb/13 6:38 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12441) Update child jobs using Remote API dosen´t reload the job´s config and changes are not applied
evernat commented on JENKINS-12441 Update child jobs using Remote API dosen´t reload the job´s config and changes are not applied Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16917) status 500 when trying to save build configuration
kutzi commented on JENKINS-16917 status 500 when trying to save build configuration Caused by core commit https://github.com/jenkinsci/jenkins/commit/36342d71e29e0620f803a7470ce96c61761648d8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10481) Expose fingerprint information from builds in REST API
drautureau commented on JENKINS-10481 Expose fingerprint information from builds in REST API I'm having the same need: this will help me to get the upstream builds involved in a release (which are locked by me) to get any related data that Jenkins can expose (could be useful to know what this release contains). @Ramon, seems that https://github.com/ramonvanalteren/pyjenkinsci is now https://github.com/ramonvanalteren/jenkinsapi ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14089) JUnit report - Quarantine intermittent tests
samuel nobs commented on JENKINS-14089 JUnit report - Quarantine intermittent tests does anyone know if this is eventually going to end up in jenkins, or do we need to write a plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16917) status 500 when trying to save build configuration
Jesse Glick commented on JENKINS-16917 status 500 when trying to save build configuration I do not think there is anything wrong with the core code. I did try to make BuildTrigger.DescriptorImpl be more type-safe so that it would restrict the instances to subtypes of BuildTrigger but this did not type-check for complex reasons (i.e. Jenkins abuses Java generics). Probably BuildTrigger.DescriptorImpl should just be final. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16917) status 500 when trying to save build configuration
kutzi commented on JENKINS-16917 status 500 when trying to save build configuration The problem with DownstreamTrigger is that it uses a subtype of BuildTrigger.DescriptorImpl as its descriptor, but is no subtype of BuildTrigger itself. I see now that that was a bad idea and am fixing it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16917) status 500 when trying to save build configuration
SCM/JIRA link daemon commented on JENKINS-16917 status 500 when trying to save build configuration Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/tasks/BuildTrigger.java http://jenkins-ci.org/commit/jenkins/fd0657ef9e34f8ce9c8802babec3873f8133ca99 Log: JENKINS-16917 hudson.plugins.downstream_ext.DownstreamTrigger.DescriptorImpl should not be extending BuildTrigger.DescriptorImpl since it does not produce a BuildTrigger from newInstance. (Generally there is no reason to subclass a Descriptor type which is already an @Extension rather than an explicit abstract supertype, but this is a bit more conservative change than just making it final.) – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16917) status 500 when trying to save build configuration
SCM/JIRA link daemon commented on JENKINS-16917 status 500 when trying to save build configuration Code changed in jenkins User: Christoph Kutzinski Path: src/main/java/hudson/plugins/downstream_ext/DownstreamTrigger.java src/main/resources/hudson/plugins/downstream_ext/DownstreamTrigger/config.jelly http://jenkins-ci.org/commit/downstream-ext-plugin/a695bc2741ec539684ce4ad31b28f47de9f7371e Log: [FIXED JENKINS-16917] do not extends BuildTrigger.DescriptorImpl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16917) status 500 when trying to save build configuration
SCM/JIRA link daemon resolved JENKINS-16917 as Fixed status 500 when trying to save build configuration Change By: SCM/JIRA link daemon (21/Feb/13 7:48 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15973) Show head and tail for long console outputs
jieryn updated JENKINS-15973 Show head and tail for long console outputs Change By: jieryn (21/Feb/13 8:13 PM) Assignee: jieryn Component/s: core Component/s: console-column This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14880) BUILD_ID doesn't contain hostname if config hasn't been saved after initial startup
jieryn updated JENKINS-14880 BUILD_ID doesn't contain hostname if config hasn't been saved after initial startup Change By: jieryn (21/Feb/13 8:14 PM) Assignee: jieryn Component/s: core Component/s: config-autorefresh This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14874) Loading Overlay IE9
jieryn updated JENKINS-14874 Loading Overlay IE9 Change By: jieryn (21/Feb/13 8:15 PM) Assignee: jieryn Component/s: configure-job-column This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15156) Builds disappear from build history after completion
SCM/JIRA link daemon commented on JENKINS-15156 Builds disappear from build history after completion Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/AbstractProject.java core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java http://jenkins-ci.org/commit/jenkins/09c7cf6ad7cfb4d88d6d8936f29b13f3ca187875 Log: JENKINS-15156 Found a problem with uninitialized run maps in new Maven modules. Not observed in actual usage, but reproducible (for me at least, though apparently not ci.jenkins-ci.org) in a test: java.lang.AssertionError: null at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:628) at jenkins.model.lazy.AbstractLazyLoadRunMap.all(AbstractLazyLoadRunMap.java:581) at jenkins.model.lazy.AbstractLazyLoadRunMap.entrySet(AbstractLazyLoadRunMap.java:243) at java.util.AbstractMap$2$1.(AbstractMap.java:378) at java.util.AbstractMap$2.iterator(AbstractMap.java:377) at hudson.util.RunList.iterator(RunList.java:103) at hudson.util.RunList.size(RunList.java:114) at hudson.maven.MavenProjectTest.testDeleteSetBuildDeletesModuleBuilds(MavenProjectTest.java:159) – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14880) BUILD_ID doesn't contain hostname if config hasn't been saved after initial startup
Henrik Skupin commented on JENKINS-14880 BUILD_ID doesn't contain hostname if config hasn't been saved after initial startup Jenkins correctly auto-detects the hostname and port as I have mentioned in my initial comment. The problem is the value of the $BUILD_URL variable, which is empty. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16917) status 500 when trying to save build configuration
dogfood commented on JENKINS-16917 status 500 when trying to save build configuration Integrated in jenkins_main_trunk #2289 JENKINS-16917 hudson.plugins.downstream_ext.DownstreamTrigger.DescriptorImpl should not be extending BuildTrigger.DescriptorImpl since it does not produce a BuildTrigger from newInstance. (Revision fd0657ef9e34f8ce9c8802babec3873f8133ca99) Result = UNSTABLE Jesse Glick : fd0657ef9e34f8ce9c8802babec3873f8133ca99 Files : core/src/main/java/hudson/tasks/BuildTrigger.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16918) @RequirePOST and similar should send a 405
Jesse Glick
created JENKINS-16918
@RequirePOST and similar should send a 405
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
core
Created:
21/Feb/13 8:39 PM
Description:
When a GET request is sent to a resource which (generally for security reasons) requires POST, an appropriate response code should be sent, so that clients such as python-jenkins may properly report the error.
Most such web methods use @RequirePOST, for which currently a 500 is sent because org.kohsuke.stapler.interceptor.RequirePOST$Processor simply throws IllegalAccessException.
Build-like requests use BuildAuthorizationToken which forwards to requirePOST.jelly with a 200, which is no good. (If a token is supplied but is incorrect, it more reasonably sends a 403, via AccessDeniedException.)
Both cases should probably send a 405 ("Method Not Allowed") with Allow: POST, though a 403 would not be inappropriate for the latter case since under some circumstances GET is still allowed for compatibility.
Project:
Jenkins
Priority:
Minor
Reporter:
Jesse Glick
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14730) Support File & Multi Extended Choice parameters
steven armstrong commented on JENKINS-14730 Support File & Multi Extended Choice parameters Hi Roni, As you say it is possible to: 1) Create a multi-job at the create job page in jenkins 2) As a build step on the multi-job create a conditional buildstep 3) When that conditional buildstep is true run a multijob phase as part of the conditional build step. This executes perfectly command wise having the desired effect from a run perspective. The issue though is that the multi-job phase which is run when the conditional buildstep is true does not show up graphically on the multi-job graphical display, meaning an end user can not see that phase being executed unless you go to the console output. So fixing the plug-in to display phases that are nested in a conditional build-step would greatly benefit end users who wish to see what exactly the multijob plugin is executing at build time without having to drill through to the console log. One of the main benefits the multijob brings is that graphical representation of chained jobs and giving the user the ability to see the plugin step through each job in the phase but that is lost if you call the multijob phase in the conditional build step. Hope that makes sense. The other fix is great though regarding the parameters. However, fixing the view for conditional buildsteps would just make the plugin so much more powerfull. Kind Regards, Steven This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-8962) Cannot change parameter value for promotion re-execution
Nathan Overbey commented on JENKINS-8962 Cannot change parameter value for promotion re-execution ok, my friends. I have found a work around. I wrote a script that executes after the promoted job. It strips out the promotion history (xml) from the build job (build.xml). I then post that xml file to http://jenkinsurl/job/test1/config.xml. It takes a bit of scripting because you'll need to find the build.xml file. Would still be nice to have this baked into the plugin in a manor that makes it easy to view the history via UI. My method wacks it in the UI. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15596) Jenkins will not start as a Windows Service after KB2661254
Dirk Kuypers commented on JENKINS-15596 Jenkins will not start as a Windows Service after KB2661254 The same works for me for Jenkins as service, just place the file as jenkins.exe.config into the directory of your jenkins.exe. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14730) Support File & Multi Extended Choice parameters
Roni Licht commented on JENKINS-14730 Support File & Multi Extended Choice parameters I understand your request and it is really nice enhancement, but you commented it on a completely different issue. I suggest you open your last request as a new issue on our project. Thanks Roni This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16300) Dashborad plugin shows 2008R2 / 2012 connected slaves as offline
morlajb commented on JENKINS-16300 Dashborad plugin shows 2008R2 / 2012 connected slaves as offline great , Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15156) Builds disappear from build history after completion
dogfood commented on JENKINS-15156 Builds disappear from build history after completion Integrated in jenkins_main_trunk #2290 JENKINS-15156 Found a problem with uninitialized run maps in new Maven modules. (Revision 09c7cf6ad7cfb4d88d6d8936f29b13f3ca187875) Result = SUCCESS Jesse Glick : 09c7cf6ad7cfb4d88d6d8936f29b13f3ca187875 Files : maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java core/src/main/java/hudson/model/AbstractProject.java core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16919) Email-ext throws NullPointerException when "attach build log" is checked on 1.480.3
Mark Orchard created JENKINS-16919 Email-ext throws NullPointerException when "attach build log" is checked on 1.480.3 Issue Type: Bug Affects Versions: current Assignee: Alex Earl Components: email-ext Created: 21/Feb/13 9:42 PM Description: List of plugins used in project: multiple-scms mercurial subversion nant sonar flexible-publish email-ext I perform a fairly simple build, use the flexible-plugin to only archive on success and then send an email. Without "attach build log" checked everything works, with it checked I get the following error: Run condition [Current build status] enabling perform for step [Archive the artifacts] Archiving artifacts Checking for post-build Performing post-build step Checking if email needs to be generated Email was triggered for: Success Sending email for trigger: Success NOT overriding default server settings, using Mailer to create session messageContentType = text/plain; charset=UTF-8 Request made to attach build log Adding recipients from recipient list Successfully created MimeMessage Sending email to: my.usern...@myplaceofemployment.com ERROR: Could not send email as a part of the post-build publishers. java.lang.NullPointerException at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:311) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:289) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:249) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:718) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:693) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) at hudson.model.Run.execute(Run.java:1546) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Some error occured trying to send the email...check the Jenkins log Environment: OS Windows_NT PROCESSOR_ARCHITECTURE x86 PROCESSOR_ARCHITEW6432 AMD64 java.runtime.version 1.6.0_26-b03 Jenkins war org.jenkins-ci.main:jenkins-war:1.480.3 Project: Jenkins Labels: plugin exception email-ext Priority: Major Reporter: Mark Orchard This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16919) Email-ext throws NullPointerException when "attach build log" is checked on 1.480.3
Alex Earl commented on JENKINS-16919 Email-ext throws NullPointerException when "attach build log" is checked on 1.480.3 What version of email-ext? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13659) Migrating to Jenkins 1.462 : Bad version number in .class file (unable to load class com.google.common.collect.ImmutableSet)
Christian Müller commented on JENKINS-13659 Migrating to Jenkins 1.462 : Bad version number in .class file (unable to load class com.google.common.collect.ImmutableSet) Done: JENKINS-16920 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
