[JIRA] [findbugs] (JENKINS-21974) Publish pmd analysis results
Pankaj Kumar created JENKINS-21974 Publish pmd analysis results Issue Type: Bug Assignee: Ulli Hafner Attachments: publish pmd analysis issue.txt Components: findbugs, pmd Created: 27/Feb/14 8:03 AM Description: I am having pmd plugin with my jenkins installation. But when i select the post build step "publish pmd analysis result", provide the path for the pmd xml file, and click on save, I get error thrown. For details i have attached the error stack trace for better understanding of the problem. Environment: Jenkins v1.545, WINDOWS 7 32 bit, IE 9 Project: Jenkins Labels: plugin configuration Priority: Major Reporter: Pankaj Kumar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-status] (JENKINS-21920) Can't take node offline
Aleksey Maksimov commented on JENKINS-21920 Can't take node offline Yes, the same applies for all nodes. After looking at the source code generating that error (hudson.slaves.OfflineCause) it looks like it shall be possible to take slave offline in secured Jenkins. I need to verify that though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [msbuild] (JENKINS-15029) Update of MSBuild plugin to 1.15 causes Parameterized trigger plugin to fail.
ikedam updated JENKINS-15029 Update of MSBuild plugin to 1.15 causes Parameterized trigger plugin to fail. Sounds not related with parameterized-trigger plugin. Points that may help: What happens without parameterized-trigger? (triggering directly) What happens changing SOURCE to other name? (it may be a reserved name) What is output when run set with Windows batch builder? (SOURCE is logged?) Attach build.xml of failed build with msbuild-plugin. Change By: ikedam (27/Feb/14 8:11 AM) Component/s: parameterized-trigger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ivy] (JENKINS-15002) Parameterized trigger passes no parameters from Ivy Project
ikedam updated JENKINS-15002 Parameterized trigger passes no parameters from Ivy Project Change By: ikedam (27/Feb/14 8:22 AM) Component/s: parameterized-trigger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ivy] (JENKINS-21975) Add notice about the combination of ivy plugin and parameterizrd-trigger plugin
ikedam created JENKINS-21975 Add notice about the combination of ivy plugin and parameterizrd-trigger plugin Issue Type: Task Assignee: Timothy Bingaman Components: ivy, parallel-test-executor Created: 27/Feb/14 8:30 AM Description: In JENKINS-15002, it is reported that parameterized-trigger plugin deos not work with ivy plugin, as ivy plugin handles DependencyGraph in its own manner. Is it still so? If so, I'll add notices in the wiki page of parameterized-trigger. (I'd like you do so also in the wiki page of ivy plugin). Project: Jenkins Priority: Minor Reporter: ikedam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-14145) Promoted Builds + Parameterized Trigger fails to pass Git revision
ikedam updated JENKINS-14145 Promoted Builds + Parameterized Trigger fails to pass Git revision Change By: ikedam (27/Feb/14 8:41 AM) Component/s: git Component/s: parameterized-trigger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-13768) default parameter values are ignored when triggering parameterized build from groovy post-build script
ikedam updated JENKINS-13768 default parameter values are ignored when triggering parameterized build from groovy post-build script Change By: ikedam (27/Feb/14 8:49 AM) Issue Type: Bug Improvement Assignee: huybrechts Component/s: core Component/s: parameterized-trigger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-21932) Job hangs if one of multiple triggered builds was aborted
Sergey Irisov updated JENKINS-21932 Job hangs if one of multiple triggered builds was aborted Change By: Sergey Irisov (27/Feb/14 8:52 AM) Attachment: slave2_config.xml Attachment: launcher_multiple_job_config.xml Attachment: slave1_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] [parameterized-trigger] (JENKINS-13548) Cyclic jobs required, but cause issues
ikedam updated JENKINS-13548 Cyclic jobs required, but cause issues Change By: ikedam (27/Feb/14 8:52 AM) Issue Type: Bug New Feature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-21932) Job hangs if one of multiple triggered builds was aborted
Sergey Irisov commented on JENKINS-21932 Job hangs if one of multiple triggered builds was aborted I can reproduce now only first case. Parent job: Launcher_trigger_multiple_job. It triggers 2 job: Slave_job and Slave_job2. Slave_job was aborted while it stays in queue. And Slave_job2 successfully finished. Launcher job hung waiting for Slave_job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-21932) Job hangs if one of multiple triggered builds was aborted
Sergey Irisov edited a comment on JENKINS-21932 Job hangs if one of multiple triggered builds was aborted I can reproduce now only first case. Parent job: Launcher_trigger_multiple_job. It triggers 2 job: Slave_job and Slave_job2. Slave_job was aborted while it stays in queue. And Slave_job2 successfully finished. Launcher job hung waiting for Slave_job. Jobs' configs are in attachment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-13548) Cyclic jobs required, but cause issues
ikedam resolved JENKINS-13548 as Won't Fix Cyclic jobs required, but cause issues This cannot be done in the framework provided by Jenkins. You need some hacks to do that. Though I think your way (triggering with wget) is the best, following plugins may help you. https://wiki.jenkins-ci.org/display/JENKINS/FSTrigger+Plugin https://wiki.jenkins-ci.org/display/JENKINS/Files+Found+Trigger Change By: ikedam (27/Feb/14 8:59 AM) Status: Open Resolved Resolution: Won't 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] [parameterized-trigger] (JENKINS-12480) Build step that runs multiple jobs in parallel, and blocks until all are complete
ikedam updated JENKINS-12480 Build step that runs multiple jobs in parallel, and blocks until all are complete I get this ticket is a request of a new feature as described by Marco. If not, please let me know what the real problem is. and update the description. Change By: ikedam (27/Feb/14 9:07 AM) Issue Type: Bug New Feature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-21932) Job hangs if one of multiple triggered builds was aborted
Oleg Nenashev edited a comment on JENKINS-21932 Job hangs if one of multiple triggered builds was aborted I suppose this issue and JENKINS-16679 have the same origin. After the initial analysis of JENKINS-16679 (I've done it several months ago; hope to find notes), I suspect that it may require a fix inside the Jenkins core. As a workaround, it is possible to analyze statuses of future tasks instead of sequential "wait" calls against the submitted projects list. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-13362) triggered parameterized run even though a parameter is not set. first it complains that is isn't set and isn't able to trigger it, then it triggers it.
ikedam updated JENKINS-13362 triggered parameterized run even though a parameter is not set. first it complains that is isn't set and isn't able to trigger it, then it triggers it. I think it is a sound behavior to say error without a specified file. How about using conditional-buildstep plugin or flexible-publish plugin? https://wiki.jenkins-ci.org/display/JENKINS/Conditional+BuildStep+Plugin https://wiki.jenkins-ci.org/display/JENKINS/Flexible+Publish+Plugin Change By: ikedam (27/Feb/14 9:16 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] [parameterized-trigger] (JENKINS-12686) Predefined parameters on a post-join build are evaluated by a child job rather than parent
ikedam commented on JENKINS-12686 Predefined parameters on a post-join build are evaluated by a child job rather than parent Please let me know how I can reproduce the problem. configurations of jobs expected behavior actual behavior I know it doesn't always happen. I want to have a detailed example configuration. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-12410) Downstream jobs not associated with upstream parent job properly
ikedam commented on JENKINS-12410 Downstream jobs not associated with upstream parent job properly Does it always happen? Would you attach build.xml of the build raised the 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] [parameterized-trigger] (JENKINS-10779) Non-existing parameters are not empty but replaced with parameter name
ikedam updated JENKINS-10779 Non-existing parameters are not empty but replaced with parameter name Change By: ikedam (27/Feb/14 9:29 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] [parameterized-trigger] (JENKINS-12290) Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
ikedam updated JENKINS-12290 Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor Change By: ikedam (27/Feb/14 9:28 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] [jenkins-multijob-plugin] (JENKINS-21804) Jenkins workspace issue
Kamlesh Singhal commented on JENKINS-21804 Jenkins workspace issue Experiencing the same issue on the same Jenkins version 1.54 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-8952) Not Expanding Environment Variable
ikedam resolved JENKINS-8952 as Not A Defect Not Expanding Environment Variable Shell script cannot export variables to subsequent build steps. Use https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin instead. Change By: ikedam (27/Feb/14 9:34 AM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-8009) Groovy script to add conditions to the parameterized trigger
ikedam resolved JENKINS-8009 as Won't Fix Groovy script to add conditions to the parameterized trigger Change By: ikedam (27/Feb/14 9:40 AM) Status: Open Resolved Resolution: Won't 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] [parameterized-trigger] (JENKINS-12290) Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
Oleg Nenashev updated JENKINS-12290 Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor Change By: Oleg Nenashev (27/Feb/14 10:06 AM) Priority: Blocker Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [disk-usage] (JENKINS-20176) Disk usage plugin write job config.xml after every build
Kent Granström commented on JENKINS-20176 Disk usage plugin write job config.xml after every build I can not see that this issue is fixed yet. I still get these items every day. 2014-02-27_08-20-46 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-26_08-20-47 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-25_08-20-46 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-24_08-20-46 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-23_08-20-45 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-22_08-20-45 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) ... Any possibility to look into this once more? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-21596) Support ReSharper commandline output
Jakob Anzenberger commented on JENKINS-21596 Support ReSharper commandline output Thanks for all these great plugins! And the resharper support is just in time for my project. Thanks for your work! The inspectcode tool works great together with the warnings plugin. But according to the github the dry plugin already supports the dupfinder tool. I just tried to use it but it just fails to parse the result.xml from dupfinder. Should I create a new issue or reopen this one? Which information should I provide? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jira] (JENKINS-21976) Rename jira cloverphp-plugin to cloverphp
Antoine Musso
created JENKINS-21976
Rename jira cloverphp-plugin to cloverphp
Issue Type:
Bug
Assignee:
Unassigned
Components:
jira
Created:
27/Feb/14 10:29 AM
Description:
The Clover PHP Wiki page 'Open Issue' link points to the wrong component.
On the wiki page https://wiki.jenkins-ci.org/display/JENKINS/Clover+PHP+Plugin we have:
{jenkins-plugin-info:pluginId=cloverphp}
That displays the information for the plugin properly.
The 'Open Issue' link search for bugs filled against 'cloverphp', but in Jira the component is registered as 'cloverphp-plugin'. As a result, no issue are opened.
Can we have the Jira component 'cloverphp-plugin' renamed to 'cloverphp'?
Thanks!
Project:
Jenkins
Priority:
Major
Reporter:
Antoine Musso
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [disk-usage] (JENKINS-20176) Disk usage plugin write job config.xml after every build
Kent Granström edited a comment on JENKINS-20176 Disk usage plugin write job config.xml after every build I can not see that this issue is fixed yet. I still get these items every day. 2014-02-27_08-20-46 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-26_08-20-47 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-25_08-20-46 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-24_08-20-46 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-23_08-20-45 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) 2014-02-22_08-20-45 hudson.plugins.disk_usage.DiskUsageProjectActionFactory (system) Changed SYSTEM View as XML (RAW) ... Any possibility to look into this once more? Perhaps I am missing something in order to omit all these This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cloverphp-plugin] (JENKINS-21976) Rename jira cloverphp-plugin to cloverphp
Steven Christou updated JENKINS-21976 Rename jira cloverphp-plugin to cloverphp Change By: Steven Christou (27/Feb/14 10:35 AM) Component/s: cloverphp-plugin Component/s: jira This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cloverphp-plugin] (JENKINS-21976) Rename jira cloverphp-plugin to cloverphp
Steven Christou commented on JENKINS-21976 Rename jira cloverphp-plugin to cloverphp Switched to cloverphp plugin component. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cloverphp-plugin] (JENKINS-21976) Rename jira cloverphp-plugin to cloverphp
Oleg Nenashev resolved JENKINS-21976 as Fixed Rename jira cloverphp-plugin to cloverphp I've modified the metadata on the plugin's Wiki page. https://wiki.jenkins-ci.org/pages/diffpages.action?pageId=57182063&originalId=71436665 Please reopen issue if this is not enough. Change By: Oleg Nenashev (27/Feb/14 10:39 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] [cloverphp-plugin] (JENKINS-21976) Rename jira cloverphp-plugin to cloverphp
Antoine Musso reopened JENKINS-21976 Rename jira cloverphp-plugin to cloverphp Assuming a mistake since the page still has the plugin id cloverphp and the plugin is still registered as cloverphp-plugin. Change By: Antoine Musso (27/Feb/14 10:54 AM) 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] [cloverphp-plugin] (JENKINS-21976) Rename jira cloverphp-plugin to cloverphp
Antoine Musso resolved JENKINS-21976 as Fixed Rename jira cloverphp-plugin to cloverphp There was a double pipe in the wiki template which caused the parameter to be ignored. Fixed finally. Thanks! Change By: Antoine Musso (27/Feb/14 11:07 AM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Ladislav Toldy commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Same problem Jenkins: 1.532.2 Build Pipeline Plugin 1.4.2 But fixed after downgrading to Jenkins: 1.532.2 Build Pipeline Plugin 1.4 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [svn-tag] (JENKINS-21925) jenkins svn tagging plugin 1.16 is broken after upgrade to Jenkins 1.550
Karsten Deubert commented on JENKINS-21925 jenkins svn tagging plugin 1.16 is broken after upgrade to Jenkins 1.550 sponsored: http://www.freedomsponsors.org/core/issue/454/jenkins-svn-tagging-plugin-116-is-broken-after-upgrade-to-jenkins-1550 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-setup] (JENKINS-13140) Disconnected slaves come back online within a few minutes
mwebber commented on JENKINS-13140 Disconnected slaves come back online within a few minutes Instead of only disconnecting, configure the slave to also have an in demand connection delay of 100. Works like a charm. I don't see a "demand connection delay" setting. Is this supplied by a particular plugin that I don't have? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-setup] (JENKINS-13140) Disconnected slaves come back online within a few minutes
mwebber edited a comment on JENKINS-13140 Disconnected slaves come back online within a few minutes Instead of only disconnecting, configure the slave to also have an in demand connection delay of 100. Works like a charm. I don't see a "demand connection delay" setting anywhere in the web UI. Is this supplied by a particular plugin that I don't have? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21977) "java.io.IOException: Failed to clean up temp dirs" because of "secret.key"
Simon Kaufmann created JENKINS-21977 "java.io.IOException: Failed to clean up temp dirs" because of "secret.key" Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 27/Feb/14 11:45 AM Description: When testing my plugin by running mvn clean test, my own tests all pass successfully. However, the cleanup for the injected ones fails: org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyTestSuite(org.jvnet.hudson.test.junit.FailedTest) Time elapsed: 0.006 sec <<< ERROR! java.io.IOException: Failed to clean up temp dirs at org.jvnet.hudson.test.TemporaryDirectoryAllocator.dispose(TemporaryDirectoryAllocator.java:86) at org.jvnet.hudson.test.TestEnvironment.dispose(TestEnvironment.java:81) at org.jvnet.hudson.test.HudsonTestCase.tearDown(HudsonTestCase.java:414) at org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyTestSuite.tearDown(JellyTestSuiteBuilder.java:138) at org.jvnet.hudson.test.junit.GroupedTest.run(GroupedTest.java:53) at junit.framework.TestSuite.runTest(TestSuite.java:255) at junit.framework.TestSuite.run(TestSuite.java:250) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) Caused by: java.nio.file.FileSystemException: C:\Users\simon\AppData\Local\Temp\hudson495525951667628343test\secret.key: The process cannot access the file bec ause it is being used by another process. at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:86) at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97) at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102) at sun.nio.fs.WindowsFileSystemProvider.implDelete(WindowsFileSystemProvider.java:269) at sun.nio.fs.AbstractFileSystemProvider.delete(AbstractFileSystemProvider.java:103) at java.nio.file.Files.delete(Files.java:1077) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.Util.deleteFile(Util.java:238) at hudson.Util.deleteRecursive(Util.java:301) at hudson.Util.deleteContentsRecursive(Util.java:203) at hudson.Util.deleteRecursive(Util.java:292) at hudson.FilePath$12.invoke(FilePath.java:1079) at hudson.FilePath$12.invoke(FilePath.java:1076) at hudson.FilePath.act(FilePath.java:914) at hudson.FilePath.act(FilePath.java:887) at hudson.FilePath.deleteRecursive(FilePath.java:1076) at org.jvnet.hudson.test.TemporaryDirectoryAllocator.dispose(TemporaryDirectoryAllocator.java:81) at org.jvnet.hudson.test.TestEnvironment.dispose(TestEnvironment.java:81) at org.jvnet.hudson.test.HudsonTestCase.tearDown(HudsonTestCase.java:414) at org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyTestSuite.tearDown(JellyTestSuiteBuilder.java:138) at org.jvnet.hudson.test.junit.GroupedTest.run(GroupedTest.java:53) at junit.framework.TestSuite.runTest(TestSuite.java:255) at junit.framework.TestSuite.run(TestSuite.java:250) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84) at org.apache.maven.surefire.junit4.JUnit4Provider.e
[JIRA] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Ladislav Toldy edited a comment on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Same problem Jenkins: 1.532.2 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] [core] (JENKINS-21977) "java.io.IOException: Failed to clean up temp dirs" because of "secret.key"
Simon Kaufmann
updated JENKINS-21977
"java.io.IOException: Failed to clean up temp dirs" because of "secret.key"
Change By:
Simon Kaufmann
(27/Feb/14 11:46 AM)
Description:
When testing my plugin by running {{mvn clean test}}, my own tests all pass successfully. However, the cleanup for the injected ones fails:{code}org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyTestSuite(org.jvnet.hudson.test.junit.FailedTest) Time elapsed: 0.006 sec <<< ERROR!java.io.IOException: Failed to clean up temp dirsat org.jvnet.hudson.test.TemporaryDirectoryAllocator.dispose(TemporaryDirectoryAllocator.java:86)at org.jvnet.hudson.test.TestEnvironment.dispose(TestEnvironment.java:81)at org.jvnet.hudson.test.HudsonTestCase.tearDown(HudsonTestCase.java:414)at org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyTestSuite.tearDown(JellyTestSuiteBuilder.java:138)at org.jvnet.hudson.test.junit.GroupedTest.run(GroupedTest.java:53)at junit.framework.TestSuite.runTest(TestSuite.java:255)at junit.framework.TestSuite.run(TestSuite.java:250)at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)Caused by: java.nio.file.FileSystemException: C:\Users\simon\AppData\Local\Temp\hudson495525951667628343test\secret.key: The process cannot access the file because it is being used by another process.at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:86)at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102)at sun.nio.fs.WindowsFileSystemProvider.implDelete(WindowsFileSystemProvider.java:269)at sun.nio.fs.AbstractFileSystemProvider.delete(AbstractFileSystemProvider.java:103)at java.nio.file.Files.delete(Files.java:1077)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:606)at hudson.Util.deleteFile(Util.java:238)at hudson.Util.deleteRecursive(Util.java:301)at hudson.Util.deleteContentsRecursive(Util.java:203)at hudson.Util.deleteRecursive(Util.java:292)at hudson.FilePath$12.invoke(FilePath.java:1079)at hudson.FilePath$12.invoke(FilePath.java:1076)at hudson.FilePath.act(FilePath.java:914)at hudson.FilePath.act(FilePath.java:887)at hudson.FilePath.deleteRecursive(FilePath.java:1076)at org.jvnet.hudson.test.TemporaryDirectoryAllocator.dispose(TemporaryDirectoryAllocator.java:81)at org.jvnet.hudson.test.TestEnvironment.dispose(TestEnvironment.java:81)at org.jvnet.hudson.test.HudsonTestCase.tearDown(HudsonTestCase.java:414)at org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyTestSuite.tearDown(JellyTestSuiteBuilder.java:138)at org.jvnet.hudson.test.junit.GroupedTest.run(GroupedTest.java:53)at junit.framework.TestSuite.runTest(TestSuite.java:255)at junit.framework.TestSuite.run(TestSuite.java:250)at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)at org.apache.maven.surefire.booter.ForkedBooter.invokeProvide
[JIRA] [coverity] (JENKINS-21481) Coverity plugin 1.3.0 crashes job with CSA/CC 6.5.1, bad parsing of VERSION
Torbjörn Axelsson commented on JENKINS-21481 Coverity plugin 1.3.0 crashes job with CSA/CC 6.5.1, bad parsing of VERSION We just upgrade to Coverity 7.0.3 and got this problem, however: # grep external /opt/cov-analysis/VERSION externalVersion=7.0.3 So we have the same problem, but it seems that the externalVersion is there in the 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] [subversion] (JENKINS-673) SCM "catch up" feature
Niklas Hambuechen commented on JENKINS-673 SCM "catch up" feature Can anybody explain if this would be part of core Jenkins or the code source, e.g. the Git 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] [git] (JENKINS-21936) Git Plugin 2.0.2 and later NullPointerException onNotifyCommit
Chris Robison commented on JENKINS-21936 Git Plugin 2.0.2 and later NullPointerException onNotifyCommit I am as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21952) Git Plugin fails to resolve tags containing a slash since 2.0.1
Mark Waite commented on JENKINS-21952 Git Plugin fails to resolve tags containing a slash since 2.0.1 Can you describe how the tags are used? Are you using the tags as the branch to checkout, or are you applying tags as part of the build process, or something completely different? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21936) Git Plugin 2.0.2 and later NullPointerException onNotifyCommit
Mark Waite commented on JENKINS-21936 Git Plugin 2.0.2 and later NullPointerException onNotifyCommit I believe this has been fixed in https://github.com/jenkinsci/git-plugin/commit/46e39047abd016f6907819d4001cc2f4982a620f . That should be included in the next release of git-plugin, probably release 2.0.4. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21936) Git Plugin 2.0.2 and later NullPointerException onNotifyCommit
Mark Waite resolved JENKINS-21936 as Fixed Git Plugin 2.0.2 and later NullPointerException onNotifyCommit Change By: Mark Waite (27/Feb/14 1:28 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] [websphere-deployer] (JENKINS-21871) Generated EAR fails to install (issues ADMC0046W)
Greg Peters started work on JENKINS-21871 Generated EAR fails to install (issues ADMC0046W) Change By: Greg Peters (27/Feb/14 1:32 PM) Status: Reopened In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-21871) Generated EAR fails to install (issues ADMC0046W)
Greg Peters updated JENKINS-21871 Generated EAR fails to install (issues ADMC0046W) Change By: Greg Peters (27/Feb/14 1:32 PM) Summary: Websphere deploy plugin Generated EAR fails to install (issues ADMC0046W) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-21596) Support ReSharper commandline output
Jakob Anzenberger edited a comment on JENKINS-21596 Support ReSharper commandline output Thanks for all these great plugins! And the resharper support is just in time for my project. Thanks for your work! The inspectcode tool works great together with the warnings plugin. But according to the github the dry plugin already supports the dupfinder tool. I just tried to use it but it just fails to parse the result.xml from dupfinder. Should I create a new issue or reopen this one? Which information should I provide? EDIT: Nevermind, I did not have the newest version installed. With 2.39 everything works fine! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [svnmerge] (JENKINS-21916) svnmerge plugin doesn't support subersion plugin 2+
SCM/JIRA link daemon commented on JENKINS-21916 svnmerge plugin doesn't support subersion plugin 2+ Code changed in jenkins User: Hugues Chabot Path: pom.xml src/main/java/jenkins/plugins/svnmerge/FeatureBranchProperty.java src/main/java/jenkins/plugins/svnmerge/IntegratableProjectAction.java http://jenkins-ci.org/commit/svnmerge-plugin/19f07a307cf678b3c968e72492ebd2b980e301e6 Log: Merge pull request #10 from jenkinsci/jenkins-21916 [FIXED JENKINS-21916] Support Subversion Plugin 2.x Compare: https://github.com/jenkinsci/svnmerge-plugin/compare/dcc521a98869...19f07a307cf6 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [svnmerge] (JENKINS-21916) svnmerge plugin doesn't support subersion plugin 2+
SCM/JIRA link daemon resolved JENKINS-21916 as Fixed svnmerge plugin doesn't support subersion plugin 2+ Change By: SCM/JIRA link daemon (27/Feb/14 1: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] [git] (JENKINS-21952) Git Plugin fails to resolve tags containing a slash since 2.0.1
Stephan Pauxberger commented on JENKINS-21952 Git Plugin fails to resolve tags containing a slash since 2.0.1 updated the description. I try to check out a deep tag (containing a slash) created by another job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21952) Git Plugin fails to resolve tags containing a slash since 2.0.1
Stephan Pauxberger updated JENKINS-21952 Git Plugin fails to resolve tags containing a slash since 2.0.1 Change By: Stephan Pauxberger (27/Feb/14 1:42 PM) Description: Since updating from 2.0.1 to 2.0.3, a job which uses tags containing a slash as "branch" does not work anymore (rel/x.y.z-... in my case) Build I my case, a sepate job creates a release tag (refs/tags/rel/my-tag).The job that stopped to work tries to check out this given tag (using a parameter: so the branch field contains the value: rel/$version)Using git plugin 2.0.1, this works. Using git plugin 2.0.3 the checkout attempt results in "Couldn't find any revision to build. Verify the repository and branch configuration for this job."Downgrading to 2.0.1 solves the problem.The problem has already been discussed in [JENKINS-14026], but the applied fix only works for slash-less 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] [teamconcert] (JENKINS-21933) PermGen leaks
Heather Fraser-Dube commented on JENKINS-21933 PermGen leaks I have raised 305293: PermGen leaks with HJPlugin to continue tracking this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-21933) PermGen leaks
Heather Fraser-Dube commented on JENKINS-21933 PermGen leaks Thanks Abhishek for the workaround. We do special class loading in order to access the toolkit(s). But the class loader should be cached and re-used. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-setup] (JENKINS-13140) Disconnected slaves come back online within a few minutes
mwebber edited a comment on JENKINS-13140 Disconnected slaves come back online within a few minutes Instead of only disconnecting, configure the slave to also have an in demand connection delay of 100. Works like a charm. I don't see a "demand connection delay" setting anywhere in the web UI. Is this supplied by a particular plugin that I don't have? Note that I'm using regular dumb slaves, not swarm. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21952) Git Plugin fails to resolve tags containing a slash since 2.0.1
Mark Waite commented on JENKINS-21952 Git Plugin fails to resolve tags containing a slash since 2.0.1 Thanks. When you reverted back to git-plugin 2.0.1, did you also revert to an earlier version of git-client-plugin, or did you remain with the current release of git-client-plugin (1.6.3)? I ask because I'm concerned that the root of the issue might be in git-client-plugin rather than git-plugin. If you only reverted the git-plugin and that was enough to resolve the issue, then the problem is most likely in the git-plugin, not in git-client-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] [git] (JENKINS-21553) Creating a new job: internal server error when using an HTTPS:// git source URL rather than a GIT:// URL
Mark Waite closed JENKINS-21553 as Cannot Reproduce Creating a new job: internal server error when using an HTTPS:// git source URL rather than a GIT:// URL Change By: Mark Waite (27/Feb/14 2:29 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21553) Creating a new job: internal server error when using an HTTPS:// git source URL rather than a GIT:// URL
Mark Waite resolved JENKINS-21553 as Cannot Reproduce Creating a new job: internal server error when using an HTTPS:// git source URL rather than a GIT:// URL Resolved as "Cannot reproduce" after waiting 10 days for a response to clarifying questions. Changes were made in plugin versions leading up to git-plugin 2.0.2 and git-client-plugin 1.6.3 which may have resolved this issue, but since the submitter has not responded, we can't confirm if those changes actually resolve the issue. Change By: Mark Waite (27/Feb/14 2:29 PM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [msbuild] (JENKINS-18632) Jenkins hangs during builds
Mark Waite updated JENKINS-18632 Jenkins hangs during builds Change By: Mark Waite (27/Feb/14 2:34 PM) Component/s: git This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [msbuild] (JENKINS-18632) Jenkins hangs during builds
Mark Waite commented on JENKINS-18632 Jenkins hangs during builds Since neither of the thread dumps includes a reference to git, I have removed git from the list of components involved in this bug report. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [perforce] (JENKINS-21972) Perforce plugin - sync to specific multiple changesets
Rob Petti assigned JENKINS-21972 to Unassigned Perforce plugin - sync to specific multiple changesets Change By: Rob Petti (27/Feb/14 2:40 PM) Assignee: Rob Petti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [perforce] (JENKINS-21972) Perforce plugin - sync to specific multiple changesets
Rob Petti commented on JENKINS-21972 Perforce plugin - sync to specific multiple changesets I won't be implementing this, because I believe it to be bad practice. You should really be using branches or streams instead. I will leave it open in case someone else wants to add it, however. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-11133) Copy artifacts from specific matrix configuration does not check stability of entire matrix
ikedam updated JENKINS-11133 Copy artifacts from specific matrix configuration does not check stability of entire matrix Change By: ikedam (27/Feb/14 2:52 PM) 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] [git] (JENKINS-21978) Couldn't find any revision to build. Verify the repository and branch configuration for this job.
Flavio Donzé created JENKINS-21978 Couldn't find any revision to build. Verify the repository and branch configuration for this job. Issue Type: Bug Assignee: Nicolas De Loof Components: git, git-client Created: 27/Feb/14 3:02 PM Description: After updating from git 1.5 to 2.0.3 and git-client from 1.3 to 1.6.3, I get the following message when I try to build from a tag: ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. Building from master works fine, I'm using the "Branch Specifier" field and "refs/tags/1.7.12" or "tags/1.7.12" as input. Environment: git 2.0.3, git-client 1.6.3 Project: Jenkins Priority: Major Reporter: Flavio Donzé This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jira] (JENKINS-21766) Jenkins create jira issue plugin does not allow configurable jira issue type: defaults to 'bug'
chris vecchione updated JENKINS-21766 Jenkins create jira issue plugin does not allow configurable jira issue type: defaults to 'bug' Change By: chris vecchione (27/Feb/14 3:47 PM) Due Date: 21 14 / Feb Mar /14 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21931) Uncaught Exception when using multiple checkout threads ( "Checkout Thread Pool Size" > 1)
Cletus D'Souza commented on JENKINS-21931 Uncaught Exception when using multiple checkout threads ( "Checkout Thread Pool Size" > 1) Has this anything to do with the code you submitted for terminating the APISession? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [artifactory] (JENKINS-21832) Can't fetch remote repositories nor deploy
Brent Duffy commented on JENKINS-21832 Can't fetch remote repositories nor deploy We're seeing the same behavior after updating from 2.1.8 to 2.2.1. Here are the steps to reproduce in a freestyle job: 1. Select "Generic Artifactory Integration" or "Gradle Artifactory Integration" under the "Build Environment" section in the job configuration. 2. Select the proper "Artifactory Server" from the drop-down. 3. No repositories show up under "Target Repository" We've found that you can work around this issue in 2.2.1 by saving the job configuration with the "Generic Artifactory Integration" check box checked, then configure your job again and the list of repositories should now show up in the "Target Repository" drop-down. It would be nice if this issue were fixed as it's a pain to edit a job config twice to get the Artifactory settings to work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21968) A SQL Exception was caught! Schema 'DBUSER' does not exist
Cletus D'Souza commented on JENKINS-21968 A SQL Exception was caught! Schema 'DBUSER' does not exist Did you set a 'Configuration Name' for each project here? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21980) Git polling fails after detached head
Dilip M created JENKINS-21980 Git polling fails after detached head Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 27/Feb/14 4:21 PM Description: Git polling depends on ‘last built’ revision. If the Jenkins job is triggered manually on different branch (detached head), the polling may result in No changes. WE have a Job which polls for changes every 5 mins. The branch is mentioned using a Parametrized plugin. Like, String parameter: name: GIT_COMMIT_TAG default: master The polling works fine. But when I run the job manually and set GIT_COMMIT_TAG to different value (which is detached head) the subsequent polling says "No changes" to build. The polling log says, Started on Feb 25, 2014 12:00:20 AM Using strategy: Default [poll] Last Built Revision: Revision 48c7cfd0bfd024abcf4e93142a78a019db0279aa (detached) Fetching changes from the remote Git repositories Fetching upstream changes from origin Polling for changes in Done. Took 1.9 sec No changes Git polling in this case will only start working after manual trigger of target branch 'master' Environment: git-client 1.2.0 git 1.5.0 Project: Jenkins Labels: git Priority: Major Reporter: Dilip M This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cpptest] (JENKINS-18727) The cppTest 9.5 xml output doesn't match the current parser rule
Dridi Boukelmoune commented on JENKINS-18727 The cppTest 9.5 xml output doesn't match the current parser rule Hi, I have sent a pull request here: https://github.com/jenkinsci/cpptest-plugin/pull/6 Dridi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [performance-plugin] (JENKINS-16627) Fail to parse jmeter report
Philippe Koutsoulis commented on JENKINS-16627 Fail to parse jmeter report Could you try with xml output format? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [buckminster] (JENKINS-21979) Add capability to set ANT LogLevel to Buckminster Plugin
Victor Roldan created JENKINS-21979 Add capability to set ANT LogLevel to Buckminster Plugin Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: buckminster Created: 27/Feb/14 4:16 PM Description: Since this buckminster bug was implemented: https://bugs.eclipse.org/bugs/show_bug.cgi?id=294440 it is now possible to set ant logging level. Current buckminster plugin implementation only passes console LogLevel Could not make it work either using the equinox arguments input box (i.e. --loglevel console=info,ant=debug) since it introduces always double quotes and fails (and also, another instance of this parameter is nevertheless passed) Environment: Tested with Jenkins 1.528 and Buckminster Plugin 1.1.1 Project: Jenkins Labels: eclipse buckminster Priority: Major Reporter: Victor Roldan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [matrix] (JENKINS-21981) Failure to save Matrix-based security authorization flag
David Lewanda created JENKINS-21981 Failure to save Matrix-based security authorization flag Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: matrix, security Created: 27/Feb/14 4:33 PM Description: In the Authorization section of the configureSecurity page, I'm trying to set a flag for the JOB/Discover field to avoid the 404 error, but everytime I do so, I get the following Exception: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) 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 org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.sess
[JIRA] [performance-plugin] (JENKINS-16627) Fail to parse jmeter report
Simon Schlachter commented on JENKINS-16627 Fail to parse jmeter report yes - as I've written above, when I force the output to xml this works. Maybe this is just something that should be added to the documentation, since the default output obviously changed between jmeter versions This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jslint] (JENKINS-21982) JSLint reports bitwise issues even though default is to allow them
Shannon Kerr created JENKINS-21982 JSLint reports bitwise issues even though default is to allow them Issue Type: Bug Assignee: Gavin Davies Components: jslint Created: 27/Feb/14 4:38 PM Description: The default mode, according the the jslint documentation, is that bitwise operators are tolerated. Even though this is the case, we are still getting: Unexpected use of '<<'. Unexpected use of '|'. Unexpected use of '&'. We tried adding an explicit include of -Dbitwise=true (and even tried false), but that did not help. Sample code that this is being reported on: this.id = newCtx << 28 | newP | newD << 8 | newI; Environment: Host OS is Ubuntu 12.04 Server. Slave is Win7 Project: Jenkins Priority: Major Reporter: Shannon Kerr This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21952) Git Plugin fails to resolve tags containing a slash since 2.0.1
Stephan Pauxberger commented on JENKINS-21952 Git Plugin fails to resolve tags containing a slash since 2.0.1 I did only revert git-plugin, git-client-plugin is current 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] [git] (JENKINS-21952) Git Plugin fails to resolve tags containing a slash since 2.0.1
Stephan Pauxberger commented on JENKINS-21952 Git Plugin fails to resolve tags containing a slash since 2.0.1 The problem lies in DefaultBuildChooser, Commit ea5cad7e27. Before this change, the implementation always fell back an unconditional call of: revisions.addAll(getHeadRevision(isPollCall, singleBranch, git, listener, data)); I think this fallback should still apply. I will provide a pull request. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-setup] (JENKINS-13140) Disconnected slaves come back online within a few minutes
Daniel Beck commented on JENKINS-13140 Disconnected slaves come back online within a few minutes mwebber: Right, sorry about that. I assumed you took a look at the option I mentioned earlier before posting a response. Just change it to Take this slave online when in demand and offline when idle (present for SSH slaves in 1.532.x) and my comment will make sense. Obviously you do not want to 'Keep this slave online as much as possible', so there's no point in selecting that value. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copy-to-slave] (JENKINS-21983) CopyToSlave exception when source contain a file starting with a .dot
Antoine Musso created JENKINS-21983 CopyToSlave exception when source contain a file starting with a .dot Issue Type: Bug Assignee: Vivekanand SV Components: copy-to-slave Created: 27/Feb/14 5:25 PM Description: I have a slave job with a file: $WORKSPACE/slave/.buildinfo I attempt to copy it to a directory on the master and got the following stacktrace: 00:00:47.432 [copy-to-slave] Copying 'html/*,/html/*', excluding nothing, from 'file:/mnt/jenkins-workspace/workspace/mw-tools-releng-tox-doc-publish/' on 'hudson.slaves.DumbSlave@6c2e5320' to 'file:/srv/org/wikimedia/doc/mw-tools-releng' on the master. 00:00:47.779 ERROR: Publisher com.michelin.cio.hudson.plugins.copytoslave.CopyToMasterNotifier aborted due to exception 00:00:47.780 hudson.util.IOException2: Failed to extract /mnt/jenkins-workspace/workspace/mw-tools-releng-tox-doc-publish/html/*,/html/* 00:00:47.780 at hudson.FilePath.readFromTar(FilePath.java:2066) 00:00:47.780 at hudson.FilePath.copyRecursiveTo(FilePath.java:1978) 00:00:47.780 at hudson.FilePath.copyRecursiveTo(FilePath.java:1889) 00:00:47.780 at com.michelin.cio.hudson.plugins.copytoslave.CopyToMasterNotifier.perform(CopyToMasterNotifier.java:95) 00:00:47.780 at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) 00:00:47.781 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) 00:00:47.781 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757) 00:00:47.781 at hudson.model.Build$BuildExecution.post2(Build.java:183) 00:00:47.781 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) 00:00:47.781 at hudson.model.Run.execute(Run.java:1690) 00:00:47.781 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 00:00:47.782 at hudson.model.ResourceController.execute(ResourceController.java:88) 00:00:47.782 at hudson.model.Executor.run(Executor.java:246) 00:00:47.782 Caused by: java.io.FileNotFoundException: /srv/org/wikimedia/doc/mw-tools-releng/html/.buildinfo (No such file or directory) 00:00:47.782 at java.io.FileOutputStream.open(Native Method) 00:00:47.782 at java.io.FileOutputStream.(FileOutputStream.java:212) 00:00:47.782 at java.io.FileOutputStream.(FileOutputStream.java:160) 00:00:47.783 at hudson.util.IOUtils.copy(IOUtils.java:35) 00:00:47.783 at hudson.FilePath.readFromTar(FilePath.java:2056) 00:00:47.783 ... 12 more 00:00:47.789 Finished: FAILURE Project: Jenkins Priority: Major Reporter: Antoine Musso This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21984) java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014
sogabe created JENKINS-21984 java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014 Issue Type: Bug Assignee: Unassigned Components: core Created: 27/Feb/14 5:27 PM Description: After installing jenkis, I am getting the following exception. It seems that the server certificate has expired. Attempting to reconnect slave 2 27, 2014 9:57:02 午後 致命的 hudson.model.DownloadService$Downloadable doPostBack Signature verification failed in downloadable 'hudson.tools.JDKInstaller' java.security.cert.CertPathValidatorException: timestamp check failed at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:139) at sun.security.provider.certpath.PKIXCertPathValidator.doValidate(PKIXCertPathValidator.java:330) at sun.security.provider.certpath.PKIXCertPathValidator.engineValidate(PKIXCertPathValidator.java:178) at java.security.cert.CertPathValidator.validate(CertPathValidator.java:250) at org.jvnet.hudson.crypto.CertificateUtil.validatePath(CertificateUtil.java:93) at jenkins.util.JSONSignatureValidator.verifySignature(JSONSignatureValidator.java:92) at hudson.model.DownloadService$Downloadable.doPostBack(DownloadService.java:258) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) 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.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) 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(Unknown Source) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Unknown Source) at org.apache.catalina.core.ApplicationFilterChain.doFilter(Unknown Source) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:90) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at com.cloudbees.jenkins.support.SupportMetricsFilter.doFilter(SupportMetricsFilter.java:105) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Unknown Source) at org.apache.catalina.core.ApplicationFilterChain.doFilter(Unknown Source) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Unknown Source) at org
[JIRA] [core] (JENKINS-21984) java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014
Jesse Glick commented on JENKINS-21984 java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014 Yes, and the corresponding functional tests are failing too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21984) java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014
Kohsuke Kawaguchi commented on JENKINS-21984 java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014 Presumably the tool installer json files are signed with wrong certificates This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21984) java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014
Kohsuke Kawaguchi assigned JENKINS-21984 to Kohsuke Kawaguchi java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014 Change By: Kohsuke Kawaguchi (27/Feb/14 5:33 PM) Assignee: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21984) java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014
Daniel Beck commented on JENKINS-21984 java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014 It'd probably be useful if the Jenkins devs were reading jenkinsci-dev occasionally. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21984) java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014
Daniel Beck edited a comment on JENKINS-21984 java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014 (my apologies, shouldn't be commenting while sick) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21952) Git Plugin fails to resolve tags containing a slash since 2.0.1
Stephan Pauxberger edited a comment on JENKINS-21952 Git Plugin fails to resolve tags containing a slash since 2.0.1 The problem lies in DefaultBuildChooser, Commit ea5cad7e27. Before this change, the implementation always fell back to an unconditional call of: revisions.addAll(getHeadRevision(isPollCall, singleBranch, git, listener, data)); I think this fallback should still apply. I will provide a pull request. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21984) java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014
Kohsuke Kawaguchi started work on JENKINS-21984 java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014 Change By: Kohsuke Kawaguchi (27/Feb/14 5:43 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21984) java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014
Kohsuke Kawaguchi commented on JENKINS-21984 java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014 https://updates.jenkins-ci.org/updates/ regenerated This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-12410) Downstream jobs not associated with upstream parent job properly
Sami Salonen commented on JENKINS-12410 Downstream jobs not associated with upstream parent job properly The problem used to be permanent in my case. The good news is that I cannot reproduce it anymore. I tried to reproduce it in two different environments without luck: Env 1: Jenkins 1.509.4 + Email Extension 2.36 + Parameterized Trigger 2.22 Env 2: Jenkins 1.532.2 + Email Extension 2.37.2 + Parameterized Trigger 2.22 I cannot comment on the original problem regarding multi-configuration projects though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21984) java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014
Kohsuke Kawaguchi commented on JENKINS-21984 java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014 Mirror triggered. Should propagate across mirrors in an hour or so. I'll come back and verify. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21952) Git Plugin fails to resolve tags containing a slash since 2.0.1
Stephan Pauxberger commented on JENKINS-21952 Git Plugin fails to resolve tags containing a slash since 2.0.1 Created Pull Request 205 (https://github.com/jenkinsci/git-plugin/pull/205). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-8952) Not Expanding Environment Variable
Nathan Nutter commented on JENKINS-8952 Not Expanding Environment Variable Thanks for the follow up and suggestion. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21984) java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014
Kohsuke Kawaguchi resolved JENKINS-21984 as Fixed java.security.cert.CertificateExpiredException: NotAfter: Thu Feb 27 04:21:29 JST 2014 Verified the fix with a fresh installation Change By: Kohsuke Kawaguchi (27/Feb/14 7:05 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19081) Download update center from master by default
Jesse Glick assigned JENKINS-19081 to Jesse Glick Download update center from master by default Change By: Jesse Glick (27/Feb/14 7:17 PM) Assignee: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19081) Download update center from master by default
Jesse Glick started work on JENKINS-19081 Download update center from master by default Change By: Jesse Glick (27/Feb/14 7:18 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-21968) A SQL Exception was caught! Schema 'DBUSER' does not exist
Grigoriy Milman commented on JENKINS-21968 A SQL Exception was caught! Schema 'DBUSER' does not exist Yes. This exception is intermittent and happened with probability near 20% By the way, thank you for your explanation related to the meaning of Configuration Name. I have setup the Configuration Name for each build job based on the build job name. By the way, some times no we see the Failed to create APISession exception in the similar way: [EnvInject] - Variables injected successfully. [EnvInject] - Injecting contributions. Building in workspace ... [EnvInject] - Unset unresolved 'USERNAME' variable. Change Log: http://.../job/NGMP.Validation.Tachy/104/changes Build Log: http:///job/NGMP.Validation.Tachy/104/console Preparing to execute si projectinfo for /.../project.pj Preparing to execute si viewproject for #/.. Checkout directory is .. A clean copy is requested; deleting contents of .. Populating clean workspace... java.lang.Exception: Failed to create APISession! Retrying after 10 seconds Change Log: http://.../job/NGMP.Validation.Tachy/104/changes Build Log: http:///job/NGMP.Validation.Tachy/104/console Preparing to execute si projectinfo for //project.pj Preparing to execute si viewproject for #/.. Checkout directory is A clean copy is requested; deleting contents of Populating clean workspace... java.lang.Exception: Failed to create APISession! Retrying after 10 seconds Change Log: http://./job/NGMP.Validation.Tachy/104/changes Build Log: http://../job/NGMP.Validation.Tachy/104/console Preparing to execute si projectinfo for /.../project.pj Preparing to execute si viewproject for #/. Checkout directory is ... A clean copy is requested; deleting contents of . Populating clean workspace... java.lang.Exception: Failed to create APISession! Retrying after 10 seconds Change Log: http://../job/NGMP.Validation.Tachy/104/changes Build Log: http://.../job/NGMP.Validation.Tachy/104/console Preparing to execute si projectinfo for /.../project.pj Preparing to execute si viewproject for #/... Checkout directory is .. A clean copy is requested; deleting contents of .. A clean copy is requested; deleting contents of . Populating clean workspace... java.lang.Exception: Failed to create APISession! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-13140) Disconnected slaves come back online within a few minutes
Daniel Beck updated JENKINS-13140 Disconnected slaves come back online within a few minutes To prevent builds, Mark this node temporarily offline. To prevent reconnect after manual disconnect, don't configure Jenkins to Keep this slave online as much as possible. Therefore this is a new feature. Reducing to minor since the original user commented this was just a misunderstanding of user options for preventing builds. Change By: Daniel Beck (27/Feb/14 8:11 PM) Issue Type: Bug New Feature Priority: Major Minor Component/s: core Component/s: slave-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] [core] (JENKINS-13140) Disconnected slaves come back online within a few minutes
Daniel Beck commented on JENKINS-13140 Disconnected slaves come back online within a few minutes As an alternative to Keep this slave online as much as possible, here's a plugin adding a retention strategy that does not reconnect slaves if they're temporarily marked offline by the user: https://github.com/daniel-beck/keep-slave-disconnected-plugin I'd consider this issue now (or with official release of this plugin at the latest) resolved. Any objections? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-19081) Download update center from master by default
Jesse Glick updated JENKINS-19081 Download update center from master by default Change By: Jesse Glick (27/Feb/14 8:16 PM) Labels: robustness updateCenter This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-setup] (JENKINS-21985) java.lang.NoClassDefFoundError: jnr/posix/POSIXHandler
Peter Eisentraut created JENKINS-21985 java.lang.NoClassDefFoundError: jnr/posix/POSIXHandler Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: slave-setup Created: 27/Feb/14 8:21 PM Description: I made a job that just does echo foo >foo.txt and is set to archive *.txt. Then I bound that job to a slave with a label. The build fails with + echo foo Archiving artifacts ERROR: Failed to archive artifacts: *.txt java.io.IOException: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: jnr/posix/POSIXHandler at hudson.FilePath.copyRecursiveTo(FilePath.java:2016) at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:57) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:140) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) at hudson.model.Run.execute(Run.java:1703) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) If I run the job on the master, it works fine. Somehow, the jnr-posix stuff isn't made available on the slave. (seems related to JENKINS-18682, which was claused because of inactivity) Project: Jenkins Labels: exception Priority: Major Reporter: Peter Eisentraut This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
