[JIRA] [pending-changes] (JENKINS-21733) cicicuit
evernat closed JENKINS-21733 as Not A Defect cicicuit Change By: evernat (10/Feb/14 8:30 AM) 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] [pending-changes] (JENKINS-21733) cicicuit
evernat resolved JENKINS-21733 as Not A Defect cicicuit Change By: evernat (10/Feb/14 8:30 AM) Status: Open Resolved Resolution: NotADefect 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] [unity3d-plugin] (JENKINS-21735) Support automatically setting a -logFile argument relative to the project path to handle concurrent builds
lacostej created JENKINS-21735 Support automatically setting a -logFile argument relative to the project path to handle concurrent builds Issue Type: Bug Assignee: lacostej Components: unity3d-plugin Created: 10/Feb/14 8:38 AM Description: If you run multiple concurrent builds they might all write on the standard location editor.log, leading to strange console outputs. One can avoid this by specifying a -logFile argument manually. We could let the plugin do it for us, maybe inside the workspace. http://docs.unity3d.com/Documentation/Manual/CommandLineArguments.html Project: Jenkins Priority: Major Reporter: lacostej 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] [next-executions] (JENKINS-21267) show time _span_ until next execution
SCM/JIRA link daemon commented on JENKINS-21267 show time _span_ until next execution Code changed in jenkins User: Ignacio Albors Path: src/main/java/hudson/plugins/nextexecutions/NextBuilds.java src/main/resources/hudson/plugins/nextexecutions/Messages.properties http://jenkins-ci.org/commit/next-executions-plugin/b5f502699d86b2829d4b1a0e09f4a0d2fc84a29a Log: JENKINS-21267 Added method to obtain the remaining time. 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] [next-executions] (JENKINS-21267) show time _span_ until next execution
SCM/JIRA link daemon commented on JENKINS-21267 show time _span_ until next execution Code changed in jenkins User: Ignacio Albors Path: pom.xml src/main/java/hudson/plugins/nextexecutions/NextBuilds.java src/main/java/hudson/plugins/nextexecutions/NextExecutionsComputerWidget.java src/main/java/hudson/plugins/nextexecutions/NextExecutionsWidget.java src/main/java/hudson/plugins/nextexecutions/columns/NextExecutionColumn.java src/main/resources/hudson/plugins/nextexecutions/Messages.properties src/main/resources/hudson/plugins/nextexecutions/NextExecutionsWidget/index.jelly http://jenkins-ci.org/commit/next-executions-plugin/87d044b91502d3f385715dcff8c9a6a9dc1fccd1 Log: Merge branch 'JENKINS-21267' Conflicts: src/main/resources/hudson/plugins/nextexecutions/NextExecutionsWidget/index.jelly Compare: https://github.com/jenkinsci/next-executions-plugin/compare/321606523bef...87d044b91502 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] [next-executions] (JENKINS-21267) show time _span_ until next execution
SCM/JIRA link daemon commented on JENKINS-21267 show time _span_ until next execution Code changed in jenkins User: Ignacio Albors Path: src/main/resources/hudson/plugins/nextexecutions/NextExecutionsWidget/index.jelly http://jenkins-ci.org/commit/next-executions-plugin/da036401adea9d5a3f8e8e8510029b9e9a4434a3 Log: JENKINS-21267 Adding tooltip to show remaining time until next build. E.g.: in 2d 1h 3m 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] [nodejs] (JENKINS-21726) Nodejs path not set correctly when running on Windows master, linux slave
Frédéric Camblor resolved JENKINS-21726 as Fixed Nodejs path not set correctly when running on Windows master, linux slave fixed in 0.2.1 Change By: Frédéric Camblor (10/Feb/14 8:48 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] [findbugs] (JENKINS-21155) swarm 1.10 incompatibility with findbugs 4.51
Ulli Hafner commented on JENKINS-21155 swarm 1.10 incompatibility with findbugs 4.51 So, now release 1.15 is available. Seems that I hit http://jira.codehaus.org/browse/MRELEASE-812 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] [robot-plugin] (JENKINS-21736) Make the archiving of output.xml optional
laurent bristiel updated JENKINS-21736 Make the archiving of output.xml optional Change By: laurent bristiel (10/Feb/14 9:20 AM) Issue Type: Bug Improvement 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] [robot-plugin] (JENKINS-21736) Make the archiving of output.xml optional
laurent bristiel created JENKINS-21736 Make the archiving of output.xml optional Issue Type: Bug Affects Versions: current Assignee: jpiironen Components: robot-plugin Created: 10/Feb/14 9:20 AM Description: When the RF plugin is called in jenkins, it copies the Robot output files from the Workspace to the server. By default those files are output.xml, log.html and report.html (this is customizable) The plugin then uses the output.xml to build another XML file used to show the data about success/failures of the tests. After that publishing step, output.xml file is not needed anymore (archived for possible traceability reasons though). It would be a good improvement to make the archiving of output.xml optional, since in many cases it is not used and it might use a lot of disk space This was discussed in Robot Framework User Group: https://groups.google.com/forum/#!msg/robotframework-users/2pr6MmhmoKc/bgMJ6YWzUCYJ Environment: Jenkins ver. 1.509.4 robot-plugin ver. 1.4.0 Project: Jenkins Priority: Major Reporter: laurent bristiel 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] [next-executions] (JENKINS-21267) show time _span_ until next execution
Ignacio Albors resolved JENKINS-21267 as Fixed show time _span_ until next execution Added a tooltip to show remaining time until next execution as requested. Change By: Ignacio Albors (10/Feb/14 9:37 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] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Marco Huber commented on JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING We have the same problem after installing Jenkins V 1.549. We copied our project from Hudson 1.398 into the new Jenkins instance, but all exisiting configurations break with this error. 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] [xunit] (JENKINS-21737) Test output are unusable
Mathieu Malaterre created JENKINS-21737 Test output are unusable Issue Type: Bug Assignee: Gregory Boissinot Attachments: Test.xml Components: xunit Created: 10/Feb/14 9:59 AM Description: I am trying to use the xUnit+CTest plugin. If I run the following shell command: ctest -D ExperimentalTest || true It produces a Test.xml into: Testing/*/Test.xml However the output seems to be some kind of base64 + gzip encoding. Therefore it is completely useless as-is. Please decode it first before presenting it. Thanks Project: Jenkins Labels: plugin Priority: Major Reporter: Mathieu Malaterre 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] [xunit] (JENKINS-21737) Test output are unusable
Mathieu Malaterre commented on JENKINS-21737 Test output are unusable Here is the compressed example taken from the cdash test suite: https://www.kitware.com/svn/CDash/trunk/tests/data/CompressedTest.xml 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] [xunit] (JENKINS-21737) Test output are unusable
Mathieu Malaterre updated JENKINS-21737 Test output are unusable Simple example to decode base64 + zlib Change By: Mathieu Malaterre (10/Feb/14 10:17 AM) Attachment: decode.py 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] [integrity-plugin] (JENKINS-21587) memory leak in Plugin 1.22 -orphaned Logger Threads
Matthias Rump commented on JENKINS-21587 memory leak in Plugin 1.22 -orphaned Logger Threads Hi Cletus, sorry for being so obstrusive, but this issue kind of drives me crazy I hope you can consider my pull-request for the next release: https://github.com/maschuru/integrity-plugin/commit/c8bea4be0ea72bd50a921828e982cd263c85ff08 Regards Matthias 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] [core] (JENKINS-21738) Project-base Matrix Authorization Strategy Option is not exists
Ramkumar Yoganathan created JENKINS-21738 Project-base Matrix Authorization Strategy Option is not exists Issue Type: Bug Assignee: Unassigned Attachments: Capture.PNG Components: core Created: 10/Feb/14 10:46 AM Description: Hello, I am unable to see the "Project-base Matrix Authorization Strategy" Option in my "Manage Jenkins" Page. Could you please help on this? Thanks, Ram Environment: Jenkins 1.550 Windows 2008 Server Project: Jenkins Priority: Major Reporter: Ramkumar Yoganathan 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] [cli] (JENKINS-16345) CLI does not work through reverse proxy
Michael Pailloncy commented on JENKINS-16345 CLI does not work through reverse proxy Same issue using Jenkins 1.531 and Jenkins behind Nginx. 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] [subversion] (JENKINS-21645) Upgrading to Subversion plugin 2.0 causes svn integration to break
Ori Osherov commented on JENKINS-21645 Upgrading to Subversion plugin 2.0 causes svn integration to break I've got the same issue myself, SVN integration has stopped working on several of my machines 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] [jobconfighistory] (JENKINS-18900) [JobConfigurationHistory] Wrong history being displayed
Steffen Breitbach assigned JENKINS-18900 to Steffen Breitbach [JobConfigurationHistory] Wrong history being displayed Change By: Steffen Breitbach (10/Feb/14 12:28 PM) Assignee: StefanBrausch SteffenBreitbach 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] [jobconfighistory] (JENKINS-18900) [JobConfigurationHistory] Wrong history being displayed
Steffen Breitbach commented on JENKINS-18900 [JobConfigurationHistory] Wrong history being displayed Hi Stefan, no problem. I've opened this issue when we were running 1.509.2 LTS and Job Configuration History 2.4 We're running 1.532.1 and Job Configuration History 2.5 and I can't reproduce the issue any more. As far as I am concerned the issue may be closed. Regards Steffen 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] [gerrit-trigger] (JENKINS-11409) Gerrit-trigger should support waiting for downstream jobs of triggered builds
SCM/JIRA link daemon commented on JENKINS-11409 Gerrit-trigger should support waiting for downstream jobs of triggered builds Code changed in jenkins User: Yannack Path: gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ToGerritRunListener.java gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritDelayedApprover.java gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger.java gerrithudsontrigger/src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritDelayedApprover/config.jelly gerrithudsontrigger/src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger/config.jelly gerrithudsontrigger/src/main/webapp/trigger/help-DelayedApproval.html gerrithudsontrigger/src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTriggerTest.java gerrithudsontrigger/src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/mock/DuplicatesUtil.java gerrithudsontrigger/src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/mock/Setup.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/5f672f2db13314377c9db239bdb6ae4491136345 Log: Delayed approval mechanism FIXED JENKINS-11409 This patch introduces the possibility for a delayed approval to be sent back to Gerrit. This is a relatively advanced use case, so the setting has been placed in the Advanced section for the Trigger settings. When one selects "delayed approval", the completion of the build will NOT send an approval back to Gerrit. Instead, the triggering event stays open, and needs to be closed later on. This can be done by using the new post-build action "Send a Gerrit delayed approval". At the moment, this notifier expects to read the name of the job and build number from build variables. If these point to an existing build which has a Gerrit event as a trigger, which has not been submitted due to "delayed approval", then that approval will be sent. In particular, this allows to modify the status of that build through other job (e.g., using Groovy scripts), and mark it UNSTABLE (e.g., if a subsequent build were to fail), which is a way one can change the result of the Approval in Gerrit. Amends: fixed broken style and broken unit 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] [gerrit-trigger] (JENKINS-11409) Gerrit-trigger should support waiting for downstream jobs of triggered builds
SCM/JIRA link daemon resolved JENKINS-11409 as Fixed Gerrit-trigger should support waiting for downstream jobs of triggered builds Change By: SCM/JIRA link daemon (10/Feb/14 12:40 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] [gerrit-trigger] (JENKINS-11409) Gerrit-trigger should support waiting for downstream jobs of triggered builds
SCM/JIRA link daemon commented on JENKINS-11409 Gerrit-trigger should support waiting for downstream jobs of triggered builds Code changed in jenkins User: Robert Sandell Path: gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ToGerritRunListener.java gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritDelayedApprover.java gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger.java gerrithudsontrigger/src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/Messages.properties gerrithudsontrigger/src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritDelayedApprover/config.jelly gerrithudsontrigger/src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger/config.jelly gerrithudsontrigger/src/main/webapp/trigger/help-DelayedApproval.html gerrithudsontrigger/src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ToGerritRunListenerTest.java gerrithudsontrigger/src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTriggerTest.java gerrithudsontrigger/src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/mock/DuplicatesUtil.java gerrithudsontrigger/src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/mock/Setup.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/c512069db1936d16eb969eab63d85e88b0e0 Log: Merge pull request #122 from yannack/delayedApprove Delayed approval mechanism FIXED JENKINS-11409 Compare: https://github.com/jenkinsci/gerrit-trigger-plugin/compare/3246d8e32d87...c512069db193 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] [integrity-plugin] (JENKINS-14703) PTC Integrity Plugin throws/catches SQL Exception in Combination with Locale Plugin
Martin Hohl commented on JENKINS-14703 PTC Integrity Plugin throws/catches SQL Exception in Combination with Locale Plugin Also occurs with Jenkins ver. 1.546 and integrity-plugin 1.22, downgrading to integrity-plugin 1.20 or integrity-plugin 1.16 doesn't help. If I remove the "Default Language" setting from the Locale plugin (leave field empty) and remove the checkmark from "Ignore browser preference and force this language to all users", then the SQL Exception disappears (the mere presence of the Locale plugin as an installed plugin apparently isn't harmful, it seems that the observed behavior is connected to the field "Default Language" in the Locale plugin). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-19194) Recipients not being saved
Alex Earl commented on JENKINS-19194 Recipients not being saved I'm pretty sure this has to do with the plugin overriding newInstance in the descriptor. For newer versions of Jenkins, this causes an issue when you also have a @DataBoundConstructor. When I update the pom.xml to use 1.532.1 as the core version and remove the newInstance, things work correctly and the recipients are saved. I'll try and determine a better way to do it so that its more backward compatible. 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] [mailer] (JENKINS-19194) Recipients not being saved
Alex Earl commented on JENKINS-19194 Recipients not being saved @Gautam, can you unpin the Mailer plugin in your config and upgrade to 1.8? 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] [robot-plugin] (JENKINS-16158) Delete button disappeared
Régis Desgroppes resolved JENKINS-16158 as Cannot Reproduce Delete button disappeared The problem disappeared without any related change to the robot framework plugin, so I guess something else was done at either jenkins core or another plugin side... Change By: Régis Desgroppes (10/Feb/14 1:47 PM) Status: Open Resolved Resolution: CannotReproduce 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] [integrity-plugin] (JENKINS-21587) memory leak in Plugin 1.22 -orphaned Logger Threads
Cletus DSouza commented on JENKINS-21587 memory leak in Plugin 1.22 -orphaned Logger Threads No, not at all! You code changes seem reasonable to me and I can certainly incorporate it in the next release. I've not seen any exceptions thrown during the terminate process, but glad you've caught it. Thanks for your persistence! Its paid of Cletus 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] [integrity-plugin] (JENKINS-14703) PTC Integrity Plugin throws/catches SQL Exception in Combination with Locale Plugin
Cletus DSouza commented on JENKINS-14703 PTC Integrity Plugin throws/catches SQL Exception in Combination with Locale Plugin Hi, the plugin doesn't do anything to be locale specific, so I'm not surprised it doesn't work. I guess it never has worked. Feel free to submit code changes and I'll be happy to review them for the next release. Thanks! Cletus 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] [analysis-core] (JENKINS-19904) PMD plugin should use maven artifactId if project name is not set
Ulli Hafner commented on JENKINS-19904 PMD plugin should use maven artifactId if project name is not set Is this in a maven or freestyle job? I thought that variables should be resolved in maven jobs. 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] [robot-plugin] (JENKINS-21739) links to robot framework report files are invalid when inside a folder
Régis Desgroppes created JENKINS-21739 links to robot framework report files are invalid when inside a folder Issue Type: Bug Assignee: jpiironen Components: robot-plugin Created: 10/Feb/14 1:59 PM Description: Links to robot framework report files are invalid (404) when the job is inside a folder (from CloudBees Folder plugin). For example, instead of: /job/my_folder/my_job/3446/robot/report/report.html ... I should get: /job/my_folder/job/my_job/3446/robot/report/report.html Project: Jenkins Priority: Major Reporter: Régis Desgroppes 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] [core] (JENKINS-21664) Plugins with optional dependencies and compiled with Java6 cause Exception in loading
ikedam closed JENKINS-21664 as Not A Defect Plugins with optional dependencies and compiled with Java6 cause Exception in loading This is not a issue with Jenkins, but Java language feature. I wrote a tips note for this problem: https://wiki.jenkins-ci.org/display/JENKINS/Tips+for+optional+dependencies Change By: ikedam (10/Feb/14 2:08 PM) Status: Open Closed Resolution: NotADefect 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] [testng] (JENKINS-20686) NPE in TestNG plugin
NetAppBlueDevil commented on JENKINS-20686 NPE in TestNG plugin Thanks. Just determined the same late Friday. The XSL we had to merge multiple result files was missing the information for the cdata-section attribute and was dropping the CDATA tags. 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] [extra-columns] (JENKINS-21740) Columns with value of a variable from script
dor cohen created JENKINS-21740 Columns with value of a variable from script Issue Type: New Feature Assignee: Fred G Components: extra-columns Created: 10/Feb/14 2:27 PM Description: In a "view" page, allowing a column to take a value from the script that's being executed. (That value could be transferred from the script to jenkins via the environment variables.) Project: Jenkins Priority: Minor Reporter: dor cohen 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] [core] (JENKINS-8927) Create a view from the XML API
Patrik Boström edited a comment on JENKINS-8927 Create a view from the XML API Found this by looking through the source code: It is possible in Jenkins 1.509.4 to create views via the REST api view.xml: ?xml version="1.0" encoding="UTF-8"? hudson.model.ListView nameHej/name filterExecutorsfalse/filterExecutors filterQueuefalse/filterQueue properties class="hudson.model.View$PropertyList"/ jobNames comparator class="hudson.util.CaseInsensitiveComparator"/ /jobNames jobFilters/ columns hudson.views.StatusColumn/ hudson.views.WeatherColumn/ hudson.views.JobColumn/ hudson.views.LastSuccessColumn/ hudson.views.LastFailureColumn/ hudson.views.LastDurationColumn/ hudson.views.BuildButtonColumn/ /columns /hudson.model.ListView Create the view: curl -vvv -X POST -d @view.xml -H "Content-Type: text/xml" http://localhost:8080/jenkins/createView?name=Pipe2 Get the configuration: curl http://localhost:8080/jenkins/view/Pipe1/config.xml Update the view: curl -X POST -d @view.xml -H "Content-Type: text/xml" http://localhost:8080/jenkins/view/Pipe1/config.xml 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] [core] (JENKINS-8927) Create a view from the XML API
Patrik Boström commented on JENKINS-8927 Create a view from the XML API Found this by looking through the source code: It is possible in Jenkins 1.509.4 to create views via the REST api view.xml: ?xml version="1.0" encoding="UTF-8"? hudson.model.ListView nameHej/name filterExecutorsfalse/filterExecutors filterQueuefalse/filterQueue properties class="hudson.model.View$PropertyList"/ jobNames comparator class="hudson.util.CaseInsensitiveComparator"/ /jobNames jobFilters/ columns hudson.views.StatusColumn/ hudson.views.WeatherColumn/ hudson.views.JobColumn/ hudson.views.LastSuccessColumn/ hudson.views.LastFailureColumn/ hudson.views.LastDurationColumn/ hudson.views.BuildButtonColumn/ /columns /hudson.model.ListView Create the view: curl -vvv -X POST -d @pipe.xml -H "Content-Type: text/xml" http://localhost:8080/jenkins/createView?name=Pipe2 Get the configuration: curl http://localhost:8080/jenkins/view/Pipe1/config.xml Update the view: curl -X POST -d @pipe.xml -H "Content-Type: text/xml" http://localhost:8080/jenkins/view/Pipe1/config.xml 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] [core] (JENKINS-8927) Create a view from the XML API
Patrik Boström edited a comment on JENKINS-8927 Create a view from the XML API Found this by looking through the source code: It is possible in Jenkins 1.509.4 to create views via the REST api view.xml: ?xml version="1.0" encoding="UTF-8"? hudson.model.ListView nameMyView/name filterExecutorsfalse/filterExecutors filterQueuefalse/filterQueue properties class="hudson.model.View$PropertyList"/ jobNames comparator class="hudson.util.CaseInsensitiveComparator"/ /jobNames jobFilters/ columns hudson.views.StatusColumn/ hudson.views.WeatherColumn/ hudson.views.JobColumn/ hudson.views.LastSuccessColumn/ hudson.views.LastFailureColumn/ hudson.views.LastDurationColumn/ hudson.views.BuildButtonColumn/ /columns /hudson.model.ListView Create the view: curl -vvv -X POST -d @view.xml -H "Content-Type: text/xml" http://localhost:8080/jenkins/createView?name=MyView Get the configuration: curl http://localhost:8080/jenkins/view/MyView/config.xml Update the view: curl -X POST -d @view.xml -H "Content-Type: text/xml" http://localhost:8080/jenkins/view/MyView/config.xml 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] [jobgenerator] (JENKINS-21741) Add ParameterFactories option to trigger parameterized build on other projects post-build actions
Balázs Adamis created JENKINS-21741 Add ParameterFactories option to trigger parameterized build on other projects post-build actions Issue Type: New Feature Assignee: Unassigned Components: jobgenerator Created: 10/Feb/14 3:05 PM Description: I would like to use parameter files to generate jobs using the jobgenerator plugin as post-build action, but unfortunately it is not possible to add parameter factories to "Trigger parameterized build on other projects" in post-build actions. See also: https://groups.google.com/forum/#!searchin/jenkinsci-users/parameter$20factories/jenkinsci-users/MmQFuTuimts/9hEzihMTgAcJ Project: Jenkins Priority: Major Reporter: Balázs Adamis 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] [jobgenerator] (JENKINS-21742) Job generator parameters are not resolved correctly for normal build steps
Balázs Adamis
created JENKINS-21742
Job generator parameters are not resolved correctly for normal build steps
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
jobgenerator
Created:
10/Feb/14 3:27 PM
Description:
Using a normal "build" step "Trigger/call builds on other projects"
and "Predefined Generator parametes" then the parameters are not resolved
correctly.
For example if I use "LANGUAGE" as generator parameter and set it to EN the
generated job will be "${LANGUAGE}_C" using "${LANGUAGE}_C" as "Generated
Job Name". Expected name is "EN_C".
Using "File Generator Parameter Factory" also resulted in one "${LANGUAGE}_C" job.
See also:
https://groups.google.com/forum/#!searchin/jenkinsci-users/parameter$20factories/jenkinsci-users/MmQFuTuimts/9hEzihMTgAcJ
Environment:
Jenkins 1.550
Job Generator 1.20
Debian Wheezy
Project:
Jenkins
Priority:
Major
Reporter:
Balázs Adamis
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] [core] (JENKINS-20858) Images missing from Jenkins UI
Franco Salas edited a comment on JENKINS-20858 Images missing from Jenkins UI Still occurs in version 1.549 (installed as a windows 7 service) Edit: We found out the problem was that we had a bot periodically cleaning the TEMP folder and so it would destroy all the Jenkins images and CSS files. Why are all images and CSS files stored in the TEMP folder? It seems to be counter productive to put all these files in a temporary folder which is shared by other applications. 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] [plugin] (JENKINS-21713) MultiJob Plugin does continue phase before current phase succeeded
Jan Henne commented on JENKINS-21713 MultiJob Plugin does continue phase before current phase succeeded Could you please tell us what you did to fix it as I can't see a new version under "manage plugins" 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] [maven-metadata-plugin] (JENKINS-21743) Enable/Implement CLI parameter submission for Maven Metadata Plugin
Pierre Hanselmann created JENKINS-21743 Enable/Implement CLI parameter submission for Maven Metadata Plugin Issue Type: Bug Affects Versions: current Assignee: Gesh Markov Components: maven-metadata-plugin Created: 10/Feb/14 3:53 PM Description: CLI parameter submission is not support for this plugin. When invoking jenkins-cli build on a specific job that use "maven metadata plugin": java -jar jenkins-cli.jar -s http://myjenkins.test.com/ build refresh-setup2-5-install-version -p STATIC_ROLLOUT=1.0.26 I get the following error: CLI parameter submission is not supported for the class eu.markov.jenkins.plugin.mvnmeta.MavenMetadataParameterDefinition type. Please file a bug report for this Here is a sample of the config.xml (Changed some namespace for anonymous reason): eu.markov.jenkins.plugin.mvnmeta.MavenMetadataParameterDefinition plugin="maven-metadata-plugin@1.0.0" nameSTATIC_ROLLOUT/name description/description repoBaseUrlhttp://nexus.x.com/content/repositories/x-repository/repoBaseUrl groupIdcom.x.x.operating/groupId artifactIdx-x-rollout/artifactId packaging/packaging defaultValue/defaultValue versionFilter/versionFilter sortOrderDESC/sortOrder maxVersions10/maxVersions /eu.markov.jenkins.plugin.mvnmeta.MavenMetadataParameterDefinition Project: Jenkins Priority: Major Reporter: Pierre Hanselmann 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] [maven-metadata-plugin] (JENKINS-21743) Enable/Implement CLI parameter submission for Maven Metadata Plugin
Pierre Hanselmann updated JENKINS-21743 Enable/Implement CLI parameter submission for Maven Metadata Plugin Change By: Pierre Hanselmann (10/Feb/14 3:55 PM) Description: CLIparametersubmissionisnotsupportforthisplugin.Wheninvokingjenkins-clibuildonaspecificjobthatusemavenmetadataplugin:java-jarjenkins-cli.jar-shttp://myjenkins.test.com/buildrefresh-setup2-5-install-version-pSTATIC_ROLLOUT=1.0.26Igetthefollowingerror:CLIparametersubmissionisnotsupportedfortheclasseu.markov.jenkins.plugin.mvnmeta.MavenMetadataParameterDefinitiontype.PleasefileabugreportforthisHereisasampleoftheconfig.xml(Changedsomenamespaceforanonymousreason):eu.markov.jenkins.plugin.mvnmeta.MavenMetadataParameterDefinitionplugin=maven-metadata-plugin@1.0.0nameSTATIC_ROLLOUT/namedescription/descriptionrepoBaseUrlhttp://nexus.x.com/content/repositories/x-repository/repoBaseUrlgroupIdcom.x.x.operating/groupIdartifactIdx-x-rollout/artifactIdpackaging/packagingdefaultValue/defaultValueversionFilter/versionFiltersortOrderDESC/sortOrdermaxVersions10/maxVersions/eu.markov.jenkins.plugin.mvnmeta.MavenMetadataParameterDefinition Thisfeaturewouldbeahugeprogressforus...Isthispluginstillmaintained.Thanksforyourhelp/feedback. 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] [ci-game] (JENKINS-21744) Unstable build shouldn't discount all points
James Howe created JENKINS-21744 Unstable build shouldnt discount all points Issue Type: Bug Assignee: redsolo Components: ci-game Created: 10/Feb/14 4:00 PM Description: It appears any job that's unstable gets no points. Therefore, you never get penalised for failing tests, or improving without toatally fixing, as those events always result in an unstable build. If I add 10 passing tests or fix 10 warnings, but the build is still unstable, I should still get those points. Project: Jenkins Priority: Major 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] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Jesse Glick assigned JENKINS-21279 to Kohsuke Kawaguchi java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING Change By: Jesse Glick (10/Feb/14 4:16 PM) Assignee: KohsukeKawaguchi 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] [core] (JENKINS-20534) Pegged CPU by writeSymlink calls
Jesse Glick assigned JENKINS-20534 to Vincent Latombe Pegged CPU by writeSymlink calls Change By: Jesse Glick (10/Feb/14 4:20 PM) Assignee: VincentLatombe 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] [core] (JENKINS-20534) Pegged CPU by writeSymlink calls
Jesse Glick started work on JENKINS-20534 Pegged CPU by writeSymlink calls Change By: Jesse Glick (10/Feb/14 4:20 PM) Status: Open InProgress 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] [gerrit-trigger] (JENKINS-15065) Gerrit server suddenly shutdown and as a consequence the Jenkins Gerrit-Trigger fails to restart.
Kevin Brotcke commented on JENKINS-15065 Gerrit server suddenly shutdown and as a consequence the Jenkins Gerrit-Trigger fails to restart. I also saw this issue. Gerrit went down in the middle of the night and Gerrit Trigger was not able to reconnect, although I was able to restart Gerrit Trigger through the console without restarting Jenkins. I saw the errors below many times in the logs. It looks like the server was down for several hours and the Gerrit Trigger connection timed out eventually. SEVERE: IOException: com.sonyericsson.hudson.plugins.gerrit.gerritevents.ssh.SshException: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection timed out at com.sonyericsson.hudson.plugins.gerrit.gerritevents.ssh.SshConnectionImpl.init(SshConnectionImpl.java:126) at com.sonyericsson.hudson.plugins.gerrit.gerritevents.ssh.SshConnectionFactory.getConnection(SshConnectionFactory.java:76) at com.sonyericsson.hudson.plugins.gerrit.gerritevents.GerritConnection.connect(GerritConnection.java:365) at com.sonyericsson.hudson.plugins.gerrit.gerritevents.GerritConnection.run(GerritConnection.java:293) Caused by: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection timed out at com.jcraft.jsch.Util.createSocket(Util.java:341) at com.jcraft.jsch.Session.connect(Session.java:192) at com.jcraft.jsch.Session.connect(Session.java:160) at com.sonyericsson.hudson.plugins.gerrit.gerritevents.ssh.SshConnectionImpl.init(SshConnectionImpl.java:122) ... 3 more Caused by: java.net.ConnectException: Connection timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:327) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:193) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:180) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:385) at java.net.Socket.connect(Socket.java:546) at java.net.Socket.connect(Socket.java:495) at java.net.Socket.init(Socket.java:392) at java.net.Socket.init(Socket.java:206) at com.jcraft.jsch.Util.createSocket(Util.java:335) ... 6 more Feb 6, 2014 2:17:32 AM com.sonyericsson.hudson.plugins.gerrit.gerritevents.GerritConnection connect SEVERE: Could not connect to Gerrit server! Host: myserver.com Port: # 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] [cloudbees-folder] (JENKINS-21724) 'Move' action does not work.
Jesse Glick commented on JENKINS-21724 Move action does not work. Oops, fixing. 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] [cloudbees-folder] (JENKINS-21724) 'Move' action does not work.
Jesse Glick started work on JENKINS-21724 Move action does not work. Change By: Jesse Glick (10/Feb/14 4:28 PM) Status: Open InProgress 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] [github-oauth] (JENKINS-16492) Upgrade from 0.12 to 0.13 breaks server
evernat resolved JENKINS-16492 as Fixed Upgrade from 0.12 to 0.13 breaks server release 0.13.1 is said to contain the fix, so resolving as fixed. Change By: evernat (10/Feb/14 4: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] [cloudbees-folder] (JENKINS-21724) 'Move' action does not work.
SCM/JIRA link daemon commented on JENKINS-21724 Move action does not work. Code changed in jenkins User: Jesse Glick Path: src/main/resources/com/cloudbees/hudson/plugins/folder/relocate/RelocateAction/action.jelly src/main/resources/com/cloudbees/hudson/plugins/folder/relocate/RelocateAction/index.jelly src/main/resources/com/cloudbees/hudson/plugins/folder/relocate/RelocateAction/index.properties src/main/resources/com/cloudbees/hudson/plugins/folder/relocate/RelocationAction/action.jelly src/main/resources/com/cloudbees/hudson/plugins/folder/relocate/RelocationAction/index.jelly src/main/resources/com/cloudbees/hudson/plugins/folder/relocate/RelocationAction/index.properties http://jenkins-ci.org/commit/cloudbees-folder-plugin/990562eb74917c6615c4894fd467b3a0607e21ba Log: FIXED JENKINS-21724 282c9b9 in 4.3 failed to rename Jelly views. 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] [cloudbees-folder] (JENKINS-21724) 'Move' action does not work.
SCM/JIRA link daemon resolved JENKINS-21724 as Fixed Move action does not work. Change By: SCM/JIRA link daemon (10/Feb/14 4:35 PM) Status: InProgress 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] [core] (JENKINS-16033) Workspace cleaning locks up all workspaces
evernat commented on JENKINS-16033 Workspace cleaning locks up all workspaces Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17526) Broken CSS when reloading Jenkins after a time of inactivity
Nick Achtien commented on JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity I was just able to reproduce this issue in version 1.549 where it was supposed to be 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] [maven] (JENKINS-15841) tried to access method hudson.model.AbstractBuild.setBuiltOnStr(Ljava/lang/String;)V
evernat commented on JENKINS-15841 tried to access method hudson.model.AbstractBuild.setBuiltOnStr(Ljava/lang/String;)V Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17526) Broken CSS when reloading Jenkins after a time of inactivity
Jon Wilson commented on JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity Still seeing this issue with Jenkins 1.549. Appears unresolved. Running Jenkins on MacOS X Mountain Lion. 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] [core] (JENKINS-17526) Broken CSS when reloading Jenkins after a time of inactivity
Nick Achtien edited a comment on JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity I was just able to reproduce this issue in version 1.549 where it was supposed to be fixed. I am running it on Mac OSX Mountain Lion. 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] [core] (JENKINS-17526) Broken CSS when reloading Jenkins after a time of inactivity
Richard Mortimer commented on JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity I think that this is the same issue as JENKINS-20682. I added some notes regarding how that might be fixed but don't have the time at the moment to delve into the workings of winstone.jar to make a production ready 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] [git-client] (JENKINS-21745) [git-client] NoClassDefFoundException: ...GitClient when trying to paste a repository URL
Thomas Keller created JENKINS-21745 [git-client] NoClassDefFoundException: ...GitClient when trying to paste a repository URL Issue Type: Bug Assignee: Nicolas De Loof Components: git-client Created: 10/Feb/14 5:22 PM Description: I want to configure a build job with git connectivity. As soon as I enter anything into the "Repository URL" field and leave the focus, the above mentioned exception pops up (see full stack trace below). What I tried so far: switched between openjdk and oracle jdk (the stack trace is from the latter) downgraded to older versions of the plugin (with no success down to 1.4.5) checked the contents of the git-client.hpi / extracted plugin, which has the file that the class loader moans about (Side note: while I could find GitClient.class in plugins/git-client/WEB-INF/lib/classes.jar, I could not find org.kohsuke.stapler.* there or in the other jars of the plugin, is this packaged somewhere else?) Is there any workaround / anything I could try to remedy this problem? Jenkins without even basic git support is a major blocker for us... Many thanks! Thomas. Git version: 1.7.9.5 Plugin version: 1.6.2 Jenkins version: 1.549 (running standalone in Jetty) $ uname -a Linux Odin 3.8.0-35-generic #52~precise1-Ubuntu SMP Thu Jan 30 17:24:40 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ java -version java version "1.7.0_51" Java(TM) SE Runtime Environment (build 1.7.0_51-b13) Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode) Full Stacktrace: javax.servlet.ServletException: java.lang.NoClassDefFoundError: org.jenkinsci.plugins.gitclient.GitClient at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) 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 jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) 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
[JIRA] [git-client] (JENKINS-21745) [git-client] NoClassDefFoundException: ...GitClient when trying to paste a repository URL
Thomas Keller updated JENKINS-21745 [git-client] NoClassDefFoundException: ...GitClient when trying to paste a repository URL Change By: Thomas Keller (10/Feb/14 5:26 PM) Description: Iwanttoconfigureabuildjobwithgitconnectivity.AssoonasIenteranythingintotheRepositoryURLfieldandleavethefocus,theabovementionedexceptionpopsup(seefullstacktracebelow).WhatItriedsofar:-switchedbetweenopenjdkandoraclejdk(thestacktraceisfromthelatter)-downgradedtoolderversionsoftheplugin(withnosuccessdownto1.4.5)-checkedthecontentsofthegit-client.hpi/extractedplugin,whichhasthefilethattheclassloadermoansabout(Sidenote:whileIcouldfindGitClient.classinplugins/git-client/WEB-INF/lib/classes.jar,Icouldnotfindorg.kohsuke.stapler.*thereorintheotherjarsoftheplugin,isthispackagedsomewhereelse?)Isthereanyworkaround/anythingIcouldtrytoremedythisproblem?Jenkinswithoutevenbasicgitsupportisamajorblockerforus...Manythanks!Thomas.---Gitversion:1.7.9.5Pluginversion:1.6.2Jenkinsversion:1.549(runningstandaloneinJetty) $uname-a LinuxOdin3.8.0-35-generic#52~precise1-UbuntuSMPThuJan3017:24:40UTC2014x86_64x86_64x86_64GNU/Linux$java-versionjavaversion1.7.0_51Java(TM)SERuntimeEnvironment(build1.7.0_51-b13)JavaHotSpot(TM)64-BitServerVM(build24.51-b03,mixedmode)FullStacktrace:javax.servlet.ServletException:java.lang.NoClassDefFoundError:org.jenkinsci.plugins.gitclient.GitClient atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:858) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:858) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:858) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:631) atorg.kohsuke.stapler.Stapler.service(Stapler.java:225) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:848) atorg.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) athudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
[JIRA] [support-core] (JENKINS-21669) Show ulimit -a
Steven Christou assigned JENKINS-21669 to Steven Christou Show ulimit -a Change By: Steven Christou (10/Feb/14 5:36 PM) Assignee: StevenChristou 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] [subversion] (JENKINS-21712) Jenkins Update breaks Subversion credential configuration
stephenconnolly commented on JENKINS-21712 Jenkins Update breaks Subversion credential configuration Upgrade to credentials 1.9.4 and you have in-place addition of credentials on the configure job screen 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] [subversion] (JENKINS-21656) Credential issues when using externals after upgrade to subversion plugin 2.0
stephenconnolly resolved JENKINS-21656 as Not A Defect Credential issues when using externals after upgrade to subversion plugin 2.0 This is the desired correct new behaviour. The old behvaiour would "sleal" credentials from anywhere that would make the job work... which could provide a vector to checkout code that you do not have permission to check out. There was no option but to resolved this in this way Change By: stephenconnolly (10/Feb/14 5:40 PM) Status: Open Resolved Resolution: NotADefect 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] [subversion] (JENKINS-21645) Upgrading to Subversion plugin 2.0 causes svn integration to break
stephenconnolly commented on JENKINS-21645 Upgrading to Subversion plugin 2.0 causes svn integration to break Please install the support-core plugin, generate a bundle and attach the three files from the `plugins` subdirectory of the bundle (do not attach the whole bundle, just the three files in the bundle's plugins directory) Most likely this is a plugin version mismatch that was not addressed by Jenkins and it's poor support of upgrading dependent plugins when installing a new one 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] [support-core] (JENKINS-21669) Show ulimit -a
Steven Christou started work on JENKINS-21669 Show ulimit -a Change By: Steven Christou (10/Feb/14 5:36 PM) Status: Open InProgress 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] [core] (JENKINS-20534) Pegged CPU by writeSymlink calls
SCM/JIRA link daemon commented on JENKINS-20534 Pegged CPU by writeSymlink calls Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/5c83c64e7af95bc5f216d841e4257c79403931d8 Log: FIXED JENKINS-20534 Noting merge of #1057. Compare: https://github.com/jenkinsci/jenkins/compare/da8eba20babf...5c83c64e7af9 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] [subversion] (JENKINS-21648) subversion no longer working on OSX build slave after update from 1.54 to 2.0
stephenconnolly commented on JENKINS-21648 subversion no longer working on OSX build slave after update from 1.54 to 2.0 Currently investigating this issue. Not confined to OS-X. See the mailing list for other details (e.g. David Aldrich is having this issue intermittently on windows and linux slaves) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
stephenconnolly commented on JENKINS-21679 After update to 2.0 all jobs lost Subversion urls and its not able to select Subversion at config (Source Code Management) Please generate a support bundle using the support-core plugin and remove everything from the bundle except the `plugins` directory. Attach the contents of the three files in the `plugins` directory of the support bundle. Most likely this is a plugin version incompatibility and these three files will list the versions and whether there is plugin loading issues 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] [core] (JENKINS-20534) Pegged CPU by writeSymlink calls
SCM/JIRA link daemon commented on JENKINS-20534 Pegged CPU by writeSymlink calls Code changed in jenkins User: Vincent Latombe Path: core/src/main/java/jenkins/model/PeepholePermalink.java http://jenkins-ci.org/commit/jenkins/c0742b8bff9fe407e568da7ed860f30d9ea8aedc Log: JENKINS-20534 Avoid usage of temporary file to write symlink. Creating a symlink is an atomic operation, and additionally usage of tmp file + rename performs very badly on NTFS file system because of the way the rename is tracked in the $MFT. In case symbolic links are not supported, we still fallback to a regular file. 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] [core] (JENKINS-20534) Pegged CPU by writeSymlink calls
SCM/JIRA link daemon resolved JENKINS-20534 as Fixed Pegged CPU by writeSymlink calls Change By: SCM/JIRA link daemon (10/Feb/14 5:45 PM) Status: InProgress 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] [subversion] (JENKINS-21648) subversion no longer working on OSX build slave after update from 1.54 to 2.0
Timothee Besset commented on JENKINS-21648 subversion no longer working on OSX build slave after update from 1.54 to 2.0 In my case it was the transition to the new credentials system that caused it. The main issue there is that the error message is completely unhelpful. On the windows slaves no svn credentials were needed, it must have picked them up from the system, cache whatever .. on OSX we upgraded, which turned the build config into using the new credentials stuff, but left it silently unconfigured .. causing the failures. 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] [core] (JENKINS-21746) LauncherDecorator should be able to override localhost location
Jesse Glick created JENKINS-21746 LauncherDecorator should be able to override localhost location Issue Type: Improvement Assignee: Unassigned Components: core Created: 10/Feb/14 5:53 PM Description: If a LauncherDecorator in fact runs a command on a different physical/virtual computer, as would be necessary to support running jobs inside some kind of container, then it also needs to be able to inform code like that in maven-plugin to use something other than InetAddress.getLocalHost to refer to the machine running the Jenkins slave agent. (TBD if anything other than replacing the hostname is necessary, e.g. defining a proxy port.) Environment: https://github.com/jenkinsci/maven-interceptors/pull/4#issuecomment-34653389 Project: Jenkins Labels: api 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] [scriptler] (JENKINS-14964) Add ability to call script from REST API
SCM/JIRA link daemon commented on JENKINS-14964 Add ability to call script from REST API Code changed in jenkins User: imod Path: src/main/java/org/jenkinsci/plugins/scriptler/ScriptlerManagment.java src/main/resources/org/jenkinsci/plugins/scriptler/ScriptlerManagment/runscript.properties src/test/java/org/jenkinsci/plugins/scriptler/restapi/ScriptlerRestApiTest.java http://jenkins-ci.org/commit/scriptler-plugin/dbb18c412fcf888eb683e68877e879ad91fa4bdf Log: Merge branch 'JENKINS-14964' of https://github.com/agudian/scriptler-plugin into agudian-JENKINS-14964 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] [scriptler] (JENKINS-14964) Add ability to call script from REST API
SCM/JIRA link daemon commented on JENKINS-14964 Add ability to call script from REST API Code changed in jenkins User: Andreas Gudian Path: src/main/java/org/jenkinsci/plugins/scriptler/ScriptlerManagment.java http://jenkins-ci.org/commit/scriptler-plugin/c6e37122cedcd83b37dd915f3f51e1a33847ea30 Log: JENKINS-14964 fix error text to suggest the correct URL 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] [core] (JENKINS-20534) Pegged CPU by writeSymlink calls
Oleg Nenashev updated JENKINS-20534 Pegged CPU by writeSymlink calls Change By: Oleg Nenashev (10/Feb/14 7:43 PM) Labels: lts-candidate performance 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] [core] (JENKINS-20534) Pegged CPU by writeSymlink calls
Oleg Nenashev commented on JENKINS-20534 Pegged CPU by writeSymlink calls Marked the issue as lts-candidate 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] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Walter Kacynski commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) Is there a particular reason why this is recently a problem? Some of my other masters don't experiencing this problem. 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] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Alex Earl edited a comment on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) @Walter are they all on the same version of email-ext? Also, do they all have the same plugins installed and so forth? 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] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Zachary Young commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Same here Jenkins 1.550 Parameterized Trigger plugin 2.22 Build Pipeline Plugin 1.4.2 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] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Walter Kacynski updated JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) Yes, unfortunately, I believe there to be a number of differences including the Jenkins core. Attached is "SPEEDY-support.zip". Change By: Walter Kacynski (10/Feb/14 8:28 PM) Attachment: SPEEDY-support.zip 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] [subversion] (JENKINS-21656) Credential issues when using externals after upgrade to subversion plugin 2.0
Ronny Schuetz commented on JENKINS-21656 Credential issues when using externals after upgrade to subversion plugin 2.0 But what if the externally referenced file/directory is actually in the same repository and clearly referenced relative to the repository root or relative to the current directory? The subversion 2.0 plugin requires the same credential twice now, which is not really required and complicates the job setup. 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] [ec2] (JENKINS-20352) computer/*/configure view doesn't render completely and displays exception
robmoore commented on JENKINS-20352 computer/*/configure view doesnt render completely and displays exception I am seeing similar issues with 1.20. Apparently it is affecting the rest of the config page as I can't save changes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21747) Artifact archiving fails with java.lang.NoClassDefFoundError
Grant Limberg created JENKINS-21747 Artifact archiving fails with java.lang.NoClassDefFoundError Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 10/Feb/14 9:08 PM Description: After upgrading to Jenkins 1.550 this morning, projects are failing when archiving artifacts. Archiving artifacts ERROR: Failed to archive artifacts: package/*.tar.gz java.io.IOException: remote file operation failed: /home/jenkins-builds/workspace/Build-RocketX-Driver-Linux at hudson.remoting.Channel@496d864e:Elysium at hudson.FilePath.act(FilePath.java:910) at hudson.FilePath.act(FilePath.java:887) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:138) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:784) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:756) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:705) at hudson.model.Run.execute(Run.java:1695) at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:73) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.io.IOException: Remote call on Elysium failed at hudson.remoting.Channel.call(Channel.java:731) at hudson.FilePath.act(FilePath.java:903) ... 11 more Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.apache.tools.ant.Location at org.apache.tools.ant.ProjectComponent.init(ProjectComponent.java:43) at org.apache.tools.ant.types.DataType.init(DataType.java:40) at org.apache.tools.ant.types.AbstractFileSet.init(AbstractFileSet.java:82) at org.apache.tools.ant.types.FileSet.init(FileSet.java:36) at hudson.Util.createFileSet(Util.java:1025) at hudson.tasks.ArtifactArchiver$ListFiles.invoke(ArtifactArchiver.java:181) at hudson.tasks.ArtifactArchiver$ListFiles.invoke(ArtifactArchiver.java:172) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2461) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:701) Environment: Ubuntu 12.04 slave Jenkins 1.550 OpenJDK 1.6.0_27 java version 1.6.0_27 OpenJDK Runtime Environment (IcedTea6 1.12.6) (6b27-1.12.6-1ubuntu0.12.04.4) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) Project: Jenkins Priority: Major Reporter: Grant Limberg 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
[JIRA] [core] (JENKINS-21747) Artifact archiving fails with java.lang.NoClassDefFoundError
Grant Limberg updated JENKINS-21747 Artifact archiving fails with java.lang.NoClassDefFoundError Change By: Grant Limberg (10/Feb/14 9:13 PM) Environment: Ubuntu12.04 SSH slaveJenkins1.550OpenJDK1.6.0_27javaversion1.6.0_27OpenJDKRuntimeEnvironment(IcedTea61.12.6)(6b27-1.12.6-1ubuntu0.12.04.4)OpenJDK64-BitServerVM(build20.0-b12,mixedmode) 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] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Alex Earl commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) I'll try and diff the SPEEDY vs others and see if anything pops out at me. 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] [core] (JENKINS-21748) Cloud slaves do not take work when master executor has 0 for the number of executors
Ryan Smith created JENKINS-21748 Cloud slaves do not take work when master executor has 0 for the number of executors Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 10/Feb/14 9:38 PM Description: If you set the master executor limit to 0, exclusive slaves will not pick up work. The Node.java canTake method returns: this node is reserved for tasks that are tied to it. Project: Jenkins Priority: Minor Reporter: Ryan Smith 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] [core] (JENKINS-21748) Cloud slaves do not take work when master executor has 0 for the number of executors
Ryan Smith
commented on JENKINS-21748
Cloud slaves do not take work when master executor has 0 for the number of executors
The logic in Node.java is broken (starting at line 334):
if(l==null getMode()== Mode.EXCLUSIVE) {
// flyweight tasks need to get executed somewhere, if every node
if (!(item.task instanceof Queue.FlyweightTask (
this instanceof Jenkins
Jenkins.getInstance().getNumExecutors() 1
Jenkins.getInstance().getMode() == Mode.EXCLUSIVE)
)) {
return CauseOfBlockage.fromMessage(Messages._Node_BecauseNodeIsReserved(getNodeName())); // this node is reserved for tasks that are tied to it
}
}
The criteria about the master's number of executors and mode should only be taken into account if this is Jenkins.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-17608) Test Link plugin, show the test results in the category notes
Josh He commented on JENKINS-17608 Test Link plugin, show the test results in the category notes I would love to see this new improvement added to plug in as well. I think it will help out a lot with work flow. Thanks Josh 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-multijob-plugin] (JENKINS-21675) Concurrent multijob build runs incorrectly link to the latest dependent build run.
David Tweet reopened JENKINS-21675 Concurrent multijob build runs incorrectly link to the latest dependent build run. This was marked as fixed without comment or fix version. As I am unclear on what was done, I am re-opening. Please let me know if additional steps to reproduce are required, or if I should be re-opening JENKINS-15965 instead. Change By: David Tweet (10/Feb/14 11:59 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] [git-server] (JENKINS-21163) Git server plugin blocks Jenkins startup
Mark Waite updated JENKINS-21163 Git server plugin blocks Jenkins startup Change By: Mark Waite (11/Feb/14 1:00 AM) Assignee: NicolasDeLoof Description: AddingtheGit server plugincausetheJenkinsservertofailonnextrestart.Jenkinsshowsthefollowingerror:hudson.util.HudsonFailedToLoad:org.jvnet.hudson.reactor.ReactorException:java.lang.Error:java.lang.reflect.InvocationTargetException athudson.WebAppMain$3.run(WebAppMain.java:234)Causedby:org.jvnet.hudson.reactor.ReactorException:java.lang.Error:java.lang.reflect.InvocationTargetException atorg.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269) atjenkins.InitReactorRunner.run(InitReactorRunner.java:44) atjenkins.model.Jenkins.executeReactor(Jenkins.java:908) atjenkins.model.Jenkins.init(Jenkins.java:807) athudson.model.Hudson.init(Hudson.java:82) athudson.model.Hudson.init(Hudson.java:78) athudson.WebAppMain$3.run(WebAppMain.java:222)Causedby:java.lang.Error:java.lang.reflect.InvocationTargetException athudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:109) athudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:169) atorg.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) atjenkins.model.Jenkins$7.runTask(Jenkins.java:897) atorg.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) atorg.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) atjava.lang.Thread.run(Thread.java:701)Causedby:java.lang.reflect.InvocationTargetException atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod) atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) atjava.lang.reflect.Method.invoke(Method.java:622) athudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105) ...8moreCausedby:java.lang.NullPointerException athudson.plugins.git.GitTool.onLoaded(GitTool.java:105) ...13more Component/s: git-usercontent Component/s: git Component/s: git-client 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] [git] (JENKINS-21654) Unable to pull the code from github
Mark Waite closed JENKINS-21654 as Cannot Reproduce Unable to pull the code from github Change By: Mark Waite (11/Feb/14 1:05 AM) 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] [git] (JENKINS-21654) Unable to pull the code from github
Mark Waite resolved JENKINS-21654 as Cannot Reproduce Unable to pull the code from github No response from the submitter, and no hints what could be causing the problem, other than possibly incorrect environment variables on the system. Change By: Mark Waite (11/Feb/14 1:05 AM) Status: Open Resolved Resolution: CannotReproduce 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] [git] (JENKINS-20674) Downgrading from Git plugin 2.0 to 1.1.29 is impossible
Mark Waite resolved JENKINS-20674 as Wont Fix Downgrading from Git plugin 2.0 to 1.1.29 is impossible Downgrading from a major version upgrade is possible, but quite difficult, since it requires also downgrading dependencies (like git-client-plugin). In this case, the git-client-plugin version 1.0.1 was required and not found. Rather than fix this downgrade problem, we should focus our effort on fixing the bugs which cause users to want to downgrade. Change By: Mark Waite (11/Feb/14 1:08 AM) Status: Open Resolved Resolution: WontFix 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] [git] (JENKINS-20674) Downgrading from Git plugin 2.0 to 1.1.29 is impossible
Mark Waite closed JENKINS-20674 as Wont Fix Downgrading from Git plugin 2.0 to 1.1.29 is impossible Change By: Mark Waite (11/Feb/14 1:10 AM) 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] [copyartifact] (JENKINS-21274) CopyArtifact plugin version 1.28 does not work if Maven plugin is disabled
SCM/JIRA link daemon commented on JENKINS-21274 CopyArtifact plugin version 1.28 does not work if Maven plugin is disabled Code changed in jenkins User: ikedam Path: src/main/java/hudson/plugins/copyartifact/CopyArtifact.java http://jenkins-ci.org/commit/copyartifact-plugin/ddb5694d400987e0af0e879ac525c4ab759e69ee Log: Merge pull request #30 from ikedam/feature/JENKINS-21274_UnexpectedClassLoading JENKINS-21274 Fixed startup failure without maven-plugin when compiled with JDK 1.6 Compare: https://github.com/jenkinsci/copyartifact-plugin/compare/d00c85521648...ddb5694d4009 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] [copyartifact] (JENKINS-21274) CopyArtifact plugin version 1.28 does not work if Maven plugin is disabled
SCM/JIRA link daemon resolved JENKINS-21274 as Fixed CopyArtifact plugin version 1.28 does not work if Maven plugin is disabled Change By: SCM/JIRA link daemon (11/Feb/14 4:49 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] [copyartifact] (JENKINS-21274) CopyArtifact plugin version 1.28 does not work if Maven plugin is disabled
SCM/JIRA link daemon commented on JENKINS-21274 CopyArtifact plugin version 1.28 does not work if Maven plugin is disabled Code changed in jenkins User: ikedam Path: src/main/java/hudson/plugins/copyartifact/CopyArtifact.java http://jenkins-ci.org/commit/copyartifact-plugin/f3a75a6bcaec0b600ddb1cf76ae1126f960c791f Log: FIXED JENKINS-21274 Fixed startup failure when maven-plugin is disabled, compiled with JDK 1.6. SEE https://wiki.jenkins-ci.org/display/JENKINS/Tips+for+optional+dependencies for details. 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] [copyartifact] (JENKINS-20398) Add a feature to configure projects to allow copy artifacts
SCM/JIRA link daemon resolved JENKINS-20398 as Fixed Add a feature to configure projects to allow copy artifacts Change By: SCM/JIRA link daemon (11/Feb/14 4:51 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.
