[JIRA] [deploy-plugin] (JENKINS-28105) deployment failed
RamyaSree Muralitharan started work on JENKINS-28105 deployment failed Change By: RamyaSree Muralitharan (27/Apr/15 8:34 AM) 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] [matrix-project-plugin] (JENKINS-28107) Matrix parent should take an executor slot until the point where children are triggered
Simon Richter created JENKINS-28107 Matrix parent should take an executor slot until the point where children are triggered Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: matrix-project-plugin Created: 27/Apr/15 10:27 AM Description: When lots of matrix jobs are queued because a slave has been unavailable, all of these are started at the same time because these do not take up executor slots. As the parent job still accesses the VCS, all of these accesses happen in parallel then and may starve each other for resources. It would be great if the job would take an executor slot, and relinquish it when it starts triggering the child jobs. Project: Jenkins Priority: Minor Reporter: Simon Richter This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-28109) Local artifact cache on slaves
Simon Richter created JENKINS-28109 Local artifact cache on slaves Issue Type: Improvement Assignee: Unassigned Components: copyartifact-plugin, core Created: 27/Apr/15 10:49 AM Description: I have a VCS triggered build job that consumes about 150 MB of artifacts which seldom change. It would be great if artifacts could be cached on the slave nodes to reduce the network load and build time. Project: Jenkins Labels: artifact performance Priority: Minor Reporter: Simon Richter This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gitlab-hook-plugin] (JENKINS-24230) allow build projects to be specified
Javier Palacios closed JENKINS-24230 as Fixed allow build projects to be specified Change By: Javier Palacios (27/Apr/15 8:54 AM) 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] [maven-plugin] (JENKINS-28070) Maven 3.3.1 build fail on Unix if Maven is the default installation
Laurent TOURREAU commented on JENKINS-28070 Maven 3.3.1 build fail on Unix if Maven is the default installation The linked issue concerns Windows not Unix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-project-plugin] (JENKINS-23902) Matrix parent takes executor slot and blocks children
Simon Richter commented on JENKINS-23902 Matrix parent takes executor slot and blocks children I saw that happen when the slave node the job should have run on was down at that time and the matrix job was queued. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [swarm-plugin] (JENKINS-24149) LogConfigurationException due to conflicting commons-logging versions
SCM/JIRA link daemon commented on JENKINS-24149 LogConfigurationException due to conflicting commons-logging versions Code changed in jenkins User: Peter Jönsson Path: client/pom.xml http://jenkins-ci.org/commit/swarm-plugin/6aaf9453d44a46db3600485cbaba73288c4c960e Log: Merge pull request #24 from oberthur/master JENKINS-24149 - LogConfigurationException Compare: https://github.com/jenkinsci/swarm-plugin/compare/704dd97a434b...6aaf9453d44a This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [swarm-plugin] (JENKINS-24149) LogConfigurationException due to conflicting commons-logging versions
SCM/JIRA link daemon commented on JENKINS-24149 LogConfigurationException due to conflicting commons-logging versions Code changed in jenkins User: Dawid Malinowski Path: client/pom.xml http://jenkins-ci.org/commit/swarm-plugin/849e550491366260cc7f8e6b831c7a51155f6982 Log: JENKINS-24149 - LogConfigurationException due to conflicting commons-logging versions This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mongodb-document-upload-plugin] (JENKINS-28108) Document cannot be updated if document with same _id already exist.
Kari Sivonen created JENKINS-28108 Document cannot be updated if document with same _id already exist. Issue Type: Improvement Assignee: Unassigned Components: mongodb-document-upload-plugin Created: 27/Apr/15 10:46 AM Description: If json document have same _id than mongoDB already, plugin not update that. For me plugin is not usable if documents cannot be updated. Project: Jenkins Priority: Major Reporter: Kari Sivonen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28086) JNLP slave connection does not consider java non-proxy settings (http.nonProxyHosts)
Horst Hermanns commented on JENKINS-28086 JNLP slave connection does not consider java non-proxy settings (http.nonProxyHosts) Yes, that is be a possible workaround together with unsetting the parameters before launching the JNLP session. From my point of view it would be better or more correct to consider non-proxy setting in slave.jar. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28106) $JENKINS_HOME/logs/slaves/$SLAVE_NAME not deleted after slave is removed
Oliver Gondža created JENKINS-28106 $JENKINS_HOME/logs/slaves/$SLAVE_NAME not deleted after slave is removed Issue Type: Bug Assignee: Oliver Gondža Components: core Created: 27/Apr/15 10:13 AM Description: JClouds plugin leaves all these directories behind after the temporary slaves are removed. Project: Jenkins Priority: Minor Reporter: Oliver Gondža This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-4152) Incremental builds should include previous builds' modules if previous build failed
Tim Drury commented on JENKINS-4152 Incremental builds should include previous builds modules if previous build failed I see this behavior happening in Jenkins 1.596.1. A job is configured for incremental build. Module A fails due to a broken unit test. A change to module B is made. The next build builds only module B so the build goes green even though module A's unit test is still broken. Unstable and failed modules should be included in the next incremental build (and subsequent builds until the module is stable). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28111) JNLP slave JVM Options are inconsistently applied
Daniel Beck commented on JENKINS-28111 JNLP slave JVM Options are inconsistently applied stephenconnolly Should this be assigned to you? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28111) JNLP slave JVM Options are inconsistently applied
SCM/JIRA link daemon commented on JENKINS-28111 JNLP slave JVM Options are inconsistently applied Code changed in jenkins User: Stephen Connolly Path: changelog.html http://jenkins-ci.org/commit/jenkins/9c9049eb4da6145261d6b5fda6ed57dd676bf108 Log: Noting merge of JENKINS-28111 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28120) Jenkins core to require Java7
SCM/JIRA link daemon commented on JENKINS-28120 Jenkins core to require Java7 Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/resources/hudson/slaves/SlaveComputer/slave-agent.jnlp.jelly pom.xml http://jenkins-ci.org/commit/jenkins/2826ea3185f5ca1df02ab54d465a14308ecffe05 Log: JENKINS-28120 As the first step of Java7 migration, ship Java7 class files without requiring Java7 runtime. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28112) JNLP file requests Java 1.5+ despite minimum version of Java being 1.6+
Daniel Beck updated JENKINS-28112 JNLP file requests Java 1.5+ despite minimum version of Java being 1.6+ Change By: Daniel Beck (27/Apr/15 9:01 PM) Assignee: stephenconnolly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28115) Division by zero in Executor.getProgress
Daniel Beck updated JENKINS-28115 Division by zero in Executor.getProgress Change By: Daniel Beck (27/Apr/15 9:02 PM) Assignee: stephenconnolly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28111) JNLP slave JVM Options are inconsistently applied
SCM/JIRA link daemon commented on JENKINS-28111 JNLP slave JVM Options are inconsistently applied Code changed in jenkins User: Stephen Connolly Path: core/src/main/resources/hudson/slaves/JNLPLauncher/main.jelly http://jenkins-ci.org/commit/jenkins/ce94434b164d1ac74132cecdc6f123787decbf48 Log: Merge pull request #1676 from stephenc/jenkins-28111 FIXED JENKINS-28111 JNLP slave JVM Options are inconsistently applied Compare: https://github.com/jenkinsci/jenkins/compare/5b4ed2dae2dd...ce94434b164d This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28115) Division by zero in Executor.getProgress
SCM/JIRA link daemon commented on JENKINS-28115 Division by zero in Executor.getProgress Code changed in jenkins User: Stephen Connolly Path: changelog.html http://jenkins-ci.org/commit/jenkins/5b4ed2dae2dd0122e65641e01c141f76ac5fd0b8 Log: Noting merge of JENKINS-28115 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-project-plugin] (JENKINS-28107) Matrix parent should take an executor slot until the point where children are triggered
Daniel Beck commented on JENKINS-28107 Matrix parent should take an executor slot until the point where children are triggered Possible workaround: Don't restrict the parent build to a slave? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [performance-plugin] (JENKINS-28110) NoStaplerConstructorException for Jenkins 1.610
Serge Zukov commented on JENKINS-28110 NoStaplerConstructorException for Jenkins 1.610 to Daniel: yes, 1.611 is also affected. Sorry, I've missed the version number in the title. In my case project uses both copy and performance plugins. I'm confirming that rolling back to 1.609 resolves the 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-28120) Jenkins core to require Java7
Kohsuke Kawaguchi created JENKINS-28120 Jenkins core to require Java7 Issue Type: Task Assignee: Kohsuke Kawaguchi Components: core Created: 27/Apr/15 9:47 PM Description: This ticket tracks the promise made in http://jenkins-ci.org/content/good-bye-java6 that we are bumping up core requirements from Java6 to Java7. Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-28110) NoStaplerConstructorException for Jenkins 1.610
Jesse Glick assigned JENKINS-28110 to Jesse Glick NoStaplerConstructorException for Jenkins 1.610 Change By: Jesse Glick (27/Apr/15 9:48 PM) Assignee: ManuelCarrasco JesseGlick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28115) Division by zero in Executor.getProgress
SCM/JIRA link daemon commented on JENKINS-28115 Division by zero in Executor.getProgress Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/model/Executor.java http://jenkins-ci.org/commit/jenkins/a574cd9574f7ce1386816c0cc10560a341861b3c Log: Merge pull request #1678 from stephenc/jenkins-28115 FIXED JENKINS-28115 Division by zero in Executor.getProgress() Compare: https://github.com/jenkinsci/jenkins/compare/cd8dbedaf0f8...a574cd9574f7 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28115) Division by zero in Executor.getProgress
SCM/JIRA link daemon resolved JENKINS-28115 as Fixed Division by zero in Executor.getProgress Change By: SCM/JIRA link daemon (27/Apr/15 8:36 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-28115) Division by zero in Executor.getProgress
SCM/JIRA link daemon commented on JENKINS-28115 Division by zero in Executor.getProgress Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/model/Executor.java http://jenkins-ci.org/commit/jenkins/e685b604d9c48bee2f728c3ecec3303e5c56 Log: FIXED JENKINS-28115 Division by zero in Executor.getProgress() ``` WARNING: Caught exception evaluating: executor.progress in /ajaxExecutors. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException ... at java.lang.Thread.run(Thread.java:744) Caused by: java.lang.ArithmeticException: / by zero at hudson.model.Executor.getProgress(Executor.java:649) ... 154 more ``` This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-combinations-parameter-plugin] (JENKINS-23609) Successful and Failed link in matrix-combinations-parameter do not work
SCM/JIRA link daemon resolved JENKINS-23609 as Fixed Successful and Failed link in matrix-combinations-parameter do not work Change By: SCM/JIRA link daemon (27/Apr/15 9:17 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] [matrix-combinations-parameter-plugin] (JENKINS-23609) Successful and Failed link in matrix-combinations-parameter do not work
SCM/JIRA link daemon commented on JENKINS-23609 Successful and Failed link in matrix-combinations-parameter do not work Code changed in jenkins User: Stephen Connolly Path: src/main/resources/hudson/plugins/matrix_configuration_parameter/MatrixCombinationsParameterDefinition/index.groovy http://jenkins-ci.org/commit/matrix-combinations-plugin/9716d77a77c6ca011c6bf28bca6a26d43056ce60 Log: FIXED JENKINS-23609 "Successful" and "Failed" links do not work Seemed to not actually be providing the run result data to the matrix. Unclear how this could ever have worked This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-parameter-plugin] (JENKINS-23577) Add support for using branches in Git Parameter plugin
Alon Chanukov commented on JENKINS-23577 Add support for using branches in Git Parameter plugin Any update on this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28112) JNLP file requests Java 1.5+ despite minimum version of Java being 1.6+
stephenconnolly started work on JENKINS-28112 JNLP file requests Java 1.5+ despite minimum version of Java being 1.6+ Change By: stephenconnolly (27/Apr/15 9:43 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] [envinject-plugin] (JENKINS-28116) Password injection no longer supplies password
Daniel Beck resolved JENKINS-28116 as Duplicate Password injection no longer supplies password Change By: Daniel Beck (27/Apr/15 9:06 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] [performance-plugin] (JENKINS-28110) NoStaplerConstructorException for Jenkins 1.610
Daniel Beck commented on JENKINS-28110 NoStaplerConstructorException for Jenkins 1.610 Referenced this issue from https://github.com/jenkinsci/jenkins/pull/1563#issuecomment-96775752 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28114) Update to 1.610 causing main Jenkins config page to throw
Daniel Beck commented on JENKINS-28114 Update to 1.610 causing main Jenkins config page to throw Referenced this issue in https://github.com/jenkinsci/jenkins/pull/1563#issuecomment-96742579 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-project-plugin] (JENKINS-27953) Fails to load a matrix project for script-security
Jesse Glick resolved JENKINS-27953 as Duplicate Fails to load a matrix project for script-security That is it. Change By: Jesse Glick (27/Apr/15 9:42 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] [core] (JENKINS-28120) Jenkins core to require Java7
SCM/JIRA link daemon commented on JENKINS-28120 Jenkins core to require Java7 Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/resources/hudson/slaves/SlaveComputer/slave-agent.jnlp.jelly pom.xml http://jenkins-ci.org/commit/jenkins/de8bba40cf593bec5fda197e09f644ae53e207a3 Log: JENKINS-28120 As the first step of Java7 migration, ship Java7 class files without requiring Java7 runtime. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-project-plugin] (JENKINS-23902) Matrix parent takes executor slot and blocks children
Daniel Beck commented on JENKINS-23902 Matrix parent takes executor slot and blocks children There have been fixes to the queue behavior until 1.610. That version or higher would be needed for any follow-up issue to make 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] [matrix-combinations-parameter-plugin] (JENKINS-23609) Successful and Failed link in matrix-combinations-parameter do not work
SCM/JIRA link daemon commented on JENKINS-23609 Successful and Failed link in matrix-combinations-parameter do not work Code changed in jenkins User: Stephen Connolly Path: src/test/java/hudson/plugins/matrix_configuration_parameter/MatrixCombinationsParameterDefinitionTest.java http://jenkins-ci.org/commit/matrix-combinations-plugin/f5c1b0bfd32e57548462bd7588113dd0ba4394e8 Log: JENKINS-23609 Re-enable Successful and Failed link tests Also None link test was actually testing Successful link! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-combinations-parameter-plugin] (JENKINS-23609) Successful and Failed link in matrix-combinations-parameter do not work
SCM/JIRA link daemon commented on JENKINS-23609 Successful and Failed link in matrix-combinations-parameter do not work Code changed in jenkins User: ikedam Path: src/main/resources/hudson/plugins/matrix_configuration_parameter/MatrixCombinationsParameterDefinition/index.groovy src/test/java/hudson/plugins/matrix_configuration_parameter/MatrixCombinationsParameterDefinitionTest.java http://jenkins-ci.org/commit/matrix-combinations-plugin/29dfcb053cb515fa20e5611a2ec638e49f0fc3cd Log: Merge pull request #8 from stephenc/jenkins-23609 FIXED JENKINS-23609 "Successful" and "Failed" links do not work Compare: https://github.com/jenkinsci/matrix-combinations-plugin/compare/b516d49d0a96...29dfcb053cb5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28111) JNLP slave JVM Options are inconsistently applied
SCM/JIRA link daemon resolved JENKINS-28111 as Fixed JNLP slave JVM Options are inconsistently applied Change By: SCM/JIRA link daemon (27/Apr/15 9:40 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28111) JNLP slave JVM Options are inconsistently applied
SCM/JIRA link daemon commented on JENKINS-28111 JNLP slave JVM Options are inconsistently applied Code changed in jenkins User: Stephen Connolly Path: core/src/main/resources/hudson/slaves/JNLPLauncher/main.jelly http://jenkins-ci.org/commit/jenkins/84e485fc5e608bccf080bf46c0e31c43c6bef474 Log: FIXED JENKINS-28111 JNLP slave JVM Options are inconsistently applied This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28093) Plugin Manager gets exception because of FileNotFound nodejs Installer
Jesse Glick assigned JENKINS-28093 to Jesse Glick Plugin Manager gets exception because of FileNotFound nodejs Installer Change By: Jesse Glick (27/Apr/15 9:46 PM) Assignee: JesseGlick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28114) Update to 1.610 causing main Jenkins config page to throw
Jesse Glick assigned JENKINS-28114 to Jesse Glick Update to 1.610 causing main Jenkins config page to throw Change By: Jesse Glick (27/Apr/15 9:47 PM) Assignee: JesseGlick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [scm-sync-configuration-plugin] (JENKINS-15128) Renaming job doesn't work with Git
Dave Cadwallader commented on JENKINS-15128 Renaming job doesnt work with Git Seems not to be fixed. When renaming a job, we get this in the logs and all future SCM syncs fail. This is using the latest v0.0.8: Apr 27, 2015 1:13:20 PM FINE hudson.plugins.scm_sync_configuration.SCMManipulator Deleting SCM hierarchy /root/jenkins/scm-sync-configuration/checkoutConfiguration/jobs/Frontend_Test from SCM ... Apr 27, 2015 1:13:20 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy deleteHierarchy Problem during remove : The git command failed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [nodejs-plugin] (JENKINS-28117) NodeJS err=13; permission denied on fedora20
Daniel Beck commented on JENKINS-28117 NodeJS err=13; permission denied on fedora20 Any noexec flags to mount around? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28111) JNLP slave JVM Options are inconsistently applied
stephenconnolly assigned JENKINS-28111 to stephenconnolly JNLP slave JVM Options are inconsistently applied Change By: stephenconnolly (27/Apr/15 9:27 PM) Assignee: stephenconnolly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-27349) Git SCM-polling uses wrong parameter values for a parametrized branchspec
SCM/JIRA link daemon commented on JENKINS-27349 Git SCM-polling uses wrong parameter values for a parametrized branchspec Code changed in jenkins User: Nicolas De loof Path: src/main/java/hudson/plugins/git/GitSCM.java src/main/java/hudson/plugins/git/util/GitUtils.java src/test/java/hudson/plugins/git/GitSCMTest.java http://jenkins-ci.org/commit/git-plugin/30766fe249c2512872c52ad96ceab1356510eba2 Log: Merge pull request #293 from jeanblanchard/fix-notify JENKINS-27349 Fix polling for parametrized branchspec Compare: https://github.com/jenkinsci/git-plugin/compare/7af820e61615...30766fe249c2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-27349) Git SCM-polling uses wrong parameter values for a parametrized branchspec
SCM/JIRA link daemon commented on JENKINS-27349 Git SCM-polling uses wrong parameter values for a parametrized branchspec Code changed in jenkins User: Jean Blanchard Path: src/main/java/hudson/plugins/git/GitSCM.java src/main/java/hudson/plugins/git/util/GitUtils.java src/test/java/hudson/plugins/git/GitSCMTest.java http://jenkins-ci.org/commit/git-plugin/d56fbee601d5c46d35fc5c05601ead12d66fba10 Log: JENKINS-27349 Polling for parametrized branchspec should resolve to default param values This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-27902) Allow to pass additional request parameter for notifyCommit
SCM/JIRA link daemon commented on JENKINS-27902 Allow to pass additional request parameter for notifyCommit Code changed in jenkins User: Nicolas De loof Path: src/main/java/hudson/plugins/git/GitStatus.java src/test/java/hudson/plugins/git/GitStatusTest.java http://jenkins-ci.org/commit/git-plugin/9e46ae773fa0f00b15dc989d3109941a664042af Log: Merge pull request #315 from christiangalsterer/JENKINS-27902 JENKINS-27902 Allow to pass additional request parameter for notifyCommit Compare: https://github.com/jenkinsci/git-plugin/compare/30766fe249c2...9e46ae773fa0 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gitlab-hook-plugin] (JENKINS-24230) allow build projects to be specified
Javier Palacios resolved JENKINS-24230 as Fixed allow build projects to be specified Change By: Javier Palacios (27/Apr/15 8:54 AM) Status: Open Resolved Assignee: VanjaRadovanović JavierPalacios 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-plugin] (JENKINS-27902) Allow to pass additional request parameter for notifyCommit
SCM/JIRA link daemon commented on JENKINS-27902 Allow to pass additional request parameter for notifyCommit Code changed in jenkins User: Christian Galsterer Path: src/main/java/hudson/plugins/git/GitStatus.java http://jenkins-ci.org/commit/git-plugin/336d7f7dfbcd427db8b180f23396ddad3cef56de Log: JENKINS-27902 Allow to pass additional request parameter for notifyCommit fixed review finding, that sha1 was not passed correctly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-27902) Allow to pass additional request parameter for notifyCommit
SCM/JIRA link daemon commented on JENKINS-27902 Allow to pass additional request parameter for notifyCommit Code changed in jenkins User: Christian Galsterer Path: src/main/java/hudson/plugins/git/GitStatus.java src/test/java/hudson/plugins/git/GitStatusTest.java http://jenkins-ci.org/commit/git-plugin/f0b2d0d16826906d5743722ae97967bf1d6303d7 Log: JENKINS-27902 Allow to pass additional request parameter for notifyCommit This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gitlab-hook-plugin] (JENKINS-25267) Gitlab hook not building on merge request object
Javier Palacios resolved JENKINS-25267 as Fixed Gitlab hook not building on merge request object This should be fully solved in the 1.4.0, release should be done during the coming two weeks, but you can download latest snapshot. Change By: Javier Palacios (27/Apr/15 8:56 AM) Status: Open Resolved Assignee: VanjaRadovanović JavierPalacios 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] [deploy-plugin] (JENKINS-28105) deployment failed
bujji dd created JENKINS-28105 deployment failed Issue Type: Bug Assignee: Unassigned Components: deploy-plugin Created: 27/Apr/15 7:23 AM Description: Deploying /usr/local/apache-tomcat-7.0.54/webapps/jenkins/jobs/buildproject/workspace/AntExample1/dist/AntExample.war to container Tomcat 7.x Remote ERROR: Build step failed with exception org.codehaus.cargo.container.ContainerException: Failed to redeploy /usr/local/apache-tomcat-7.0.54/webapps/jenkins/jobs/buildproject/workspace/AntExample1/dist/AntExample.war at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.java:189) at hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:73) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:116) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:103) at hudson.FilePath.act(FilePath.java:989) at hudson.FilePath.act(FilePath.java:967) at hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:103) at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:61) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670) at hudson.model.Run.execute(Run.java:1766) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Caused by: org.codehaus.cargo.container.tomcat.internal.TomcatManagerException: The username you provided is not allowed to use the text-based Tomcat Manager (error 403) at org.codehaus.cargo.container.tomcat.internal.TomcatManager.invoke(TomcatManager.java:555) at org.codehaus.cargo.container.tomcat.internal.TomcatManager.list(TomcatManager.java:686) at org.codehaus.cargo.container.tomcat.internal.TomcatManager.getStatus(TomcatManager.java:699) at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.java:174) ... 16 more Caused by: java.io.IOException: Server returned HTTP response code: 403 for URL: http://localhost:2020/manager/text/list at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1626) at org.codehaus.cargo.container.tomcat.internal.TomcatManager.invoke(TomcatManager.java:544) ... 19 more org.codehaus.cargo.container.tomcat.internal.TomcatManagerException: The username you provided is not allowed to use the text-based Tomcat Manager (error 403) at org.codehaus.cargo.container.tomcat.internal.TomcatManager.invoke(TomcatManager.java:555) at org.codehaus.cargo.container.tomcat.internal.TomcatManager.list(TomcatManager.java:686) at org.codehaus.cargo.container.tomcat.internal.TomcatManager.getStatus(TomcatManager.java:699) at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.java:174) at hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:73) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:116) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:103) at hudson.FilePath.act(FilePath.java:989) at hudson.FilePath.act(FilePath.java:967) at hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:103) at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:61) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721) at hudson.model.Build$BuildExecution.post2(Build.java:183) at
[JIRA] [git-plugin] (JENKINS-23992) Jenkins git-plugin not parsing HTML in build reason
Javier Palacios resolved JENKINS-23992 as Fixed Jenkins git-plugin not parsing HTML in build reason This is solved in the new version nearly ready for release. It reduces the cause to a single line, which become a plain string. You can download current snapshot, although I expect to release it in the next two weeks. Change By: Javier Palacios (27/Apr/15 8:51 AM) Status: Open Resolved Assignee: NicolasDeLoof JavierPalacios 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-plugin] (JENKINS-28109) Local artifact cache on slaves
Daniel Beck commented on JENKINS-28109 Local artifact cache on slaves Use a real artifacts repository like Artifactory, and a client which does artifact caching, like Gradle or Maven. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-28109) Local artifact cache on slaves
Daniel Beck updated JENKINS-28109 Local artifact cache on slaves Unrelated to core. Change By: Daniel Beck (27/Apr/15 12:34 PM) Component/s: 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] [performance-plugin] (JENKINS-27547) Performance Trend Per Test Case For Jmeter Give Error javax.servlet.ServletException
Igor Iric started work on JENKINS-27547 Performance Trend Per Test Case For Jmeter Give Error javax.servlet.ServletException Change By: Igor Iric (27/Apr/15 1:33 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] [performance-plugin] (JENKINS-27547) Performance Trend Per Test Case For Jmeter Give Error javax.servlet.ServletException
Igor Iric stopped work on JENKINS-27547 Performance Trend Per Test Case For Jmeter Give Error javax.servlet.ServletException Change By: Igor Iric (27/Apr/15 1:33 PM) Status: InProgress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-28109) Local artifact cache on slaves
Simon Richter commented on JENKINS-28109 Local artifact cache on slaves Relation to core: events on the master (e.g. project deletion) require action on the slaves, while the plugin runs in a project build only. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [performance-plugin] (JENKINS-28110) NoStaplerConstructorException for Jenkins 1.610
Johannes Schüth
commented on JENKINS-28110
NoStaplerConstructorException for Jenkins 1.610
Stack trace
javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.performance.PerformancePublisher from {"parsers":{"glob":"","kind":"hudson.plugins.performance.JMeterParser$DescriptorImpl"},"modeOfThreshold":"false","errorUnstableThreshold":"","errorFailedThreshold":"","errorUnstableResponseTimeThreshold":"","relativeUnstableThresholdNegative":"","relativeUnstableThresholdPositive":"","relativeFailedThresholdNegative":"","relativeFailedThresholdPositive":"","compareBuildPrevious":"false","nthBuildNumber":"","comparisonType":"ART","modePerformancePerTestCase":true,"modeThroughput":false,"stapler-class":"hudson.plugins.performance.PerformancePublisher","$class":"hudson.plugins.performance.PerformancePublisher"}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
at org.eclipse.jetty.server.Server.handle(Server.java:370)
at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489)
at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960)
at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240)
at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668)
at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)
at
[JIRA] [performance-plugin] (JENKINS-28110) NoStaplerConstructorException for Jenkins 1.610
Johannes Schüth created JENKINS-28110 NoStaplerConstructorException for Jenkins 1.610 Issue Type: Bug Assignee: Manuel Carrasco Components: performance-plugin Created: 27/Apr/15 1:39 PM Description: When adding the performance plugin to the post build steps and selecting a jmeter report saving will fail with a NoStaplerConstrucorException. Environment: JDK 1.8.0_25 x64 , Jenkins 1.611 1.610 - Performance Plugin Version 1.12 Project: Jenkins Priority: Blocker Reporter: Johannes Schüth This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28112) JNLP file requests Java 1.5+ despite minimum version of Java being 1.6+
stephenconnolly created JENKINS-28112 JNLP file requests Java 1.5+ despite minimum version of Java being 1.6+ Issue Type: Bug Assignee: Unassigned Components: core Created: 27/Apr/15 1:47 PM Description: The generated JNLP file has version="1.5+" this should be version="1.6+" at present with a view to moving to version="1.7+" or version="1.8+" once the core JVM required version is increased Project: Jenkins Priority: Minor Reporter: stephenconnolly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28111) JNLP slave JVM Options are inconsistently applied
stephenconnolly created JENKINS-28111 JNLP slave JVM Options are inconsistently applied Issue Type: Bug Assignee: Unassigned Components: core Created: 27/Apr/15 1:45 PM Description: The JVM Options are injected into the JNLP file as the java-vm-args attribute but the command line launch option does not reflect the requirements for JVM Options. The "Run from slave command line" option should include the specified JVM options for the non-javaws varietals. Project: Jenkins Priority: Minor Reporter: stephenconnolly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-28109) Local artifact cache on slaves
Daniel Beck commented on JENKINS-28109 Local artifact cache on slaves Jenkins doesn't even delete project workspaces when projects are deleted, so deleting any other caches would be surprising behavior. This would require fairly complex behavior anyway, as nodes could be offline when the project gets deleted (and there would be the expectation that it'd get deleted the next time the slave is online). Pretty big can of worms right there for questionable benefit. FWIW all of this could be implemented in the plugin through extension points that already exist AFAICT, so requires no core improvements. (I just don't think this would be useful.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28113) BuildTrigger should accept any ParameterizedJob downstream
Jesse Glick created JENKINS-28113 BuildTrigger should accept any ParameterizedJob downstream Issue Type: Bug Assignee: Unassigned Components: core Created: 27/Apr/15 2:10 PM Description: ReverseBuildTrigger supports any ParameterizedJob, behaving as a DependencyDeclarer if both sides are AbstractProject, behaving as a simple Trigger otherwise. BuildTrigger should do the same, behaving as a DependencyDeclarer as now if both sides are AbstractProject, behaving as a simple Notifier otherwise. Would allow Build other projects to select a workflow job. Workarounds: JENKINS-26050, if implemented; use of ReverseBuildTrigger, in the common case that it does not matter which side declares the trigger (but not when Item.CONFIGURE is restricted on one side, job templates are in use, etc.). Project: Jenkins Labels: workflow Priority: Minor Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-28110) NoStaplerConstructorException for Jenkins 1.610
Johannes Schüth edited a comment on JENKINS-28110 NoStaplerConstructorException for Jenkins 1.610 The exception occurs when jenkins tries to instanciate the PerformanceReportParser from the json. This can't work since the PerformanceReportParser class is abstract. I can only assume that somehow something went wrong when creating the json object. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [performance-plugin] (JENKINS-28110) NoStaplerConstructorException for Jenkins 1.610
Johannes Schüth commented on JENKINS-28110 NoStaplerConstructorException for Jenkins 1.610 The exception jenkins tries to instanciate the PerformanceReportParser from the json. This can't work since the PerformanceReportParser class is abstract. I can only assume that somehow something went wrong when creating the json object. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-27998) Git plugin fails to clone with ssh protected passphrase
Mark Waite updated JENKINS-27998 Git plugin fails to clone with ssh protected passphrase Change By: Mark Waite (28/Apr/15 12:08 AM) Summary: Gitpluginfailsto connect clonewithsshprotectedpassphrase This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-monitor-plugin] (JENKINS-28102) Getting error with build Monitor plugin
viral shah commented on JENKINS-28102 Getting error with build Monitor plugin HI Daniel, I managed to fix the issue by uninstalling the plugin Claim build . As per your advised i saw the logs and it was showing some exception due to claim build so tried to uninstall it and it worked. But i dont know if you have to fix anything from your side ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [mercurial-plugin] (JENKINS-28121) Mercurial GeneralSCM step does not create intermediary directories.
Geoffrey Edwards
created JENKINS-28121
Mercurial GeneralSCM step does not create intermediary directories.
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
mercurial-plugin, workflow-plugin
Created:
27/Apr/15 10:28 PM
Description:
Base slave install with nothing in the home directory.
Standard Freestyle project creates the full path ($JENKINS_HOME\\workspacejob name).
Workflow project fails the scm step with 'abort: The system cannot find the path specified: $JENKINS_HOME\workspace\job name\'
Manually creating the $JENKINS_HOME\workspace directory fixes the issue unless the scm step specifies a sub-directory, in which case the parent of the sub-directory also has to be manually created.
Workflow script was a simple:
node('slave-name') {
checkout([$class: 'MercurialSCM', ...])
}
Environment:
Jenkins Master (Fedora 22 - Server 64bit)
Jenkins Slave (Win7 - 64bit)
Jenkins Version - v1.611
Mercurial Plugin - v1.52
Workflow Plugin - v1.5
Project:
Jenkins
Labels:
workflow
scm
Priority:
Major
Reporter:
Geoffrey Edwards
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-label-assignment-plugin] (JENKINS-28123) Jobs stay queued forever if label assignment is initially unavailable
Christian Goetze
commented on JENKINS-28123
Jobs stay queued forever if label assignment is initially unavailable
The way a node can become available is also via a script, which modifies the labels on nodes and then runs:
jenkins.model.Jenkins.instance.labels.each { it.reset() }
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-plugin] (JENKINS-28032) Included Regions do not work when monitoring all branches
Jacek Sniecikowski updated JENKINS-28032 Included Regions do not work when monitoring all branches The issue appears to boil down to the way changelist is being gathered via the git log command. That is happening in 'showRevision' method (CliGitAPIImpl.java): git log --full-history --no-abbrev --format=raw -M -m --raw oldSHA..newSha When the SHAs come from different branches, the result has more entries than expected, so 'isRevExcluded' method in GiSCM.java will check changes that were already built before. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-label-assignment-plugin] (JENKINS-28123) Jobs stay queued forever if label assignment is initially unavailable
Christian Goetze created JENKINS-28123 Jobs stay queued forever if label assignment is initially unavailable Issue Type: Bug Assignee: Unassigned Components: groovy-label-assignment-plugin Created: 27/Apr/15 10:59 PM Description: If a job sets a label and no node is available to run the job, the job just stays queued forever even if an appropriate node later becomes available. Is there some (groovy) way to "tickle" the job in the queue? Project: Jenkins Priority: Minor Reporter: Christian Goetze This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [cloudbees-folder-plugin] (JENKINS-28043) Reload configs of all jobs in folder
Brantone commented on JENKINS-28043 Reload configs of all jobs in folder Yeah, my bad, I was pretty sure I had selected the correct component for Cloudbees Folder Will add repro steps. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [logstash-plugin] (JENKINS-28040) Allow logstash plugin to feed a syslog server
Rusty Gerard commented on JENKINS-28040 Allow logstash plugin to feed a syslog server While I think this functionality belongs in the syslog-logger plugin rather than the logstash plugin, it might be useful to share the BuildData object I created for the logstash plugin across both. Cyrille Le Clerc, what do you think? The logstash plugin sends data across as JSON. Would it be useful to split out BuildData.java in logstash out to share across both plugins so they share a common format? https://github.com/jenkinsci/logstash-plugin/blob/master/src/main/java/jenkins/plugins/logstash/persistence/BuildData.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] [cloudbees-folder-plugin] (JENKINS-28043) Reload configs of all jobs in folder
Brantone updated JENKINS-28043 Reload configs of all jobs in folder Change By: Brantone (28/Apr/15 1:00 AM) Description: Ifmanualchangesmadetoconfig.xml,hittingJenkinsManage ReloadConfigurationfromDiskdoesnotseemtoactuallytakejobswithinthefolder. Actually Repro:1 . Createfolder2 . Createjobwithinfolder3 . thatmaybeaJenkinscoreissue MakechangesbyhanddirectlytoFoldersconfig.xml4.MakechangesbyhanddirectlytoJobsconfig.xml5.Reloadconfig6.Folderhasupdates , worthcheckingthough butJobdoesnotreflectchanges . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-combinations-parameter-plugin] (JENKINS-23609) Successful and Failed link in matrix-combinations-parameter do not work
ikedam closed JENKINS-23609 as Fixed Successful and Failed link in matrix-combinations-parameter do not work 1.0.8 with this fix released. It will be available in a day. Change By: ikedam (27/Apr/15 10:14 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-plugin] (JENKINS-27998) Git plugin fails to connect
Mark Waite edited a comment on JENKINS-27998 Git plugin fails to connect It is possible to fix that. Someone would need to add support for passphrase protected ssh keys to the git plugin authentication, or if it is implemented and not working, they would need to fix the bug. Pull requests with automated tests are welcomed. Regarding your comment about it being a security flaw, I don't see how entering the passphrase into a web form in Jenkins is any more secure than using an ssh key with no passphrase. In both cases, there is enough information stored in Jenkins to use the credential, without any additional prompting. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-27998) Git plugin fails to connect
Mark Waite commented on JENKINS-27998 Git plugin fails to connect It is possible to fix that. Someone would need to add support for passphrase protected ssh keys to the git plugin authentication, or if it is implemented and not working, they would need to fix the bug. Regarding your comment about it being a security flaw, I don't see how entering the passphrase into a web form in Jenkins is any more secure than using an ssh key with no passphrase. In both cases, there is enough information stored in Jenkins to use the credential, without any additional prompting. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [multijob-plugin] (JENKINS-23460) 'pkg.jenkins-ci.org' unavailable (or running very slow)
Brantone commented on JENKINS-23460 pkg.jenkins-ci.org unavailable (or running very slow) Not sure this is an issue with Multi-Job plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testlink-plugin] (JENKINS-25062) Jenkins Testlink plugin cannot find testing result, shows Not run
kishore vnjam commented on JENKINS-25062 Jenkins Testlink plugin cannot find testing result, shows Not run Was there any update on this issue? I am running in to similar issue. Following are my versions: TestLink Version : 1.9.13 Jenkins Version : 1.610 Plugin Version : 3.10 I tried the steps mentioned in the tutorial and is not updating the TestLink results ( it is listing all the tests as Not Run just as mentioned in the original issue). Is this version incompatibility or any work arounds? Appreciate any help/suggestions on this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-27998) Git plugin fails to connect
Jamie Doornbos commented on JENKINS-27998 Git plugin fails to connect The credentials for the original key do have a passphrase attached; the SSH agent plugin is using it correctly. But it looks like the git plugin is not. I tested a key with no passphrase and confirmed that the git plugin does work in that case. Is it possible to fix this? It seems like a security flaw to have to always use keys with no passphrase. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testlink-plugin] (JENKINS-28122) Plugin doesn't update the test cases status properly on testlink (ver:1.9.13)
kishore vnjam updated JENKINS-28122 Plugin doesnt update the test cases status properly on testlink (ver:1.9.13) Change By: kishore vnjam (27/Apr/15 11:13 PM) Description: Triedfollowingthetutorials,testcompletedwithSUCCESSstatus.ThetestcaseinTestlinkisreportedasNotRun.ItneverupdatesthestatusonTestLink. AttachingthescreensfrombothJenkinsandTestLink. Pleaseletmeknowif youneedanyadditionalinformationtofurthertroubleshootthis.Thanks. Attachment: 28122-TestResults-Jenkins.JPG Attachment: 28122-TestLink-JobDefinition.JPG Attachment: 28122-jenkins-workspace.tar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testlink-plugin] (JENKINS-25062) Jenkins Testlink plugin cannot find testing result, shows Not run
Bruno P. Kinoshita commented on JENKINS-25062 Jenkins Testlink plugin cannot find testing result, shows Not run Not really Kishore. I'm busy relocating and starting with a new job. Should you have a pull request, let me know and we can merge / release it. Bruno This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Zeus Minos commented on JENKINS-14572 Git plug-in fetches all tags even when refspec is provided Is there any temp workaround ? Fetching all the tags in our case is just a waist of time. 00:01:28.364 C:\Program Files\Git\cmd\git.exe -c core.askpass=true fetch --tags --progress g...@gitlab.dev.local:superman/b.git +refs/heads/:refs/remotes/origin/ --depth=1 00:07:05.694 C:\Program Files\Git\cmd\git.exe config remote.origin.url g...@gitlab.dev.local:superman/b.git # timeout=10 As you can see It takes about 7 min to execute the next cmd. This is just a waist of time :-/ Please share with me any workaround This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [label-linked-jobs-plugin] (JENKINS-27588) Labels used in Label Factory are shown as not used
Dominique Brice commented on JENKINS-27588 Labels used in Label Factory are shown as not used Plugin page updated. Stefan Kalmelid, how's the new version working on your prod instance? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-28032) Included Regions do not work when monitoring all branches
Mark Waite commented on JENKINS-28032 Included Regions do not work when monitoring all branches When you say "monitor all branches", the plugin thinks that means "if a previously unbuilt SHA1 is detected on any branch, then compute the differences between the most recent build and that unbuilt SHA1 and pass those differences through the inclusion and exclusion filters". There is an option in the plugin to make comparisons to a specific named branch, rather than to the last build, but I'm not sure if even that would meet your needs. You might try a different experiment, using the multi-branch plugin to automatically create and delete jobs for branches as they are created and deleted. I'm not sure that plugin allows inclusion / exclusion, but it is probably worth an experiment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28124) userContent is corrupt in 1.610
Igor Koyfman created JENKINS-28124 userContent is corrupt in 1.610 Issue Type: Bug Assignee: Unassigned Components: core Created: 28/Apr/15 3:46 AM Description: After updating to 1.610 a part of userContent, which in our case is less than 1 MB or python scripts, is full of bad characters. Everything works again after reverting to 1.607. It's an identical corruption in all jobs on all nodes; I suspect it's whatever gets transferred last. Project: Jenkins Priority: Major Reporter: Igor Koyfman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Zeus Minos commented on JENKINS-14572 Git plug-in fetches all tags even when refspec is provided @Mark Waite I will really love to do it, but unfortunately my days are way too short to do that. This issue is not impacting just me. I am sure that there are other folks around here with better understanding of this plugin and they can do it in a blink of an eye. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Zeus Minos edited a comment on JENKINS-14572 Git plug-in fetches all tags even when refspec is provided @Robert More: Thank you for your replay . Well Shallow Clone has been active since day 1 in our jobs and still 7 min. Guys can you please allow us to customize the git parameters in the coming versions. In first place I do not need or want to fetch any tags :-/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Robert Moore commented on JENKINS-14572 Git plug-in fetches all tags even when refspec is provided In our case, we just want a flag to disable the "initial" fetch of all tags. With Gerrit plugin, we're fetching a unique refspec afterward, so there's no need for us to do more than "git init". Would it be possible to have the option of disabling the initial fetch/clone? We don't need anything more complex than that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Zeus Minos commented on JENKINS-14572 Git plug-in fetches all tags even when refspec is provided @MArk Waite What do you mean by "Investigating the area of plugin where the --tag argument is passed?". Isn't such behavior hardcoded in the plugin? If not how shall I disabled it? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Zeus Minos commented on JENKINS-14572 Git plug-in fetches all tags even when refspec is provided @Robert More: Thank you for your replay . Well Shallow Clone has been active since day 1 in our jobs and still 7 min. Guys can you please allow us to customize the git parameters in the coming versions This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Mark Waite commented on JENKINS-14572 Git plug-in fetches all tags even when refspec is provided That's a fair approach as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Robert Moore commented on JENKINS-14572 Git plug-in fetches all tags even when refspec is provided We've been able to reduce cloning time by using a reference repo. We first created a bare clone in a shared space on each build slave, then use this as a reference repo in the build job. Now it clones from the reference, but it's a much faster FS operation rather than network. It's still not ideal, since we don't really need the repo to consume disk (or duplicated into the builds), but it's cut out ~2 minutes of the build job. In the project configuration, navigate to "Source code management" - "Additional Behaviours" - "Advanced Clone Behaviors". Check "Shallow Clone" and then the absolute path to the local cloned repo. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Robert Moore edited a comment on JENKINS-14572 Git plug-in fetches all tags even when refspec is provided We've been able to reduce cloning time by using a reference repo. We first created a bare clone in a shared space on each build slave, then use this as a reference repo in the build job. Now it clones from the reference, but it's a much faster FS operation rather than network. It's still not ideal, since we don't really need the repo to consume disk (or duplicated into the builds), but it's cut out ~2 minutes of the build job. In the project configuration, navigate to "Source code management" - "Additional Behaviours" - "Advanced Clone Behaviors". Check "Shallow Clone" and then the absolute path to the local cloned repo. EDIT: If you're not already using "Advanced Clone Behaviours", be sure to add it from the "Add" button. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Mark Waite commented on JENKINS-14572 Git plug-in fetches all tags even when refspec is provided The plugin already has significant challenges the plugin maintaining compatibility among its many different use cases. I'd rather not provide even more opportunities for user surprises by allowing general purpose customization of the parameters passed to git. If we allow you to pass a custom parameter to a specific git command, it seems like that will then guarantee that the plugin must use that exact command and honor that exact parameter indefinitely. As an example, previously the plugin used "git clone" to populate the repository. When credentials support was added, that was switched to "git fetch". In the future, it may switch back to "git clone". Allowing you to pass arbitrary parameters to a subset of git commands used by the plugin seems like it will either make compatibility even more difficult, or make future changes even more difficult. Have you considered investigating the area of the plugin where the --tags argument is passed, seeking a way to remove that call to --tags without harming the rest of the plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Mark Waite commented on JENKINS-14572 Git plug-in fetches all tags even when refspec is provided Zeus Minos, I mean that you can fork your own copy of the git client plugin source code and the git plugin source code on GitHub, compile them, locate the places in the source code where the --tag argument is passed to command line git, then you can experiment with modifying the behavior to better match what you want. That will allow you to modify and test your changes. If you find the changes are useful to you and don't break other use cases, you could provide unit tests which confirm the new behavior you've added, and can submit them as a pull request for possible inclusion in the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Zeus Minos edited a comment on JENKINS-14572 Git plug-in fetches all tags even when refspec is provided @Mark Waite I will really love to do it, but unfortunately my days are way too short to do that. This issue is not impacting just me. I am sure that there are other folks around here with better understanding of this plugin and they can do it in a blink of an eye. Worst case I will say bye bye to this plugin and I will handle that like in the old days "Executed Windows Batch cmd" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-project-plugin] (JENKINS-28107) Matrix parent should take an executor slot until the point where children are triggered
Simon Richter commented on JENKINS-28107 Matrix parent should take an executor slot until the point where children are triggered That helps distribute the load a bit, but is still suboptimal (rather than 30 concurrent parent jobs I now have 10). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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.
