[JIRA] [mask-passwords-plugin] (JENKINS-26421) Password masking is masking even string fields
Marek Knappe created JENKINS-26421 Password masking is masking even string fields Issue Type: Bug Assignee: Daniel Petisme Attachments: Screenshot - 14_01_2015 , 10_21_51 AM.png, Screenshot - 14_01_2015 , 10_23_42 AM.png, Screenshot - 14_01_2015 , 10_24_26 AM.png Components: mask-passwords-plugin Created: 14/Jan/15 12:24 AM Description: I tried to use masking plugin, but it's masking everything, not only the ones I used: Project: Jenkins Priority: Minor Reporter: Marek Knappe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26420) Specifying sha1 without branch name in the notifyCommit URL triggers builds for all jobs (potentially hundreds)
Mark Waite commented on JENKINS-26420 Specifying sha1 without branch name in the notifyCommit URL triggers builds for all jobs (potentially hundreds) Can you explain further what you would propose as a solution to the problem? As far as I can tell, if jobs are configured to listen to poll on the notifyCommit, and the SHA1 passed as a parameter is part of the notifyCommit, then that SHA1 should be built, if it is available in the repository. That seems like "do the work I requested" rather than "denial of service". I don't see a significant difference between an arbitrary SHA1 and a change on the master. Would it be better to have a global switch in Jenkins which allows the Jenkins core to ignore the value passed as sha1? Administrators concerned about users invoking jobs with arbitrary SHA1 values could then ignore that value, accepting that by ignoring the value from some users, they must ignore it from all users. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26420) Specifying sha1 without branch name in the notifyCommit URL triggers builds for all jobs (potentially hundreds)
Mark Waite updated JENKINS-26420 Specifying sha1 without branch name in the notifyCommit URL triggers builds for all jobs (potentially hundreds) Change By: Mark Waite (14/Jan/15 3:08 AM) 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] [core] (JENKINS-26420) Specifying sha1 without branch name in the notifyCommit URL triggers builds for all jobs (potentially hundreds)
Mark Waite edited a comment on JENKINS-26420 Specifying sha1 without branch name in the notifyCommit URL triggers builds for all jobs (potentially hundreds) Can you explain further what you would propose as a solution to the problem? As far as I can tell, if jobs are configured to listen to poll on the notifyCommit, and the SHA1 passed as a parameter is part of the notifyCommit, then that SHA1 should be built, if it is available in the repository. That seems like "do the work I requested" rather than "denial of service". I don't see a significant difference between an arbitrary SHA1 and a change on the master. Would it be better to have a global switch in Jenkins which allows the Jenkins core to ignore the value passed as sha1? Administrators concerned about users invoking jobs with arbitrary SHA1 values could then ignore that value, accepting that by ignoring the value from some users, they must ignore it from all users. Would it be better to have a global switch which requires that if there is a sha1 value, then there must also be a branch value, otherwise the request is ignored? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mask-passwords-plugin] (JENKINS-26421) Password masking is masking even string fields
Marek Knappe commented on JENKINS-26421 Password masking is masking even string fields I don't pretty new installation of jenkins, should I install that ? That's my list of plugins in case of need: Ant Plugin Credentials Plugin Crowd 2 Integration CVS Plug-in Docker plugin Durable Task Plugin Dynamic Parameter Plug-in Extended Choice Parameter Plug-In Extensible Choice Parameter plugin External Monitor Job Type Plugin GIT client plugin Git Parameter Plug-In GIT plugin Git server plugin Javadoc Plugin Jira Issue Updater JIRA plugin JUnit Plugin LDAP Plugin Mailer Plugin MapDB API Plugin Mask Passwords Plugin Matrix Authorization Strategy Plugin Matrix Project Plugin Maven Integration plugin OWASP Markup Formatter Plugin PAM Authentication plugin SCM API Plugin Scriptler SSH Credentials Plugin SSH Slaves plugin Subversion Plug-in Token Macro Plugin Translation Assistance plugin Windows Slaves Plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26420) Specifying sha1 without branch name in the notifyCommit URL triggers builds for all jobs (potentially hundreds)
Mark Waite edited a comment on JENKINS-26420 Specifying sha1 without branch name in the notifyCommit URL triggers builds for all jobs (potentially hundreds) Can you explain further what you would propose as a solution to the problem? As far as I can tell, if jobs are configured to listen to poll on the notifyCommit, and the SHA1 passed as a parameter is part of the notifyCommit, then that SHA1 should be built, if it is available in the repository. That seems like "do the work I requested" rather than "denial of service". I don't see a significant difference between an arbitrary SHA1 and a change on the master. Would it be better to have a global switch in Jenkins which allows the Jenkins core to ignore the value passed as sha1? Administrators concerned about users invoking jobs with arbitrary SHA1 values could then ignore that value, accepting that by ignoring the value from some users, they must ignore it from all users. Would it be better to have a global switch which requires that if there is a sha1 value, then there must also be a branch value, otherwise the request is ignored? Also, can you clarify if there is any significance to the "without branch name" portion of the report? When I insert branch=master as another URL argument, I believe I see the same result, that all jobs for repositories seem to launch all the jobs 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] [core] (JENKINS-26420) Specifying sha1 without branch name in the notifyCommit URL triggers builds for all jobs (potentially hundreds)
Mark Waite edited a comment on JENKINS-26420 Specifying sha1 without branch name in the notifyCommit URL triggers builds for all jobs (potentially hundreds) Can you explain further what you would propose as a solution to the problem? As far as I can tell, if jobs are configured to listen to poll on the notifyCommit, and the SHA1 passed as a parameter is part of the notifyCommit, then that SHA1 should be built, if it is available in the repository. That seems like "do the work I requested" rather than "denial of service". I don't see a significant difference between an arbitrary SHA1 and a change on the master. Would it be better to have a global switch in Jenkins which allows the Jenkins core to ignore the value passed as sha1? Administrators concerned about users invoking jobs with arbitrary SHA1 values could then ignore that value, accepting that by ignoring the value from some users, they must ignore it from all users. Would it be better to have a global switch which requires that if there is a sha1 value, then there must also be a branch value, otherwise the request is ignored? Alternately, if the passed SHA1 is the same as the preceding SHA1, it might be possible to ignore the request (since the preceding build was the same SHA1, the git plugin generally assumes the same SHA1 does not need to be built twice). Also, can you clarify if there is any significance to the "without branch name" portion of the report? When I insert branch=master as another URL argument, I believe I see the same result, that all jobs for repositories seem to launch all the jobs 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] [mask-passwords-plugin] (JENKINS-26421) Password masking is masking even string fields
Daniel Beck commented on JENKINS-26421 Password masking is masking even string fields Do you have the envinject plugin installed as well? What happens when you disable 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] [mask-passwords-plugin] (JENKINS-26421) Password masking is masking even string fields
Daniel Beck commented on JENKINS-26421 Password masking is masking even string fields If you don't need it, don't install 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] [testlink-plugin] (JENKINS-26386) test Link plugin in3.10 with Jenkin 1.588 and testlink 1.9(customized) throwing error-
sreelesh kunnath commented on JENKINS-26386 test Link plugin in3.10 with Jenkin 1.588 and testlink 1.9(customized) throwing error- please help me to resolve this situation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cobertura-plugin] (JENKINS-26410) Dashboard links broken when inside folder
Oliver Gondža started work on JENKINS-26410 Dashboard links broken when inside folder Change By: Oliver Gondža (13/Jan/15 5:00 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26380) Deadlock between Queue and Jenkins model
SCM/JIRA link daemon commented on JENKINS-26380 Deadlock between Queue and Jenkins model Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/durabletask/executors/OnceRetentionStrategy.java http://jenkins-ci.org/commit/durable-task-plugin/cce88cad22f78997d6a7b839fb3f2f75b4ce94c9 Log: Merge pull request #2 from stephenc/jenkins-26380 JENKINS-26380 Terminate nodes correctly Compare: https://github.com/jenkinsci/durable-task-plugin/compare/6325fef67a86...cce88cad22f7 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26203) Icon images are broken when using UNC paths
SCM/JIRA link daemon commented on JENKINS-26203 Icon images are broken when using UNC paths Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/ClassicPluginStrategy.java http://jenkins-ci.org/commit/jenkins/08b957c12f5c6587c108bd761b090355c231cfaa Log: FIXED JENKINS-26203 Noting merge of #1503. Compare: https://github.com/jenkinsci/jenkins/compare/b0908bd5ae64...08b957c12f5c This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26418) perforce software plugin returns Unable to update workspace when in multiconfig project
Idbe Holdme created JENKINS-26418 perforce software plugin returns Unable to update workspace when in multiconfig project Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 13/Jan/15 5:46 PM Description: When setting up a Multi-configuration project and allowing multiple builds to run at the same time (disable "Run each configuration sequentially"), the build fails for all the configurations exept one with the following error: P4JAVA: can't create directory for /path/to/file/file.sh ERROR: Unable to update workspace: hudson.AbortException: P4JAVA: Error(s) My guess is that since there are multiple p4 accesses going on at the same time, something screws up and boom. Project: Jenkins Priority: Minor Reporter: Idbe Holdme This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26203) Icon images are broken when using UNC paths
SCM/JIRA link daemon resolved JENKINS-26203 as Fixed Icon images are broken when using UNC paths Change By: SCM/JIRA link daemon (13/Jan/15 5:57 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] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Paulo Moreira edited a comment on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Hello, I have installed and have no problems with it! Windows Node: svn, version 1.8.11 Linux Node: svn, version 1.8.8 Jenkins - configuration - Subversion = 1.8 Subversion Plugin = 2.5 All jobs migrated from 1.7, all do: Always check out a fresh copy Delete workspace before build starts bRestart Jenkins/b This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Paulo Moreira edited a comment on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Hello, I have installed and have no problems with it! Windows Node: svn, version 1.8.11 Linux Node: svn, version 1.8.8 Jenkins - configuration - Subversion = 1.8 Subversion Plugin = 2.5 All jobs migrated from 1.7, all do: Always check out a fresh copy Delete workspace before build starts Restart Jenkins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26203) Icon images are broken when using UNC paths
SCM/JIRA link daemon commented on JENKINS-26203 Icon images are broken when using UNC paths Code changed in jenkins User: Felix Belzunce Arcos Path: core/src/main/java/hudson/ClassicPluginStrategy.java http://jenkins-ci.org/commit/jenkins/6351a8a25826679a69648e772e163dafdfc5cae3 Log: JENKINS-26203 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Bart van der Schans commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Hi Paulo, Setting the subversion version to 1.8 solved my format '100' issue! Thanks for sharing. Putting it back to 1.7 also does a correct 1.7 checkout now. Maybe there was some non-initialized value for the version that tricked the plugin in a incorrect checkout? Bart This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26380) Deadlock between Queue and Jenkins model
SCM/JIRA link daemon commented on JENKINS-26380 Deadlock between Queue and Jenkins model Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/durabletask/executors/OnceRetentionStrategy.java http://jenkins-ci.org/commit/durable-task-plugin/18733f566e3ddb1dafe32dfb16025586cb76306f Log: JENKINS-26380 Terminate nodes 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] [core] (JENKINS-26380) Deadlock between Queue and Jenkins model
Jesse Glick resolved JENKINS-26380 as Fixed Deadlock between Queue and Jenkins model I guess should be considered fixed with that change. Change By: Jesse Glick (13/Jan/15 5:43 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] [promoted-builds-plugin] (JENKINS-20912) promoted-builds plugin NullPointerException on getParameterValues
John Mellor commented on JENKINS-20912 promoted-builds plugin NullPointerException on getParameterValues I have configured the build for manual promotion only, and I can get to the point of actually doing the promotion, but then I get an API mismatch bug. I'm using latest Jenkins (1.596) and the latest Promoted Build Plugin (2.19) on a fully up-to-date Ubuntu 12.04 64bit host. The promotion mechanism is simple, calling a single shell script to push the artifacts to a debian repo. I'm scratching my head at this point. What's wrong? The traceback when I promote looks like: javax.servlet.ServletException: java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) 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:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) 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.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) 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
[JIRA] [claim-plugin] (JENKINS-19422) Claim publisher exception when trying to claim a build is aborted
Roger Myung commented on JENKINS-19422 Claim publisher exception when trying to claim a build is aborted I am getting the "Allow broken build claiming is waiting for a checkpoint on MY JOB NAME" message on a successful build. It does not seem to have any effect. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-20912) promoted-builds plugin NullPointerException on getParameterValues
Daniel Beck resolved JENKINS-20912 as Duplicate promoted-builds plugin NullPointerException on getParameterValues This actually duplicates JENKINS-20166 and was fixed in Promoted Builds 2.15. Change By: Daniel Beck (13/Jan/15 7:12 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-26032) Prefer BuildStepMonitor.NONE
Sandeep Dhingra commented on JENKINS-26032 Prefer BuildStepMonitor.NONE Hi Daniel , The issue is performance summariser doesn't work if we change BuildStepMonitor.BUILD to Build.NONE.We want the report to get published after the test is over.Though we see *.jtl files,the report doesn't get published.If you need sponsorship for this issue,we can think about that too .Please let us know on these lines. Thanks Sandeep This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26407) Support expandableTextbox form validation
Oliver Gondža created JENKINS-26407 Support expandableTextbox form validation Issue Type: Improvement Assignee: Unassigned Components: core Created: 13/Jan/15 8:51 AM Project: Jenkins Labels: ui 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] [core] (JENKINS-26407) Support expandableTextbox form validation
Oliver Gondža assigned JENKINS-26407 to Oliver Gondža Support expandableTextbox form validation Change By: Oliver Gondža (13/Jan/15 8:51 AM) Assignee: OliverGondž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] [artifactory-plugin] (JENKINS-26403) SNI Support when using Artifactory behind HTTPS
Night Wolf commented on JENKINS-26403 SNI Support when using Artifactory behind HTTPS Both Certs are valid. The problem is they both exist on the same host. Typically SSL wants a unique IP per host. Hence the need for SNI. This plugin uses artifactory's build info plugin which uses httpclient. Http client only added SNI support in 4.3.2 see https://issues.apache.org/jira/plugins/servlet/mobile#issue/HTTPCLIENT-1119 So the plugin needs to be updated with a new version on buildinfo which needs a later version of httpclient. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [phing-plugin] (JENKINS-26390) Allow phing instances installed through composer
Bert Hekman updated JENKINS-26390 Allow phing instances installed through composer Change By: Bert Hekman (13/Jan/15 8:24 AM) Description: Thephingpluginonlysupportsagloballyinstalledphinginstance,butitwouldbenicetoallowtheplugintoworkwithaperprojectphinginstanceinstalledthroughcomposer.A really solutionthatcomestomymindisaddinganextratextfieldinthephingbuildstepwithpathtophinginstance/executable This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scripttrigger-plugin] (JENKINS-26405) Rest-API-Triggered Polling not working with ScriptTrigger
Ronald Angerer created JENKINS-26405 Rest-API-Triggered Polling not working with ScriptTrigger Issue Type: Bug Assignee: Gregory Boissinot Components: scripttrigger-plugin Created: 13/Jan/15 8:08 AM Description: When calling notifyCommit via Rest (jenkins url/git/notifyCommit?url="" usually SCM-Polling of the related jobs starts immediately. This works perfectly when using "Poll SCM" setting but not with "ScriptTrigger - Poll with a shell or batch script". Script trigger polling should behave the same way as default polling and start the script when notifyCommit is called. The current workaround is to poll periodically with the "Schedule" setting. Environment: Jenkins 1.554.3 scripttrigger 0.31 GIT plugin 2.2.12 GIT client plugin 1.15.0 Project: Jenkins Priority: Minor Reporter: Ronald Angerer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26406) description-setter plugin cannot set html anymore
Arnt Witteveen created JENKINS-26406 description-setter plugin cannot set html anymore Issue Type: Bug Assignee: Unassigned Components: core Created: 13/Jan/15 8:30 AM Description: Upgrading from 1.578 to 1.596, I find that all the links I have in the build descriptions don't work in the build history (they do work on the build's main page). I use the description-setter to set discriptions like: a href=""win console/a to link directly to the console form each job. (And 3 more links, to the build results and then the same for the mac build of this Multi-configuration project). These links still show as links on job/myjob/xx/ but only the text shows in the build history 'sidebar'. I add these links mostly for use from the sidebar (to save clicks and page load time when going to the console and build artefacts for a specific build). Looking through the Jenkins Changelog, I'm guessing this may be the result of the change in 1.593 (or maybe issue 16184?). The plugin itself did not change. I'm not sure if this change was intentional or not, at least nothing in the changelog seems to indicate it was. Environment: Jenkins 1.596 with description-setter plugin 1.9 (and other plugins, including build-name-setter ) Project: Jenkins Labels: buildhistory user-experience Priority: Minor Reporter: Arnt Witteveen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory-plugin] (JENKINS-26403) SNI Support when using Artifactory behind HTTPS
Daniel Beck commented on JENKINS-26403 SNI Support when using Artifactory behind HTTPS Why not just use a valid SSL cert (e.g. for *.build.coy.com.au)? Or simply a cert for repo.build.coy.com.au? Or does SNI not work for some reason? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-26338) Entering Emulator Executable value does not work
chiara chiappini commented on JENKINS-26338 Entering Emulator Executable value does not work I Issued https://github.com/jenkinsci/android-emulator-plugin/pull/43 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-26338) Entering Emulator Executable value does not work
chiara chiappini commented on JENKINS-26338 Entering Emulator Executable value does not work Ok, I am gonna fix that and issue a pull request. Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-26408) Sauce connect fails to start
Pasi Romo created JENKINS-26408 Sauce connect fails to start Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: sauce-ondemand-plugin Created: 13/Jan/15 9:05 AM Description: I updated Jenkins Sauce OnDemand plugin to the latest version (1.111) and after doing this sauce connect fails to open a new tunnel connection: FATAL: java.io.IOException: Cannot run program "/usr/local/tomcat/sc-4.3.6-linux/bin/sc" (in directory "/usr/local/tomcat/sc-4.3.6-linux"): error=2 I am running the jenkins on 64-bit Linux. The reason why the execution fails is that the sauce on demand plugin for some reason installs a 32-bit binary on jenkins server (i.e. under sc-4.3.6-linux32) but tries to run sc-binary under sc-4.3.6-linux. This has not been a problem with the previous releases. Project: Jenkins Priority: Critical Reporter: Pasi Romo This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-18125) Changelog empty or contains all changes
Liya Katz commented on JENKINS-18125 Changelog empty or contains all changes Do you have any estimation when it will be 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] [hp-application-automation-tools-plugin] (JENKINS-26308) LoadRunner Scenario Always Times Out
Connor Gilbert edited a comment on JENKINS-26308 LoadRunner Scenario Always Times Out Added a $5 bounty This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-10686) Polling on slaves can hang
Rob Petti commented on JENKINS-10686 Polling on slaves can hang Upgrade to the latest version, switch to the p4-plugin, or use the system groovy script I mentioned above to kill hung polling threads. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-20912) promoted-builds plugin NullPointerException on getParameterValues
John Mellor updated JENKINS-20912 promoted-builds plugin NullPointerException on getParameterValues This problem is still occurring, using the latest Jenkins and the latest promoted-builds plugin. The plugin is unusable. Workaround: back out to the ancient 2.13 version from 2 years ago, which functions. Change By: John Mellor (13/Jan/15 2:13 PM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-20912) promoted-builds plugin NullPointerException on getParameterValues
Daniel Beck commented on JENKINS-20912 promoted-builds plugin NullPointerException on getParameterValues Cannot reproduce on Jenkins 1.596 and Promoted Builds 2.19 with pristine home directory (i.e. newly set up instance to investigate this). Please provide more information on the conditions needed for this issue to occur. Versions of Jenkins and the plugin involved, very detailed steps to reproduce the problem, exact stack trace (since details like line numbers may be different), etc. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-26308) LoadRunner Scenario Always Times Out
Connor Gilbert commented on JENKINS-26308 LoadRunner Scenario Always Times Out Added a 5 bounty This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Bart van der Schans edited a comment on JENKINS-18935 Make Subversion plugin support Subversion 1.8 removing comment, as it was misleading (newline in format file doesn't seem to make a difference) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-10686) Polling on slaves can hang
Alexey Larsky commented on JENKINS-10686 Polling on slaves can hang I use 1.3.33 version - latest in LTS. It periodically hungs on slaves. PS. Thank you. The script is working. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26380) Deadlock between Queue and Jenkins model
Steven Christou commented on JENKINS-26380 Deadlock between Queue and Jenkins model I created PR 1 to fix the OnceRetentionStrategy. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26318) Subversion Plug in 2.5 causes sporadic problems with MultiJob Plug in
Christian Grobauer updated JENKINS-26318 Subversion Plug in 2.5 causes sporadic problems with MultiJob Plug in Change By: Christian Grobauer (13/Jan/15 10:25 AM) Summary: Submersion Subversion Plugin2.5causessporadicproblemswithMultiJobPlugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-18125) Changelog empty or contains all changes
Liya Katz updated JENKINS-18125 Changelog empty or contains all changes Change By: Liya Katz (13/Jan/15 9:41 AM) Environment: Jenkins LTS 1. 509.1 595 Gitplugin: 1 2 . 3. 4 Gitclientplugin1 . 1.5. 0 GitHubAPIplugin1.59GitHubPlugin1.10GitHubPullRequestBuilder1.16-6 Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [support-core-plugin] (JENKINS-26409) ClientAbortException logged when cancelling a support bundle download
Félix Belzunce Arcos created JENKINS-26409 ClientAbortException logged when cancelling a support bundle download Issue Type: Bug Assignee: Félix Belzunce Arcos Components: support-core-plugin Created: 13/Jan/15 9:44 AM Description: When generating a support bundle through the GUI and finally selecting "Cancel" on the download window, `ClientAbortException: java.net.SocketException: Broken pipe` is logged in the catalina.log file. As a use decision, this should not occur as is it absolutely not an error. Environment: support-core-2.20 Tomcat Project: Jenkins Priority: Minor Reporter: Félix Belzunce Arcos This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cobertura-plugin] (JENKINS-26410) Dashboard links broken when inside folder
Oliver Gondža
created JENKINS-26410
Dashboard links broken when inside folder
Issue Type:
Bug
Assignee:
Oliver Gondža
Components:
cobertura-plugin
Created:
13/Jan/15 10:08 AM
Description:
I have a Dashboard view inside a folder with code coverage portlet. Job URLs in that portlet are broken as they use domain relative URLs without leading '/' like 'job/Folder/view/Result/job/Folder/job/my_job/42/' while i should be '/job/Folder/job/my_job/42/' (or '/job/Folder/view/Result/job/my_job/42/').
On first sight it seems fixable removing href attribute.
t:buildLink jobName="${r.parent.name}" job="${r.parent}" number="${r.number}" href="" /
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] [core] (JENKINS-26380) Deadlock between Queue and Jenkins model
stephenconnolly commented on JENKINS-26380 Deadlock between Queue and Jenkins model https://github.com/jenkinsci/durable-task-plugin/pull/2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-plugin] (JENKINS-26301) status.json raises 500 error
Emmanuel Mathot commented on JENKINS-26301 status.json raises 500 error Same issue for me, no way to find any useful information in the logs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory-plugin] (JENKINS-26403) SNI Support when using Artifactory behind HTTPS
Daniel Beck commented on JENKINS-26403 SNI Support when using Artifactory behind HTTPS That wasn't clear to me from the report. Thanks for the explanation! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-16290) git parameter plugin doesn't support Jenkins slave setup with git repos checked out only on slaves
Luc Sarzyniec commented on JENKINS-16290 git parameter plugin doesnt support Jenkins slave setup with git repos checked out only on slaves OK, thank you for your answer and your workaround BTW, any idea if it will be fixed soon ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26318) Submersion Plug in 2.5 causes sporadic problems with MultiJob Plug in
JM D commented on JENKINS-26318 Submersion Plug in 2.5 causes sporadic problems with MultiJob Plug in Facing the same issue, though I don't have MultiJob plug in installed, so this is not an interoperability issue. Reverted back Subversion Plugin to v2.4.5. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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
Henri Gomez commented on JENKINS-25267 Gitlab hook not building on merge request object Did there is a way with gitlab hook plugin to build on merge request (with contents to be merged) ? I playes with Gitlab Merge Request Plugin (https://github.com/jenkinsci/gitlab-merge-request-builder-plugin) but it seems no more maintened. I would be great to have its features included in Gitlab Hook. Any plan for ? Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26412) Advertize the slave process died
Oliver Gondža created JENKINS-26412 Advertize the slave process died Issue Type: Improvement Assignee: Oliver Gondža Components: core, remoting Created: 13/Jan/15 12:35 PM Description: When slave process is terminated an exception is logged in both slave log and build log. This is very confusing for users (especially when different exceptions can be thrown, see bellow). Register shutdown hook to notify channel counterparts that JVM is being turned off so Jenkins can act accordingly. JNLPLauncher: FATAL: java.io.EOFException hudson.remoting.RequestAbortedException: java.io.EOFException at hudson.remoting.Request.abort(Request.java:295) at hudson.remoting.Channel.terminate(Channel.java:814) at org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.java:616) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:111) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) at ..remote call to jnlp(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.Request.call(Request.java:171) at hudson.remoting.Channel.call(Channel.java:751) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:941) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:556) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.io.EOFException at org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.java:616) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:111) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) CommandLauncher: FATAL: java.io.IOException: Unexpected termination of the channel hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.abort(Request.java:295) at hudson.remoting.Channel.terminate(Channel.java:814) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) at ..remote call to jnlp(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.Request.call(Request.java:171) at hudson.remoting.Channel.call(Channel.java:751) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:173) at com.sun.proxy.$Proxy47.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979) at hudson.Launcher$ProcStarter.join(Launcher.java:388) at hudson.tasks.Maven.perform(Maven.java:328) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at
[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Bart van der Schans commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Hi, I ran into the same " (format '100')" error. Of course there is no such format (yet for a long time). The current format is '12' for 1.8.x. The problem seem to be that on a checkout no newline is added to the format file ".svn/format". It does read '12', but it doesn't add the newline and then the plugin reads the file as '100' instead of '12' (which could also be considered a bug). As a quick fix you can run: cd /your/jenkins/workspace; for f in $( ls */.svn/format ); do echo "12" $f ; done But after a run the value is overwritten again. Bart This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-24608) Test result link displays twice on matrix project page
Matthew Ayala commented on JENKINS-24608 Test result link displays twice on matrix project page I am having the same issue with Jenkins 1.596 and NUnit 0.16, this is without Matrix projects. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-25336) ABI name parsing is broken
Richard Thompson commented on JENKINS-25336 ABI name parsing is broken The ABI field needs to be made mandatory and accept google_apis/armeabi-v7a, google_apis/x86, google_apis/x86_64, default/armeabi-v7a, default/x86, default/x86_64. The ABI name invalid character replacement needs to be updated to replace the / with another character from a-zA-Z0-9._- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket-plugin] (JENKINS-26413) BitBucket trigger doesn't need to InitializeLogFile
Félix Belzunce Arcos created JENKINS-26413 BitBucket trigger doesnt need to InitializeLogFile Issue Type: Improvement Assignee: Félix Belzunce Arcos Components: bitbucket-plugin Created: 13/Jan/15 12:51 PM Description: BitBucket trigger doesn't need to InitializeLogFile. https://github.com/jenkinsci/bitbucket-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/BitBucketTrigger.java#L102 Project: Jenkins Priority: Minor Reporter: Félix Belzunce Arcos This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26414) Add support for new C4 instance types
Daniel Beck updated JENKINS-26414 Add support for new C4 instance types Change By: Daniel Beck (13/Jan/15 1:42 PM) Issue Type: Bug NewFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26411) Interrupt running builds when disconnecting the node
Oliver Gondža created JENKINS-26411 Interrupt running builds when disconnecting the node Issue Type: Improvement Assignee: Oliver Gondža Components: core Created: 13/Jan/15 12:04 PM Description: Interrupt build with meaningful message when slave disconnected from UI. Current implementation fail the build with: FATAL: hudson.remoting.Channel$OrderlyShutdown hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Request.abort(Request.java:295) at hudson.remoting.Channel.terminate(Channel.java:814) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1029) at hudson.remoting.Channel$2.handle(Channel.java:483) at hudson.remoting.AbstractByteArrayCommandTransport$1.handle(AbstractByteArrayCommandTransport.java:61) at org.jenkinsci.remoting.nio.NioChannelHub$2.run(NioChannelHub.java:597) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:111) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) at ..remote call to jnlp(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.Request.call(Request.java:171) at hudson.remoting.Channel.call(Channel.java:751) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:173) at com.sun.proxy.$Proxy47.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1029) at hudson.remoting.Channel$2.handle(Channel.java:483) at hudson.remoting.AbstractByteArrayCommandTransport$1.handle(AbstractByteArrayCommandTransport.java:61) at org.jenkinsci.remoting.nio.NioChannelHub$2.run(NioChannelHub.java:597) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:111) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: Command close created at at hudson.remoting.Command.init(Command.java:56) at hudson.remoting.Channel$CloseCommand.init(Channel.java:1023) at hudson.remoting.Channel$CloseCommand.init(Channel.java:1021) at hudson.remoting.Channel.close(Channel.java:1104) at hudson.remoting.Channel.close(Channel.java:1087) at
[JIRA] [credentials-plugin] (JENKINS-26099) Configurable ID for Credentials
SCM/JIRA link daemon commented on JENKINS-26099 Configurable ID for Credentials Code changed in jenkins User: Jesse Glick Path: src/main/java/com/cloudbees/jenkins/plugins/sshcredentials/impl/BaseSSHUser.java src/main/java/com/cloudbees/jenkins/plugins/sshcredentials/impl/BasicSSHUserPassword.java src/main/java/com/cloudbees/jenkins/plugins/sshcredentials/impl/BasicSSHUserPrivateKey.java http://jenkins-ci.org/commit/ssh-credentials-plugin/397bec75840835c953708f006d4ad74a7f9b5926 Log: Making BaseSSHUser extend BaseStandardCredentials simplifies code and may be helpful for JENKINS-26099. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-25336) ABI name parsing is broken
Richard Thompson commented on JENKINS-25336 ABI name parsing is broken There is a pull request for the AVD naming here https://github.com/jenkinsci/android-emulator-plugin/pull/42. It would be good to get this merged please as it's stopping use of Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-18125) Changelog empty or contains all changes
Mark Waite commented on JENKINS-18125 Changelog empty or contains all changes No, I don't have an estimation when it will be fixed. I don't have access to GitHub Enterprise. I cannot duplicate the problem. The bug report has not included enough instructions to show me that others can duplicate the problem. I won't investigate the bug more deeply without detailed instructions which allow me to duplicate the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket-plugin] (JENKINS-26413) BitBucket trigger doesn't need to InitializeLogFile
SCM/JIRA link daemon commented on JENKINS-26413 BitBucket trigger doesnt need to InitializeLogFile Code changed in jenkins User: Nicolas De loof Path: src/main/java/com/cloudbees/jenkins/plugins/BitBucketTrigger.java http://jenkins-ci.org/commit/bitbucket-plugin/284d44828abe7b4b96744b93fa5187699698e616 Log: Merge pull request #5 from fbelzunc/JENKINS-26413 FIXED JENKINS-26413 BitBucket trigger doesn't need to InitializeLogFile Compare: https://github.com/jenkinsci/bitbucket-plugin/compare/3e96df05dbf8...284d44828abe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket-plugin] (JENKINS-26413) BitBucket trigger doesn't need to InitializeLogFile
SCM/JIRA link daemon resolved JENKINS-26413 as Fixed BitBucket trigger doesnt need to InitializeLogFile Change By: SCM/JIRA link daemon (13/Jan/15 1:00 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] [bitbucket-plugin] (JENKINS-26413) BitBucket trigger doesn't need to InitializeLogFile
SCM/JIRA link daemon commented on JENKINS-26413 BitBucket trigger doesnt need to InitializeLogFile Code changed in jenkins User: Felix Belzunce Arcos Path: src/main/java/com/cloudbees/jenkins/plugins/BitBucketTrigger.java http://jenkins-ci.org/commit/bitbucket-plugin/663e539aabbaf8c3eaf1a2686e1e65bc5009d55e Log: JENKINS-26413 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26414) Add support for new C4 instance types
Trevor Baker created JENKINS-26414 Add support for new C4 instance types Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 13/Jan/15 1:30 PM Description: Please add support for the new C4 instance types. https://aws.amazon.com/blogs/aws/now-available-new-c4-instances/ Project: Jenkins Priority: Major Reporter: Trevor Baker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-26416) Jenkins Does Not Confirm An Executor Matches Its Node Requirements Before Running A Job On It
Kevin Randino
created JENKINS-26416
Jenkins Does Not Confirm An Executor Matches Its Node Requirements Before Running A Job On It
Issue Type:
Bug
Assignee:
vjuranek
Components:
groovy-plugin
Created:
13/Jan/15 3:38 PM
Description:
I created a job which contains a groovy script. The groovy script's job is to put a large number of builds into the Jenkins queue which are set to wait until machines with a specific label are found to run them. Only one of these jobs is set to run at a time on each machine.
By default, machines are set with the label "uninstalled". Once this job runs on them, that label is changed from "uninstalled" to "installing" and when finished "installed". The job is only allowed to run on nodes with the label "uninstalled" on them.
Right now, if a single machine has the "uninstalled" label attached to it, all of the jobs in the queue will set themselves to run on that node. Once a single job in the queue starts on that machine, that "uninstalled" label is set to "installing", which SHOULD take it out of the running for the other jobs to run on it. When that job completes, however, the jobs in the queue will still run on that node, even though it no longer has an "uninstalled" label.
Jenkins' queue should be changed so that before a job is transferred from the "Buildable" queue into the executor, it should check first to make sure that it still complies with the labels on the node it plans to build on. At random times Jenkins will catch on before the build actually goes off, but more often than not, all of the jobs in the queue will run on this one node instead of waiting for other ones to come in.
I have been looking at the Jenkins code for the queue and the maintain() method seems to be what needs changing here. It appears as though the JobOffer occurs before a last minute check for blockers that occurs on line 62 of the following code. Can anyone confirm if what I am looking at is right?
Queue.java
public synchronized void maintain() {
LOGGER.log(Level.FINE, "Queue maintenance started {0}", this);
// The executors that are currently waiting for a job to run.
MapExecutor,JobOffer parked = new HashMapExecutor,JobOffer();
{// update parked
for (Computer c : Jenkins.getInstance().getComputers()) {
for (Executor e : c.getExecutors()) {
if (e.isParking()) {
parked.put(e,new JobOffer(e));
}
}
}
}
{// blocked - buildable
for (BlockedItem p : new ArrayListBlockedItem(blockedProjects.values())) {// copy as we'll mutate the list
if (!isBuildBlocked(p) allowNewBuildableTask(p.task)) {
// ready to be executed
Runnable r = makeBuildable(new BuildableItem(p));
if (r != null) {
p.leave(this);
r.run();
}
}
}
}
// waitingList - buildable/blocked
while (!waitingList.isEmpty()) {
WaitingItem top = peek();
if (top.timestamp.compareTo(new GregorianCalendar())0)
break; // finished moving all ready items from queue
top.leave(this);
Task p = top.task;
if (!isBuildBlocked(top) allowNewBuildableTask(p)) {
// ready to be executed immediately
Runnable r = makeBuildable(new BuildableItem(top));
if (r != null) {
r.run();
} else {
new BlockedItem(top).enter(this);
}
} else {
// this can't be built now because another build is in progress
// set this project aside.
new BlockedItem(top).enter(this);
}
}
final QueueSorter s = sorter;
if (s != null)
s.sortBuildableItems(buildables);
// allocate buildable jobs to executors
for
[JIRA] [ghprb-plugin] (JENKINS-26415) Default success/failure message of GHPRB can't be saved
yan bi commented on JENKINS-26415 Default success/failure message of GHPRB cant be saved Actually, the change of default message in jenkins system configure is setted, because after saving it, the comment message is changed. But when I look into System Configure, it was still the standard default message as "Test FAILed" or "Test PASSed" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-26416) Jenkins Does Not Confirm A Node's Executor Matches Its Label Requirements Before Running A Job On It
Daniel Beck resolved JENKINS-26416 as Not A Defect Jenkins Does Not Confirm A Nodes Executor Matches Its Label Requirements Before Running A Job On It This has nothing to do with Groovy Plugin. It's not an issue report either. To get support in how to use Jenkins, email the mailing lists or join #jenkins on Freenode. That said, Jenkins caches label assignments. It may work if you force the cache to update. Check the sources. Change By: Daniel Beck (13/Jan/15 3:44 PM) Status: Open Resolved Assignee: vjuranek Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-24887) Workflow support of Copyartifact
Jesse Glick started work on JENKINS-24887 Workflow support of Copyartifact Change By: Jesse Glick (13/Jan/15 3:07 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] [copyartifact-plugin] (JENKINS-24887) Workflow support of Copyartifact
Jesse Glick assigned JENKINS-24887 to Tom FENNELLY Workflow support of Copyartifact Change By: Jesse Glick (13/Jan/15 3:07 PM) Assignee: TomFENNELLY This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Bart van der Schans commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Looking into the .svn/wc.db version: $ sqlite3 .svn/wc.db "PRAGMA user_version" 100 And on a correctly 1.8.11 checkout repo: $ sqlite3 .svn/wc.db "PRAGMA user_version" 31 So it looks like the wrong version gets stored on a clean checkout. I've also tried with svnkit 1.8.7 (1.8.6 is bundled), but that makes no difference. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-26415) Default success/failure message of GHPRB can't be saved!!
yan bi created JENKINS-26415 Default success/failure message of GHPRB cant be saved!! Issue Type: Bug Assignee: yan bi Components: github-plugin Created: 13/Jan/15 3:12 PM Description: When I want to change the default success or failure messsage of GHPRB in Jenkins System Configure, it doesn't work. Every time after I click the save button, the setting-up that I have done is gone! Environment: debian Project: Jenkins Priority: Critical Reporter: yan bi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-26415) Default success/failure message of GHPRB can't be saved
Daniel Beck updated JENKINS-26415 Default success/failure message of GHPRB cant be saved Change By: Daniel Beck (13/Jan/15 3:24 PM) Summary: Defaultsuccess/failuremessageofGHPRBcantbesaved !! Assignee: yanbi HonzaBrázdil Component/s: ghprb-plugin Component/s: github-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] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Paulo Moreira commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Hello, I have installed and have no problems with it! Windows Node: svn, version 1.8.11 Linux Node: svn, version 1.8.8 Jenkins - configuration - Subversion = 1.8 Subversion Plugin = 2.5 All jobs migrated from 1.7, all do: Always check out a fresh copy Delete workspace before build starts This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-26416) Jenkins Does Not Confirm A Node's Executor Matches Its Label Requirements Before Running A Job On It
Kevin Randino updated JENKINS-26416 Jenkins Does Not Confirm A Nodes Executor Matches Its Label Requirements Before Running A Job On It Change By: Kevin Randino (13/Jan/15 3:39 PM) Summary: JenkinsDoesNotConfirm An ANodes ExecutorMatchesIts Node Label RequirementsBeforeRunningAJobOnIt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26380) Deadlock between Queue and Jenkins model
Jesse Glick updated JENKINS-26380 Deadlock between Queue and Jenkins model Change By: Jesse Glick (13/Jan/15 3:37 PM) Labels: deadlockdocker jenkins regression This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-26417) Allow to customize refspec/tags of the clone/fetch commands
Vincent Latombe created JENKINS-26417 Allow to customize refspec/tags of the clone/fetch commands Issue Type: New Feature Assignee: Nicolas De Loof Components: git-client-plugin Created: 13/Jan/15 3:54 PM Description: When using custom refspecs, we may not want to fetch the usual refs/heads/:refs/remotes/remote/ that is usually fetched when cloning a repository. Also, for repositories that contain a lot of tags, it may not be interesting to fetch tags in a CI job, as what is usually needed is one branch's head. Project: Jenkins Priority: Major Reporter: Vincent Latombe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-26416) Jenkins Does Not Confirm A Node's Executor Matches Its Label Requirements Before Running A Job On It
Daniel Beck commented on JENKINS-26416 Jenkins Does Not Confirm A Nodes Executor Matches Its Label Requirements Before Running A Job On It Jenkins core is not acting as expected jenkins.model.Jenkins.trimLabels() documents this specific issue (Label.reset() does not, presumably because it's non-public). The problem is that, even if it's so accessible through the use of plugins, you are programming Jenkins using its internal API. So you cannot disregard internal structures or their constraints. Additionally, you're way beyond what would usually be possible to do with labels so it's not unreasonable that your use case is not covered by Jenkins internals without some additional work and understanding on your part. If Jenkins wouldn't update effective labels after submitting the slave node config form, it'd be different. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-26416) Jenkins Does Not Confirm A Node's Executor Matches Its Label Requirements Before Running A Job On It
Kevin Randino commented on JENKINS-26416 Jenkins Does Not Confirm A Nodes Executor Matches Its Label Requirements Before Running A Job On It Fair enough, I suppose I am expecting more out of Jenkins than the average user would need, and the average case in which they would encounter this issue is nearly nil. I apologize for the false bug report, when working with Groovy changes I will stick to the proper mailing lists or IRC from now on. Sorry for the waste of time, your help is greatly appreciated though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-26416) Jenkins Does Not Confirm A Node's Executor Matches Its Label Requirements Before Running A Job On It
Kevin Randino commented on JENKINS-26416 Jenkins Does Not Confirm A Nodes Executor Matches Its Label Requirements Before Running A Job On It Hey Daniel, I'm realizing now that I should have set it as a "core" issue instead of a groovy-plugin one, my mistake on that. I still believe that this is a Jenkins issue however as Jenkins core is not acting as expected. I would never expect Jenkins to run a job on a node that is not suited for that job through the assigned labels. Cached or not, Jenkins should still run a sanity check on its jobs before running them. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [libvirt-slave-plugin] (JENKINS-12523) Could not initialize class org.libvirt.Connect
Florent Poinsaut commented on JENKINS-12523 Could not initialize class org.libvirt.Connect Nice job ! I take a look to this page : https://wiki.jenkins-ci.org/display/JENKINS/Pull+Request+to+Repositories However, if your pull request doesn't seem to be getting any attention after a week or so, then unfortunately we don't have existing developers reviewing incoming pull requests. Perhaps the repository is not actively maintained any more. In this case, we don't want your pull request to be in limbo forever, and hence we'd like you to escalate as follows: If you are comfortable with the change and you feel it should be merged in the absence of a review, please drop us an e-mail on the dev list and ask for commit access (please provide your GitHub account name and the repository name you would like to contribute to). See the later section for more information about what you should be careful about. As explained in Governance Document#Howtojointheproject, we give out commit access to anyone who asks for it. Once the committership is granted, please merge the change, and consider making a new release. If you feel that the code really needs to be reviewed by someone more knowledgeable, then similarly drop us an e-mail on the dev list and tell us why/what should be reviewed. And If your job is not merged next week, you can ask it by mail. Regards, This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-26416) Jenkins Does Not Confirm A Node's Executor Matches Its Label Requirements Before Running A Job On It
Daniel Beck commented on JENKINS-26416 Jenkins Does Not Confirm A Nodes Executor Matches Its Label Requirements Before Running A Job On It Take a guess why I know so well how labels caching works So, yeah, Jenkins opts for providing access to the massive internal (plugin + Groovy scripts) API basically everything it has, including the ugly parts rather than a shiny facade that isn't nearly powerful enough. I think it's generally the right choice, but it comes with issues like this one. Note that the main problem here may be that using labels for something as dynamic as this looks like the wrong approach (as the caching indicates, they are thought of as fairly static). Check out the extension points modifying queue behavior (e.g. QueueTaskDispatcher), maybe what you're doing would be best implemented in a 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] [promoted-builds-plugin] (JENKINS-20912) promoted-builds plugin NullPointerException on getParameterValues
Daniel Beck commented on JENKINS-20912 promoted-builds plugin NullPointerException on getParameterValues In other words, you experience a completely unrelated issue that has nothing to do with the one reported here. Read the description, this is about automatic promotion resulting in an NPE in Promotion.getParameterValues, while yours is manual promotion resulting in a CCE in Status.doBuild. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-26099) Configurable ID for Credentials
SCM/JIRA link daemon commented on JENKINS-26099 Configurable ID for Credentials Code changed in jenkins User: Jesse Glick Path: src/main/java/com/cloudbees/plugins/credentials/impl/BaseStandardCredentials.java src/main/java/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl.java src/main/java/com/cloudbees/plugins/credentials/impl/UsernamePasswordCredentialsImpl.java src/main/resources/com/cloudbees/plugins/credentials/impl/BaseStandardCredentials/help-description.html src/main/resources/com/cloudbees/plugins/credentials/impl/BaseStandardCredentials/help-description_ja.html src/main/resources/com/cloudbees/plugins/credentials/impl/BaseStandardCredentials/help-id.html src/main/resources/com/cloudbees/plugins/credentials/impl/BaseStandardCredentials/id-and-description.jelly src/main/resources/com/cloudbees/plugins/credentials/impl/BaseStandardCredentials/id-and-description_de.properties src/main/resources/com/cloudbees/plugins/credentials/impl/BaseStandardCredentials/id-and-description_ja.properties src/main/resources/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl/credentials.jelly src/main/resources/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl/credentials_de.properties src/main/resources/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl/credentials_ja.properties src/main/resources/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl/help-description.html src/main/resources/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl/help-description_ja.html src/main/resources/com/cloudbees/plugins/credentials/impl/UsernamePasswordCredentialsImpl/credentials.jelly src/main/resources/com/cloudbees/plugins/credentials/impl/UsernamePasswordCredentialsImpl/credentials_de.properties src/main/resources/com/cloudbees/plugins/credentials/impl/UsernamePasswordCredentialsImpl/credentials_ja.properties src/main/resources/com/cloudbees/plugins/credentials/impl/UsernamePasswordCredentialsImpl/help-description.html src/main/resources/com/cloudbees/plugins/credentials/impl/UsernamePasswordCredentialsImpl/help-description_ja.html http://jenkins-ci.org/commit/credentials-plugin/d993c3879e07809edb0af847076eedcd984d7d7c Log: JENKINS-26099 First draft of ability to pick an ID for credentials. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26420) Specifying sha1 without branch name in the notifyCommit URL triggers builds for all jobs (potentially hundreds)
Karl Ostmo created JENKINS-26420 Specifying sha1 without branch name in the notifyCommit URL triggers builds for all jobs (potentially hundreds) Issue Type: Improvement Assignee: Nicolas De Loof Components: git-plugin Created: 13/Jan/15 11:00 PM Description: If all Jenkins jobs are configured for polling of URL of the Git repository, then invoking curl on the following URL will spawn builds for all of the jobs: http://yourserver/jenkins/git/notifyCommit?url="" of the Git repositorysha1=commit ID Since this URL doesn't require authentication even for secured Jenkins, any user can (accidentally) cause Denial of Service while all Jobs run for an arbitrary commit ID. There may be hundreds of jobs configured for polling, so this can clog up the build queue for a long time. Project: Jenkins Priority: Major Reporter: Karl Ostmo This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-26419) *ResultDir* and *TestDir* build-in UFT environment variables are set to _Path of the folder in which the test is located_
Faisal Ali
created JENKINS-26419
*ResultDir* and *TestDir* build-in UFT environment variables are set to _Path of the folder in which the test is located_
Issue Type:
Bug
Assignee:
Ofir Shaked
Components:
hp-application-automation-tools-plugin
Created:
13/Jan/15 8:19 PM
Description:
This JIRA is the simplification of JIRA "JENKINS-25877".
Default values for the following build-in UFT (Unified Functional Testing) Environment Variables are :
Environment.Value("ResultDir"): Folder Path where the current TEST RESULTS are saved. e.g \path_to_the_test\RES#
Environment.Value("TestDir") : Path of the folder in which the test is located. e.g \path_to_the_test
But using hp-application-automation-tools-plugin, The values of both these build-in UFT Environment Variables are overwritten and set to the test location. Therefore, not creating the (ResultDir) RES# folder e.g
Environment.Value("ResultDir"):Path of the folder in which the test is located
Environment.Value("TestDir") : Path of the folder in which the test is located
Project:
Jenkins
Priority:
Minor
Reporter:
Faisal Ali
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-26419) *ResultDir* and *TestDir* build-in UFT environment variables are set to _Path of the folder in which the test is located_
Faisal Ali updated JENKINS-26419 *ResultDir* and *TestDir* build-in UFT environment variables are set to _Path of the folder in which the test is located_ Change By: Faisal Ali (13/Jan/15 8:22 PM) Priority: Minor Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-26419) *ResultDir* and *TestDir* build-in UFT environment variables are set to _Path of the folder in which the test is located_
Faisal Ali updated JENKINS-26419 *ResultDir* and *TestDir* build-in UFT environment variables are set to _Path of the folder in which the test is located_ Change By: Faisal Ali (13/Jan/15 8:21 PM) Description: ThisJIRAisthesimplificationofJIRAJENKINS-25877.Defaultvaluesforthefollowingbuild-inUFT(UnifiedFunctionalTesting)*EnvironmentVariables*are:*Environment.Value(ResultDir)*:_FolderPathwherethecurrent*+TESTRESULTS+*aresaved.e.g\path_to_the_test\RES#_*Environment.Value(TestDir)*:_Pathofthefolderinwhichthetestislocated.e.g\path_to_the_test_h4.Butusing * + _hp-application-automation-tools-plugin_ * + ,Thevaluesofboththesebuild-inUFTEnvironmentVariablesareoverwrittenandsettothe*+testlocation+*.Therefore,notcreatingthe(ResultDir)RES#foldere.g*Environment.Value(ResultDir)*:_Pathofthefolderinwhichthetestislocated_*Environment.Value(TestDir)*:_Pathofthefolderinwhichthetestislocated_ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
