[JIRA] (JENKINS-16796) Git fails to collect commits during build
Mark Waite commented on JENKINS-16796 Git fails to collect commits during build I detected a case where I seemed to be able to "miss" commits from the build, though I think I can explain the reason and why the solution requires clearing the workspace. In my case, I had selected "shallow clone" in the Advanced section and had defined an "excluded region" to include one file. When a commit was made which only modified that file, the plugin correctly did not start the job. That is expected, but because of the "shallow clone", I suspect that the commit was never pulled into the repository at all. My solution was to delete the workspace, clear the "shallow clone" setting, and perform another build. That brought in the missing commit as far as I can tell. 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-16557) Git changes reported if in "excluded regions"
Mark Waite commented on JENKINS-16557 Git changes reported if in "excluded regions" I think the git plugin has the correct behavior in this case. I think the exclusion is intended to prevent polling causing the job to execute when a change is made in a revision which is excluded. I don't think the submission should be hidden from the user by not being included in the change list, since the change will be applied to the working copy and will be visible in the file 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-16940) Git publisher fails with "Invalid id: origin/master" when trying to publish changes
Mark Waite updated JENKINS-16940 Git publisher fails with "Invalid id: origin/master" when trying to publish changes Change By: Mark Waite (23/Feb/13 5:16 AM) Description: Using the git plugin to publish a merged change to a central repository previously was successful. With the 1.2.0 version of the git plugin it is no longer able to push changes to the central repository after they have merged and are successfully built.The stack trace reports:Commencing build of Revision 363396d76a09a12a2f4b5d94fb4e9981e05ad4a9 (origin/proposals)Merging Revision 363396d76a09a12a2f4b5d94fb4e9981e05ad4a9 (origin/proposals) onto masterFATAL: Invalid id: origin/masterjava.lang.IllegalArgumentException: Invalid id: origin/master at org.eclipse.jgit.lib.ObjectId.fromString(ObjectId.java:232) at hudson.plugins.git.GitSCM.computeMergeChangeLog(GitSCM.java:1331) at hudson.plugins.git.GitSCM.access$1200(GitSCM.java:57) at hudson.plugins.git.GitSCM$3.invoke(GitSCM.java:1188) at hudson.plugins.git.GitSCM$3.invoke(GitSCM.java:1133) at hudson.FilePath.act(FilePath.java:852) at hudson.FilePath.act(FilePath.java:834) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1133) 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)Steps to recreate the problem: - configure a Git repository into which the Jenkins user can push changes - create a "master" branch and a "proposals" branch on the Git repository - define a Jenkins job which clones the Git repository with ssh protocol - configure the Jenkins job git plugin to merge from " */proposals " and " */master " branches to the "master-proposals" branch - define a post build action to push the resulting merge to the origin/master branch - Submit a change to the central git repository on the "proposals" branch - Run the Jenkins job to confirm it will combine the master and proposals branches - Confirm the Jenkins job fails to push the combined change = IllegalArgumentException because JGit cannot convert "origin/master" into a SHA1, while the older git plugin ObjectId implementation seemed to make that conversion successfully.Refer to merge-proposals.xml for the job definition I used in my tests. 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-16940) Git publisher fails with "Invalid id: origin/master" when trying to publish changes
markewaite commented on JENKINS-16940 Git publisher fails with "Invalid id: origin/master" when trying to publish changes Refer to https://issues.jenkins-ci.org/browse/JENKINS-16888 for a similar issue with a different symptom but likely the same root cause. 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-16941) Git publisher post build action fails on slave agent - unable to serialize
markewaite created JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Attachments: merge-proposals.xml Components: git Created: 23/Feb/13 5:09 AM Description: Using the git plugin to publish a merged change to a central repository previously was successful from either the master node or a slave agent. With the 1.2.0 version of the git plugin it is no longer able to push changes to the central repository after they have merged and are successfully built on the slave. The stack trace reports: Commencing build of Revision 363396d76a09a12a2f4b5d94fb4e9981e05ad4a9 (origin/proposals) hudson.util.IOException2: remote file operation failed: /var/lib/jenkins/mwaite6-slave/workspace/merge-proposals at hudson.remoting.Channel@4a6ecaf9:fc-agile-2011 at hudson.FilePath.act(FilePath.java:848) at hudson.FilePath.act(FilePath.java:834) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1133) 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: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@7c0a37f8 at hudson.remoting.UserRequest.serialize(UserRequest.java:166) at hudson.remoting.UserRequest.(UserRequest.java:62) at hudson.remoting.Channel.call(Channel.java:671) at hudson.FilePath.act(FilePath.java:841) ... 10 more Caused by: java.io.NotSerializableException: hudson.model.FreeStyleBuild at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1180) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) at hudson.remoting.UserRequest._serialize(UserRequest.java:155) at hudson.remoting.UserRequest.serialize(UserRequest.java:164) ... 13 more Steps to recreate the problem: configure a Git repository into which the Jenkins user can push changes create a "master" branch and a "proposals" branch on the Git repository define a Jenkins job which clones the Git repository with ssh protocol configure the Jenkins job git plugin to merge from "/proposals" and "/master" to "master-proposals" configure the Jenkins job to run on a slave agent (not master) define a post build action to push the resulting merge to the origin/master branch Submit a change to the central git repository on the "proposals" branch Run the Jenkins job to confirm it will combine the master and proposals branches Confirm the Jenkins job fails to push the combined change = IllegalArgumentException because JGit cannot convert "origin/master" into a SHA1, while the older git plugin ObjectId implementation seemed to make that conversion successfully. Refer to merge-proposals.xml for the job definition I used in my tests. Environment: Linux master server, separate Linux or Windows slave
[JIRA] (JENKINS-16940) Git publisher fails with "Invalid id: origin/master" when trying to publish changes
markewaite created JENKINS-16940 Git publisher fails with "Invalid id: origin/master" when trying to publish changes Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Attachments: merge-proposals.xml Components: git Created: 23/Feb/13 5:06 AM Description: Using the git plugin to publish a merged change to a central repository previously was successful. With the 1.2.0 version of the git plugin it is no longer able to push changes to the central repository after they have merged and are successfully built. The stack trace reports: Commencing build of Revision 363396d76a09a12a2f4b5d94fb4e9981e05ad4a9 (origin/proposals) Merging Revision 363396d76a09a12a2f4b5d94fb4e9981e05ad4a9 (origin/proposals) onto master FATAL: Invalid id: origin/master java.lang.IllegalArgumentException: Invalid id: origin/master at org.eclipse.jgit.lib.ObjectId.fromString(ObjectId.java:232) at hudson.plugins.git.GitSCM.computeMergeChangeLog(GitSCM.java:1331) at hudson.plugins.git.GitSCM.access$1200(GitSCM.java:57) at hudson.plugins.git.GitSCM$3.invoke(GitSCM.java:1188) at hudson.plugins.git.GitSCM$3.invoke(GitSCM.java:1133) at hudson.FilePath.act(FilePath.java:852) at hudson.FilePath.act(FilePath.java:834) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1133) 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) Steps to recreate the problem: configure a Git repository into which the Jenkins user can push changes create a "master" branch and a "proposals" branch on the Git repository define a Jenkins job which clones the Git repository with ssh protocol configure the Jenkins job git plugin to merge from "/proposals" and "/master" to "master-proposals" define a post build action to push the resulting merge to the origin/master branch Submit a change to the central git repository on the "proposals" branch Run the Jenkins job to confirm it will combine the master and proposals branches Confirm the Jenkins job fails to push the combined change = IllegalArgumentException because JGit cannot convert "origin/master" into a SHA1, while the older git plugin ObjectId implementation seemed to make that conversion successfully. Refer to merge-proposals.xml for the job definition I used in my tests. Environment: Linux master server executing job on master server Project: Jenkins Priority: Major 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-16939) Missing .png
Dave Abrahams created JENKINS-16939 Missing .png Issue Type: Bug Affects Versions: current Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 23/Feb/13 4:49 AM Description: The white minus sign in the red circle shows up just fine when there's a sync problem, but when the sync is good, the icon is missing. The URL generated for the image is http:///static/3798c065/images/16x16/.png, which looks suspicious to say the least! Environment: Ubuntu 32-bit Project: Jenkins Labels: plugin Priority: Minor Reporter: Dave Abrahams 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 i think looking at the claim plugin (https://wiki.jenkins-ci.org/display/JENKINS/Claim+plugin) and then going from there would be an easy approach, but first we'd need to come up with a list of features we want 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-12629) Using jenkins-cli connecting to HTTPS port fails due to hostname mismatch in certificate
dogfood commented on JENKINS-12629 Using jenkins-cli connecting to HTTPS port fails due to hostname mismatch in certificate Integrated in jenkins_main_trunk #2293 [FIXED JENKINS-12629] (Revision 2edf32221f13e36c2c5c44c9f91a068966b59218) Result = SUCCESS kohsuke : 2edf32221f13e36c2c5c44c9f91a068966b59218 Files : cli/src/main/java/hudson/cli/CLI.java cli/src/main/resources/hudson/cli/client/Messages.properties cli/src/main/java/hudson/cli/NoCheckTrustManager.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-12629) Using jenkins-cli connecting to HTTPS port fails due to hostname mismatch in certificate
SCM/JIRA link daemon resolved JENKINS-12629 as Fixed Using jenkins-cli connecting to HTTPS port fails due to hostname mismatch in certificate Change By: SCM/JIRA link daemon (23/Feb/13 12:07 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-12629) Using jenkins-cli connecting to HTTPS port fails due to hostname mismatch in certificate
SCM/JIRA link daemon commented on JENKINS-12629 Using jenkins-cli connecting to HTTPS port fails due to hostname mismatch in certificate Code changed in jenkins User: Kohsuke Kawaguchi Path: cli/src/main/java/hudson/cli/CLI.java cli/src/main/java/hudson/cli/NoCheckTrustManager.java cli/src/main/resources/hudson/cli/client/Messages.properties http://jenkins-ci.org/commit/jenkins/2edf32221f13e36c2c5c44c9f91a068966b59218 Log: [FIXED JENKINS-12629] Added the -noCertificateCheck option (the option name is consistent with the slave.jar) that lets users bypass the HTTPS certificate check. This allows trivial man-in-the-middle attack, so HTTPS will no longer be HTTPS. – 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-12629) Using jenkins-cli connecting to HTTPS port fails due to hostname mismatch in certificate
Kohsuke Kawaguchi commented on JENKINS-12629 Using jenkins-cli connecting to HTTPS port fails due to hostname mismatch in certificate The reason SSH client doesn't work with the groovy command is because ssh(1) lacks the ability to read a script file for the master. You can work around this relatively easily by reading the script from stdin: ssh yourjenkins.acme.com groovy = < myscript.groovy This has obvious downside that you won't be able to access stdin from your groovy script, but it's probably prettier than the work around that involves the groovysh command. 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-15539) Provide a link to the jacoco.exec
Kohsuke Kawaguchi commented on JENKINS-15539 Provide a link to the jacoco.exec Created https://github.com/jenkinsci/jacoco-plugin/pull/17 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 The workaround I have found that seems to work so far is to set the SVN checkout option "Use 'svn update' as much as possible". That way it doesn't try to do a delete, just does an update. This work around is ok for some jobs, but others really need to use the "Emulate a clean checkout" option to ensure everything is clean. So I guess I am reiterating that this is still a big issue and is there anyway to get a fix into the latest LTS 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-16933) Make Jira plugin write more compact comments
Julien Carsique resolved JENKINS-16933 as Fixed Make Jira plugin write more compact comments Merged in 1.36. Change By: Julien Carsique (22/Feb/13 10:26 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-16933) Make Jira plugin write more compact comments
SCM/JIRA link daemon commented on JENKINS-16933 Make Jira plugin write more compact comments Code changed in jenkins User: Julien Carsique Path: src/main/java/hudson/plugins/jira/Updater.java http://jenkins-ci.org/commit/jira-plugin/da892ae12edce4639224a6c94f716f94375f74ca Log: JENKINS-16933 - format 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-16933) Make Jira plugin write more compact comments
SCM/JIRA link daemon commented on JENKINS-16933 Make Jira plugin write more compact comments Code changed in jenkins User: Julien Carsique Path: src/main/java/hudson/plugins/jira/Updater.java http://jenkins-ci.org/commit/jira-plugin/b233e4a4bebd3d79168966ff8472a152010853bf Log: JENKINS-16933 - More compact Jira comments 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-16938) Information lost when build is stopped by user
Dave Abrahams created JENKINS-16938 Information lost when build is stopped by user Issue Type: Bug Affects Versions: current Assignee: Praqma Support Components: audit-trail, logging Created: 22/Feb/13 10:03 PM Description: When a user clicks the little white-on-red "X" in the Web GUI to stop a job, that fact is not reflected anywhere in the console output or in the build list. This is important information, as the failed build doesn't reflect a problem with the software under construction/test. Environment: Ubuntu Project: Jenkins Labels: jenkins Priority: Major Reporter: Dave Abrahams 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-15538) Show source highlighting on the whole class
SCM/JIRA link daemon commented on JENKINS-15538 Show source highlighting on the whole class Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/plugins/jacoco/report/ClassReport.java src/main/java/hudson/plugins/jacoco/report/CoverageReport.java src/main/java/hudson/plugins/jacoco/report/MethodReport.java src/main/java/hudson/plugins/jacoco/report/SourceAnnotator.java src/main/resources/hudson/plugins/jacoco/report/ClassReport/index.jelly http://jenkins-ci.org/commit/jacoco-plugin/f778bc07de88008fe9862930ba8723da4ea087c1 Log: [FIXED JENKINS-15538] added whole class coverage highlighting The code is refactored a bit so that the same line-by-line annotation code can be used by multiple callers. For the time being, the class coverage highlight is rendered along with the per-method break down, but one might prefer some tweak to this, such as using tabs. Compare: https://github.com/jenkinsci/jacoco-plugin/compare/b7985928f638...f778bc07de88 – 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-15538) Show source highlighting on the whole class
SCM/JIRA link daemon resolved JENKINS-15538 as Fixed Show source highlighting on the whole class Change By: SCM/JIRA link daemon (22/Feb/13 10:00 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-16693) Heap error while polling Git Plug-in after upgrade to 1.1.26.
markewaite commented on JENKINS-16693 Heap error while polling Git Plug-in after upgrade to 1.1.26. Thanks for running the command. A 300 MB output file to answer the question "isRevExcluded" seems excessive. Reverting back to 1.1.21 switched from back from using "git show" to using "git whatchanged". I don't know what issues were being fixed by switching from "git whatchanged" to "git show", but I suspect that they are described in the history of the plugin on github. If it works for you at 1.1.21, that's probably sufficient for now. Eventually the topic will need to be revisited so that the "git show" used in isRevExcluded can be replaced with something faster and more predictable. 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-12206) Parameter in Custom Workspace
evernat resolved JENKINS-12206 as Incomplete Parameter in Custom Workspace No response from the reporter, so resolving as incomplete. Please reopen if the issue is still reproduced. Change By: evernat (22/Feb/13 9:20 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-16919) Email-ext throws NullPointerException when "attach build log" is checked on 1.480.3
Mark Orchard commented on JENKINS-16919 Email-ext throws NullPointerException when "attach build log" is checked on 1.480.3 Cool, thanks. I'll try that... Time to go learn howto git! 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-16937) GIT 1.2.0 authenticates as the wrong user
Jason Black created JENKINS-16937 GIT 1.2.0 authenticates as the wrong user Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 22/Feb/13 9:01 PM Description: With the previous version of the plugin, I am able to run and select a specific folder from my Git repository to run a suite of tests on. However, with the newer version, I receive this message: Command "git fetch -t origin +refs/heads/:refs/remotes/origin/" returned status code 128: stdout: stderr: R access for project1 DENIED to jenkins (Or there may be no repository at the given path. Did you spell it correctly?) fatal: The remote end hung up unexpectedly I thoroughly perused my configuration settings, and they're all told to point to g...@git.repository.internal.com, hence use the user git. The only fix was to revert to the previous version. Environment: VMWare environment: kernel 2.6.32-100.37.1.el6uek.x86_64 Project: Jenkins Labels: plugin exception git build Priority: Major Reporter: Jason Black 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 Best thing to do is fork the plugin on GitHub, make the changes and push to your fork then issue a pull request. 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 updated JENKINS-16919 Email-ext throws NullPointerException when "attach build log" is checked on 1.480.3 Hi Alex, I'm not entirely sure this is the right place to ask (actually I'm sure it isn't). I've added the option to compress the build log before attaching it to the email, I've tested the change on my local jenkins instance, and would like to push the change back into the email-ext repo, but I'm not sure what the process is, for now I've attached a git patch file to this ticket. Change By: Mark Orchard (22/Feb/13 8:55 PM) Attachment: zip-build-before-attach.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-16936) Extension point for secure users of Api
recampbell assigned JENKINS-16936 to recampbell Extension point for secure users of Api Change By: recampbell (22/Feb/13 8:34 PM) Assignee: recampbell 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-16936) Extension point for secure users of Api
Jesse Glick created JENKINS-16936 Extension point for secure users of Api Issue Type: Improvement Assignee: Unassigned Components: core Created: 22/Feb/13 8:27 PM Description: As a security fix, hudson.model.Api no longer permits the jsonp parameter, or xpath with a primitive result set. This is the safest policy but in certain cases it is useful to whitelist particular requesters known to be harmless. The INSECURE system property should be deprecated or deleted and an extension point introduced so various policies can be added by plugins: whitelists based on host name, requests with no Referer, etc. Project: Jenkins Labels: security Priority: Major 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-13959) StackOverflowException on Job Finish
Larry Grill edited a comment on JENKINS-13959 StackOverflowException on Job Finish Correction in my previous comment. That Jenkins instance was using Git plugin v 1.1.28. I moved it up to Git plugin v 1.2.0, restored the Mailer plugin config to the job that had failed and now it works fine again. Perhaps this is related to the Git v 1.1.28. If you go to the git plugin change log page, version 1.1.28 does not even show up: https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-Changelog I would recommend moving to git 1.2.0 and see if this cures the issue for you too. 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-16935) The default no-name package breaks the rendering
SCM/JIRA link daemon commented on JENKINS-16935 The default no-name package breaks the rendering Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/plugins/jacoco/report/AbstractReport.java src/main/java/hudson/plugins/jacoco/report/PackageReport.java http://jenkins-ci.org/commit/jacoco-plugin/b7985928f638252affa72cc04843d9daf65e67fa Log: [FIXED JENKINS-16935] Give the default no-name package a non-empty name. The empty name breaks the display and hyperlinks. Compare: https://github.com/jenkinsci/jacoco-plugin/compare/5dd58d0e7858...b7985928f638 – 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-16935) The default no-name package breaks the rendering
SCM/JIRA link daemon resolved JENKINS-16935 as Fixed The default no-name package breaks the rendering Change By: SCM/JIRA link daemon (22/Feb/13 8:13 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-16935) The default no-name package breaks the rendering
Kohsuke Kawaguchi created JENKINS-16935 The default no-name package breaks the rendering Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: jacoco Created: 22/Feb/13 8:12 PM Description: If we have classes in the default no-name package (the one without a package delcaration), The coverage break-down by package is not clickable. Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi 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-13959) StackOverflowException on Job Finish
Larry Grill commented on JENKINS-13959 StackOverflowException on Job Finish Correction in my previous comment. That Jenkins instance was using Git plugin v 1.1.28. I moved it up to Git plugin v 1.2.0, restored the Mailer plugin config to the job that had failed and now it works fine again. Perhaps this is related to the Git v 1.1.28. If you go to the git plugin change log page, version 1.1.28 does not even show up: https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-Changelog I would recommend moving to git 1.2.0 and see if this cures the issue for you too. 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-13959) StackOverflowException on Job Finish
Larry Grill edited a comment on JENKINS-13959 StackOverflowException on Job Finish We have a similar configuration that fails the the same error. Ours uses SVN + Git + Mailer. I deleted the Mailer configuration the build succeeded. Environment: Jenkins: 1.502 Git plugin: 1.1.28 SVN plugin: 1.45 Mailer plugin: 1.40 I will continue to investigate. 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-10524) winstone.ClientSocketException: Failed to write to client
Jesse Glick
commented on JENKINS-10524
winstone.ClientSocketException: Failed to write to client
I have been tormented by similar exceptions (usually java.net.SocketException: Connection reset, but sometimes also java.io.IOException: Broken pipe from Jetty in 1.457 IIRC), which pollute the log file with junk.
org.kohsuke.stapler.compression.CompressionFilter.reportException is what actually sends the log record. Not sure what “code is written such that we simply swallow this exception”.
Unfortunately I have not yet managed to reproduce the problem in a controlled environment. Have tried installing a plugin with
@Extension
public class XXX extends PageDecorator {
public void sleep() throws InterruptedException, IOException {
Stapler.getCurrentResponse().flushBuffer();
Thread.sleep(5000);
}
}
and a matching footer.jelly
"1.0" encoding="UTF-8"?>
xmlns:j="jelly:core" xmlns:st="jelly:stapler" xmlns:d="jelly:define" xmlns:i="jelly:fmt">
Sleeping…
${it.sleep()}
done.
which makes a page take a long time to load, but halting it halfway prints nothing to the Jenkins console. Installing the Monitoring plugin changes nothing. Tried Jenkins trunk, 1.480.3, 1.466.2. Tried Stop button in Chrome, as well as running curl and interrupting the process before the page finishes loading.
So if I can ever figure out how to reproduce this, I will try to patch reportException to check for exceptions (incl. nested causes) that seem to indicate a broken socket, and if so not send them to LOGGER (or use FINE rather than WARNING).
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-13959) StackOverflowException on Job Finish
Larry Grill commented on JENKINS-13959 StackOverflowException on Job Finish We have a similar configuration that fails the the same error. Ours uses SVN + Git + Mailer. I deleted the Mailer configuration the build succeeded. Environment: Jenkins: 1.502 Git plugin: 1.20 SVN plugin: 1.45 Mailer plugin: 1.40 I will continue to investigate. 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-16934) Consider excludes from POM.xml
Markus KARG created JENKINS-16934 Consider excludes from POM.xml Issue Type: New Feature Affects Versions: current Assignee: Ognjen Bubalo Components: jacoco Created: 22/Feb/13 7:24 PM Description: It would be great if the JaCoCo plugin would read the excludes from POM.xml when used within a Maven-type job. At is annoying that one must give excludes manually in the JaCoCo config when having already set them in the POM. Environment: Jenkins 1.502 / Tomcat 6 / Debian 6 / JDK 1.6.0_18 / x86 Project: Jenkins Priority: Major Reporter: Markus KARG 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
Markus KARG commented on JENKINS-16904 JaCoCo Plugin incorrectly uses POM-configured excludes Sorry for posting this issue on the wrong mailing list (https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/I12AzTaro90)! 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
Markus KARG commented on JENKINS-16903 JaCoCo Plugin marks build as UNSTABLE, but the coverage was sufficient If I understand that thread correctly, by intention the former JaCoCo plugin reported UNSTABLE when the coverage was between MIN and MAX? This is strange, because I (and possibly lots of others) would expect a build to be UNSTABLE when below MIN, but to be STABLE (but not perfectly shining) when between MIN and MAX. So do I understand correctly, that in the next release, the build will be reported as STABLE while coverage is between MIN and MAX, or can you point me to a URL where the exact future policy is described? 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-16931) It is not possible to define roaming jobs
Justin Ryan started work on JENKINS-16931 It is not possible to define roaming jobs Change By: Justin Ryan (22/Feb/13 6:57 PM) Status: Open In Progress 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-16933) Make Jira plugin write more compact comments
Julien Carsique updated JENKINS-16933 Make Jira plugin write more compact comments Change By: Julien Carsique (22/Feb/13 6:24 PM) Status: Reopened Open 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-16933) Make Jira plugin write more compact comments
Julien Carsique edited a comment on JENKINS-16933 Make Jira plugin write more compact comments (deleted) 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-16933) Make Jira plugin write more compact comments
Julien Carsique reopened JENKINS-16933 Make Jira plugin write more compact comments Change By: Julien Carsique (22/Feb/13 6:23 PM) Resolution: Fixed 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-16933) Make Jira plugin write more compact comments
Julien Carsique resolved JENKINS-16933 as Fixed Make Jira plugin write more compact comments Using a custom build 1.36-SNAPSHOT waiting for pull-request merge. See https://issues.jenkins-ci.org/browse/JENKINS-16933 Change By: Julien Carsique (22/Feb/13 6:23 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-16933) Make Jira plugin write more compact comments
Julien Carsique edited a comment on JENKINS-16933 Make Jira plugin write more compact comments https://github.com/jenkinsci/jira-plugin/pull/18 About the changed files list (recordScmChanges option), it would be great to write them collapsed by default but the only current Wiki solution seems to be a custom macro so I didn't change them. Note however, the refactoring I did changed the order: files are now listed right after the corresponding aggregated comment whereas before that change, they were listed after the initial list of aggregated comments. I guess it's a trivial and acceptable change. 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-16693) Heap error while polling Git Plug-in after upgrade to 1.1.26.
Don Ross commented on JENKINS-16693 Heap error while polling Git Plug-in after upgrade to 1.1.26. I did... it ran for about over ten minutes and spit out a 300mb output file. My suspicion was that this was too much for Jenkins slave to absorb, so I increased the heap size to 2gb, but it still didn't help, at which point I opened the ticket. Reverting back to 1.1.21 caused this command to no longer run and resolved my immediate 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-16888) Usage of ObjectID.fromString in computeMergeChangeLog leads to "java.lang.IllegalArgumentException: Invalid id"
Nicolas De Loof commented on JENKINS-16888 Usage of ObjectID.fromString in computeMergeChangeLog leads to "java.lang.IllegalArgumentException: Invalid id" thanks for detailled analysis, I will investigate for a fix 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-16873) Root workspace directory is removed when doing initial clone
Nicolas De Loof resolved JENKINS-16873 as Fixed Root workspace directory is removed when doing initial clone Change By: Nicolas De Loof (22/Feb/13 5:34 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-11337) Git plugin only triggers a build for one branch
Przemek Dyk commented on JENKINS-11337 Git plugin only triggers a build for one branch I cannot reproduce this bug using jenkins 1.424, 1.497 or 1.502 with git plugin 1.2.0 Accidentally 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-7702) Could not load Logmanager "org.apache.juli.ClassLoaderLogManager"
Jesse Glick commented on JENKINS-7702 Could not load Logmanager "org.apache.juli.ClassLoaderLogManager" Filed a Tomcat bug report: https://issues.apache.org/bugzilla/show_bug.cgi?id=54601 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-7702) Could not load Logmanager "org.apache.juli.ClassLoaderLogManager"
Jesse Glick commented on JENKINS-7702 Could not load Logmanager "org.apache.juli.ClassLoaderLogManager" Grails plugin fix: https://github.com/jenkinsci/grails-plugin/pull/5 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
Nicolas De Loof resolved JENKINS-16911 as Fixed An invalid git reference repository path now causes clone to fail, previously did not fail Change By: Nicolas De Loof (22/Feb/13 5:29 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-16933) Make Jira plugin write more compact comments
Julien Carsique commented on JENKINS-16933 Make Jira plugin write more compact comments About the changed files list (recordScmChanges option), it would be great to write them collapsed by default but the only current Wiki solution seems to be a custom macro so I didn't change them. Note however, the refactoring I did changed the order: files are now listed right after the corresponding aggregated comment whereas before that change, they were listed after the initial list of aggregated comments. I guess it's a trivial and acceptable change. 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-16933) Make Jira plugin write more compact comments
Julien Carsique created JENKINS-16933 Make Jira plugin write more compact comments Issue Type: Improvement Assignee: Julien Carsique Components: jira Created: 22/Feb/13 5:21 PM Description: The comments written by the Jira plugin are useful but takes too much space, reducing the whole history readability. Also, we need a browser link to the changeset; that is currently only available when activating the recordScmChanges option (which is really verbose). Current style Integrated in nuxeo-distribution-master #1399 NXP-11039 - Log STDERR in case of JVM launch issue (Revision 4c335fd87af6dd98e7d84de7a06009800d928817) Result = SUCCESS New style SUCCESS: Integrated in nuxeo-distribution-master #1399 NXP-11039 - Log STDERR in case of JVM launch issue (jcarsique: 4c335fd87af6dd98e7d84de7a06009800d928817) Project: Jenkins Priority: Minor Reporter: Julien Carsique 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-16609) Backup build results/artifacts only for "Keep this build forever" marked builds
SCM/JIRA link daemon commented on JENKINS-16609 Backup build results/artifacts only for "Keep this build forever" marked builds Code changed in jenkins User: Thomas Fuerer Path: http://jenkins-ci.org/commit/thin-backup-plugin/dbeb5bdbda609d35eaa7a0ea6e7a6baf549aa6ff Log: Merge pull request #2 from rjnichols/master JENKINS-16609: New feature - only back up build results/artifacts on builds which are marked "Keep this build forever" 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-7976) Aggregate downstream test results does not work for Matrix projects
Ireneusz Makowski commented on JENKINS-7976 Aggregate downstream test results does not work for Matrix projects It seems that matrix job don't aggregate test results at all from each axis. There is an issue with getting test results from axis? Could you please look into this deeper? The best example here are tests executed as one of axis and dasboard-view-plugin with Test Results Grid always displays 0 for matrix builds with tests. 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-16314) cvs plugin removes sticky branch tag
James Morgan commented on JENKINS-16314 cvs plugin removes sticky branch tag Just to add the error this is causing is Provider message: The cvs command failed. Command output: cvs commit: Up-to-date check failed for `pom.xml' cvs [commit aborted]: correct above errors first! 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
Vincent Latombe commented on JENKINS-15846 Deadlock during Maven builds Parsing POM step without 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-16314) cvs plugin removes sticky branch tag
James Morgan commented on JENKINS-16314 cvs plugin removes sticky branch tag Hi, I've upgraded to v2.8 this morning and trying to release from a branch. The plugin is stripping the Tbranch info still. cvs checkout -P -r RC_repServer2_6 -d test repServer /api-base.cfg/1.3/Wed Apr 18 11:55:58 2012// /build.xml/1.3/Thu Feb 07 09:55:32 2013// /changeLog/1.7/Mon Dec 19 15:25:41 2011// /pom.xml/1.7.2.6/Fri Feb 22 11:38:24 2013// /schema-base.cfg/1.3/Tue Jan 31 14:02:16 2012// /server-base.cfg/1.5/Wed Feb 06 17:39:30 2013// D/db D/doc D/dtd D/tcl And handrolling the cvs checkout instead of using the plugin gives + cvs co -r RC_repServer2_6 -d test repServer /api-base.cfg/1.3/Wed Apr 18 11:55:58 2012//TRC_repServer2_6 /build.xml/1.3/Thu Feb 7 09:55:32 2013//TRC_repServer2_6 /changeLog/1.7/Mon Dec 19 15:25:41 2011//TRC_repServer2_6 /schema-base.cfg/1.3/Tue Jan 31 14:02:16 2012//TRC_repServer2_6 /server-base.cfg/1.5/Wed Feb 6 17:39:30 2013//TRC_repServer2_6 D/db D/doc D/dtd D/tcl /pom.xml/1.7.2.6/Fri Feb 22 11:38:24 2013//TRC_repServer2_6 Is this same issue? If not i'll raise it as a new defect. Many thanks James 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-16932) Exception: net.sf.json.JSONException: JSONObject["tag"] not found when doing a rebuild
Jason Swager created JENKINS-16932 Exception: net.sf.json.JSONException: JSONObject["tag"] not found when doing a rebuild Issue Type: Bug Affects Versions: current Assignee: ragesh_nair Components: rebuild Created: 22/Feb/13 3:44 PM Description: When attempting to do a rebuild of a set of jobs, the following error is encountered: Exception: net.sf.json.JSONException: JSONObject["tag"] not found. Not all of our jobs generate this error, which makes me think it is a particular plugin/parameter that has the problem. The job uses normal text string, the NodeLabel parameter (to dictate the slave), multiple Build Selector for Copy Artifact parameters. Environment: Jenkins 1.501, Rebuild 1.17 Project: Jenkins Priority: Major Reporter: Jason Swager 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-16932) Exception: net.sf.json.JSONException: JSONObject["tag"] not found when doing a rebuild
Jason Swager commented on JENKINS-16932 Exception: net.sf.json.JSONException: JSONObject["tag"] not found when doing a rebuild Full Stack Trace: javax.servlet.ServletException: net.sf.json.JSONException: JSONObject["tag"] not found. at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:615) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) 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.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.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) 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.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) 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.CharacterEncodingFilte
[JIRA] (JENKINS-12205) Test result trend not displayed in matrix project configuration top page
Ireneusz Makowski commented on JENKINS-12205 Test result trend not displayed in matrix project configuration top page Any news on it? I have exactly the same problem here. 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-16920) Running native Maven projects on JDK 5 using Jenkins hosted on Tomcat 7 fails
Jesse Glick updated JENKINS-16920 Running native Maven projects on JDK 5 using Jenkins hosted on Tomcat 7 fails Change By: Jesse Glick (22/Feb/13 3:23 PM) Priority: Major Critical Component/s: maven 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-15846) Deadlock during Maven builds Parsing POM step
Jesse Glick commented on JENKINS-15846 Deadlock during Maven builds Parsing POM step Is this with or without the aforementioned system property set? 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-16666) Jabber plugins stops working after upgrading to Jenkins 1.499
kutzi commented on JENKINS-1 Jabber plugins stops working after upgrading to Jenkins 1.499 > Can you look into your Jenkins war file and confirm that it's the current one and that this class is there? 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-16666) Jabber plugins stops working after upgrading to Jenkins 1.499
Laurentius Purba commented on JENKINS-1 Jabber plugins stops working after upgrading to Jenkins 1.499 It was confirmed that the war file is correct with version 1.4999. Also, there was no older war lying around that started my Jenkins. Thanks! -laurent 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-16931) It is not possible to define roaming jobs
Daniel Spilker commented on JENKINS-16931 It is not possible to define roaming jobs I think the problem has been introduced with this commit: https://github.com/jenkinsci/job-dsl-plugin/commit/550c5379e11985f77f8db0b54070810e8110ec2a 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-16746) Unable to send email since Jenkins 1.500
Ravi Teja Lokineni edited a comment on JENKINS-16746 Unable to send email since Jenkins 1.500 Sorry, Alex confused you with someone else .. 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-16746) Unable to send email since Jenkins 1.500
Ravi Teja Lokineni commented on JENKINS-16746 Unable to send email since Jenkins 1.500 Same with you as well? 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-16931) It is not possible to define roaming jobs
Daniel Spilker commented on JENKINS-16931 It is not possible to define roaming jobs The problem seems to be the element in the emptyTemplate in Job.groovy defaults to false. It should default to true and the label _expression_ should set it to false. 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-16746) Unable to send email since Jenkins 1.500
Alex Earl resolved JENKINS-16746 as Not A Defect Unable to send email since Jenkins 1.500 Duplicate activation.jar in tomcat Change By: Alex Earl (22/Feb/13 1:42 PM) Status: Reopened 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-16931) It is not possible to define roaming jobs
Daniel Spilker
created JENKINS-16931
It is not possible to define roaming jobs
Issue Type:
Bug
Assignee:
Justin Ryan
Components:
job-dsl-plugin
Created:
22/Feb/13 1:40 PM
Description:
It is currently not possible to define jobs which can run on any node. The checkbox for "Restrict where this project can be run" is always set even if the label element is omitted. In the config.xml the element is always set it false.
As a workaround, a configure block can be used.
job {
...
configure { it / canRoam(true) }
...
}
Environment:
jenkins 1.492, job-dsl-plugin 1.12
Project:
Jenkins
Priority:
Major
Reporter:
Daniel Spilker
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-16375) show job difference does not work, url escaped twice
Christian Eichenberger resolved JENKINS-16375 as Fixed show job difference does not work, url escaped twice Works fine in 2.2 Change By: Christian Eichenberger (22/Feb/13 1:27 PM) Status: Reopened 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-16930) Jenkins Server requirements for Windows Services ( RAM, Hardisk, Processors)
kutzi resolved JENKINS-16930 as Not A Defect Jenkins Server requirements for Windows Services ( RAM, Hardisk, Processors) Please use the mailing list for such questions! Change By: kutzi (22/Feb/13 1:10 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-16930) Jenkins Server requirements for Windows Services ( RAM, Hardisk, Processors)
kutzi closed JENKINS-16930 as Not A Defect Jenkins Server requirements for Windows Services ( RAM, Hardisk, Processors) Change By: kutzi (22/Feb/13 1:10 PM) Status: Resolved Closed 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-16746) Unable to send email since Jenkins 1.500
Ravi Teja Lokineni commented on JENKINS-16746 Unable to send email since Jenkins 1.500 Hey alex try searching for find -iname *activation*.jar 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-16746) Unable to send email since Jenkins 1.500
Ravi Teja Lokineni commented on JENKINS-16746 Unable to send email since Jenkins 1.500 Yes, Alex. Our tomcat server had been recently deployed with another webapp which had a different version of activation.jar. I had undeployed this new application and everything is back to normal. 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-16666) Jabber plugins stops working after upgrading to Jenkins 1.499
kutzi updated JENKINS-1 Jabber plugins stops working after upgrading to Jenkins 1.499 Change By: kutzi (22/Feb/13 1:02 PM) Due Date: 20/ Feb Mar /13 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-16930) Jenkins Server requirements for Windows Services ( RAM, Hardisk, Processors)
Linards L edited a comment on JENKINS-16930 Jenkins Server requirements for Windows Services ( RAM, Hardisk, Processors) from java 1.5 hardware requierments to limitless requierments. Please refer to these resources for quick start: http://shop.oreilly.com/product/0636920010326.do http://www.cloudbees.com/sites/default/files/whitepapers/7WaysToOptimizeJenkins.pdf In the short - it depends on the count of jobs, tools the jobs use, security patterns and mechanisms you use and the network congestion you face. Either way, there is no answer for the question (incl. this) not containing any targeted items to be used in Jenkins CI. 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-16746) Unable to send email since Jenkins 1.500
Alex Earl commented on JENKINS-16746 Unable to send email since Jenkins 1.500 Ravi is this issue "fixed" for you then? 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-16930) Jenkins Server requirements for Windows Services ( RAM, Hardisk, Processors)
Linards L commented on JENKINS-16930 Jenkins Server requirements for Windows Services ( RAM, Hardisk, Processors) from java 1.5 hardware requierments to limitless requierments. Please refer to these resources for quick start: http://shop.oreilly.com/product/0636920010326.do http://www.cloudbees.com/sites/default/files/whitepapers/7WaysToOptimizeJenkins.pdf In the short - it depends on the count of jobs, tools the jobs use, security patters and mechanisms you use and yhe network congestion you face. Either way, there is no answer for the question (incl. this) not cotnaining any targeted items to be used in Jenkins CI. 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-16930) Jenkins Server requirements for Windows Services ( RAM, Hardisk, Processors)
Priyank Soni created JENKINS-16930 Jenkins Server requirements for Windows Services ( RAM, Hardisk, Processors) Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: infrastructure Created: 22/Feb/13 12:50 PM Description: What are the hardware requirements for Jenkins build server. [Windows Services] Due Date: 22/Feb/13 12:00 AM Environment: Jenkins Server requirements for Windows Services ( RAM, Hardisk, Processors) Fix Versions: current Project: Jenkins Priority: Major Reporter: Priyank Soni 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-16749) Exception in EmailTrigger
Alex Earl commented on JENKINS-16749 Exception in EmailTrigger Looks like you are using the Regression trigger, didn't see that the first time I looked at the stack trace. 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 Also, what version of email-ext are you using? 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-16861) Add support for the Claim Plugin
Alex Earl
commented on JENKINS-16861
Add support for the Claim Plugin
When using a script in the recipient list, your last line of the script must be a string with comma separated addresses.
def committers = []
// loop through and grab committers from somewhere cool
// here comes the last line
committers.unique().join(',')
When trying to do content (body) you want to create a template, not a script.
${SCRIPT, template="output-claim-info.template"}
Did you try this?
import hudson.tasks.Mailer.UserProperty
address = user.getProperty(hudson.tasks.Mailer.UserProperty.class).address
You can definitely provide default recipients, just do something like this:
Project Recipient List: some...@somewhere.com, ${SCRIPT, script="get-claim-recipient.groovy"}
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 resolved JENKINS-16919 as Fixed Email-ext throws NullPointerException when "attach build log" is checked on 1.480.3 Fixed NPE when error occurs sending email. Change By: Alex Earl (22/Feb/13 12:17 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-16861) Add support for the Claim Plugin
Markus Hjerto
commented on JENKINS-16861
Add support for the Claim Plugin
Thank you very much Alex. Your pointers, combined with Chris's implementation in JENKINS-12421, did the trick. I now have a way to solve this, but I was only able to make it run when I did it as a pre-send script, which means that the script must be duplicated in every job (hundreds).
So, you say it is possible to run this script directly from the Project Recipient List? I've added ${SCRIPT, script="get-claim-recipient.groovy"} to a job's Default Content (for debugging) and it seems to run. But I'm not able to output any text from the script. It does not accept %>sometext<% (unexpected token: <). I've also tried println("Hello"); but nothing is written in the email. logger.println() also does not work (No such property: logger for class).
Also, I'm not able to make mailext/groovy accept "address = user.getProperty(hudson.tasks.Mailer.UserProperty).getAddress();". (No such property: hudson for class). This line works well if it is a pre-send script. I've tried to import hudson.model.User.* as well.
And finally, if I do it like this, then will I be able to provide any default recipients (for non-claimed jobs) in the job configuration? Maybe I should simply wait for JENKINS-14508.
I obviously don't have enough knowledge here, so I apologize for all my novice questions and humbly hope for some more guidelines.
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-16123) Valgrind plugin does not work when providing multiple Executable Arguments for run.
Johannes Ohlemacher commented on JENKINS-16123 Valgrind plugin does not work when providing multiple Executable Arguments for run. sorry for the delay. The last few weeks were pretty tough and i had absolutely no time for the plugin. The next release will likely contain some major changes, but those changes still need some polishment. I'm going to do that now, so you can expect the new version to be released at end of next week. 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-16123) Valgrind plugin does not work when providing multiple Executable Arguments for run.
Tomasz Ducin commented on JENKINS-16123 Valgrind plugin does not work when providing multiple Executable Arguments for run. When is the new version going 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-15931) Build is hanging on newly created EC2 slaves
Antti Rasinen commented on JENKINS-15931 Build is hanging on newly created EC2 slaves Both server and slave dumps contain threads that are waiting for a channel. Look for xunit in the dumps. 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-15931) Build is hanging on newly created EC2 slaves
Antti Rasinen updated JENKINS-15931 Build is hanging on newly created EC2 slaves This error happens very frequently at our site. I've attached here a thread dumps from the master and from the slave. The dumps were taken at separate incidents, however. Also I've attached lsof -p output for the slave. Change By: Antti Rasinen (22/Feb/13 11:30 AM) Attachment: jstack_master.txt Attachment: jstack_slave.out Attachment: lsof_slave.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-16919) Email-ext throws NullPointerException when "attach build log" is checked on 1.480.3
SCM/JIRA link daemon commented on JENKINS-16919 Email-ext throws NullPointerException when "attach build log" is checked on 1.480.3 Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java http://jenkins-ci.org/commit/email-ext-plugin/9f207ef592417158ad01c711c1a6b9349c9edb5a Log: Fix JENKINS-16919 Fixed NPE by checking return of the getters for the SendFailedException. – 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-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 Done! I've made a small modification and it works fine on our Jenkins instance. It can be downloaded over here: https://buildhive.cloudbees.com/job/jenkinsci/job/jenkins-clone-workspace-scm-plugin/7/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-16929) GNU make + GCC parser can't handle UTF-8
James Howe created JENKINS-16929 GNU make + GCC parser can't handle UTF-8 Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: warnings Created: 22/Feb/13 10:57 AM Description: All the text shown by the plugin suffers from a UTF-8 as ASCII encoding error. This is particularly annoying as GCC is outputting fancy quotes. For example: unused variable ‘n’ Project: Jenkins Priority: Minor Reporter: James Howe 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-16928) Jenkins build fails with fatal error for Maven 2 build of project with mavmaven-soapui-plugin
kutzi updated JENKINS-16928 Jenkins build fails with fatal error for Maven 2 build of project with mavmaven-soapui-plugin Change By: kutzi (22/Feb/13 10:34 AM) Priority: Major Critical 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 I'll leave this open because of the NPE exception and leave the fix in that I have now. 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
Vincent Latombe edited a comment on JENKINS-15846 Deadlock during Maven builds Parsing POM step New samples of the deadlock (with thread dumps from master and slave). In the example, only one job is stuck : app-sell2.0_v16.2_cr5743145_ci 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
Vincent Latombe updated JENKINS-15846 Deadlock during Maven builds Parsing POM step New samples of the deadlock. In the example, only one job is stuck : app-sell2.0_v16.2_cr5743145_ci Change By: Vincent Latombe (22/Feb/13 10:27 AM) Attachment: masterThreadDump.txt Attachment: slaveThreadDump.txt 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
Nickolay Rumyantsev commented on JENKINS-15466 Fatal Error No Class Definition found for Kernel32 I have the same issue raised during the workspace cleaning. Jenkins 1.480.3 Slave: Win2003, java 6_22 and 7_15 (both tested) 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-16928) Jenkins build fails with fatal error for Maven 2 build of project with mavmaven-soapui-plugin
kutzi assigned JENKINS-16928 to kutzi Jenkins build fails with fatal error for Maven 2 build of project with mavmaven-soapui-plugin Change By: kutzi (22/Feb/13 10:04 AM) Assignee: kutzi 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.
