[JIRA] [core] (JENKINS-10401) jenkins using 100% CPU if trying to archive unexisting artifact
aeschbacher commented on JENKINS-10401 jenkins using 100% CPU if trying to archive unexisting artifact Lloyd, First, thank you for your comments. Back in 2011, as I reported the issue, I was working with a poor HW, and with huge (45GB) workspaces. This is not the case anymore (migrated on better HW, workspaces are smaller) , so I did not reproduce the same problem since that time, even though I keep using Jenkins a intensively for many projects. I confirm that the issue can be closed. Best regards, Fabrice This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
SCM/JIRA link daemon commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/CauseAction.java http://jenkins-ci.org/commit/jenkins/aa677ed8486559433ff71a50cf4f5bbf8fc46cd8 Log: JENKINS-20499 Don't fail horribly with null causes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
SCM/JIRA link daemon commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/model/CauseAction.java http://jenkins-ci.org/commit/jenkins/0c76f85f8dd563963072323c68f25236d901a9ca Log: Merge pull request #1248 from daniel-beck/JENKINS-20499 JENKINS-20499 Don't fail horribly with null causes Compare: https://github.com/jenkinsci/jenkins/compare/b3bb235d5740...0c76f85f8dd5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Oleg Nenashev updated JENKINS-20499 unable to retry job execution for failed job in build-pipeline marked as lts-candidate Change By: Oleg Nenashev (01/Jun/14 8:05 AM) Labels: lts-candidate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-15788) #threads and http sessions increasing
evernat commented on JENKINS-15788 #threads and http sessions increasing If it's really related, "org.kohsuke.stapler.compression.CompressionFilter reportException" was a well known problem at the time. It was worked around in a later Jenkins version. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20031) NPE on plugin install
SCM/JIRA link daemon resolved JENKINS-20031 as Fixed NPE on plugin install Change By: SCM/JIRA link daemon (01/Jun/14 8:28 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20031) NPE on plugin install
SCM/JIRA link daemon commented on JENKINS-20031 NPE on plugin install Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/PluginManager.java http://jenkins-ci.org/commit/jenkins/a4b63d2dc0ced54196f0ac69fe040246b7579090 Log: FIXED JENKINS-20031 Useful error message when UC not found This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20031) NPE on plugin install
SCM/JIRA link daemon commented on JENKINS-20031 NPE on plugin install Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/PluginManager.java http://jenkins-ci.org/commit/jenkins/19f4cbcce14ddb0d2d1a06b40af69b8aab2b4ede Log: Merge pull request #1242 from daniel-beck/JENKINS-20031 FIXED JENKINS-20031 Useful error message when UC not found Compare: https://github.com/jenkinsci/jenkins/compare/7ee4da9acc0c...19f4cbcce14d This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
dogfood commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Integrated in jenkins_main_trunk #3417 JENKINS-20499 Don't fail horribly with null causes (Revision aa677ed8486559433ff71a50cf4f5bbf8fc46cd8) Result = SUCCESS daniel-beck : aa677ed8486559433ff71a50cf4f5bbf8fc46cd8 Files : core/src/main/java/hudson/model/CauseAction.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20031) NPE on plugin install
SCM/JIRA link daemon commented on JENKINS-20031 NPE on plugin install Code changed in jenkins User: Oleg Nenashev Path: changelog.html http://jenkins-ci.org/commit/jenkins/c5158d228b9f123fe0f4dd1cd671af7e6f0fde35 Log: Noting #1242 (JENKINS-20031) Signed-off-by: Oleg Nenashev o.v.nenas...@gmail.com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-8358) A disabled project is always DISABLED even is the project is building
SCM/JIRA link daemon commented on JENKINS-8358 A disabled project is always DISABLED even is the project is building Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/model/AbstractProject.java http://jenkins-ci.org/commit/jenkins/d5fc738e636f74856b95ddb26417a0c2ae020dfa Log: Merge pull request #1249 from daniel-beck/JENKINS-8358 FIX JENKINS-8358 Use DISABLED_ANIME icon while building Compare: https://github.com/jenkinsci/jenkins/compare/c5158d228b9f...d5fc738e636f This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-8358) A disabled project is always DISABLED even is the project is building
SCM/JIRA link daemon commented on JENKINS-8358 A disabled project is always DISABLED even is the project is building Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/AbstractProject.java http://jenkins-ci.org/commit/jenkins/916340750e5b1588248a92e7d6730c62e5978552 Log: FIX JENKINS-8358 Use DISABLED_ANIME icon while building This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-23256) Job hangs trying to resolve Perforce emails, in a non-perforce job
davyboyhayes commented on JENKINS-23256 Job hangs trying to resolve Perforce emails, in a non-perforce job I will take snapshots of the build machine and master and test these out on Monday, rolling back to the previous build and attempt to roll individual plugins forward to eek out what caused the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22934) Rules for showing/hiding SCMTrigger.pollingThreadCount option are broken
SCM/JIRA link daemon commented on JENKINS-22934 Rules for showing/hiding SCMTrigger.pollingThreadCount option are broken Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/triggers/SCMTrigger.java core/src/main/resources/hudson/triggers/SCMTrigger/global.jelly http://jenkins-ci.org/commit/jenkins/91ef9113262359ab45ed710d6ecad0f73df7b434 Log: Merge pull request #1230 from daniel-beck/JENKINS-22934 FIXED JENKINS-22934 Show poll thread count option when necessary. Compare: https://github.com/jenkinsci/jenkins/compare/1b81efbdf342...91ef91132623 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22934) Rules for showing/hiding SCMTrigger.pollingThreadCount option are broken
SCM/JIRA link daemon commented on JENKINS-22934 Rules for showing/hiding SCMTrigger.pollingThreadCount option are broken Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/triggers/SCMTrigger.java core/src/main/resources/hudson/triggers/SCMTrigger/global.jelly http://jenkins-ci.org/commit/jenkins/e4902e7e8ab7a21e84ea21a36395b0e2a5077019 Log: FIXED JENKINS-22934 Show poll thread count option when necessary. Show the option when the configured value is not the default Show the option even when projects are in other ItemGroups Only consider AbstractProjects This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22934) Rules for showing/hiding SCMTrigger.pollingThreadCount option are broken
SCM/JIRA link daemon resolved JENKINS-22934 as Fixed Rules for showing/hiding SCMTrigger.pollingThreadCount option are broken Change By: SCM/JIRA link daemon (01/Jun/14 8:56 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22693) Resource leak in hudson.model.FileParameterValue
SCM/JIRA link daemon resolved JENKINS-22693 as Fixed Resource leak in hudson.model.FileParameterValue Change By: SCM/JIRA link daemon (01/Jun/14 9:12 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22693) Resource leak in hudson.model.FileParameterValue
SCM/JIRA link daemon commented on JENKINS-22693 Resource leak in hudson.model.FileParameterValue Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/model/FileParameterValue.java http://jenkins-ci.org/commit/jenkins/8767ddb192cf752c7d28f512884b9ecd3b9cdbd4 Log: FIXED JENKINS-22693 - Properly close InputStreams in FileParameterValue Signed-off-by: Oleg Nenashev o.v.nenas...@gmail.com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22693) Resource leak in hudson.model.FileParameterValue
SCM/JIRA link daemon commented on JENKINS-22693 Resource leak in hudson.model.FileParameterValue Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/model/FileParameterValue.java http://jenkins-ci.org/commit/jenkins/d2fb6d918c97b7b568eeff5b43e7095cbcb5d107 Log: Merge pull request #1225 from synopsys-arc-oss/jenkins22693-inputstream-fix FIXED JENKINS-22693 - Properly close InputStreams in FileParameterValue Compare: https://github.com/jenkinsci/jenkins/compare/e7ca7ae9ec4a...d2fb6d918c97 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20031) NPE on plugin install
dogfood commented on JENKINS-20031 NPE on plugin install Integrated in jenkins_main_trunk #3418 FIXED JENKINS-20031 Useful error message when UC not found (Revision a4b63d2dc0ced54196f0ac69fe040246b7579090) Result = SUCCESS daniel-beck : a4b63d2dc0ced54196f0ac69fe040246b7579090 Files : core/src/main/java/hudson/PluginManager.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23263) Move hudson.tasks.junit to a bundled plugin
Oleg Nenashev updated JENKINS-23263 Move hudson.tasks.junit to a bundled plugin Change By: Oleg Nenashev (01/Jun/14 9:27 AM) Summary: Movehudson.tasks.junittoa bundled plugin Issue Type: Bug NewFeature Component/s: 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/d/optout.
[JIRA] [core] (JENKINS-23263) Move hudson.tasks.junit to a plugin
Oleg Nenashev created JENKINS-23263 Move hudson.tasks.junit to a plugin Issue Type: Bug Assignee: Oleg Nenashev Components: core, junit, xunit Created: 01/Jun/14 9:27 AM Description: There're plenty of bugs and feature requests for the JUnit Archiver (and related stuff). This functionality stills inside the Jenkins Core. In addition, the xUnit Plugin mostly replaces the publisher functionality, but it depends from hudson.tasks.junit internals. Proposals: Move JUnit to a separate plugin Mark the JUnit Publisher as "deprecated" in the documentation Move test suites to test-harness and test-acceptance projects Project: Jenkins Priority: Major Reporter: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18626) Incorrect age in the test results
SCM/JIRA link daemon resolved JENKINS-18626 as Fixed Incorrect age in the test results Change By: SCM/JIRA link daemon (01/Jun/14 9:34 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/d/optout.
[JIRA] [core] (JENKINS-18626) Incorrect age in the test results
SCM/JIRA link daemon commented on JENKINS-18626 Incorrect age in the test results Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/tasks/junit/CaseResult.java http://jenkins-ci.org/commit/jenkins/4af464a624ee88d479a77f401be9d4f10ffaa791 Log: Merge pull request #576 from JoelJ/patch-2 FIXED JENKINS-18626 - Test result page keeps identifying tests as age 1 Compare: https://github.com/jenkinsci/jenkins/compare/bab3176f82b5...4af464a624ee This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22934) Rules for showing/hiding SCMTrigger.pollingThreadCount option are broken
dogfood commented on JENKINS-22934 Rules for showing/hiding SCMTrigger.pollingThreadCount option are broken Integrated in jenkins_main_trunk #3419 FIXED JENKINS-22934 Show poll thread count option when necessary. (Revision e4902e7e8ab7a21e84ea21a36395b0e2a5077019) Result = SUCCESS daniel-beck : e4902e7e8ab7a21e84ea21a36395b0e2a5077019 Files : core/src/main/java/hudson/triggers/SCMTrigger.java core/src/main/resources/hudson/triggers/SCMTrigger/global.jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22693) Resource leak in hudson.model.FileParameterValue
dogfood commented on JENKINS-22693 Resource leak in hudson.model.FileParameterValue Integrated in jenkins_main_trunk #3419 FIXED JENKINS-22693 - Properly close InputStreams in FileParameterValue (Revision 8767ddb192cf752c7d28f512884b9ecd3b9cdbd4) Result = SUCCESS o.v.nenashev : 8767ddb192cf752c7d28f512884b9ecd3b9cdbd4 Files : core/src/main/java/hudson/model/FileParameterValue.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-8358) A disabled project is always DISABLED even is the project is building
dogfood commented on JENKINS-8358 A disabled project is always DISABLED even is the project is building Integrated in jenkins_main_trunk #3419 FIX JENKINS-8358 Use DISABLED_ANIME icon while building (Revision 916340750e5b1588248a92e7d6730c62e5978552) Result = SUCCESS daniel-beck : 916340750e5b1588248a92e7d6730c62e5978552 Files : core/src/main/java/hudson/model/AbstractProject.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22617) Can't delete crash report
SCM/JIRA link daemon commented on JENKINS-22617 Cant delete crash report Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/jenkins/diagnosis/HsErrPidList/index.jelly http://jenkins-ci.org/commit/jenkins/b517eb7925a0ac50bf499d30732b986efbf6d276 Log: FIX JENKINS-22617 Fix path to deletion of VM error log This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22617) Can't delete crash report
SCM/JIRA link daemon commented on JENKINS-22617 Cant delete crash report Code changed in jenkins User: Oleg Nenashev Path: core/src/main/resources/jenkins/diagnosis/HsErrPidList/index.jelly http://jenkins-ci.org/commit/jenkins/ee3ea5dc47ffa980ef73930c7f9658c532fad9ee Log: Merge pull request #1247 from daniel-beck/JENKINS-22617 FIX JENKINS-22617 Fix path to deletion of JVM Crash error log Compare: https://github.com/jenkinsci/jenkins/compare/23e0e919bebd...ee3ea5dc47ff This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19250) Want to know which user started a build that is sitting in the queue
SCM/JIRA link daemon commented on JENKINS-19250 Want to know which user started a build that is sitting in the queue Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/Queue.java core/src/main/resources/lib/hudson/queue.jelly http://jenkins-ci.org/commit/jenkins/19e40a9338a70dbf51f6236be7fcf2fc9b7fb511 Log: FIX JENKINS-19250 Add causes to queue item tool tip This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19250) Want to know which user started a build that is sitting in the queue
SCM/JIRA link daemon commented on JENKINS-19250 Want to know which user started a build that is sitting in the queue Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/Queue.java core/src/main/resources/lib/hudson/queue.jelly http://jenkins-ci.org/commit/jenkins/b1520376340096fe47b19f5b906e275e42fb0a61 Log: Merge pull request #1245 from daniel-beck/JENKINS-19250 FIX JENKINS-19250 Add causes to queue item tool tip Compare: https://github.com/jenkinsci/jenkins/compare/73c00442d24e...b15203763400 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-17114) Reason for job starvation icon is wrong
SCM/JIRA link daemon commented on JENKINS-17114 Reason for job starvation icon is wrong Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/queue/CauseOfBlockage.java core/src/main/resources/hudson/model/Messages.properties core/src/main/resources/hudson/model/queue/CauseOfBlockage/BecauseLabelIsOffline/summary.jelly core/src/main/resources/hudson/model/queue/CauseOfBlockage/BecauseLabelIsOffline/summary.properties http://jenkins-ci.org/commit/jenkins/5aa32c8681410eccfabf68397692f2402e615a48 Log: FIX JENKINS-17114 Distinguish 'nodes offline' from 'no nodes' Jenkins currently does not distinguish between 'All nodes for a label are offline' and 'There are no nodes for a label'. This is exacerbated by the current wording: All nodes of label 'foo' are offline Instead of just changing the wording to something not seeming to imply existence of such nodes, add a second wording that clearly states that there are no such nodes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-17114) Reason for job starvation icon is wrong
SCM/JIRA link daemon commented on JENKINS-17114 Reason for job starvation icon is wrong Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/queue/CauseOfBlockage.java core/src/main/resources/hudson/model/Messages.properties core/src/main/resources/hudson/model/queue/CauseOfBlockage/BecauseLabelIsOffline/summary.jelly core/src/main/resources/hudson/model/queue/CauseOfBlockage/BecauseLabelIsOffline/summary.properties http://jenkins-ci.org/commit/jenkins/a63606d0b735e80ac6a29504d1173f35e42004bc Log: Merge pull request #1252 from daniel-beck/JENKINS-17114 FIX JENKINS-17114 Distinguish 'nodes offline' from 'no nodes' Compare: https://github.com/jenkinsci/jenkins/compare/b15203763400...a63606d0b735 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22690) RPM install jenkins.repo file
SCM/JIRA link daemon commented on JENKINS-22690 RPM install jenkins.repo file Code changed in jenkins User: Matthew Barr Path: rpm/SPECS/jenkins.spec http://jenkins-ci.org/commit/jenkins/a08b16d281d9f7a34f3cffaefdc21a941d71aebf Log: Remove repo file from RPM. https://issues.jenkins-ci.org/browse/JENKINS-22690 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22690) RPM install jenkins.repo file
SCM/JIRA link daemon resolved JENKINS-22690 as Fixed RPM install jenkins.repo file Change By: SCM/JIRA link daemon (01/Jun/14 11:55 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/d/optout.
[JIRA] [core] (JENKINS-22690) RPM install jenkins.repo file
SCM/JIRA link daemon commented on JENKINS-22690 RPM install jenkins.repo file Code changed in jenkins User: Oleg Nenashev Path: rpm/SPECS/jenkins.spec http://jenkins-ci.org/commit/jenkins/a3d07dcb19abd04ed7acf3541c0ac749e0a02902 Log: Merge pull request #1202 from matthewbarr/JENKINS-22690 FIXED JENKINS-22690 Remove repo file from RPM Compare: https://github.com/jenkinsci/jenkins/compare/0f6258b6cbdf...a3d07dcb19ab This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-11673) Support https in RPM service scripts
SCM/JIRA link daemon commented on JENKINS-11673 Support https in RPM service scripts Code changed in jenkins User: Oleg Nenashev Path: rpm/SOURCES/jenkins.init.in rpm/SOURCES/jenkins.sysconfig.in http://jenkins-ci.org/commit/jenkins/3e191ba236d768c53dee92afb1651971c4b9 Log: Merge pull request #1227 from n8felton/JENKINS-11673 FIXES JENKINS-11673 - Support https in RPM service scripts Compare: https://github.com/jenkinsci/jenkins/compare/a3d07dcb19ab...3e191ba236d7 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-11673) Support https in RPM service scripts
SCM/JIRA link daemon commented on JENKINS-11673 Support https in RPM service scripts Code changed in jenkins User: n8felton Path: rpm/SOURCES/jenkins.init.in rpm/SOURCES/jenkins.sysconfig.in http://jenkins-ci.org/commit/jenkins/00b6d99be6b5a23fbef3b53e34368c4e5c30de9d Log: FIXES JENKINS-11673 - Support https in RPM service scripts Adding support for --httpsKeyStore and --httpsKeyStorePassword agruments. Follows guide at https://wiki.jenkins-ci.org/display/JENKINS/Starting+and+Accessing+Jenkins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-11673) Support https in RPM service scripts
Oleg Nenashev resolved JENKINS-11673 as Fixed Support https in RPM service scripts Change By: Oleg Nenashev (01/Jun/14 11:59 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22617) Can't delete crash report
dogfood commented on JENKINS-22617 Cant delete crash report Integrated in jenkins_main_trunk #3421 FIX JENKINS-22617 Fix path to deletion of VM error log (Revision b517eb7925a0ac50bf499d30732b986efbf6d276) Result = SUCCESS daniel-beck : b517eb7925a0ac50bf499d30732b986efbf6d276 Files : core/src/main/resources/jenkins/diagnosis/HsErrPidList/index.jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-alias-setter] (JENKINS-23264) Alias configuration is shared by all jobs
Oliver Gondža created JENKINS-23264 Alias configuration is shared by all jobs Issue Type: Bug Assignee: Oliver Gondža Components: build-alias-setter Created: 01/Jun/14 12:19 PM Description: Alias configuration is shared by all jobs. Project: Jenkins Priority: Critical Reporter: Oliver Gondža This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-11673) Support https in RPM service scripts
dogfood commented on JENKINS-11673 Support https in RPM service scripts Integrated in jenkins_main_trunk #3422 FIXES JENKINS-11673 - Support https in RPM service scripts (Revision 00b6d99be6b5a23fbef3b53e34368c4e5c30de9d) Result = SUCCESS n8felton : 00b6d99be6b5a23fbef3b53e34368c4e5c30de9d Files : rpm/SOURCES/jenkins.sysconfig.in rpm/SOURCES/jenkins.init.in This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19250) Want to know which user started a build that is sitting in the queue
dogfood commented on JENKINS-19250 Want to know which user started a build that is sitting in the queue Integrated in jenkins_main_trunk #3422 FIX JENKINS-19250 Add causes to queue item tool tip (Revision 19e40a9338a70dbf51f6236be7fcf2fc9b7fb511) Result = SUCCESS daniel-beck : 19e40a9338a70dbf51f6236be7fcf2fc9b7fb511 Files : core/src/main/resources/lib/hudson/queue.jelly core/src/main/java/hudson/model/Queue.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-17114) Reason for job starvation icon is wrong
dogfood commented on JENKINS-17114 Reason for job starvation icon is wrong Integrated in jenkins_main_trunk #3422 FIX JENKINS-17114 Distinguish 'nodes offline' from 'no nodes' (Revision 5aa32c8681410eccfabf68397692f2402e615a48) Result = SUCCESS daniel-beck : 5aa32c8681410eccfabf68397692f2402e615a48 Files : core/src/main/resources/hudson/model/queue/CauseOfBlockage/BecauseLabelIsOffline/summary.jelly core/src/main/resources/hudson/model/queue/CauseOfBlockage/BecauseLabelIsOffline/summary.properties core/src/main/resources/hudson/model/Messages.properties core/src/main/java/hudson/model/queue/CauseOfBlockage.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-16264) Posting config.xml to master node advertised to work
SCM/JIRA link daemon commented on JENKINS-16264 Posting config.xml to master node advertised to work Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/jenkins/model/Jenkins/MasterComputer/_api.jelly http://jenkins-ci.org/commit/jenkins/af67ae868e0d150e4d73e48a301c831bc2732b0c Log: FIX JENKINS-16264 Don't advertise POSTing config.xml on master This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [throttle-concurrents] (JENKINS-13619) Add ability to throttle number of concurrent builds of matrix configurations per node
SCM/JIRA link daemon commented on JENKINS-13619 Add ability to throttle number of concurrent builds of matrix configurations per node Code changed in jenkins User: Oleg Nenashev Path: pom.xml src/main/java/hudson/plugins/throttleconcurrents/ThrottleJobProperty.java src/main/java/hudson/plugins/throttleconcurrents/ThrottleMatrixProjectOptions.java src/main/java/hudson/plugins/throttleconcurrents/ThrottleQueueTaskDispatcher.java src/main/resources/hudson/plugins/throttleconcurrents/Messages.properties src/main/resources/hudson/plugins/throttleconcurrents/ThrottleJobProperty/config.jelly src/main/resources/hudson/plugins/throttleconcurrents/ThrottleMatrixProjectOptions/config.jelly src/main/resources/hudson/plugins/throttleconcurrents/ThrottleMatrixProjectOptions/config.properties src/test/java/hudson/plugins/throttleconcurrents/ThrottleJobPropertyTest.java http://jenkins-ci.org/commit/throttle-concurrent-builds-plugin/abd999baf869d0bc598ed6fc522303c629117ed3 Log: Merge pull request #18 from jenkinsci/throttle-matrix-configurations JENKINS-13619 - Throttle matrix configurations Compare: https://github.com/jenkinsci/throttle-concurrent-builds-plugin/compare/4fa0bb541fbb...abd999baf869 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-16264) Posting config.xml to master node advertised to work
SCM/JIRA link daemon commented on JENKINS-16264 Posting config.xml to master node advertised to work Code changed in jenkins User: Oliver Gondža Path: core/src/main/resources/jenkins/model/Jenkins/MasterComputer/_api.jelly http://jenkins-ci.org/commit/jenkins/bdfcd2625381e3e9153c1de5ead82abe96ab1c16 Log: Merge pull request #1258 from daniel-beck/JENKINS-16264 FIX JENKINS-16264 Don't advertise POSTing config.xml on master This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix] (JENKINS-16521) Multi-Project Throttle Categories don't work with Matrix jobs
Oleg Nenashev resolved JENKINS-16521 as Duplicate Multi-Project Throttle Categories dont work with Matrix jobs Marking as duplicate. Let's track the further activity in JENKINS-13619 Change By: Oleg Nenashev (01/Jun/14 1:15 PM) Status: InProgress 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/d/optout.
[JIRA] [matrix] (JENKINS-16521) Multi-Project Throttle Categories don't work with Matrix jobs
Oleg Nenashev commented on JENKINS-16521 Multi-Project Throttle Categories dont work with Matrix jobs @Andrea This is a similar issue. I'll provide a Dev Build of the plugin in JENKINS-13619 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-9938) Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to exception
Oleg Nenashev resolved JENKINS-9938 as Cannot Reproduce Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to exception The issue has been caused by the channel termination. There were many fixes for nodes handling, hence the issue should be reproduced on newest Jenkins versions Change By: Oleg Nenashev (01/Jun/14 1:43 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Agen judi online terpercaya hokybet
very fantastic posting. Where else could anyone get that kind of information in such a perfect way of writing? I have a speech next week, and I was looking for more info ;) obat pembesar penis http://vimax.ml - vimax http://vimax.ml/ - pro extender http://vimax.ml/vimax-extender.html - neosize xl http://vimax.ml/neosize-xl.html -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Agen-judi-online-terpercaya-hokybet-tp4678816p4704754.html Sent from the Jenkins issues mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Agen judi online terpercaya hokybet
I am not sure where you’re getting your info, but good topic. I needs to spend some time learning much more or understanding more. Thanks for magnificent info I was looking for this information for my mission. Prediksi Togel http://black-id.us - Togel Hari ini http://www1.pemaintogel.info - Togel Hongkong http://black-id.us/category/togel-hongkong/ - Togel Singapura http://black-id.us/category/togel-singapura/ -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Agen-judi-online-terpercaya-hokybet-tp4678816p4704755.html Sent from the Jenkins issues mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Agen judi online terpercaya hokybet
I used to be more than happy to find this site.I wanted to thanks for this nice read!! I undoubtedly having fun with each little little bit of it and I've you bookmarked to take a look at new stuff you post. Anyway, in my language, there will not be much good source like this. Video Bokep http://tantegirangku.ml - Bokep artis indo http://bokep3gp.ml - bokep 3gp Terbaru http://free-down.net - Cerita Sex Dewasa http://cerita.prediksitogeljitu.in -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Agen-judi-online-terpercaya-hokybet-tp4678816p4704756.html Sent from the Jenkins issues mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Agen judi online terpercaya hokybet
Took me time to read all the comments, however I really loved the article. It proved to be very useful to me and I'm positive to all of the commenters here! It's all the time good when you can't only learn, but in addition engaged! I am certain you had joy penning this article. Anyway, in my language, there aren't much good source like this. Agen Bola http://asia303.at.ua | Judi Online 303A http://asia303.at.ua | Sbobet Casino http://agenbola168.com Terpercaya -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Agen-judi-online-terpercaya-hokybet-tp4678816p4704757.html Sent from the Jenkins issues mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [throttle-concurrents] (JENKINS-19986) Throttle Concurrent Builds plugin doesn't appear to work
David Kaelbling commented on JENKINS-19986 Throttle Concurrent Builds plugin doesnt appear to work I'm also unable to throttle even very simple matrix jobs, running Jenkins 1.565 and version 1.8.2 of the plugin. The job setup is: Throttle this project alone Maximum total concurrent builds: 0 Maximum concurrent builds per node: 1 One user-defined axis When I launch it no throttling is done every available executor starts processing one of the configurations. I tried throttling by category (changing the project limits 0) and got the same behavior, both for generic limits and node-specific category limits. How can I help debug 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/d/optout.
[JIRA] [throttle-concurrents] (JENKINS-19986) Throttle Concurrent Builds plugin doesn't appear to work
Oleg Nenashev commented on JENKINS-19986 Throttle Concurrent Builds plugin doesnt appear to work See JENKINS-13619 for all issues related to MATRIX jobs. The new release of the plugin will provide throttling of matrix configurations in "Categories" mode at least This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix] (JENKINS-21423) Matrix jobs consistently fail when run concurrently
Oleg Nenashev assigned JENKINS-21423 to Oleg Nenashev Matrix jobs consistently fail when run concurrently Change By: Oleg Nenashev (01/Jun/14 2:45 PM) Assignee: OlegNenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix] (JENKINS-21423) Matrix jobs consistently fail when run concurrently
Oleg Nenashev commented on JENKINS-21423 Matrix jobs consistently fail when run concurrently Sorry, I've forgot to reply to this issue several months ago. I'll try to investigate the issue on my installations This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-16264) Posting config.xml to master node advertised to work
dogfood commented on JENKINS-16264 Posting config.xml to master node advertised to work Integrated in jenkins_main_trunk #3424 FIX JENKINS-16264 Don't advertise POSTing config.xml on master (Revision af67ae868e0d150e4d73e48a301c831bc2732b0c) Result = SUCCESS daniel-beck : af67ae868e0d150e4d73e48a301c831bc2732b0c Files : core/src/main/resources/jenkins/model/Jenkins/MasterComputer/_api.jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-23146) StringIndexOutOfBoundsException on subversion checkout
Daniel Beck commented on JENKINS-23146 StringIndexOutOfBoundsException on subversion checkout FYI, I use a build of 'big solution' plus PR 83 on my main instance for a week now (a few hundred mostly freestyle projects across multiple teams, maybe 100 or so builds every day), and have not experienced any problems. Once I open a PR with the change, you could download a snapshot build. Any interest among the watchers in verifying the solution works? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-19396) Extra logging added to Maven builds makes the build log hard to read - org.apache.maven.cli.event.ExecutionEventLogger
cowwoc commented on JENKINS-19396 Extra logging added to Maven builds makes the build log hard to read - org.apache.maven.cli.event.ExecutionEventLogger @Daniel Beck, Sorry, the last comment was directed at you. I am getting a very verbose syntax: [pool-3-thread-1] INFO org.apache.maven.cli.transfer.Slf4jMavenTransferListener - Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.4/maven-install-plugin-2.4.pom It looks like the logging pattern is at fault. I am expecting the line to begin with "Downloading". Is there any way to make it less verbose? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Daniel Beck commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Oleg: Better file a separate issue to make PR 1248 eligible for LTS. Oliver will never even see this unresolved issue for a different component. (And I still maintain this is a Build Pipeline bug, adding a null cause shouldn't happen) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvfb] (JENKINS-23155) Only run plugin under Linux
cowwoc commented on JENKINS-23155 Only run plugin under Linux 1.0.11-beta3 works for me. Thank you! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-15094) Parameters: NPE in canTake() procedures may kill all executors
SCM/JIRA link daemon commented on JENKINS-15094 Parameters: NPE in canTake() procedures may kill all executors Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/hudson/cli/BuildCommand.java core/src/main/java/hudson/model/ParameterDefinition.java core/src/main/java/hudson/model/ParametersAction.java core/src/main/java/hudson/model/ParametersDefinitionProperty.java core/src/test/java/hudson/model/ParametersActionTest.java test/src/test/groovy/hudson/cli/BuildCommandTest.groovy http://jenkins-ci.org/commit/jenkins/9402bd82cdafdde8b28a99c2cd6fede9409499a1 Log: Merge pull request #1229 from synopsys-arc-oss/CLI_null_ParameteValue READYFIXED JENKINS-15094 - Handle null parameter values to avoid massive executor deaths This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-15094) Parameters: NPE in canTake() procedures may kill all executors
SCM/JIRA link daemon commented on JENKINS-15094 Parameters: NPE in canTake() procedures may kill all executors Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/cli/BuildCommand.java core/src/main/java/hudson/model/ParameterDefinition.java core/src/main/java/hudson/model/ParametersAction.java core/src/main/java/hudson/model/ParametersDefinitionProperty.java http://jenkins-ci.org/commit/jenkins/7b894f57b78be0e4d847fe1c971955d2cbb08e58 Log: FIXED JENKINS-15094 - Handle null parameter values in BuildCommand (CLI) and Parameter classes (CLI). The change adds missing checks for null ParameterValue, which may be passed from the CLI. It prevents the death of Jenkins executors during the canTake() check of node labels. Signed-off-by: Oleg Nenashev o.v.nenas...@gmail.com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-15094) Parameters: NPE in canTake() procedures may kill all executors
SCM/JIRA link daemon commented on JENKINS-15094 Parameters: NPE in canTake() procedures may kill all executors Code changed in jenkins User: Oleg Nenashev Path: core/src/test/java/hudson/model/ParametersActionTest.java test/src/test/groovy/hudson/cli/BuildCommandTest.groovy http://jenkins-ci.org/commit/jenkins/cd23fac9950c1c0762731372df2c109d4bb80db3 Log: JENKINS-15094 - Unit tests for the issue Signed-off-by: Oleg Nenashev o.v.nenas...@gmail.com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-15094) Parameters: NPE in canTake() procedures may kill all executors
SCM/JIRA link daemon resolved JENKINS-15094 as Fixed Parameters: NPE in canTake() procedures may kill all executors Change By: SCM/JIRA link daemon (01/Jun/14 4:30 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-15094) Parameters: NPE in canTake() procedures may kill all executors
Oleg Nenashev updated JENKINS-15094 Parameters: NPE in canTake() procedures may kill all executors Marked the issue as lts-candidate Change By: Oleg Nenashev (01/Jun/14 4:33 PM) Labels: lts-candidate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-15094) Parameters: NPE in canTake() procedures may kill all executors
SCM/JIRA link daemon commented on JENKINS-15094 Parameters: NPE in canTake() procedures may kill all executors Code changed in jenkins User: Oliver Gondža Path: changelog.html http://jenkins-ci.org/commit/jenkins/00292ff44c38a4d6c1423020f13f97e48efd7bad Log: Marking JENKINS-15094 major bug This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23244) Slave build history page has no data and spawns a ton of very long-lived blocking threads on the master
Daniel Beck commented on JENKINS-23244 Slave build history page has no data and spawns a ton of very long-lived blocking threads on the master abayer: What changed? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23244) Slave build history page has no data and spawns a ton of very long-lived blocking threads on the master
abayer commented on JENKINS-23244 Slave build history page has no data and spawns a ton of very long-lived blocking threads on the master Nothing - just time after startup and first attempt to load it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22612) Parametrizeds jobs do not save after to exclude a parameter
Daniel Beck commented on JENKINS-22612 Parametrizeds jobs do not save after to exclude a parameter Can this be reproduced in 1.560+? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22699) Add option to archive artifacts only when successful
SCM/JIRA link daemon commented on JENKINS-22699 Add option to archive artifacts only when successful Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/tasks/ArtifactArchiver.java core/src/main/resources/hudson/tasks/ArtifactArchiver/config.jelly core/src/main/resources/hudson/tasks/ArtifactArchiver/config.properties core/src/main/resources/hudson/tasks/Messages.properties test/src/test/java/hudson/tasks/ArtifactArchiverTest.java http://jenkins-ci.org/commit/jenkins/6df89e3340c2e31a67b83384f5333ee23bd7fcc8 Log: FIXED JENKINS-22699 Add option to archive only if successful This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22699) Add option to archive artifacts only when successful
SCM/JIRA link daemon resolved JENKINS-22699 as Fixed Add option to archive artifacts only when successful Change By: SCM/JIRA link daemon (01/Jun/14 5:21 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22699) Add option to archive artifacts only when successful
SCM/JIRA link daemon commented on JENKINS-22699 Add option to archive artifacts only when successful Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/tasks/ArtifactArchiver.java core/src/main/resources/hudson/tasks/ArtifactArchiver/config.jelly core/src/main/resources/hudson/tasks/ArtifactArchiver/config.properties core/src/main/resources/hudson/tasks/Messages.properties test/src/test/java/hudson/tasks/ArtifactArchiverTest.java http://jenkins-ci.org/commit/jenkins/a71240c88a4bdf1c5adbf5da3acbaf68de84a92c Log: Merge pull request #1205 from daniel-beck/JENKINS-22699 FIXED JENKINS-22699 - JUnit Archiver. Add option to archive only when successful Compare: https://github.com/jenkinsci/jenkins/compare/bdad023bd46e...a71240c88a4b This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-15094) Parameters: NPE in canTake() procedures may kill all executors
dogfood commented on JENKINS-15094 Parameters: NPE in canTake() procedures may kill all executors Integrated in jenkins_main_trunk #3425 JENKINS-15094 - Unit tests for the issue (Revision cd23fac9950c1c0762731372df2c109d4bb80db3) FIXED JENKINS-15094 - Handle null parameter values in BuildCommand (CLI) and Parameter classes (CLI). (Revision 7b894f57b78be0e4d847fe1c971955d2cbb08e58) Result = SUCCESS o.v.nenashev : cd23fac9950c1c0762731372df2c109d4bb80db3 Files : core/src/test/java/hudson/model/ParametersActionTest.java test/src/test/groovy/hudson/cli/BuildCommandTest.groovy o.v.nenashev : 7b894f57b78be0e4d847fe1c971955d2cbb08e58 Files : core/src/main/java/hudson/model/ParametersAction.java core/src/main/java/hudson/cli/BuildCommand.java core/src/main/java/hudson/model/ParametersDefinitionProperty.java core/src/main/java/hudson/model/ParameterDefinition.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [throttle-concurrents] (JENKINS-13619) Add ability to throttle number of concurrent builds of matrix configurations per node
Oleg Nenashev updated JENKINS-13619 Add ability to throttle number of concurrent builds of matrix configurations per node Attached the plugin package from https://jenkins.ci.cloudbees.com/job/plugins/job/throttle-concurrent-builds-plugin/33/org.jenkins-ci.plugins$throttle-concurrents/ Change By: Oleg Nenashev (01/Jun/14 6:00 PM) Attachment: throttle-concurrents-1.8.3-SNAPSHOT.hpi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvfb] (JENKINS-23155) Only run plugin under Linux
zregvart resolved JENKINS-23155 as Fixed Only run plugin under Linux Hi, I've released version 1.0.11. Change By: zregvart (01/Jun/14 6:03 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/d/optout.
[JIRA] [core] (JENKINS-22699) Add option to archive artifacts only when successful
dogfood commented on JENKINS-22699 Add option to archive artifacts only when successful Integrated in jenkins_main_trunk #3426 FIXED JENKINS-22699 Add option to archive only if successful (Revision 6df89e3340c2e31a67b83384f5333ee23bd7fcc8) Result = SUCCESS daniel-beck : 6df89e3340c2e31a67b83384f5333ee23bd7fcc8 Files : core/src/main/java/hudson/tasks/ArtifactArchiver.java core/src/main/resources/hudson/tasks/ArtifactArchiver/config.properties test/src/test/java/hudson/tasks/ArtifactArchiverTest.java core/src/main/resources/hudson/tasks/Messages.properties core/src/main/resources/hudson/tasks/ArtifactArchiver/config.jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-alias-setter] (JENKINS-23264) Alias configuration is shared by all jobs
SCM/JIRA link daemon commented on JENKINS-23264 Alias configuration is shared by all jobs Code changed in jenkins User: Oliver Gondža Path: pom.xml src/main/java/org/jenkinsci/plugins/buildaliassetter/BuildAliasSetter.java src/main/resources/org/jenkinsci/plugins/buildaliassetter/BuildAliasSetter/config.jelly src/test/java/org/jenkinsci/plugins/buildaliassetter/AliasSettingTest.java http://jenkins-ci.org/commit/build-alias-setter-plugin/3b7dfb88ccb30fdec02151e8c7dd686e8d0d48b5 Log: FIXED JENKINS-23264 Alias configuration is shared by all jobs Compare: https://github.com/jenkinsci/build-alias-setter-plugin/compare/9f63bcc98118...3b7dfb88ccb3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-alias-setter] (JENKINS-23264) Alias configuration is shared by all jobs
SCM/JIRA link daemon resolved JENKINS-23264 as Fixed Alias configuration is shared by all jobs Change By: SCM/JIRA link daemon (01/Jun/14 6:30 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/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22654) Multi-configuration projects display with wrong Delivery Pipeline Stage Name
Patrik Boström commented on JENKINS-22654 Multi-configuration projects display with wrong Delivery Pipeline Stage Name Can't reproduce the issue. I created a job A which is a freestyle one, a job B which is a multi-configuration job. A will trigger B. Configured stage and task names. When looking in the view the configured stage name and task name is 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/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22654) Multi-configuration projects display with wrong Delivery Pipeline Stage Name
Patrik Boström edited a comment on JENKINS-22654 Multi-configuration projects display with wrong Delivery Pipeline Stage Name Hi, Can't reproduce the issue. I created a job A which is a freestyle one, a job B which is a multi-configuration job. A will trigger B. Configured stage and task names. When looking in the view the configured stage name and task name is 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/d/optout.
[JIRA] [build-alias-setter] (JENKINS-21734) When a job is copied, the aliases as copied over and corrupt the new job
SCM/JIRA link daemon commented on JENKINS-21734 When a job is copied, the aliases as copied over and corrupt the new job Code changed in jenkins User: Oliver Gondža Path: src/main/java/org/jenkinsci/plugins/buildaliassetter/BuildAliasSetter.java src/test/java/org/jenkinsci/plugins/buildaliassetter/IntegrationTest.java http://jenkins-ci.org/commit/build-alias-setter-plugin/616aa104304c2a36f9804a513541af89ac8253da Log: FIXED JENKINS-21734 When a job is copied, the aliases as copied over and corrupt the new 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/d/optout.
[JIRA] [build-alias-setter] (JENKINS-21734) When a job is copied, the aliases as copied over and corrupt the new job
SCM/JIRA link daemon resolved JENKINS-21734 as Fixed When a job is copied, the aliases as copied over and corrupt the new job Change By: SCM/JIRA link daemon (01/Jun/14 7: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/d/optout.
[JIRA] [build-alias-setter] (JENKINS-21734) When a job is copied, the aliases as copied over and corrupt the new job
Oliver Gondža commented on JENKINS-21734 When a job is copied, the aliases as copied over and corrupt the new job I was not able to reproduce the exact stacktrace but aliases ware indeed copied. Fixed in 0.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/d/optout.
[JIRA] [hockeyapp] (JENKINS-22848) Hockeyapp plugin can't publish from remote slaves
Oliver H commented on JENKINS-22848 Hockeyapp plugin cant publish from remote slaves No this is not normal! I tried to do a release again, but somehow the maven-release-plugin does not work on this machine. I will hopefully look at this tomorrow, but you want to get the updated plugin right now you can download it here: https://dl.dropboxusercontent.com/u/8978467/hockeyapp.hpi and install it manually. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23248) CLI: get-job calls are causing file descriptor leaks.
Craig Phillips commented on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. /tmp/jenk_fd.1 2014-06-01 21:03:34.006155887 +0100 +++ /tmp/jenk_fd.2 2014-06-01 21:09:27.053382015 +0100 @@ -52342 +52341,0 @@ -l-wx-- 1 kcc users 64 Jun 1 20:45 57103 - socket:282820885 @@ -55657 +55655,0 @@ lr-x- 1 kcc users 64 Jun 1 20:59 60087 - /user1/jenkins/jobs/scm-poll-jenkins-branch-monitor/builds/2014-06-01_21-01-01/log @@ -55662 +55660 @@ lr-x- 1 kcc users 64 Jun 1 21:01 60091 - pipe:282533977 +lr-x-- 1 kcc users 64 Jun 1 21:01 60091 - socket:283188722 @@ -55747 +55745 @@ lrwx- 1 kcc users 64 Jun 1 21:03 60169 - socket:282813330 +lrwx-- 1 kcc users 64 Jun 1 21:03 60169 - socket:283188811 @@ -55807 +55804,0 @@ lrwx- 1 kcc users 64 Jun 1 21:03 60222 - socket:282819646 @@ -55824,0 +55822 @@ +lrwx-- 1 kcc users 64 Jun 1 21:04 60239 - socket:282821225 @@ -55825,0 +55824,5 @@ +lrwx-- 1 kcc users 64 Jun 1 21:04 60240 - socket:282821552 +lrwx-- 1 kcc users 64 Jun 1 21:05 60241 - socket:282821858 +l-wx-- 1 kcc users 64 Jun 1 21:05 60242 - socket:282947156 +lrwx-- 1 kcc users 64 Jun 1 21:07 60243 - socket:282947065 +lr-x-- 1 kcc users 64 Jun 1 21:05 60244 - socket:283309559 This is just a small sample within several minutes of one another. I can send a larger delta if needs be. The leak is now at 6 files, which you can see from the line numbers in the diff. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23248) CLI: get-job calls are causing file descriptor leaks.
Craig Phillips commented on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. Running garbage collection in the JVM doesn't clear them down either. I think I mentioned this already. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23248) CLI: get-job calls are causing file descriptor leaks.
Daniel Beck commented on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp] (JENKINS-22848) Hockeyapp plugin can't publish from remote slaves
Daniel Beck commented on JENKINS-22848 Hockeyapp plugin cant publish from remote slaves Oliver: There's a bug in Maven Release Plugin, maybe you're hit by that? https://groups.google.com/forum/#!topic/jenkinsci-dev/qkmbl3HrYgk This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-12229) Loading Overlay does not go away - FF8
Daniel Beck commented on JENKINS-12229 Loading Overlay does not go away - FF8 Does this issue still occur on recent Jenkins versions? There have been robustness improvements in recent releases related to the config page. Also relevant would be which plugins you have installed in which versions. Due to the nature of plugins and the config page, a broken plugin can break your entire config page. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-6338) Job's cyclic dependency not detected
Daniel Beck commented on JENKINS-6338 Jobs cyclic dependency not detected There is code in the build trigger cause to specifically not recurse into parent triggers infinitely. It's safe to assume this is a supported scenario. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-alias-setter] (JENKINS-20405) When an alias is re-assigned to a newer build, the alias url should no longer point to the older build
SCM/JIRA link daemon commented on JENKINS-20405 When an alias is re-assigned to a newer build, the alias url should no longer point to the older build Code changed in jenkins User: Oliver Gondža Path: src/main/java/org/jenkinsci/plugins/buildaliassetter/Alias.java src/main/java/org/jenkinsci/plugins/buildaliassetter/PermalinkStorage.java src/test/java/org/jenkinsci/plugins/buildaliassetter/AliasSettingTest.java src/test/java/org/jenkinsci/plugins/buildaliassetter/IntegrationTest.java src/test/java/org/jenkinsci/plugins/buildaliassetter/util/DummyProvider.java http://jenkins-ci.org/commit/build-alias-setter-plugin/84258ee3298dc6c4e6e8f8a2188e105977e6d566 Log: FIXED JENKINS-20405 Show only the most recent alias permalink with given name This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-alias-setter] (JENKINS-20405) When an alias is re-assigned to a newer build, the alias url should no longer point to the older build
SCM/JIRA link daemon resolved JENKINS-20405 as Fixed When an alias is re-assigned to a newer build, the alias url should no longer point to the older build Change By: SCM/JIRA link daemon (01/Jun/14 9:01 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/d/optout.
[JIRA] [testlink] (JENKINS-23265) TestLink plugin indicates test case as not run and TestLink is not updated with build status
mirou mirou created JENKINS-23265 TestLink plugin indicates test case as not run and TestLink is not updated with build status Issue Type: Bug Assignee: Bruno P. Kinoshita Attachments: customer_field.png, jenkins-conf1.png, jenkins-conf2.png, jenkins_console.png, jenkins_results_testlink.png Components: testlink Created: 01/Jun/14 9:39 PM Description: version jenkins:1.565 version testlink:1.9.10 plugin testlink:3.10 I just created a job to run an automated test, it allows you to run a file. ".bat" (display bonjour) when I run the build, it ends successfully but Testlink is not updated and testng-results.xml does not exist. I attached configuration Testlink and jenkins Project: Jenkins Priority: Major Reporter: mirou mirou This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp] (JENKINS-22848) Hockeyapp plugin can't publish from remote slaves
Jonathan Crooke commented on JENKINS-22848 Hockeyapp plugin cant publish from remote slaves Installed manually, then - 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/d/optout.
[JIRA] [hockeyapp] (JENKINS-22848) Hockeyapp plugin can't publish from remote slaves
Oliver H commented on JENKINS-22848 Hockeyapp plugin cant publish from remote slaves @Daniel: That was exactly my problem. I already found this bug yesterday and tried some things, which didn't work out. But now i've got it working with: mvn org.apache.maven.plugins:maven-release-plugin:2.5:perform. Release doesn't work anyhow, because authorization failed (got my credentials in settings.xml). Will investigate this evening. Thanx! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18687) Intermittent failure whilst recording test results caused by java.util.MissingResourceException
Lucie Votypkova commented on JENKINS-18687 Intermittent failure whilst recording test results caused by java.util.MissingResourceException It happens on our instance when java which is in java.home of slave.jar is updated. Do you remember if there was some java updates during slave connection in jenkins? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
