[JIRA] [core] (JENKINS-24765) Jenkins doesn't escape commas when creating job URLs
Yaniv Kaul commented on JENKINS-24765 Jenkins doesn't escape commas when creating job URLs Create a matrix job, with these axis: axis 1: A B axis 2: -m rc,d -m e1,e2 This will result in the following link - which will not escape rc,d (the comma!) when trying to access the job URL. BTW, a similar issue we have just found is inability to create a workspace with the '@' character - although it's allowed in the matrix! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [radiatorview] (JENKINS-23096) radiatorviewplugin has incorrect links for jobs in folders
Baptiste Mathus updated JENKINS-23096 radiatorviewplugin has incorrect links for jobs in folders Change By: Baptiste Mathus (21/Sep/14 6:32 AM) Component/s: radiatorview This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [dependency-check-jenkins] (JENKINS-21762) OWASP DependencyChecker cve.2.9.h2.db still in use after successful build
Steve Springett commented on JENKINS-21762 OWASP DependencyChecker cve.2.9.h2.db still in use after successful build Michael, FILE_LOCK=SERIALIZED is enabled in the plugin by default and cannot be changed. What do you mean a 'hung' thread? DC will update it's NIST database every week or so and can appear it's doing nothing - but it logs to the jenkins log - not the console. You might want to try using a shared database - rather than one located in the project workspace. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [copyartifact] (JENKINS-24626) Parameter values of build selector change when upgrading CopyArtifact
ikedam started work on JENKINS-24626 Parameter values of build selector change when upgrading CopyArtifact Change By: ikedam (21/Sep/14 3:56 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-24626) Parameter values of build selector change when upgrading CopyArtifact
ikedam updated JENKINS-24626 Parameter values of build selector change when upgrading CopyArtifact Change By: ikedam (21/Sep/14 3:56 AM) Priority: Blocker Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-24626) Parameter values of build selector change when upgrading CopyArtifact
ikedam commented on JENKINS-24626 Parameter values of build selector change when upgrading CopyArtifact https://github.com/jenkinsci/copyartifact-plugin/pull/44 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-19844) Maven agent socket bind too inflexible (allow Jenkins in virtualized environment)
Oliver Doepner reopened JENKINS-19844 Maven agent socket bind too inflexible (allow Jenkins in virtualized environment) This issue was closed by mistake. The fix mentioned in the comments is for JENKINS-19884 "Improve test failure summary appearance" and has nothing to do with this issue here : JENKINS-19844 "Maven agent socket bind too inflexible" Probably someone got the similar issue numbers (19884 and 19844) mixed up. Change By: Oliver Doepner (21/Sep/14 2:53 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] [groovy-postbuild] (JENKINS-14154) Groovy script can not resolve import classes like hudson.scm.SubversionSCM
ikedam assigned JENKINS-14154 to ikedam Groovy script can not resolve import classes like hudson.scm.SubversionSCM Change By: ikedam (21/Sep/14 2:03 AM) Assignee: wolfs ikedam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-postbuild] (JENKINS-14154) Groovy script can not resolve import classes like hudson.scm.SubversionSCM
ikedam started work on JENKINS-14154 Groovy script can not resolve import classes like hudson.scm.SubversionSCM Change By: ikedam (21/Sep/14 2:03 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-postbuild] (JENKINS-14154) Groovy script can not resolve import classes like hudson.scm.SubversionSCM
ikedam commented on JENKINS-14154 Groovy script can not resolve import classes like hudson.scm.SubversionSCM https://github.com/jenkinsci/groovy-postbuild-plugin/pull/18 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [script-security] (JENKINS-24650) Add syntax highlighting like the Scriptler and Groovy plugin have
ikedam updated JENKINS-24650 Add syntax highlighting like the Scriptler and Groovy plugin have Now this is an issue for script-security as textareas of scripts are controlled by script-security since groovy-postbuild 2.0. Change By: ikedam (21/Sep/14 1:51 AM) Assignee: wolfs Jesse Glick Component/s: script-security Component/s: groovy-postbuild This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
sharon xia commented on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported The test is done on 1.565.2. I will do another test to run it on a previous 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] [script-security] (JENKINS-15210) Add variable resolution to "additional groovy class path"
ikedam updated JENKINS-15210 Add variable resolution to "additional groovy class path" Changed component to script-security plugin as the classpaths resolution is done by Script Security plugin since groovy-postbuild 2.0 . I think this feature assumes to use libraries generated in builds. It's not generally secure, and should not be allowed. It should be run with another JVM instance, that is, you should launch new java processes. @jglick Can you have a look at this? I think this can be closed with "Won't Fix". Change By: ikedam (21/Sep/14 1:05 AM) Assignee: wolfs Jesse Glick Component/s: script-security Component/s: groovy-postbuild This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [groovy-postbuild] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
ikedam resolved JENKINS-16863 as Duplicate After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable The same root cause to JENKINS-14154. Change By: ikedam (21/Sep/14 1:06 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
sharon xia commented on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported Yes correct. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [groovy-postbuild] (JENKINS-15212) More flexible and effective security for Groovy Postbuild
SCM/JIRA link daemon commented on JENKINS-15212 More flexible and effective security for Groovy Postbuild Code changed in jenkins User: ikedam Path: pom.xml http://jenkins-ci.org/commit/groovy-postbuild-plugin/bd8493379c7979187eecf99da32ffefe23c589b7 Log: JENKINS-15212 Added compatibleSinceVersion to display warnings that upgrading from 1.X requires reconfiguration. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [groovy-postbuild] (JENKINS-15212) More flexible and effective security for Groovy Postbuild
SCM/JIRA link daemon commented on JENKINS-15212 More flexible and effective security for Groovy Postbuild Code changed in jenkins User: ikedam Path: src/main/java/org/jvnet/hudson/plugins/groovypostbuild/GroovyPostbuildRecorder.java http://jenkins-ci.org/commit/groovy-postbuild-plugin/6846753d9d994c2c9a0fc654b9ffbce6c2991d6f Log: JENKINS-15212 removeBadge(s) whitelisted. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [groovy-postbuild] (JENKINS-24694) Whitelisted method to test whether matrix parent build
SCM/JIRA link daemon commented on JENKINS-24694 Whitelisted method to test whether matrix parent build Code changed in jenkins User: ikedam Path: src/main/java/org/jvnet/hudson/plugins/groovypostbuild/GroovyPostbuildRecorder.java src/main/resources/org/jvnet/hudson/plugins/groovypostbuild/GroovyPostbuildRecorder/help-runForMatrixParent.html src/test/java/org/jvnet/hudson/plugins/groovypostbuild/GroovyPostbuildRecorderTest.java http://jenkins-ci.org/commit/groovy-postbuild-plugin/23412b45281d0409f754a00ab0b3d2023486a1a2 Log: [FIXED JENKINS-24694] Added manager.buildIsA to test a type of build. mainly used for test whether the build is a matrix parent. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [groovy-postbuild] (JENKINS-24694) Whitelisted method to test whether matrix parent build
SCM/JIRA link daemon resolved JENKINS-24694 as Fixed Whitelisted method to test whether matrix parent build Change By: SCM/JIRA link daemon (21/Sep/14 12:03 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] [groovy-postbuild] (JENKINS-24694) Whitelisted method to test whether matrix parent build
SCM/JIRA link daemon commented on JENKINS-24694 Whitelisted method to test whether matrix parent build Code changed in jenkins User: ikedam Path: src/main/java/org/jvnet/hudson/plugins/groovypostbuild/GroovyPostbuildRecorder.java src/main/resources/org/jvnet/hudson/plugins/groovypostbuild/GroovyPostbuildRecorder/help-runForMatrixParent.html src/test/java/org/jvnet/hudson/plugins/groovypostbuild/GroovyPostbuildRecorderTest.java http://jenkins-ci.org/commit/groovy-postbuild-plugin/f145cae857d26657426a4a540ad20b32748345a0 Log: Merge pull request #15 from ikedam/feature/JENKINS-24694_matrixtestmethod JENKINS-24694 Whitelisted method to test whether a matrix parent build Compare: https://github.com/jenkinsci/groovy-postbuild-plugin/compare/00a39a3f1414...f145cae857d2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24785) BUILD_CAUSE useless in multi-configuration jobs
tsondergaard commented on JENKINS-24785 BUILD_CAUSE useless in multi-configuration jobs I have made a commit here to try to fix this problem. The idea is to introduce a ROOT_BUILD_CAUSE variable that expands Cause.UpstreamCause to it's root causes. https://github.com/tsondergaard/envinject-plugin/commit/842b5a2e0eb7a04da34d5920dbd304a02dac0dfb It doesn't quite compile because Cause.UpstreamCause.getUpstreamCauses() cannot be found by the compiler. I assume it is because this function is not marked with @Exported(visibility=3), but I don't know enough about Java or the jenkins code base to be sure. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-19222) EnvInject undefines NODE_NAME environment variable on master
Daniel Beck
updated JENKINS-19222
EnvInject undefines NODE_NAME environment variable on master
Still occurs on 1.580 with Envinject 1.90; while the plugin is disabled, the environment variable NODE_NAME is set.
Updated issue title to match recent comments' information.
Change By:
Daniel Beck
(20/Sep/14 10:17 PM)
Summary:
Update to 1.527 breaks ${
EnvInject undefines
NODE_NAME
} as node parameter
environment variable
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] [envinject] (JENKINS-24785) BUILD_CAUSE useless in multi-configuration jobs
Daniel Beck commented on JENKINS-24785 BUILD_CAUSE useless in multi-configuration jobs I confirm this issue still occurs on Jenkins 1.580 with Env-Inject 1.90 and Matrix Project 1.3. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24785) BUILD_CAUSE useless in multi-configuration jobs
tsondergaard created JENKINS-24785 BUILD_CAUSE useless in multi-configuration jobs Issue Type: Bug Assignee: Gregory Boissinot Components: envinject Created: 20/Sep/14 7:57 PM Description: BUILD_CAUSE is always set to UPSTREAMTRIGGER in the slaves/children of of multi-configuration jobs, which is not very useful. Environment: Jenkins version 1.509.4, envinject version 1.85 Project: Jenkins Priority: Major Reporter: tsondergaard This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [radargun] (JENKINS-24784) Build doesn't terminate properly when interrupted
vjuranek created JENKINS-24784 Build doesn't terminate properly when interrupted Issue Type: Bug Assignee: vjuranek Components: radargun Created: 20/Sep/14 7:50 PM Description: When the build is interrupted, in console it show ERROR: null, all actions (master and slaves) show to be in progress and probably most important it that master as well as slaves keep running. Project: Jenkins Priority: Major Reporter: vjuranek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24763) Long running OldDataMonitor.doDiscard() results in thread starvation
Jesse Glick updated JENKINS-24763 Long running OldDataMonitor.doDiscard() results in thread starvation Change By: Jesse Glick (20/Sep/14 7:30 PM) Labels: lock performance threads This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24763) Long running OldDataMonitor.doDiscard() results in thread starvation
Jesse Glick commented on JENKINS-24763 Long running OldDataMonitor.doDiscard() results in thread starvation 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] [git] (JENKINS-22601) Provide option for -f / force in "git push" (after tagging)
Mark Waite assigned JENKINS-22601 to Mark Waite Provide option for -f / force in "git push" (after tagging) Change By: Mark Waite (20/Sep/14 6:47 PM) Assignee: Nicolas De Loof Mark Waite This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22601) Provide option for -f / force in "git push" (after tagging)
Mark Waite commented on JENKINS-22601 Provide option for -f / force in "git push" (after tagging) Are the changes included in git plugin 2.2.6 sufficient to meet this case as well? The git publisher now takes an optional setting to force push. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24772) git polling performs deprecated call to Run.getEnvironment at hudson.plugins.git.GitSCM.getParamExpandedRepos(GitSCM.java:355)
Mark Waite resolved JENKINS-24772 as Fixed git polling performs deprecated call to Run.getEnvironment at hudson.plugins.git.GitSCM.getParamExpandedRepos(GitSCM.java:355) Fixed in git plugin 2.2.6, released 20 Sep 2014 Change By: Mark Waite (20/Sep/14 6:45 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] [git] (JENKINS-24516) git polling results exception because ssh is not found
Mark Waite closed JENKINS-24516 as Fixed git polling results exception because ssh is not found Fixed in git plugin 2.2.6, released 20 Sep 2014 Change By: Mark Waite (20/Sep/14 6:44 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-19029) Add support for gitlist in git scm browser
Mark Waite closed JENKINS-19029 as Fixed Add support for gitlist in git scm browser Fixed in git plugin 2.2.6, released 20 Sep 2014 Change By: Mark Waite (20/Sep/14 6:44 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24467) ssh not found by git because PATH has been unexpectedly changed
Mark Waite closed JENKINS-24467 as Fixed ssh not found by git because PATH has been unexpectedly changed Fixed in git plugin 2.2.6, released 20 Sep 2014 Change By: Mark Waite (20/Sep/14 6:45 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24772) git polling performs deprecated call to Run.getEnvironment at hudson.plugins.git.GitSCM.getParamExpandedRepos(GitSCM.java:355)
Mark Waite closed JENKINS-24772 as Fixed git polling performs deprecated call to Run.getEnvironment at hudson.plugins.git.GitSCM.getParamExpandedRepos(GitSCM.java:355) Change By: Mark Waite (20/Sep/14 6:45 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24082) Be able to force push for branch on git publisher
Mark Waite closed JENKINS-24082 as Fixed Be able to force push for branch on git publisher Fixed in git plugin 2.2.6, released 20 Sep 2014 Change By: Mark Waite (20/Sep/14 6:43 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core] (JENKINS-13056) Obtain reference build from SCM/Trigger
Roland Schulz commented on JENKINS-13056 Obtain reference build from SCM/Trigger Now that the API for querying the parent in SCM is available is it possible to make progress on this issue? I have bought your Inca Trails game to show support . Sebastian, your use case sounds different. For us the only logical way to get the reference build is to query the SCM (because of post submit code-review). You should open a separate 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] [core] (JENKINS-11543) UTF-8 encoding issue of build parameters as soon as including File parameter
Daniel Beck resolved JENKINS-11543 as Fixed UTF-8 encoding issue of build parameters as soon as including File parameter Fix scheduled for 1.582. Change By: Daniel Beck (20/Sep/14 6:39 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-12379) Archive the artifacts should allow specifying the target artifacts path
Daniel Beck updated JENKINS-12379 Archive the artifacts should allow specifying the target artifacts path Would the solution in the attached screenshots work for everyone? It essentially splits pattern and user-defined common prefix in two. It's not as powerful as the TeamCity approach, but should cover almost all use cases without having to resort to shell scripts. Change By: Daniel Beck (20/Sep/14 5:50 PM) Attachment: Screen Shot 2014-09-20 at 19.44.35.png Attachment: Screen Shot 2014-09-20 at 19.45.28.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [copyartifact] (JENKINS-12379) Archive the artifacts should allow specifying the target artifacts path
Daniel Beck edited a comment on JENKINS-12379 Archive the artifacts should allow specifying the target artifacts path Would the proposed solution in the attached screenshots work for everyone? It essentially splits pattern and user-defined common prefix in two. It's not as powerful as the TeamCity approach, but should cover almost all use cases without having to resort to shell scripts. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [copyartifact] (JENKINS-12379) Archive the artifacts should allow specifying the target artifacts path
Daniel Beck assigned JENKINS-12379 to Daniel Beck Archive the artifacts should allow specifying the target artifacts path Change By: Daniel Beck (20/Sep/14 5:53 PM) Assignee: 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] [findbugs] (JENKINS-24743) Findbug and PMD are broken in Jenkins 1.565.2
Ulli Hafner commented on JENKINS-24743 Findbug and PMD are broken in Jenkins 1.565.2 Which versions did you install (findbugs, pmd, analysis-core)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-13554) Re: Matrix jobs does not automatically remove old artifacts for configurations
Daniel Beck commented on JENKINS-13554 Re: Matrix jobs does not automatically remove old artifacts for configurations Note that artifacts get deleted properly if you explicitly set that option in the build discarder. You may need to keep one more top-level build than has artifacts. I tested build discarding with keeping 3 builds with artifacts, and 5 builds in general. After build 6 finished, only 4-6 had artifacts, top level builds 2-6 existed, and per-configuration builds 1-6 existed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [credentials] (JENKINS-24662) New username/password credentials screen rendering issue
Daniel Beck edited a comment on JENKINS-24662 New username/password credentials screen rendering issue I can reproduce this every time on the form mentioned. In my case, Username with Password is the default credentials type, and changing it fixes the form (after first moving the button so it obscures part of the form for a moment). Jenkins 1.581-SNAPSHOT running regularly (no hpi:run) Credentials Plugin 1.16.1 CentOS 6 server OS X Firefox 32.0.2 client This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-24662) New username/password credentials screen rendering issue
Daniel Beck updated JENKINS-24662 New username/password credentials screen rendering issue Change By: Daniel Beck (20/Sep/14 4:38 PM) Attachment: Screen Shot 2014-09-20 at 18.35.46.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [credentials] (JENKINS-24662) New username/password credentials screen rendering issue
Daniel Beck reopened JENKINS-24662 New username/password credentials screen rendering issue I can reproduce this every time on the form mentioned. Jenkins 1.581-SNAPSHOT running regularly (no hpi:run) Credentials Plugin 1.16.1 CentOS 6 server OS X Firefox 32.0.2 client Change By: Daniel Beck (20/Sep/14 4:34 PM) Resolution: Cannot Reproduce 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] [matrix] (JENKINS-13554) Re: Matrix jobs does not automatically remove old artifacts for configurations
Joshua Kugler commented on JENKINS-13554 Re: Matrix jobs does not automatically remove old artifacts for configurations The behavior we were experiencing was that artifacts were not properly deleted when jobs were "expired." This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24763) Long running OldDataMonitor.doDiscard() results in thread starvation
recampbell updated JENKINS-24763 Long running OldDataMonitor.doDiscard() results in thread starvation I see Jesse's point about JobConfigHistorySaveableListener – it's certainly the root cause. Nevertheless, OldDataMonitor could be more robust by reducing the scope of it's lock – to better handle other poorly performing SaveableListeners. So I'll change this to an Improvement if that suits you. Change By: recampbell (20/Sep/14 4:20 PM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-24662) New username/password credentials screen rendering issue
recampbell resolved JENKINS-24662 as Cannot Reproduce New username/password credentials screen rendering issue It seems this only reproduces when using hpi:run Change By: recampbell (20/Sep/14 4:11 PM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24718) Git plugin should populate 'scmName' property in api output
Will Saxon commented on JENKINS-24718 Git plugin should populate 'scmName' property in api output The description on this issue is incorrect. The scmName is populated, it just doesn't get returned with the particular Run being queried. If I set an scmName when I set up the job, the first build run has the scmName, but if I change the scmName and run the job again, subsequent runs keep the original scmName. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [radiatorview] (JENKINS-11573) Radiator view plugin does not render correctly in all browsers
Baptiste Mathus resolved JENKINS-11573 as Won't Fix Radiator view plugin does not render correctly in all browsers See https://wiki.jenkins-ci.org/display/JENKINS/Browser+Compatibility+Matrix for general rules about browser support. If you need that, please consider filing a pull request. Cheers Change By: Baptiste Mathus (20/Sep/14 2:43 PM) Status: Open Resolved Assignee: howama Baptiste Mathus Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [radiatorview] (JENKINS-9132) Adjustable refresh rate
Baptiste Mathus commented on JENKINS-9132 Adjustable refresh rate I don't think this is likely to happen since the radiator view is actually an extended view, reusing standard Jenkins mechanism. That being said, if you can give it a try and propose a pull request, please do. I'll have a look at it. Cheers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [radiatorviewplugin] (JENKINS-24104) Feedback views broken with Jenkins v1.572, v1.573, v1.574. Versions before are OK.
Baptiste Mathus resolved JENKINS-24104 as Duplicate Feedback views broken with Jenkins v1.572, v1.573, v1.574. Versions before are OK. Duplicate of JENKINS-23924 Change By: Baptiste Mathus (20/Sep/14 2:33 PM) Status: Open Resolved Assignee: Baptiste Mathus 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] [radiatorview] (JENKINS-23924) New div layout breaks Radiator view
Baptiste Mathus updated JENKINS-23924 New div layout breaks Radiator view Change By: Baptiste Mathus (20/Sep/14 1:29 PM) Attachment: 2e05b1d1907b8c3368046499f11b3165.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [radiatorview] (JENKINS-23924) New div layout breaks Radiator view
Baptiste Mathus updated JENKINS-23924 New div layout breaks Radiator view Change By: Baptiste Mathus (20/Sep/14 1:28 PM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [radiatorview] (JENKINS-23306) Unstable jobs are shown with the same size as stable ones
Baptiste Mathus assigned JENKINS-23306 to Baptiste Mathus Unstable jobs are shown with the same size as stable ones Change By: Baptiste Mathus (20/Sep/14 1:24 PM) Assignee: howama Baptiste Mathus This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [radiatorview] (JENKINS-23306) Unstable jobs are shown with the same size as stable ones
Baptiste Mathus resolved JENKINS-23306 as Fixed Unstable jobs are shown with the same size as stable ones Fixed with 186f58de0c9308b645de8afd639b046515b1b958 merge. Change By: Baptiste Mathus (20/Sep/14 1: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] [radiatorview] (JENKINS-10587) Add option to remove Culprits from Radiator View
Baptiste Mathus assigned JENKINS-10587 to Baptiste Mathus Add option to remove Culprits from Radiator View Change By: Baptiste Mathus (20/Sep/14 1:26 PM) Assignee: howama Baptiste Mathus This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [radiatorview] (JENKINS-23306) Unstable jobs are shown with the same size as stable ones
SCM/JIRA link daemon commented on JENKINS-23306 Unstable jobs are shown with the same size as stable ones Code changed in jenkins User: Baptiste Mathus Path: src/main/java/hudson/model/ProjectViewEntry.java http://jenkins-ci.org/commit/radiatorview-plugin/cafd297384a5cc6afb5b0497783d4ff91faf8505 Log: If no failing jobs, consider unstable as failures. Fixes JENKINS-23306 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [radiatorview] (JENKINS-23306) Unstable jobs are shown with the same size as stable ones
SCM/JIRA link daemon commented on JENKINS-23306 Unstable jobs are shown with the same size as stable ones Code changed in jenkins User: Baptiste Mathus Path: src/main/java/hudson/model/ProjectViewEntry.java http://jenkins-ci.org/commit/radiatorview-plugin/186f58de0c9308b645de8afd639b046515b1b958 Log: Merge branch 'JENKINS-23306' Compare: https://github.com/jenkinsci/radiatorview-plugin/compare/56bad2b56319...186f58de0c93 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24745) hundson failed to create symlink cause incorrect function
Daniel Beck commented on JENKINS-24745 hundson failed to create symlink cause incorrect function Another possible option would be to try setting the system property hudson.Util.noSymLink to true. But getting rid of FAT is a good idea anyway... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Magnus Sandberg commented on JENKINS-22294 Priority is not used in the scheduling Sorry if the way to configure this is not clear. Please suggest changes to the wiki. In any case increasing the logging will help in most cases as the detailed log will tell you what Strategies are tried and what one is finally matched and 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] [matrix] (JENKINS-13554) Re: Matrix jobs does not automatically remove old artifacts for configurations
Daniel Beck commented on JENKINS-13554 Re: Matrix jobs does not automatically remove old artifacts for configurations Issue confirmed on Jenkins 1.580 with Matrix Project Plugin 1.3. Of course, the problem is that the Matrix Project type distinguishes between regular "Delete Build" and "Delete this build and all configurations in this build", so it's not straightforward to say what the correct behavior should be. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [job-dsl-plugin] (JENKINS-24146) rbenv support for job dsl plugin
Daniel Spilker updated JENKINS-24146 rbenv support for job dsl plugin Pull request: https://github.com/jenkinsci/job-dsl-plugin/pull/267 Change By: Daniel Spilker (20/Sep/14 9:22 AM) Assignee: Daniel Spilker Joseph Hughes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [job-dsl-plugin] (JENKINS-24420) Add job-dsl-plugin support for delivery-pipeline-plugin
Daniel Spilker commented on JENKINS-24420 Add job-dsl-plugin support for delivery-pipeline-plugin Pull request is open for review: https://github.com/jenkinsci/job-dsl-plugin/pull/283 Will be released in 1.26. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24776) Poll permissions not recognized after upgrade
Alexander Obuhovich commented on JENKINS-24776 Poll permissions not recognized after upgrade Thanks for figuring figuring that out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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.
