[JIRA] [parameterized-trigger] (JENKINS-21586) Triggered project is not built with the same svn revision as the project which triggered it
trejkaz commented on JENKINS-21586 Triggered project is not built with the same svn revision as the project which triggered it Rats. So my options are to either check out the whole repository and live with the time and disk space penalty, or report something to subversion-plugin to make it possible to either check out a sub-URL with the same revision, or to choose which directories get checked out for the top URL. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [junit] (JENKINS-6842) Tooltips not updated in history graph of test results
evernat commented on JENKINS-6842 Tooltips not updated in history graph of test results reproduced with Jenkins 1.549 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-6354) test history graphs can be generated without any y labels, providing minimal meaning
evernat commented on JENKINS-6354 test history graphs can be generated without any y labels, providing minimal meaning reproduced with Jenkins 1.549 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-9746) Failed to retrieve Subversion credentials
evernat resolved JENKINS-9746 as Incomplete Failed to retrieve Subversion credentials No response from the reporter, so resolving as incomplete. Change By: evernat (02/Feb/14 9:57 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-9275) execute shell: javax.servlet.ServletException: This page expects a form submission
evernat resolved JENKINS-9275 as Incomplete execute shell: javax.servlet.ServletException: This page expects a form submission No response from the reporter, so resolving as incomplete. Change By: evernat (02/Feb/14 10:01 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-9754) Poll SCM with too few values - Exception
evernat commented on JENKINS-9754 Poll SCM with too few values - Exception reproduced with Jenkins 1.549 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-9660) SVNCancelException: svn: authentication cancelled
evernat resolved JENKINS-9660 as Incomplete SVNCancelException: svn: authentication cancelled No response from the reporter, so resolving as incomplete. Change By: evernat (02/Feb/14 10:03 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-9276) Often jenkings returns 324 (net::ERR_EMPTY_RESPONSE) instead of the project page being requested, refreshing
evernat resolved JENKINS-9276 as Incomplete Often jenkings returns 324 (net::ERR_EMPTY_RESPONSE) instead of the project page being requested, refreshing No response from the reporter, so resolving as incomplete. Change By: evernat (02/Feb/14 10:05 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-9081) revision history feature consumes large amount of heap
evernat resolved JENKINS-9081 as Incomplete revision history feature consumes large amount of heap No response from the reporter, so resolving as incomplete. Change By: evernat (02/Feb/14 10:06 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-9234) Unable to change project name
evernat resolved JENKINS-9234 as Incomplete Unable to change project name No response from the reporter, so resolving as incomplete. Change By: evernat (02/Feb/14 10:05 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-8821) Remote API to createItem configuration inconsistant
evernat resolved JENKINS-8821 as Incomplete Remote API to createItem configuration inconsistant No response from the reporter, so resolving as incomplete. Change By: evernat (02/Feb/14 10:07 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16524) JENKINS VERSION 1.500 NOT WORKING CORRECTLY
evernat resolved JENKINS-16524 as Incomplete JENKINS VERSION 1.500 NOT WORKING CORRECTLY No response from the reporter, so resolving as incomplete. Change By: evernat (02/Feb/14 10:09 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21612) f:combobox is narrow
SCM/JIRA link daemon resolved JENKINS-21612 as Fixed f:combobox is narrow Change By: SCM/JIRA link daemon (02/Feb/14 10:12 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] [core] (JENKINS-21612) f:combobox is narrow
SCM/JIRA link daemon commented on JENKINS-21612 f:combobox is narrow Code changed in jenkins User: Oliver Gondža Path: core/src/main/resources/lib/form/combobox.jelly http://jenkins-ci.org/commit/jenkins/b9cccf6bdcb083f6f85d16c264c8bcff205f3c19 Log: Merge pull request #1110 from ikedam/feature/JENKINS-21612_setting-input_for_combbox FIXED JENKINS-21612 fixed wrong CSS class for f:combobox. Compare: https://github.com/jenkinsci/jenkins/compare/5cef1300b8cb...b9cccf6bdcb0 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [master-slave] (JENKINS-8510) FATAL: Could not initialize class hudson.util.jna.GNUCLibrary when archiving artifacts from Windows JNLP Slave into Linux Server
evernat resolved JENKINS-8510 as Incomplete FATAL: Could not initialize class hudson.util.jna.GNUCLibrary when archiving artifacts from Windows JNLP Slave into Linux Server No response from the reporter, so resolving as incomplete. Change By: evernat (02/Feb/14 10:10 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21612) f:combobox is narrow
SCM/JIRA link daemon commented on JENKINS-21612 f:combobox is narrow Code changed in jenkins User: ikedam Path: core/src/main/resources/lib/form/combobox.jelly http://jenkins-ci.org/commit/jenkins/cfbf4ca45ec97c05b47b69d1d59d3f5ae1f50c82 Log: FIXED JENKINS-21612 fixed wrong CSS class for f:combobox. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven2] (JENKINS-8504) New Maven version download hangs when completed
evernat resolved JENKINS-8504 as Incomplete New Maven version download hangs when completed No response from the reporter, so resolving as incomplete. Change By: evernat (02/Feb/14 10:12 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [master-slave] (JENKINS-8370) Job is getting stuck before it can even start building
evernat resolved JENKINS-8370 as Incomplete Job is getting stuck before it can even start building No response from the reporter, so resolving as incomplete. Change By: evernat (02/Feb/14 10:13 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-8277) Impossible to create a task with create right without configure.
evernat resolved JENKINS-8277 as Incomplete Impossible to create a task with create right without configure. No response from the reporter, so resolving as incomplete. Change By: evernat (02/Feb/14 10:14 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [violations] (JENKINS-8203) UTF-8 not supported as source files
evernat resolved JENKINS-8203 as Incomplete UTF-8 not supported as source files No response from the reporter, so resolving as incomplete. Change By: evernat (02/Feb/14 10:15 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven2] (JENKINS-7857) ERROR: Maven JVM terminated unexpectedly with exit code 0
evernat resolved JENKINS-7857 as Incomplete ERROR: Maven JVM terminated unexpectedly with exit code 0 No response from the reporter, so resolving as incomplete. Change By: evernat (02/Feb/14 10:19 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [www] (JENKINS-7420) Can't read exception stack trace when test fails
evernat resolved JENKINS-7420 as Incomplete Cant read exception stack trace when test fails No response from the reporter, so resolving as incomplete. Change By: evernat (02/Feb/14 10:21 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-7655) Another case of frozen build
evernat resolved JENKINS-7655 as Incomplete Another case of frozen build No response from the reporter, so resolving as incomplete. Change By: evernat (02/Feb/14 10:20 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-7329) 1.368: builds get slower as the day goes on.
evernat resolved JENKINS-7329 as Incomplete 1.368: builds get slower as the day goes on. No response from the reporter, so resolving as incomplete. Change By: evernat (02/Feb/14 10:21 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven2] (JENKINS-7158) Advanced maven opts Incremental build and Build modules in parallel not working as expected
evernat resolved JENKINS-7158 as Incomplete Advanced maven opts Incremental build and Build modules in parallel not working as expected No response from the reporter, so resolving as incomplete. Change By: evernat (02/Feb/14 10:23 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven2] (JENKINS-6829) Build fails
evernat resolved JENKINS-6829 as Incomplete Build fails No response from the reporter, so resolving as incomplete. Change By: evernat (02/Feb/14 10:23 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-timeout] (JENKINS-13349) Time out clock refresh after output
ikedam commented on JENKINS-13349 Time out clock refresh after output https://github.com/jenkinsci/build-timeout-plugin/pull/17 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-21013) Matrix project support for Parameters from properties file
SCM/JIRA link daemon commented on JENKINS-21013 Matrix project support for Parameters from properties file Code changed in jenkins User: ikedam Path: src/main/resources/hudson/plugins/parameterizedtrigger/FileBuildParameters/config.jelly src/main/resources/hudson/plugins/parameterizedtrigger/FileBuildParameters/help-combinationFilter.html src/main/resources/hudson/plugins/parameterizedtrigger/FileBuildParameters/help-onlyExactRuns.html src/main/resources/hudson/plugins/parameterizedtrigger/FileBuildParameters/help-useMatrixChild.html http://jenkins-ci.org/commit/parameterized-trigger-plugin/645485f8ddff890bfff6f99e66ba97f814f38725 Log: JENKINS-21013 Add helps for FileBuildParameters with MatrixProjects. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21013) Matrix project support for Parameters from properties file
SCM/JIRA link daemon commented on JENKINS-21013 Matrix project support for Parameters from properties file Code changed in jenkins User: ikedam Path: src/main/java/hudson/plugins/parameterizedtrigger/FileBuildParameters.java src/main/resources/hudson/plugins/parameterizedtrigger/BlockableBuildTriggerConfig/config.jelly src/main/resources/hudson/plugins/parameterizedtrigger/BuildTrigger/config.jelly src/main/resources/hudson/plugins/parameterizedtrigger/BuildTriggerConfig/config.jelly src/main/resources/hudson/plugins/parameterizedtrigger/FileBuildParameters/config.jelly src/main/resources/hudson/plugins/parameterizedtrigger/FileBuildParameters/help-combinationFilter.html src/main/resources/hudson/plugins/parameterizedtrigger/FileBuildParameters/help-onlyExactRuns.html src/main/resources/hudson/plugins/parameterizedtrigger/FileBuildParameters/help-useMatrixChild.html src/main/resources/hudson/plugins/parameterizedtrigger/TriggerBuilder/config.jelly src/test/java/hudson/plugins/parameterizedtrigger/test/FileBuildTriggerConfigTest.java http://jenkins-ci.org/commit/parameterized-trigger-plugin/1b68ab5925792f75a44b8bba20414dace49cab12 Log: Merge pull request #60 from ikedam/feature/JENKINS-21013_file-from-matrix-build JENKINS-21013 Matrix project support for "Parameters from properties file". Compare: https://github.com/jenkinsci/parameterized-trigger-plugin/compare/fea0e125f597...1b68ab592579 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21013) Matrix project support for Parameters from properties file
SCM/JIRA link daemon resolved JENKINS-21013 as Fixed Matrix project support for Parameters from properties file Change By: SCM/JIRA link daemon (02/Feb/14 12:32 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] [parameterized-trigger] (JENKINS-21013) Matrix project support for Parameters from properties file
SCM/JIRA link daemon commented on JENKINS-21013 Matrix project support for Parameters from properties file Code changed in jenkins User: ikedam Path: src/main/resources/hudson/plugins/parameterizedtrigger/BlockableBuildTriggerConfig/config.jelly src/main/resources/hudson/plugins/parameterizedtrigger/BuildTrigger/config.jelly src/main/resources/hudson/plugins/parameterizedtrigger/BuildTriggerConfig/config.jelly src/main/resources/hudson/plugins/parameterizedtrigger/FileBuildParameters/config.jelly src/main/resources/hudson/plugins/parameterizedtrigger/TriggerBuilder/config.jelly http://jenkins-ci.org/commit/parameterized-trigger-plugin/fe091d9a821cd178f29f1079aafa250f29d3278a Log: JENKINS-21013 Don't show options for MatrixProject when used as a builder. This works perfect only with Jenkins = 1.495. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21013) Matrix project support for Parameters from properties file
SCM/JIRA link daemon commented on JENKINS-21013 Matrix project support for Parameters from properties file Code changed in jenkins User: ikedam Path: src/main/java/hudson/plugins/parameterizedtrigger/FileBuildParameters.java src/main/resources/hudson/plugins/parameterizedtrigger/FileBuildParameters/config.jelly http://jenkins-ci.org/commit/parameterized-trigger-plugin/737b06a372a40824084fbf753d4a29336af57afc Log: FIXED JENKINS-21013 Matrix project support for "Parameters from properties 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] [parameterized-trigger] (JENKINS-21013) Matrix project support for Parameters from properties file
SCM/JIRA link daemon commented on JENKINS-21013 Matrix project support for Parameters from properties file Code changed in jenkins User: ikedam Path: src/test/java/hudson/plugins/parameterizedtrigger/test/FileBuildTriggerConfigTest.java http://jenkins-ci.org/commit/parameterized-trigger-plugin/bf0d4e23cbb5d34466c04d5175228987f44becff Log: JENKINS-21013 Added tests for FileBuildParameters with MatrixProject. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-19693) Build Number field expect positive number, so it is impossible to use named builds here
SCM/JIRA link daemon commented on JENKINS-19693 Build Number field expect positive number, so it is impossible to use named builds here Code changed in jenkins User: Alexis Morelle Path: src/main/java/hudson/plugins/copyartifact/SpecificBuildSelector.java src/main/resources/hudson/plugins/copyartifact/SpecificBuildSelector/config.jelly src/main/webapp/help-specificBuild.html src/test/java/hudson/plugins/copyartifact/SpecificBuildSelectorTest.java http://jenkins-ci.org/commit/copyartifact-plugin/f0a01c82472879e9bd9b72022b6bd16363b603b6 Log: FIXED JENKINS-19693 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-19693) Build Number field expect positive number, so it is impossible to use named builds here
SCM/JIRA link daemon resolved JENKINS-19693 as Fixed Build Number field expect positive number, so it is impossible to use named builds here Change By: SCM/JIRA link daemon (02/Feb/14 12:50 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] [rubyMetrics] (JENKINS-21614) rcov Reports Waste Memory and Hurt Performance
recampbell updated JENKINS-21614 rcov Reports Waste Memory and Hurt Performance Change By: recampbell (02/Feb/14 2:18 PM) Labels: memory This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [rubyMetrics] (JENKINS-21614) rcov Reports Waste Memory and Hurt Performance
recampbell created JENKINS-21614 rcov Reports Waste Memory and Hurt Performance Issue Type: Bug Assignee: david_calavera Components: rubyMetrics Created: 02/Feb/14 2:17 PM Description: The rubyMetrics plugin's rcov embeds the entire source code of the project into the build.xml (hudson.plugins.rubyMetrics.rcov.RcovBuildAction.results.files) https://github.com/jenkinsci/rubymetrics-plugin/blob/master/src/main/java/hudson/plugins/rubyMetrics/rcov/model/RcovResult.java#L9 This results 1 in a 37 mb build.xml and a 576mb DOM 2. 1 For a project with 179034 LOC over 1500 files. 2 As measured from a heap dump Project: Jenkins Priority: Major Reporter: recampbell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-21615) MultiJob 1.11 phases broken when upgraded from 1.9
Ireneusz Makowski created JENKINS-21615 MultiJob 1.11 phases broken when upgraded from 1.9 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jenkins-multijob-plugin Created: 02/Feb/14 3:20 PM Description: When there were 2 phases in multijob with only one job executed per phase then all the jobs are executed at once, and phases are ignored! The second braking change is failure of entire phase and multijob when one of the jobs fails during build! Upgrade should change this value to Never not Failure, because it changes flows after upgrade to 1.11. Environment: Windows 2008 R2 64 bit, Jenkins 1.532.1 LTS Fix Versions: current Project: Jenkins Labels: plugin jenkins lts lts-candidate Priority: Blocker Reporter: Ireneusz Makowski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17655) Multijob plugin does not support Folder plugin
Ireneusz Makowski commented on JENKINS-17655 Multijob plugin does not support Folder plugin What about this pull request? Could you also look at braking change in 1.11? https://issues.jenkins-ci.org/browse/JENKINS-21615 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21615) MultiJob 1.11 phases broken when upgraded from 1.9
hagzag commented on JENKINS-21615 MultiJob 1.11 phases broken when upgraded from 1.9 Checking the issue - AFAIK it shouldn't, I will update ASAP This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21129) Unable to test multiple connections without restarting Jenkins server
Greg Peters commented on JENKINS-21129 Unable to test multiple connections without restarting Jenkins server Are you using the latest plugin version? you should be using v1.2 and not v1.1. Please provide the steps needed to reproduce this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-21615) MultiJob 1.11 phases broken when upgraded from 1.9
Ireneusz Makowski commented on JENKINS-21615 MultiJob 1.11 phases broken when upgraded from 1.9 Great. Waiting for info. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21616) multiconfiguration job when added to a multijob phase doesn't show as executing in multijob graphical view
steven armstrong created JENKINS-21616 multiconfiguration job when added to a multijob phase doesnt show as executing in multijob graphical view Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jenkins-multijob-plugin Created: 02/Feb/14 4:31 PM Description: When adding a multi-configuration job to a multijob phase, the multi-configuration job shows correctly in the multijob graphical view. However, upon building the multijob it will functionally execute multi-configuration job as desired which is confirmed if you look at the main multijobs main console output, but it doesn't generate a console log or appear in the multijobs main graphical view so it looks like it has actually failed to initiate the phase containing the multi-configuration job. Could this be fixed to show the multi-configration job as executing and generate a console log and timings like free-style jobs do in the multijob graphical view? Environment: Windows 2008 R2 Project: Jenkins Priority: Major Reporter: steven armstrong This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21615) MultiJob 1.11 phases broken when upgraded from 1.9
Alex Nickolaevsky commented on JENKINS-21615 MultiJob 1.11 phases broken when upgraded from 1.9 Hi, First issue: please provide more info regarding the configuration of multijob project and sub jobs projects. Second: Stop phase execution on failure was the default behaviour in previous versions. Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cli] (JENKINS-20128) HTTP two-way remoting does not work (jenkins-cli.jar without JNLP)
Nadav Samet commented on JENKINS-20128 HTTP two-way remoting does not work (jenkins-cli.jar without JNLP) This still happens on 1.549. Can you re-open? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cli] (JENKINS-20128) HTTP two-way remoting does not work (jenkins-cli.jar without JNLP)
Nadav Samet edited a comment on JENKINS-20128 HTTP two-way remoting does not work (jenkins-cli.jar without JNLP) I am still seeing "Protocol violation: Unexpected single newline character in chunk size' 0x0a" on Jenkins 1.549. Can you re-open? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21617) List Subversion Tags job parameter wants svn credentials but there is no way to fill it
Marat Mavlyutov created JENKINS-21617 List Subversion Tags job parameter wants svn credentials but there is no way to fill it Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2014-02-02 at 22.07.46.png Components: subversion Created: 02/Feb/14 6:08 PM Description: steps to reproduce: 1. add "List Subversion Tags" parameter at dummy job 2. input any valid svn+ssh url to "Repository URL" field there is a red message: Unable to access svn+ssh://my_svn_url.com : svn: E200015: No credential to try. Authentication failed (show details) but there is no any dropdowns to fill credentials Environment: jenkins 1.549 subversion plugin 2.0 Project: Jenkins Priority: Critical Reporter: Marat Mavlyutov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [security] (JENKINS-9008) SIGSEGV (JVM crash) in Jenkins native method hudson.security.PAMSecurityRealm$PAMAuthenticationProvider.authenticate
Jamshid Afshar commented on JENKINS-9008 SIGSEGV (JVM crash) in Jenkins native method hudson.security.PAMSecurityRealm$PAMAuthenticationProvider.authenticate I think the root bug is in a standard RedHat/CentOS 6 PAM module related to finger print scanners. Fix with "yum remove fprintd-pam". For repro see: https://github.com/kohsuke/libpam4j/issues/8. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git clone command
Mark Waite commented on JENKINS-20387 Timeout (10min) on git clone command Pull request has been submitted to git-client-plugin https://github.com/jenkinsci/git-client-plugin/pull/92 and to git-plugin https://github.com/jenkinsci/git-plugin/pull/197 proposing to include timeout setting in the Git plugin user interface. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20445) Git plugin timeout is too small
Mark Waite commented on JENKINS-20445 Git plugin timeout is too small Pull request has been submitted to git-client-plugin https://github.com/jenkinsci/git-client-plugin/pull/92 and to git-plugin https://github.com/jenkinsci/git-plugin/pull/197 proposing to include timeout setting in the Git plugin user interface. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17742) Pick Up Committer from Upstream Job
Alex Earl commented on JENKINS-17742 Pick Up Committer from Upstream Job The discussion on the pull request has led me to implement a RecipientProvider extension point. This will allow people to implement their own plugins that add functionality. It will be much easier for people to create pull requests with new ways of providing recipients. I hope to get it into the next release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [bazaar] (JENKINS-18955) Add multiple scm support to Bazaar plugin
Julien Boumard commented on JENKINS-18955 Add multiple scm support to Bazaar plugin Hi Sebastian, On my side I haven't had any news, so for now you can use the fork I made and it should 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] [core] (JENKINS-21618) wrong Load statistics: busy executors in minus
hiteswar kumar created JENKINS-21618 wrong Load statistics: busy executors in minus Issue Type: Bug Assignee: Unassigned Attachments: wrong load statistics.png Components: core Created: 03/Feb/14 2:28 AM Description: At Load statistics, it showing busy executors in minus(negative). which seems wrong. it should be in plus . please share fix for this. Environment: Jenkins ver. 1.480.3 Project: Jenkins Priority: Major Reporter: hiteswar 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] [xunit] (JENKINS-20024) com.thoughtworks.xstream.converters.ConversionException: QTestLibType on Jenkins 1.524 and later
Steve Mokris commented on JENKINS-20024 com.thoughtworks.xstream.converters.ConversionException: QTestLibType on Jenkins 1.524 and later Yes, I just updated to version 1.81, and it's working nicely. Thanks, Gregory! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21540) NPE while renaming job
Daniel Beck resolved JENKINS-21540 as Duplicate NPE while renaming job Known issue of an older version of copyartifact plugin. Also, 1.480.x is obsolete, upgrade to 1.532.x to have anyone care about this. Change By: Daniel Beck (03/Feb/14 6:46 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21618) wrong Load statistics: busy executors in minus
Daniel Beck updated JENKINS-21618 wrong Load statistics: busy executors in minus Change By: Daniel Beck (03/Feb/14 6:50 AM) Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-reviewbot] (JENKINS-20396) Applying patch always fail when using perforce
David Resnick commented on JENKINS-20396 Applying patch always fail when using perforce @sylvainbenner Using your workaround I was able to get a single trivial Perforce patch to work. But non-trivial ones fail, though I don't see a reason for them to. Are you able to use the plugin against Perforce? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
rogerhu commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) The problem is upon configuring a job using an HTTP-based URL with Git credentials, the plug-in attempts to do form validation and verify whether the HTTP authentication succeeded. Because of the recent updates to store this info as a temporary store so that subsequent Git commands will succeed with these credentials, the validation can fail in the absence of a workspace directory. In other words, the warning message "Failed to connect to repository : Command "git config --local credential.helper store" appears and can be ignored, but it's a false alarm. The job will fetch correctly if ran. For instance, if Jenkins was started from the / dir, then git will attempt to access .git/config from the root directory, resulting in permissions denied. Should the creation of the local credential simply just not be done in the absence of a workspace directory? See: https://github.com/jenkinsci/git-client-plugin/pull/97 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-21587) memory leak in Plugin 1.22 -orphaned Logger Threads
Matthias Rump commented on JENKINS-21587 memory leak in Plugin 1.22 -orphaned Logger Threads Hi Cletus, Yes, the threads are are in the integrity client's VM, NOT in Jenkins, so you're right, the plugin itself does not have the problem. But nevertheless the plugin seems to be the course of this issue, as we did not see this number of daemon threads on the same client, same API, with plugin version 1.18. So what's you proposal? connecting the plugin directly to the Server and keeping my fingers crossed it won't kill my production system? schedule a restart of my integration server client every hour? stepping back to plugin version 1.18 (with all other known issues)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-21587) memory leak in Plugin 1.22 -orphaned Logger Threads
Matthias Rump reopened JENKINS-21587 memory leak in Plugin 1.22 -orphaned Logger Threads see last comment Change By: Matthias Rump (03/Feb/14 7:38 AM) Resolution: WontFix 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] [ant] (JENKINS-16549) When using ant build step, artifact links in build properties are broken
Denis Syrokvash commented on JENKINS-16549 When using ant build step, artifact links in build properties are broken looks, like i can't reproduce it any more (using jenkinks v1.549, ant plugin v1.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] [ant] (JENKINS-16549) When using ant build step, artifact links in build properties are broken
evernat resolved JENKINS-16549 as Cannot Reproduce When using ant build step, artifact links in build properties are broken ok, thanks Change By: evernat (03/Feb/14 7:54 AM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
