[JIRA] [performance-plugin] (JENKINS-21786) Performance Per Test Case Mode display type use Max. value instead of Average one !
Philippe Koutsoulis commented on JENKINS-21786 Performance Per Test Case Mode display type use Max. value instead of Average one ! ... Eventually, we may also want to have this configurable based on whether to take median, or average or 95-percentile... It would be great This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22641) Jenkins no longer kills running processes after job fails
Andrei Neculau commented on JENKINS-22641 Jenkins no longer kills running processes after job fails I can confirm this issue with 0.558 on a Debian 7.4 and Ubuntu 12.04 with Open/Oracle 6/7 JDKs, on master/slave. And I can also confirm that downgrading to 0.552 solved it (didn't have the time to do a "bisect" on intermediary versions). Thanks for reporting the issue! I thought I'm misunderstanding the processtreekiller feature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
Xin Huang commented on JENKINS-13253 Slave connection reset issues since 1.456 Our team is facing the connection reset issue, too. We've tried various version of Jenkins, ranging from 1.4xx to 1.6xx, but the issue seems somewhat random: Before the issue happens, the slave works well. However, several slaves are just don't work. Tried re-create slave VMs, doesn't help much. Newly created slave would suffer the issue after working well for 1 or 2 days. Build lasts from several minutes to hours, usually connection reset happens 1~2 hours after build starts, (long-lasting jobs) but slave is not offline. What's wired, one of our master/slaves never suffered from such issue. It's using 1.469 Change new server to this version doesn't help. We are using Windows 7 Enterprise 64bit on LAN, all slaves are hosted on vSphere. Slaves are connected via web start/install as service. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [active-directory] (JENKINS-22669) login failed after upgrade to 1.37 from 1.36
podskalsky commented on JENKINS-22669 login failed after upgrade to 1.37 from 1.36 I have the same problem an my Solaris(sparc) system This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22669) login failed after upgrade to 1.37 from 1.36
podskalsky edited a comment on JENKINS-22669 login failed after upgrade to 1.37 from 1.36 I have the same problem at my Solaris(sparc) system This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22612) Parametrizeds jobs do not save after to exclude a parameter
ikedam commented on JENKINS-22612 Parametrizeds jobs do not save after to exclude a parameter Hmm... so this differs from JENKINS-22275 . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [maven] (JENKINS-22673) Sites for nested Maven multi-module projects deeper than one level are archived flat
Marcel Steinbach created JENKINS-22673 Sites for nested Maven multi-module projects deeper than one level are archived flat Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: maven Created: 18/Apr/14 11:48 AM Description: Multi-module projects with nesting more than one level are archived in a flat fashion by the maven-plugin. This results in broken links in the archived maven-site. E.g. ROOT site/ +-A |-A +-x -x +-y- -y +-B -B +-z -z Project: Jenkins Priority: Major Reporter: Marcel Steinbach This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [maven] (JENKINS-22673) Sites for nested Maven multi-module projects deeper than one level are archived flat
Marcel Steinbach
updated JENKINS-22673
Sites for nested Maven multi-module projects deeper than one level are archived flat
Change By:
Marcel Steinbach
(18/Apr/14 11:49 AM)
Description:
Multi-moduleprojectswithnestingmorethanonelevelarearchivedinaflatfashionbythemaven-plugin.Thisresultsinbrokenlinksinthearchivedmaven-site.E.g.
{code}
ROOTsite/+-A|-A|+-x|-x|+-y-|-y+-B|-B+-z|-z
{code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-22674) Show larger load statistics graphs
Daniel Beck created JENKINS-22674 Show larger load statistics graphs Issue Type: Improvement Assignee: Daniel Beck Attachments: Screen Shot 2014-04-18 at 13.49.41.png Components: core Created: 18/Apr/14 11:51 AM Description: On modern screens, the load statistics appear very small, while leaving the bulk of the /load-statistics page empty. This should be improved. Project: Jenkins Priority: Major Reporter: Daniel Beck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [shelve-project-plugin] (JENKINS-8063) Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384
ben patterson commented on JENKINS-8063 Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384 Hi - Thanks for the ping. I cut the release this morning. v1.5 should be available for use within the next day. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [shelve-project-plugin] (JENKINS-8063) Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384
ben patterson resolved JENKINS-8063 as Fixed Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384 Change By: ben patterson (18/Apr/14 12:53 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] [emailext-template] (JENKINS-22610) Removing (deleting) Email Notification Templates will cause the associated builds to fail.
Alex Earl resolved JENKINS-22610 as Fixed Removing (deleting) Email Notification Templates will cause the associated builds to fail. Added check in prebuild that was there in perform to make sure the template requested exists. Outputs a warning to the build log instead of crashing. Change By: Alex Earl (18/Apr/14 1: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] [emailext-template] (JENKINS-22610) Removing (deleting) Email Notification Templates will cause the associated builds to fail.
SCM/JIRA link daemon commented on JENKINS-22610 Removing (deleting) Email Notification Templates will cause the associated builds to fail. Code changed in jenkins User: Alex Earl Path: src/main/java/org/jenkinsci/plugins/emailext_template/ExtendedEmailTemplatePublisher.java http://jenkins-ci.org/commit/email-ext-template-plugin/7c9af27c8455e30e9818e85b9351720126778e4a Log: Fix JENKINS-22610 Added check if the returned value from getTemplateById is null. Write error to the build log if the template is missing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [emailext-template] (JENKINS-22610) Removing (deleting) Email Notification Templates will cause the associated builds to fail.
SCM/JIRA link daemon commented on JENKINS-22610 Removing (deleting) Email Notification Templates will cause the associated builds to fail. Code changed in jenkins User: Alex Earl Path: src/main/resources/org/jenkinsci/plugins/emailext_template/Messages.properties src/test/java/org/jeninsci/plugins/emailext_plugin/ExtendedEmailTemplatePublisherTest.java http://jenkins-ci.org/commit/email-ext-template-plugin/eb140463bb9fc0166caf3a5c0dc2f692b8010c6b Log: Add test for JENKINS-22610 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [shelve-project-plugin] (JENKINS-10544) shelve project button missing on some projects
ben patterson resolved JENKINS-10544 as Fixed shelve project button missing on some projects Fixed in release v 1.5 Change By: ben patterson (18/Apr/14 1:07 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] [shelve-project-plugin] (JENKINS-11374) Add deletion option on list of Shelved Projects
ben patterson resolved JENKINS-11374 as Fixed Add deletion option on list of Shelved Projects Available in v 1.5 of plugin Change By: ben patterson (18/Apr/14 1:08 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-15225) The failing test age counters should ignore grey builds
Daniel Beck resolved JENKINS-15225 as Duplicate The failing test age counters should ignore grey builds Appears to duplicate JENKINS-15634. Change By: Daniel Beck (18/Apr/14 1:34 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [embeddable-build-status] (JENKINS-17028) Build status icons don't refresh due to Cache-Control setting in HTTP response
SCM/JIRA link daemon commented on JENKINS-17028 Build status icons dont refresh due to Cache-Control setting in HTTP response Code changed in jenkins User: Oliver Gondža Path: src/main/java/org/jenkinsci/plugins/badge/StatusImage.java http://jenkins-ci.org/commit/embeddable-build-status-plugin/e9ced649ebc212cbb3e2d3485517d3fc3e3a1012 Log: FIXED JENKINS-17028 Merge pull request #6 from rozza/JENKINS-17028 Added Cache-Control: no-cache - refs Compare: https://github.com/jenkinsci/embeddable-build-status-plugin/compare/76463a6e8b4a...e9ced649ebc2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [git-client] (JENKINS-22675) Jenkins GIT Plugin unable to access repository using HTTPS with self-signed certificate
jose porcel created JENKINS-22675 Jenkins GIT Plugin unable to access repository using HTTPS with self-signed certificate Issue Type: Bug Assignee: Nicolas De Loof Components: git-client, gitlab-merge-request-jenkins Created: 18/Apr/14 2:05 PM Description: When trying to configure a new job and setting GIT repository Jenkins always fails regardless of the configuration when using HTTPS with credentials. Here is the error message Failed to connect to repository : handshake alert: unrecognized_name Local git install has configured git config --global http.sslVerify false Project: Jenkins Priority: Major Reporter: jose porcel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18058) NegativeArraySizeException when trying to enable a job using Jenkins CLI
Jason Carlberg updated JENKINS-18058 NegativeArraySizeException when trying to enable a job using Jenkins CLI We have observed NegativeArraySizeExceptions along with java OutOfMemory errors while using Jenkins CLI to schedule build jobs from a master job. Followed the recommendations to increase heap size, but continued to get java heap errors. After enabling "-XX:+HeapDumpOnOutOfMemoryError", there have been some heap dumps produced that are smaller than our max heap size. Using these JVM args in Jenkins 1.551: jvmarg value="-Xmx1024m" / jvmarg value="-XX:+HeapDumpOnOutOfMemoryError" / jvmarg value="-XX:MaxPermSize=512m" / Heap dumps are attached. Change By: Jason Carlberg (18/Apr/14 2:16 PM) Attachment: java_pid1524.hprof Attachment: java_pid3928.hprof This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [publish-over-ssh] (JENKINS-22676) Collapse list of servers for Publish Over SSH by default
Brant Boehmann created JENKINS-22676 Collapse list of servers for Publish Over SSH by default Issue Type: New Feature Assignee: bap Components: publish-over-ssh Created: 18/Apr/14 2:42 PM Description: Our manage jenkins page is becoming unwieldy because of our very long list of ssh servers we are using. It would be nice if that list were collapsed in some way by default. Project: Jenkins Priority: Minor Reporter: Brant Boehmann This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21341) Job failure on remote node running JDK1.8 - java.lang.NoSuchMethodException: java.lang.UNIXProcess.destroyProcess(int)
René de Groot commented on JENKINS-21341 Job failure on remote node running JDK1.8 - java.lang.NoSuchMethodException: java.lang.UNIXProcess.destroyProcess(int) Where can I find in witch version this fix will be available? There is no mention on http://jenkins-ci.org/changelog I think I have the same issue with Jenkins ver. 1.559 on OS-X and java version "1.8.0". FATAL: Could not initialize class hudson.util.ProcessTree$UnixReflection java.lang.NoClassDefFoundError: Could not initialize class hudson.util.ProcessTree$UnixReflection at hudson.util.ProcessTree$UnixProcess.kill(ProcessTree.java:553) at hudson.util.ProcessTree$UnixProcess.killRecursively(ProcessTree.java:573) at hudson.util.ProcessTree$UnixProcess.killRecursively(ProcessTree.java:572) at hudson.util.ProcessTree$Unix.killAll(ProcessTree.java:497) at hudson.Launcher$LocalLauncher.kill(Launcher.java:798) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:546) at hudson.model.Run.execute(Run.java:1700) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21341) Job failure on remote node running JDK1.8 - java.lang.NoSuchMethodException: java.lang.UNIXProcess.destroyProcess(int)
Christopher Orr commented on JENKINS-21341 Job failure on remote node running JDK1.8 - java.lang.NoSuchMethodException: java.lang.UNIXProcess.destroyProcess(int) According to the "upcoming changes" link in the changelog, it will be available 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-22641) Jenkins no longer kills running processes after job fails
Todd Perry commented on JENKINS-22641 Jenkins no longer kills running processes after job fails An update: apparently it doesn't matter whether the job failed or not and this is not necessary to reproduce it. The problem is only critical to us for failed jobs, since a failed job doesn't run the final step which shuts down the running servlet container. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22670) Linebreak project names less aggressively
SCM/JIRA link daemon commented on JENKINS-22670 Linebreak project names less aggressively Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/Functions.java core/src/test/java/hudson/FunctionsTest.java http://jenkins-ci.org/commit/jenkins/35b00941372eafcf8991ff9c10f2d9ec7ac1b347 Log: FIXED JENKINS-22670 Less aggressive word breaking This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22670) Linebreak project names less aggressively
SCM/JIRA link daemon resolved JENKINS-22670 as Fixed Linebreak project names less aggressively Change By: SCM/JIRA link daemon (18/Apr/14 5: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] [core] (JENKINS-22670) Linebreak project names less aggressively
SCM/JIRA link daemon commented on JENKINS-22670 Linebreak project names less aggressively Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/hudson/Functions.java core/src/test/java/hudson/FunctionsTest.java http://jenkins-ci.org/commit/jenkins/a7eb8b7eb3f5ad9d24e276ba8610a77be987fa65 Log: Merge pull request #1195 from daniel-beck/JENKINS-22670 FIXED JENKINS-22670 Less aggressive word breaking Compare: https://github.com/jenkinsci/jenkins/compare/c7f813e205c6...a7eb8b7eb3f5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ec2] (JENKINS-22300) Need ability to associate public ip address for slave nodes
SCM/JIRA link daemon commented on JENKINS-22300 Need ability to associate public ip address for slave nodes Code changed in jenkins User: Francis Upton Path: src/main/java/hudson/plugins/ec2/SlaveTemplate.java src/main/resources/hudson/plugins/ec2/SlaveTemplate/config.jelly src/test/java/hudson/plugins/ec2/SlaveTemplateTest.java src/test/java/hudson/plugins/ec2/TemplateLabelsTest.java http://jenkins-ci.org/commit/ec2-plugin/df1f10fbb2e9c440c65ca2961dc396b227ef080d Log: Merge pull request #84 from ferrants/master JENKINS-22300 Added checkbox to spin up slaves on VPC with a public IP Compare: https://github.com/jenkinsci/ec2-plugin/compare/c47cd08eb7de...df1f10fbb2e9 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ec2] (JENKINS-22300) Need ability to associate public ip address for slave nodes
SCM/JIRA link daemon commented on JENKINS-22300 Need ability to associate public ip address for slave nodes Code changed in jenkins User: Matt Ferrante Path: src/main/java/hudson/plugins/ec2/SlaveTemplate.java src/main/resources/hudson/plugins/ec2/SlaveTemplate/config.jelly src/test/java/hudson/plugins/ec2/SlaveTemplateTest.java src/test/java/hudson/plugins/ec2/TemplateLabelsTest.java http://jenkins-ci.org/commit/ec2-plugin/eed6dfc73a36b99f258ba0c8f0a6c2c0e1380151 Log: JENKINS-22300 Added checkbox to spin up slaves on VPC with a public IP This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22674) Show larger load statistics graphs
SCM/JIRA link daemon commented on JENKINS-22674 Show larger load statistics graphs Code changed in jenkins User: Oliver Gondža Path: core/src/main/resources/hudson/model/LoadStatistics/main.jelly http://jenkins-ci.org/commit/jenkins/63dbf2fa336002c8069bd0ea3029f708082a1c24 Log: Merge pull request #1198 from daniel-beck/JENKINS-22674 FIXED JENKINS-22674 Use JS to resize graph. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22674) Show larger load statistics graphs
SCM/JIRA link daemon commented on JENKINS-22674 Show larger load statistics graphs Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/hudson/model/LoadStatistics/main.jelly http://jenkins-ci.org/commit/jenkins/33e8a8ff005d1f31be3d6a83a68db31d59de4e14 Log: FIXED JENKINS-22674 Use JS to resize graph. This will make the load statistics graphs fit the window width. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22674) Show larger load statistics graphs
SCM/JIRA link daemon resolved JENKINS-22674 as Fixed Show larger load statistics graphs Change By: SCM/JIRA link daemon (18/Apr/14 5:56 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-22670) Linebreak project names less aggressively
dogfood commented on JENKINS-22670 Linebreak project names less aggressively Integrated in jenkins_main_trunk #3319 FIXED JENKINS-22670 Less aggressive word breaking (Revision 35b00941372eafcf8991ff9c10f2d9ec7ac1b347) Result = SUCCESS daniel-beck : 35b00941372eafcf8991ff9c10f2d9ec7ac1b347 Files : core/src/test/java/hudson/FunctionsTest.java core/src/main/java/hudson/Functions.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-22409) API Token no longer working for API calls
Peter Downs edited a comment on JENKINS-22409 API Token no longer working for API calls The following version combinations all reproduce the error: • Jenkins v1.550 / Github OAuth v0.14 • Jenkins v1.558 / Github OAuth v0.14 • Jenkins v1.559 / Github OAuth v0.14 @Justin, what combination worked for you – Jenkins v1.550 / Github OAuth v0.15-SNAPSHOT? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22409) API Token no longer working for API calls
Peter Downs commented on JENKINS-22409 API Token no longer working for API calls The following version combinations all reproduce the error: • Jenkins v1.550 / Github OAuth v0.14 • Jenkins v1.558 / Github OAuth v0.14 • Jenkins v1.559 / Github OAuth v0.14 @Justin, what combination worked for you – Jenkins v1.559 / Github OAuth v0.15-SNAPSHOT? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21882) v1.551 + GitHub OAuth == broken api token access
Peter Downs commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access Is there any further progress on this? It's unclear from this thread if the issue is resolved by using the 0.15-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] [envinject] (JENKINS-14437) envinject fails to really set/override build parameters
Klaus Schniedergers commented on JENKINS-14437 envinject fails to really set/override build parameters This started to happen to our instance after a restart (it worked before).' I am setting an environment variable via "Prepare an environment for the run-Properties Content", but it is not set in a build step. Jenkins: LTS 1.532.3 EnvInject: 1.89 It's affecting all jobs/projects. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22674) Show larger load statistics graphs
dogfood commented on JENKINS-22674 Show larger load statistics graphs Integrated in jenkins_main_trunk #3320 FIXED JENKINS-22674 Use JS to resize graph. (Revision 33e8a8ff005d1f31be3d6a83a68db31d59de4e14) Result = SUCCESS daniel-beck : 33e8a8ff005d1f31be3d6a83a68db31d59de4e14 Files : core/src/main/resources/hudson/model/LoadStatistics/main.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] [perforce] (JENKINS-22027) Perforce Fire Storm . . .
Oleg Nenashev commented on JENKINS-22027 Perforce Fire Storm . . . Yes, the implementation of such "cache" makes sense. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22677) Allow Post-Steps to run on failed/unstable builds
sebastian_dietrich created JENKINS-22677 Allow Post-Steps to run on failed/unstable builds Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: core Created: 18/Apr/14 8:07 PM Description: Currently a post-step can only be run *) if build succeeds *) if build succeeds or is unstable or *) regardless of build result Please provide a 4th option *) if build is unstable This will make it possible to e.g. run cleanup tasks if a build became instable e.g. we run a quick maven build only with test goal, if that fails we would like to run a maven build with clean test goal Project: Jenkins Labels: post-build Priority: Major Reporter: sebastian_dietrich This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [pollscm] (JENKINS-22678) Ability to restrict Poll SCM to a specific path
cowwoc created JENKINS-22678 Ability to restrict Poll SCM to a specific path Issue Type: Improvement Assignee: Vincent Latombe Components: pollscm Created: 18/Apr/14 8:13 PM Description: Use-case: We have one repository for multiple operating systems, but different Jenkins jobs per operating system. Each job wants to get triggered if it's platform-specific files got modified, but not when the other platforms got modified. We should be able to specify multiple filespec entries, where a filespec entry could be a fully-specified path, or a path containing a wildcard. http://stackoverflow.com/q/5243593/14731 shows there is demand for this, but I'm using Mercurial instead of git. This feature should really apply across all SCMs. Project: Jenkins Priority: Major Reporter: cowwoc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [pollscm] (JENKINS-22678) Ability to restrict Poll SCM to a specific path
Vincent Latombe closed JENKINS-22678 as Wont Fix Ability to restrict Poll SCM to a specific path Hi, this request doesn't belong to the scope of pollscm plugin. This plugin has a single purpose, which is to provide a button to trigger a manual polling. What you are requesting may be addressed to core, but even though, I don't see how this could be implemented in a generic way with the current SCM extension point. Change By: Vincent Latombe (18/Apr/14 8:21 PM) Status: Open Closed Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-22679) Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
Bruce Edge
created JENKINS-22679
Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
promoted-builds
Created:
18/Apr/14 8:47 PM
Description:
Up until upgrading to 2.17 I could reference my build parameters (from "This build is parameterized" section). Now these parameters are silently replace with empty strings when the promotion is run automatically after the build.
If I run the promotion again, it works.
From the promotion job:
${RELEASES}/${PROMOTED_NUMBER}/${CONFIG}/develop-${CONFIG}-${PROMOTED_NUMBER}.ipa
I logged the env for a promotion run immediately after and one run later manually.
For the immediate case, all my parameters above, CONFIG, RELEASES are null whereas they are correct for the later manual invocation.
Note that promoted builds specific parameters are OK, it's just all the rest that are not.
What makes this worse is that the jenkins updater doesn't offer a downgrade option for this plugin.
Environment:
Linux
Project:
Jenkins
Priority:
Critical
Reporter:
Bruce Edge
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-20597) Jenkins asks for confirmation before leaving edited 'View Configuration' page
SCM/JIRA link daemon commented on JENKINS-20597 Jenkins asks for confirmation before leaving edited View Configuration page Code changed in jenkins User: Oliver Gondža Path: core/src/main/resources/hudson/logging/LogRecorder/configure.jelly core/src/main/resources/hudson/model/Computer/configure.jelly core/src/main/resources/hudson/model/ComputerSet/_new.jelly core/src/main/resources/hudson/model/ComputerSet/configure.jelly core/src/main/resources/hudson/model/Job/configure.jelly core/src/main/resources/hudson/model/Run/configure.jelly core/src/main/resources/hudson/model/User/configure.jelly core/src/main/resources/hudson/model/View/configure.jelly core/src/main/resources/hudson/model/labels/LabelAtom/configure.jelly core/src/main/resources/hudson/security/GlobalSecurityConfiguration/index.groovy core/src/main/resources/jenkins/model/Jenkins/configure.jelly core/src/main/resources/lib/form/confirm.js http://jenkins-ci.org/commit/jenkins/fc471153db957be8d06d2fea63306e8b2f060462 Log: Merge pull request #1175 from daniel-beck/JENKINS-21720-2 FIXED JENKINS-20597 JENKINS-21720 Improved config confirmation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-20597) Jenkins asks for confirmation before leaving edited 'View Configuration' page
SCM/JIRA link daemon resolved JENKINS-20597 as Fixed Jenkins asks for confirmation before leaving edited View Configuration page Change By: SCM/JIRA link daemon (18/Apr/14 9:25 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-20597) Jenkins asks for confirmation before leaving edited 'View Configuration' page
SCM/JIRA link daemon commented on JENKINS-20597 Jenkins asks for confirmation before leaving edited View Configuration page Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/hudson/model/Job/configure.jelly core/src/main/resources/hudson/model/Run/configure.jelly http://jenkins-ci.org/commit/jenkins/ee64eb920cee5af9f430cfcdfd341714549960ce Log: FIXED JENKINS-20597 Only ask when user can change This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21720) Don't ask for confirmation when it doesn't make any sense
SCM/JIRA link daemon commented on JENKINS-21720 Dont ask for confirmation when it doesnt make any sense Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/hudson/logging/LogRecorder/configure.jelly core/src/main/resources/hudson/model/Computer/configure.jelly core/src/main/resources/hudson/model/ComputerSet/_new.jelly core/src/main/resources/hudson/model/View/configure.jelly core/src/main/resources/hudson/security/GlobalSecurityConfiguration/index.groovy core/src/main/resources/jenkins/model/Jenkins/configure.jelly core/src/main/resources/lib/form/confirm.js http://jenkins-ci.org/commit/jenkins/d85b86e71921f3a43a1c49701f66a1ba2b23477d Log: FIXED JENKINS-21720 Improved config confirmation. Ask for confirmation when navigating away from node, global, security, view and log configuration after changes. Don't require confirmation when pressing keys without changing (e.g. pressing Tab for navigation) and when pressing Advanced buttons. Don't require confirmation when submitting the form. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21720) Don't ask for confirmation when it doesn't make any sense
SCM/JIRA link daemon resolved JENKINS-21720 as Fixed Dont ask for confirmation when it doesnt make any sense Change By: SCM/JIRA link daemon (18/Apr/14 9:25 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-21720) Don't ask for confirmation when it doesn't make any sense
SCM/JIRA link daemon commented on JENKINS-21720 Dont ask for confirmation when it doesnt make any sense Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/hudson/model/ComputerSet/configure.jelly core/src/main/resources/hudson/model/Run/configure.jelly core/src/main/resources/hudson/model/User/configure.jelly core/src/main/resources/hudson/model/labels/LabelAtom/configure.jelly http://jenkins-ci.org/commit/jenkins/cd0fae16f00805e63832c4009a4d6984622327c0 Log: JENKINS-21720 Added User, Run, ComputerSet, and LabelAtom This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21720) Don't ask for confirmation when it doesn't make any sense
SCM/JIRA link daemon commented on JENKINS-21720 Dont ask for confirmation when it doesnt make any sense Code changed in jenkins User: Oliver Gondža Path: core/src/main/resources/hudson/logging/LogRecorder/configure.jelly core/src/main/resources/hudson/model/Computer/configure.jelly core/src/main/resources/hudson/model/ComputerSet/_new.jelly core/src/main/resources/hudson/model/ComputerSet/configure.jelly core/src/main/resources/hudson/model/Job/configure.jelly core/src/main/resources/hudson/model/Run/configure.jelly core/src/main/resources/hudson/model/User/configure.jelly core/src/main/resources/hudson/model/View/configure.jelly core/src/main/resources/hudson/model/labels/LabelAtom/configure.jelly core/src/main/resources/hudson/security/GlobalSecurityConfiguration/index.groovy core/src/main/resources/jenkins/model/Jenkins/configure.jelly core/src/main/resources/lib/form/confirm.js http://jenkins-ci.org/commit/jenkins/fc471153db957be8d06d2fea63306e8b2f060462 Log: Merge pull request #1175 from daniel-beck/JENKINS-21720-2 FIXED JENKINS-20597 JENKINS-21720 Improved config confirmation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22680) Ability to restrict Poll SCM to a specific path
cowwoc created JENKINS-22680 Ability to restrict Poll SCM to a specific path Issue Type: Improvement Assignee: Unassigned Components: core Created: 18/Apr/14 9:48 PM Description: Use-case: We have one repository for multiple operating systems, but different Jenkins jobs per operating system. Each job wants to get triggered if it's platform-specific files got modified, but not when the other platforms got modified. We should be able to specify multiple filespec entries, where a filespec entry could be a fully-specified path, or a path containing a wildcard. http://stackoverflow.com/q/5243593/14731 shows there is demand for this, but I'm using Mercurial instead of git. This feature should really apply across all SCMs. Project: Jenkins Priority: Major Reporter: cowwoc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [pollscm] (JENKINS-22678) Ability to restrict Poll SCM to a specific path
cowwoc commented on JENKINS-22678 Ability to restrict Poll SCM to a specific path Moved to JENKINS-22680. 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] [core] (JENKINS-22681) Last build of project reloaded when project asked for later build
Jesse Glick created JENKINS-22681 Last build of project reloaded when project asked for later build Issue Type: Bug Assignee: Jesse Glick Components: core Created: 18/Apr/14 10:01 PM Description: A user encountered a problem whereby a MavenModuleSetBuild would, soon after starting, be shown as completed (and failed) even though really it was still running (so for example reloading the console link sufficed to show new output, but it would not automatically refresh). It turned out that reload had been called on the build while it was still running, triggered by the Delivery Pipeline plugin attempting (in BuildUtil) to load a build by a number that was bigger than the actual last build number of the project. (Ultimately this was due to an UpstreamCause in a historical build of another project referring to an unrelated build of a different project that used to have the same name as the project showing the issue. Thus the upstream build link was dead.) Apparently Delivery Pipeline makes frequent and repeated calls to /view/*/api/json when a browser window is displaying the view, even if it is idle , so this would happen quite often. When getBuildByNumber was called with the bogus build number, this delegated to search with direction EXACT, which triggered the fix of JENKINS-19418. Unfortunately that called load on the currently highest build number—that of the running build—creating a new build object (with a state of COMPLETED and result of FAILURE, as if being loaded during a Jenkins restart after a crash), and stashing that corrupt new build object into the index. (search then returned null, correctly, since the build number did not match what was requested.) So while the original build object was fine, and ultimately wrote out the correct build.xml record, in the meantime web requests were serving a clone which claimed to have already failed. Since the console log showed ongoing progress and then success, this was a source of much confusion. (After the build really finished, the next spurious reload created a copy with the correct state/result fields, adding even more confusion since it would look like to another observer like the bug had never happened.) I tried to reproduce this in a clean 1.532.2 installation by creating a freestyle project; building #1; adding a shell build step to sleep; starting a build of #2, watching its console log; and then in another browser tab trying to load /job/p/3, expecting a 404. This did not cause #2 to suddenly stop updating; I am guessing that an additional required trigger condition is the presence of a plugin which causes build.xml to be written before the build finishes. (Jenkins core only writes it when the build is finalized, but plugins may call Run.save earlier, for various reasons.) If there is no build.xml, then load would return null and not update the index. At any rate, I did manage to reproduce the basic flaw in a unit test quite easily. After calling search with EXACT and a number larger than any existing build, subsequent calls with the number of the last build returned a different copy. Simply switching to getById fixes the problem according to this test, without regressing JENKINS-19418, at least according to its test. And with this fix, indeed reload is no longer called on existing builds (at least running ones), and the bug symptoms disappeared. Environment: 1.532.2 Project: Jenkins Labels: lazy-loading Priority: Major Reporter: Jesse Glick This
[JIRA] [core] (JENKINS-22681) Last build of project reloaded when project asked for later build
Jesse Glick started work on JENKINS-22681 Last build of project reloaded when project asked for later build Change By: Jesse Glick (18/Apr/14 10:01 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21720) Don't ask for confirmation when it doesn't make any sense
dogfood commented on JENKINS-21720 Dont ask for confirmation when it doesnt make any sense Integrated in jenkins_main_trunk #3321 FIXED JENKINS-21720 Improved config confirmation. (Revision d85b86e71921f3a43a1c49701f66a1ba2b23477d) JENKINS-21720 Added User, Run, ComputerSet, and LabelAtom (Revision cd0fae16f00805e63832c4009a4d6984622327c0) Result = SUCCESS daniel-beck : d85b86e71921f3a43a1c49701f66a1ba2b23477d Files : core/src/main/resources/hudson/model/View/configure.jelly core/src/main/resources/hudson/security/GlobalSecurityConfiguration/index.groovy core/src/main/resources/hudson/model/ComputerSet/_new.jelly core/src/main/resources/hudson/logging/LogRecorder/configure.jelly core/src/main/resources/jenkins/model/Jenkins/configure.jelly core/src/main/resources/lib/form/confirm.js core/src/main/resources/hudson/model/Computer/configure.jelly daniel-beck : cd0fae16f00805e63832c4009a4d6984622327c0 Files : core/src/main/resources/hudson/model/labels/LabelAtom/configure.jelly core/src/main/resources/hudson/model/User/configure.jelly core/src/main/resources/hudson/model/ComputerSet/configure.jelly core/src/main/resources/hudson/model/Run/configure.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-20597) Jenkins asks for confirmation before leaving edited 'View Configuration' page
dogfood commented on JENKINS-20597 Jenkins asks for confirmation before leaving edited View Configuration page Integrated in jenkins_main_trunk #3321 FIXED JENKINS-20597 Only ask when user can change (Revision ee64eb920cee5af9f430cfcdfd341714549960ce) Result = SUCCESS daniel-beck : ee64eb920cee5af9f430cfcdfd341714549960ce Files : core/src/main/resources/hudson/model/Run/configure.jelly core/src/main/resources/hudson/model/Job/configure.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-22681) Last build of project reloaded when project asked for later build
Jesse Glick updated JENKINS-22681 Last build of project reloaded when project asked for later build Change By: Jesse Glick (18/Apr/14 10:37 PM) Labels: lazy-loading lts-candidateperformance This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22681) Last build of project reloaded when project asked for later build
Jesse Glick commented on JENKINS-22681 Last build of project reloaded when project asked for later build Marking as a performance issue since in cases where gratuitous load is called often, this can add significant load to the system. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22640) Notify commit can't find job by URI
Dmitry Moskowski resolved JENKINS-22640 as Not A Defect Notify commit cant find job by URI Just found "Poll SCM" checkbox turned off. Don't know why it's required to be checked... but thats solves my problem. Thanks for help! Change By: Dmitry Moskowski (18/Apr/14 10:48 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22681) Last build of project reloaded when project asked for later build
SCM/JIRA link daemon commented on JENKINS-22681 Last build of project reloaded when project asked for later build Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java core/src/test/java/jenkins/model/lazy/AbstractLazyLoadRunMapTest.java core/src/test/java/jenkins/model/lazy/FakeMap.java http://jenkins-ci.org/commit/jenkins/b6b7bfd27c9b5551fde04416ee9b7b5faf16ad99 Log: FIXED JENKINS-22681 Fix of JENKINS-19418 should have used getById, not load, to avoid reloading the last build gratuitously. Compare: https://github.com/jenkinsci/jenkins/compare/e12e40adc6c2...b6b7bfd27c9b This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22681) Last build of project reloaded when project asked for later build
SCM/JIRA link daemon commented on JENKINS-22681 Last build of project reloaded when project asked for later build Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/Run.java http://jenkins-ci.org/commit/jenkins/b55c157813c0f5dc3cb06d0503834d21115aebc9 Log: JENKINS-22681 Additional logging useful for diagnosing certain lazy-loading bugs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-19418) Random HTTP 404 when viewing build details
SCM/JIRA link daemon commented on JENKINS-19418 Random HTTP 404 when viewing build details Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java core/src/test/java/jenkins/model/lazy/AbstractLazyLoadRunMapTest.java core/src/test/java/jenkins/model/lazy/FakeMap.java http://jenkins-ci.org/commit/jenkins/b6b7bfd27c9b5551fde04416ee9b7b5faf16ad99 Log: FIXED JENKINS-22681 Fix of JENKINS-19418 should have used getById, not load, to avoid reloading the last build gratuitously. Compare: https://github.com/jenkinsci/jenkins/compare/e12e40adc6c2...b6b7bfd27c9b This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [promoted-builds] (JENKINS-16209) Promoted builds plugin can't promote a build earlier than an existing promoted build
Jamey Graham commented on JENKINS-16209 Promoted builds plugin cant promote a build earlier than an existing promoted build the semantics of the permalink seems off. The behavior of the permalink is "latest build that has been promoted" vs. the specified "latest promoted build" (even the promotion status page shows that the older build is the latest promoted). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [git-client] (JENKINS-19593) git HTTP request failed in Jenkins
Everard Brown reopened JENKINS-19593 git HTTP request failed in Jenkins This problem still exists as originally described. CentOS: 5.10 git: 1.7.1 Jenkins: 1.532.3 Git Plugin: 2.2.1 Git Client Plugin: 1.8.0 No proxy https connection with self-signed cert When using git via CLI, "git ls-remote -h https://git.abc.com/git/repos/abc.git HEAD" on the jenkins server it works with no issue. Change By: Everard Brown (19/Apr/14 12:08 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22681) Last build of project reloaded when project asked for later build
dogfood commented on JENKINS-22681 Last build of project reloaded when project asked for later build Integrated in jenkins_main_trunk #3322 JENKINS-22681 Additional logging useful for diagnosing certain lazy-loading bugs. (Revision b55c157813c0f5dc3cb06d0503834d21115aebc9) FIXED JENKINS-22681 Fix of JENKINS-19418 should have used getById, not load, to avoid reloading the last build gratuitously. (Revision b6b7bfd27c9b5551fde04416ee9b7b5faf16ad99) Result = SUCCESS Jesse Glick : b55c157813c0f5dc3cb06d0503834d21115aebc9 Files : core/src/main/java/hudson/model/Run.java Jesse Glick : b6b7bfd27c9b5551fde04416ee9b7b5faf16ad99 Files : core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java core/src/test/java/jenkins/model/lazy/AbstractLazyLoadRunMapTest.java core/src/test/java/jenkins/model/lazy/FakeMap.java changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [git-client] (JENKINS-19593) git HTTP request failed in Jenkins
Everard Brown edited a comment on JENKINS-19593 git HTTP request failed in Jenkins This problem still exists as originally described. CentOS: 6.5 git: 1.7.1 Jenkins: 1.532.3 Git Plugin: 2.2.1 Git Client Plugin: 1.8.0 No proxy https connection with self-signed cert When using git via CLI, "git ls-remote -h https://git.abc.com/git/repos/abc.git HEAD" on the jenkins server it works with no issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22682) HTTP request failed
Everard Brown created JENKINS-22682 HTTP request failed Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git, git-client Created: 19/Apr/14 12:37 AM Description: No proxy https connection with self-signed cert When using git via CLI, "git ls-remote -h https://git.abc.com/git/repos/abc.git HEAD" on the jenkins server it works with no issue but when adding the repository in the project configuration, we see the following: Failed to connect to repository : Command "ls-remote -h https://git.abc.com/git/repos/abc.git HEAD" returned status code 128: stdout: stderr: error: while accessing https://git.abc.com/git/repos/abc.git/info/refs fatal: HTTP request failed Environment: CentOS: 6.5 git: 1.7.1 Jenkins: 1.532.3 Git Plugin: 2.2.1 Git Client Plugin: 1.8.0 Project: Jenkins Priority: Blocker Reporter: Everard Brown This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [git-client] (JENKINS-19593) git HTTP request failed in Jenkins
Everard Brown resolved JENKINS-19593 as Not A Defect git HTTP request failed in Jenkins Inadvertently re-opened this issue but our issue is not exactly the same. Change By: Everard Brown (19/Apr/14 12:38 AM) Status: Reopened Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-19593) git HTTP request failed in Jenkins
Everard Brown edited a comment on JENKINS-19593 git HTTP request failed 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.
[JIRA] [git] (JENKINS-22682) git HTTP request failed in Jenkins
Everard Brown updated JENKINS-22682 git HTTP request failed in Jenkins Change By: Everard Brown (19/Apr/14 12:39 AM) Summary: git HTTPrequestfailed inJenkins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21882) v1.551 + GitHub OAuth == broken api token access
Michael Glass commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access Peter Downs 0.15-snapshot solves some peoples' issues but not everyones' This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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.
