[JIRA] [core] (JENKINS-27405) Jenkins Windows Batch Command does not show output of the executable
Daniel Beck resolved JENKINS-27405 as Not A Defect Jenkins Windows Batch Command does not show output of the executable This is an issue tracker, not a support site. And for a bug report, this doesn't contain nearly enough information. Besides, your Jenkins version is obsolete. Change By: Daniel Beck (13/Mar/15 7:00 AM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-24673) SimpleBuildWrapper
Marcus Jacobsson commented on JENKINS-24673 SimpleBuildWrapper Was looking a bit more on this now that I got some free time again, the only thing we need right now is to be able to create a wrapper for the listener output. So we can filter the output and color code the output. For example we have a plugin that formats or output simular to https://wiki.jenkins-ci.org/display/JENKINS/Timestamper and https://wiki.jenkins-ci.org/display/JENKINS/AnsiColor+Plugin as well as a plugin to filer out passwords from the console. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-27164) docker-build-publish-plugin broken compatibility with token-macro-plugin
SCM/JIRA link daemon commented on JENKINS-27164 docker-build-publish-plugin broken compatibility with token-macro-plugin Code changed in jenkins User: Michael Neale Path: src/main/java/com/cloudbees/dockerpublish/DockerBuilder.java http://jenkins-ci.org/commit/docker-build-publish-plugin/44bf30f1468af3e2a5ace3a7a03d95dcf65949fd Log: Fix for JENKINS-27164. Token expand before tag splitting This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27406) Provide an option to enable remembering of last entered build parameter
Benjamin Asbach created JENKINS-27406 Provide an option to enable remembering of last entered build parameter Issue Type: Improvement Assignee: Unassigned Components: core Created: 13/Mar/15 7:43 AM Description: I'll suggest an option to enabled remembering of last used build parameter (at least for string and boolean parameters). For example we need to build for some hours with some specific parameter, afterwards with some others. This might vary multiple times a day. So the default parameter is not the right mechanism. The default mechanism might be reused. I could image that you've another option for some parameters "remember last provided parameter" which automatically fills the default parameter value after the parameter page. Project: Jenkins Priority: Minor Reporter: Benjamin Asbach This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-27164) docker-build-publish-plugin broken compatibility with token-macro-plugin
Michael Neale resolved JENKINS-27164 as Fixed docker-build-publish-plugin broken compatibility with token-macro-plugin Fixed in 0.12 which should be in a maven repo near you shortly. Thanks for spotting this and also diagnosing what was the cause - made the fix easy. Change By: Michael Neale (13/Mar/15 7:43 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27406) Provide an option to enable remembering of last used build parameter
Benjamin Asbach updated JENKINS-27406 Provide an option to enable remembering of last used build parameter Change By: Benjamin Asbach (13/Mar/15 7:44 AM) Summary: Provide an option to enable remembering of last entered used build parameter This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27407) Build Wait for completion should be false
Satpal Chander created JENKINS-27407 Build Wait for completion should be false Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 13/Mar/15 8:37 AM Description: When using the snippet generator for build. If the wait for completion is not checked then the snippet generated is: build job: 'my_job', wait: false When the wait for completion is checked: build job: 'my_job' This implies that the default is wait for completion Given that the user has to select (check) 'wait for completion' the default should be false and not assumed that the user want wait for completion by default e.g: build job: 'my_job' this should be Not wait for completion build job: 'my_job', wait: true I'm pretty sure that wait for completion has not been the default for downstream jobs. Environment: Current workflow plugin Project: Jenkins Labels: plugin workflow Priority: Minor Reporter: Satpal Chander This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27407) Build Wait for completion should be false
Daniel Beck updated JENKINS-27407 Build Wait for completion should be false Alternatively, check the box by default or invert the meaning of the checkbox to "Don't wait". Change By: Daniel Beck (13/Mar/15 8:46 AM) Issue Type: Bug Improvement Labels: plugin workflow This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27358) Unable to find a build for artifact copy when parameters tag is empty
Michal Kovarik closed JENKINS-27358 as Cannot Reproduce Unable to find a build for artifact copy when parameters tag is empty Change By: Michal Kovarik (13/Mar/15 8:46 AM) Status: Open Closed Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-27358) Unable to find a build for artifact copy when parameters tag is empty
Michal Kovarik commented on JENKINS-27358 Unable to find a build for artifact copy when parameters tag is empty I wasn't able to reproduced on new jenkins. I fixed this issue by downgrading plugin back to version 1.33 and update to 1.35. And now it works. I was using Jenkins ver. 1.565.1 then I upgraded via yum (on RHEL machine) to Jenkins ver. 1.596.1. So there was probably some misconfiguration. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27407) Build Wait for completion should be false
Satpal Chander commented on JENKINS-27407 Build Wait for completion should be false ~daniel Need to ensure that the default behaviour of build isn't changed. For example in JobDSL the default for downstream is not to block, the user makes a diliberate choice to select blockdownstream. Hope that makes sense. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27407) Build Wait for completion should be false
Daniel Beck commented on JENKINS-27407 Build Wait for completion should be false That's why I propose to change the UI rather than change the default value if not explicitly set. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [openshift-deployer-plugin] (JENKINS-27408) Add region selection to settings of a project
Andreas Mack created JENKINS-27408 Add region selection to settings of a project Issue Type: Improvement Assignee: Siamak Sadeghianfar Components: openshift-deployer-plugin Created: 13/Mar/15 9:09 AM Description: Hi, it would be great if one could specify the region in openshift online to deploy to. Is this already possible with environment? Thanks! Project: Jenkins Priority: Minor Reporter: Andreas Mack This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-plugin] (JENKINS-27409) adding base clearcase on multiple scm plugin causes exceptions even for basic configuration
Paul Morris
created JENKINS-27409
adding base clearcase on multiple scm plugin causes exceptions even for basic configuration
Issue Type:
Bug
Assignee:
Vincent Latombe
Components:
clearcase-plugin, multiple-scms-plugin
Created:
13/Mar/15 9:22 AM
Description:
I added my Base Clearcase config after adding a perforce config. And got an exception.
Then i tried just with the clear case config and got the exception just the same. Both configs work fine individually, but the clear case one does not work with the multiple SCM's plugin:
javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class org.jenkinsci.plugins.multiplescms.MultiSCM from {"value":"4","scmList":{"viewname":"nightly_${JOB_NAME}_view","viewpath":"ccview","configspec":"element * CHECKEDOUT\nelement * /main/LATEST","extractLoadRules":{"loadrules":"RISiTools\\DotNetTools\\StyleCop"},"useupdate":true,"changeset":{"value":"branch"},"branch":"main","label":"","excludedRegions":"","mkviewoptionalparam":"","filterOutDestroySubBranchEvent":false,"rmviewonrename":false,"multiSitePollBuffer":"0","stapler-class":"hudson.plugins.clearcase.ClearCaseSCM","kind":"hudson.plugins.clearcase.ClearCaseSCM","$class":"hudson.plugins.clearcase.ClearCaseSCM"}}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java: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 hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
[JIRA] [core] (JENKINS-26580) For JNLP slaves the master-slave communication should be encrypted
SCM/JIRA link daemon commented on JENKINS-26580 For JNLP slaves the master-slave communication should be encrypted Code changed in jenkins User: Akshay Dayal Path: src/main/java/hudson/remoting/engine/JnlpProtocol1.java src/main/java/hudson/remoting/engine/JnlpProtocol2.java http://jenkins-ci.org/commit/remoting/9a427e0614c7fea4a7d77cd7a4ded90ff2023c9b Log: JENKINS-26580 Add more documentation for the JNLP protocols. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-26580) For JNLP slaves the master-slave communication should be encrypted
SCM/JIRA link daemon commented on JENKINS-26580 For JNLP slaves the master-slave communication should be encrypted Code changed in jenkins User: Akshay Dayal Path: src/main/java/hudson/remoting/Engine.java src/main/java/hudson/remoting/engine/EngineUtil.java src/main/java/hudson/remoting/engine/JnlpProtocol.java src/main/java/hudson/remoting/engine/JnlpProtocol1.java src/main/java/hudson/remoting/engine/JnlpProtocol2.java src/main/java/hudson/remoting/engine/JnlpProtocolFactory.java src/main/java/org/jenkinsci/remoting/engine/EngineUtil.java src/main/java/org/jenkinsci/remoting/engine/JnlpProtocol.java src/main/java/org/jenkinsci/remoting/engine/JnlpProtocol1.java src/main/java/org/jenkinsci/remoting/engine/JnlpProtocol2.java src/main/java/org/jenkinsci/remoting/engine/JnlpProtocolFactory.java src/test/java/hudson/remoting/engine/EngineUtilTest.java src/test/java/hudson/remoting/engine/JnlpProtocol1Test.java src/test/java/hudson/remoting/engine/JnlpProtocol2Test.java src/test/java/org/jenkinsci/remoting/engine/EngineUtilTest.java src/test/java/org/jenkinsci/remoting/engine/JnlpProtocol1Test.java src/test/java/org/jenkinsci/remoting/engine/JnlpProtocol2Test.java http://jenkins-ci.org/commit/remoting/82096802749f87044727605efb978b19ae636382 Log: JENKINS-26580 Updates based on feedback. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-26580) For JNLP slaves the master-slave communication should be encrypted
SCM/JIRA link daemon commented on JENKINS-26580 For JNLP slaves the master-slave communication should be encrypted Code changed in jenkins User: Akshay Dayal Path: pom.xml src/main/java/hudson/remoting/Engine.java src/main/java/hudson/remoting/engine/EngineUtil.java src/main/java/hudson/remoting/engine/JnlpProtocol.java src/main/java/hudson/remoting/engine/JnlpProtocol1.java src/main/java/hudson/remoting/engine/JnlpProtocol2.java src/main/java/hudson/remoting/engine/JnlpProtocolFactory.java src/test/java/hudson/remoting/engine/EngineUtilTest.java src/test/java/hudson/remoting/engine/JnlpProtocol1Test.java src/test/java/hudson/remoting/engine/JnlpProtocol2Test.java http://jenkins-ci.org/commit/remoting/90dd966a0c40c900dd58347fbfbc7958d8b40b65 Log: JENKINS-26580 Refactor slave JNLP engine to make it easier to add more protocols in the future. The engine will now call a factory that returns a list of protocols to try in order. Developers can implement new protocols in separate classes and add them to the factory to be used. Added tests for existing protocols. I noticed the Engine class doesn't have a corresponding Test class. It would be nice to add one, but I think it needs more refactoring before it would be realistic to add tests for it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26580) For JNLP slaves the master-slave communication should be encrypted
SCM/JIRA link daemon commented on JENKINS-26580 For JNLP slaves the master-slave communication should be encrypted Code changed in jenkins User: Akshay Dayal Path: src/main/java/hudson/remoting/Engine.java http://jenkins-ci.org/commit/remoting/9fb70849ac5edd38e26ca6f9200f2c3aa753e398 Log: JENKINS-26580 Fixed indentation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Jan Hollevoet commented on JENKINS-23232 SEVERE: I/O error in channel Chunked connection Now I am at 1.565.3. Right after the upgrade, this error was still hitting us. Then I reconfigured all Windows slaves as JNLP nodes with the same revision of the client software (2.46). After this, the situation improved a lot. The number /usr/sbin/lsof | grep protocol | grep [jenkins-pid] | wc -l increased less fast than before. And the server is much more stable. I have the impression that the Windows clients are the root cause of the error. Maybe I should reconfigure them simply as SSH slaves. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-blocker-plugin] (JENKINS-27402) Timer task hudson.model.Queue$MaintainTask@77a17751 failed: doesn't trigger more builds
SCM/JIRA link daemon commented on JENKINS-27402 Timer task hudson.model.Queue$MaintainTask@77a17751 failed: doesn't trigger more builds Code changed in jenkins User: cigam Path: src/main/java/hudson/plugins/buildblocker/BlockingJobsMonitor.java http://jenkins-ci.org/commit/build-blocker-plugin/c897d676f06275c60ca2f0081c475b082c837f84 Log: Merged Pull Requests #2 (Added support for the Folders plugin) and #3 (Regex validation JENKINS-27402) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25270) Add option to disable configuration confirmation dialog
Jan Mashat commented on JENKINS-25270 Add option to disable configuration confirmation dialog I agree that it's quite annoying - and we're not using CVS - so I installed a browser plugin to block all confirmation dialogs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27410) Use of Environment Variable in Script File Path for Shell Scripts should be posssible
Heiner Tittelbach created JENKINS-27410 Use of Environment Variable in Script File Path for Shell Scripts should be posssible Issue Type: Improvement Assignee: Gregory Boissinot Components: scripttrigger-plugin Created: 13/Mar/15 10:13 AM Description: Environment Variable in Script File Path for Shell Scripts is not resolved. The script is not found. Project: Jenkins Priority: Minor Reporter: Heiner Tittelbach This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-blocker-plugin] (JENKINS-27411) Validate whether a regexp is well formatted
Victor Martinez created JENKINS-27411 Validate whether a regexp is well formatted Issue Type: Improvement Assignee: Unassigned Components: build-blocker-plugin Created: 13/Mar/15 10:18 AM Description: As I Jenkins user I would like to have a way to validate whether a particular regex is well formatted beforehand. There was a bug which has been already fixed ( JENKINS-27402 ) but still if you don't specify the right regex it won't apply properly and might be hard to debug. Project: Jenkins Priority: Minor Reporter: Victor Martinez This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27412) Stability issues faced with Jenkins 1.596.1 due to blocked threads
Ludovic Vercruysse created JENKINS-27412 Stability issues faced with Jenkins 1.596.1 due to blocked threads Issue Type: Bug Assignee: Unassigned Attachments: threaddump_jenkins.txt Components: core Created: 13/Mar/15 10:21 AM Description: Dear, In the ticket https://issues.jenkins-ci.org/browse/JENKINS-27379, I mentioned that we were facing issues with our Jenkins instance (based on the previous LTS 1.580.3) and you advised us to upgrade our instances to the new LTS 1.596.1. This has been done yesterday, but we are still facing stability issues due to blocked threads. Could you please investigate, based on the threaddump enclosed to this ticket and advice us on what we could check / do ? Best regards Project: Jenkins Priority: Blocker Reporter: Ludovic Vercruysse This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27379) Stability issues faced with Jenkins 1.580.3 due to blocked threads
Ludovic Vercruysse closed JENKINS-27379 as Cannot Reproduce Stability issues faced with Jenkins 1.580.3 due to blocked threads I close this ticket, as we have upgraded our version to the latest LTS 1.596.1. As we are still facing the same issue, another JIRA ticket has been created: JENKINS-27412 Follow-up will be done in JENKINS-27412. Change By: Ludovic Vercruysse (13/Mar/15 10:23 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-blocker-plugin] (JENKINS-27411) Validate whether a regexp is well formatted
Victor Martinez updated JENKINS-27411 Validate whether a regexp is well formatted Change By: Victor Martinez (13/Mar/15 10:23 AM) Attachment: Screen Shot 2015-03-13 at 11.21.40.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27412) Stability issues faced with Jenkins 1.596.1 due to blocked threads
Daniel Beck commented on JENKINS-27412 Stability issues faced with Jenkins 1.596.1 due to blocked threads Please install Support Core Plugin and create a support bundle from it, and attach it to this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26300) CPS interpreter fails on calls to find(), findAll() default methods
Jesse Glick resolved JENKINS-26300 as Duplicate CPS interpreter fails on calls to find(), findAll() default methods Change By: Jesse Glick (13/Mar/15 10:48 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21251) Slave channel timeout seemingly caused by usage of System.currentTimeMillis()
SCM/JIRA link daemon commented on JENKINS-21251 Slave channel timeout seemingly caused by usage of System.currentTimeMillis() Code changed in jenkins User: James Nord Path: src/main/java/hudson/remoting/AtmostOneThreadExecutor.java src/main/java/hudson/remoting/Channel.java src/main/java/hudson/remoting/PingThread.java src/main/java/hudson/remoting/Request.java src/main/java/hudson/remoting/SingleLaneExecutorService.java src/main/java/hudson/remoting/SynchronousExecutorService.java http://jenkins-ci.org/commit/remoting/7f35e250f5d535a9dbe16e67a47443aab568e7c4 Log: Merge pull request #33 from jenkinsci/JENKINS-21251_take2 JENKINS-21251 Slave channel timeout seemingly caused by usage of System.currentTimeMillis() Compare: https://github.com/jenkinsci/remoting/compare/c4df5cb9c458...7f35e250f5d5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27412) Stability issues faced with Jenkins 1.596.1 due to blocked threads
Ludovic Vercruysse updated JENKINS-27412 Stability issues faced with Jenkins 1.596.1 due to blocked threads Change By: Ludovic Vercruysse (13/Mar/15 10:48 AM) Attachment: support.zip This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27412) Stability issues faced with Jenkins 1.596.1 due to blocked threads
Ludovic Vercruysse commented on JENKINS-27412 Stability issues faced with Jenkins 1.596.1 due to blocked threads Please find the bundle enclosed to this ticket. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging-plugin] (JENKINS-27359) [PATCH] instant-messaging-plugin prevents JVM from shutting down
Johno Crawford commented on JENKINS-27359 [PATCH] instant-messaging-plugin prevents JVM from shutting down Thanks for the merge, when do you think you might release the next version of instant-messaging-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-25270) Add option to disable configuration confirmation dialog
Daniel Beck commented on JENKINS-25270 Add option to disable configuration confirmation dialog The goal here should be to not have false positive warnings rather than add an option for this. I'm fairly sure this is due to AJAX loading contents of select fields. (e.g. Credentials) An overview of the HTTP requests sent on the config screen would be helpful. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-27328) Plugin hangs the jobs just after printing version out to console (Praqma case 12801)
Bue Petersen resolved JENKINS-27328 as Cannot Reproduce Plugin hangs the jobs just after printing version out to console (Praqma case 12801) This wasn't related to the plugin. Change By: Bue Petersen (13/Mar/15 11:04 AM) Status: In Progress Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-26923) Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy in Maven Job
Ivar Kanters commented on JENKINS-26923 Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy in Maven Job Yes! removing the commons-io jar did the trick for me too! Thanks a lot! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27271) Safe navigation operator does not work in Groovy CPS
Jesse Glick assigned JENKINS-27271 to Jesse Glick Safe navigation operator does not work in Groovy CPS Change By: Jesse Glick (13/Mar/15 11:10 AM) Assignee: Kohsuke Kawaguchi Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27271) Safe navigation operator does not work in Groovy CPS
Jesse Glick started work on JENKINS-27271 Safe navigation operator does not work in Groovy CPS Change By: Jesse Glick (13/Mar/15 11:10 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27412) Stability issues faced with Jenkins 1.596.1 due to blocked threads
Daniel Beck commented on JENKINS-27412 Stability issues faced with Jenkins 1.596.1 due to blocked threads You seem to have severe I/O issues. There are tons of requests logged that stall on disk I/O. You only recently disabled the Disk Usage plugin, possibly because of the deadlocks yesterday, right? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-27309) Plugin always leads to merge failure (case 12800)
Bue Petersen commented on JENKINS-27309 Plugin always leads to merge failure (case 12800) Can you try to enable the logging plugin to get more information from logging on the slaves? https://wiki.jenkins-ci.org/display/JENKINS/Logging+Plugin It will catch your logs on the slaves. Logging specifically on the pretested integration plugin, use this namespace: org.jenkinsci.plugins.pretestedintegration It should supply us with more information. If you won't share with community, you can send it to us on supp...@praqma.net with reference to this case. I will have a look at it. For now, you are the only one reporting problems with the merge. By the way, here is an example list of git commands used from the plugin - you could try them: git checkout -B master origin/master git pull origin master git merge -m "Accumulated commit of the following from branch 'origin/ready/teamFeature': commit ab22116e7c135b57771c3fe740b5c1c78610df7a Author: john Doe Date: Fri Mar 06 02:30:25 2015 +0100 Updated info file 5. time on branch ready/teamFeature commit 126ee365f36cbc991e4feb8d579ceedb9c737875 Author: ReleasePraqma Date: Fri Mar 06 02:30:25 2015 +0100 Merge commit '9aa057053388508f0c353eb56ed6985a3da536bb' into ready/teamFeature commit cbe04ecab067454aadddc4f8943cb14016092ae0 Author: john Doe Date: Fri Mar 06 02:30:24 2015 +0100 4. time updating info file on branch ready/teamFeature commit 24365566f7828e9cae95fbbd31e6585b2f6764ed Author: john Doe Date: Fri Mar 06 02:30:24 2015 +0100 Updated info file again on branch ready/teamFeature - my first change is about this - my next change is a refactor. commit b77e511955bfdb435a3ff9284c50c7b0aca3bb0a Author: john Doe Date: Fri Mar 06 02:30:24 2015 +0100 Updated info file on branch ready/teamFeature " ab22116e7c135b57771c3fe740b5c1c78610df7a --no-ff git push origin master git push origin :ready/teamFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27412) Stability issues faced with Jenkins 1.596.1 due to blocked threads
Daniel Beck commented on JENKINS-27412 Stability issues faced with Jenkins 1.596.1 due to blocked threads Alright, you need much more RAM. 1340 Maven projects, known as insane memory hog, on just 4 GB RAM is pretty insane. If possible, disable fingerprinting. Jenkins spends way too much time to parse fingerprint data, probably because it's held in soft references IIRC. Also, discard unloadable data, disabling Disk Usage plugin results in tons of unloadable data (which makes loading builds and projects slower I think). Get rid of whatever plugin logs j.p.model.JobFailedTimeInfo#recordFailedTimeInfo, it looks like this forces Jenkins to continuously load builds from disk and (because too little RAM) discard them again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging-plugin] (JENKINS-27359) [PATCH] instant-messaging-plugin prevents JVM from shutting down
kutzi commented on JENKINS-27359 [PATCH] instant-messaging-plugin prevents JVM from shutting down I like to check 1 or 2 things and aim for a release in the next few days This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-monitor-plugin] (JENKINS-27183) Deadlock
Oliver Gondža commented on JENKINS-27183 Deadlock https://github.com/jenkinsci/jenkins/pull/1597 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-monitor-plugin] (JENKINS-27183) Deadlock
SCM/JIRA link daemon commented on JENKINS-27183 Deadlock Code changed in jenkins User: Felix Belzunce Arcos Path: core/src/main/java/hudson/model/AbstractItem.java http://jenkins-ci.org/commit/jenkins/fb5540e38c935676d7f58e9d2ce7a84275bb898f Log: JENKINS-27183 Avoid deadlock when using build-monitor-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] [build-monitor-plugin] (JENKINS-27183) Deadlock
SCM/JIRA link daemon commented on JENKINS-27183 Deadlock Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/hudson/model/AbstractItem.java http://jenkins-ci.org/commit/jenkins/4edbb2565b72d3ac64f520c128a7afcfeba92c33 Log: Merge pull request #1597 from fbelzunc/JENKINS-27183 [FIXED JENKINS-27183] Avoid deadlock when using build-monitor-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] [build-monitor-plugin] (JENKINS-27183) Deadlock
SCM/JIRA link daemon resolved JENKINS-27183 as Fixed Deadlock Change By: SCM/JIRA link daemon (13/Mar/15 11:44 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27388) Build parameters are injected as typeless strings into workflow script
Jesse Glick resolved JENKINS-27388 as Duplicate Build parameters are injected as typeless strings into workflow script Change By: Jesse Glick (13/Mar/15 11:52 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27228) Input result should log who made the change
Jesse Glick resolved JENKINS-27228 as Duplicate Input result should log who made the change Change By: Jesse Glick (13/Mar/15 11:51 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27412) Stability issues faced with Jenkins 1.596.1 due to blocked threads
Ludovic Vercruysse commented on JENKINS-27412 Stability issues faced with Jenkins 1.596.1 due to blocked threads Please find below remarks to your suggestions: RAM: we are currently updating the parameter -Xmx of our JVM to use -Xmx8192m (the server itself has 12 Gb of RAM), we will let you know if this has a positive impact Disk usage plugin: this plugin was previsouly disabled (as we were using Jenkins 1.509.4), but during the delivery process, it has been delivered again by mistake. That's why you see so many errors in the logs of yesterday, but none in the logs of today (I have disabled it yesterday evening). Fingerprinting: most of our projects are maven ones; as far as I have understood from fingerprinting, it is not possible to disable it for maven projects. Could you please translate "IIRC" ? I do not understand it. Discard unloadable data: could you please tell how to do this ? References to j.p.model.JobFailedTimeInfo#recordFailedTimeInfo: we are checking from which plugin this log comes (seems to be an history 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] [workflow-plugin] (JENKINS-27295) Boolean parameters injected as String
Jesse Glick updated JENKINS-27295 Boolean parameters injected as String By design; parameter values traditionally have been injected as environment variables, so Workflow just followed suit. Now when using parameter value implementations defined in core, or in a plugin depending on core 1.568+, the new getValue method could be called. For compatibility reasons, we cannot change the type of the existing variables, but we could introduce new variables (or a map variable parameters, etc.) based on the rich types. Unfortunately there is no clear way to distinguish whether a given ParameterValue implementation is specifying getValue. The Javadoc says it can return this as a fallback, yet the default implementation is null, which may be a legitimate return value in an override. Perhaps we need to just use Util.isOverridden, which is undesirable since it would give incorrect results if there are any proxying implementations, though probably there are not. Change By: Jesse Glick (13/Mar/15 11:57 AM) Summary: Boolean parameters injected as Strings into Groovy Workflow Plugin environment String Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27412) Stability issues faced with Jenkins 1.596.1 due to blocked threads
Daniel Beck commented on JENKINS-27412 Stability issues faced with Jenkins 1.596.1 due to blocked threads Could you please translate "IIRC" ? I do not understand it. http://acronyms.thefreedictionary.com/IIRC Discard unloadable data: could you please tell how to do this ? You go to the /manage page and click the link/button in the warning at the top. Installing the Monitoring Plugin may also provide interesting information, like a graph of (heap) memory usage over time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27413) Handle file parameters
Jesse Glick
created JENKINS-27413
Handle file parameters
Issue Type:
New Feature
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
13/Mar/15 12:06 PM
Description:
JENKINS-27295 discusses getting values from various kinds of parameters. Handling FileParameterValue is another matter. buildEnvironment (what is called today) is useless since it gives only a file name. createBuildWrapper is the way this works in a freestyle project, but this cannot work in a workflow; even if it were to return a SimpleBuildWrapper (JENKINS-24673) it is not clear where that would be called, since we can only use it from a workspace. getValue as currently implemented is useless since a FileItem does not have whitelisted methods, and anyway we would not want the flow itself to be copying streams to the workspace; this needs to be done by infrastructure. The only way forward I can see at the moment is for getValue to return a SimpleBuildWrapper, so that your flow could read
node {
wrap([$delegate: parameters.myFileParam]) {
sh 'cat myFileParam'
}
}
Project:
Jenkins
Priority:
Major
Reporter:
Jesse Glick
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27412) Stability issues faced with Jenkins 1.596.1 due to blocked threads
Daniel Beck edited a comment on JENKINS-27412 Stability issues faced with Jenkins 1.596.1 due to blocked threads Could you please translate "IIRC" ? I do not understand it. http://acronyms.thefreedictionary.com/IIRC Note that fingerprint loading is probably a symptom of build loading, i.e. if you add RAM so builds don't need to be (re)loaded all the time, this may well stop being a problem. Discard unloadable data: could you please tell how to do this ? You go to the /manage page and click the link/button in the warning at the top. Installing the Monitoring Plugin may also provide interesting information, like a graph of (heap) memory usage over time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-monitor-plugin] (JENKINS-27183) Deadlock when renaming and updating item in the same view
Oliver Gondža updated JENKINS-27183 Deadlock when renaming and updating item in the same view Change By: Oliver Gondža (13/Mar/15 12:17 PM) Summary: Deadlock when renaming and updating item in the same view Labels: lts-candidate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testng-plugin] (JENKINS-27414) unable to restart jenkins and load testng-plugin
Prateek Bagrecha created JENKINS-27414 unable to restart jenkins and load testng-plugin Issue Type: Bug Assignee: Nalin Makar Components: testng-plugin Created: 13/Mar/15 12:25 PM Description: I installed testng-plugin and restarted the tomcat but testng-plugin is still on showing up in "Add build step" drop down list. When I upload testng-plugin.hpi, it says I need to start restart jenkins, which its is not allowing A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace javax.servlet.ServletException: hudson.lifecycle.RestartNotSupportedException: Default Windows lifecycle does not support restart. at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) 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:725) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) Project: Jenkins Priority: Critical Reporter: Prateek Bagrecha This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testng-plugin] (JENKINS-27414) unable to restart jenkins and load testng-plugin
Daniel Beck commented on JENKINS-27414 unable to restart jenkins and load testng-plugin What Jenkins version is this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testng-plugin] (JENKINS-27414) unable to restart jenkins and load testng-plugin
Prateek Bagrecha commented on JENKINS-27414 unable to restart jenkins and load testng-plugin Version is 1.602 the latest one This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25270) Add option to disable configuration confirmation dialog
Jan Mashat commented on JENKINS-25270 Add option to disable configuration confirmation dialog Yeah you're right...these AJAX calls are triggering the confirmation dialog... /job/test/descriptorByName/hudson.plugins.git.UserRemoteConfig/fillCredentialsIdItems /job/test/descriptorByName/hudson.plugins.git.GitSCM/fillGitToolItems /job/test/descriptorByName/hudson.scm.SubversionSCM$ModuleLocation/fillCredentialsIdItems /job/test/descriptorByName/hudson.scm.CvsRepository/fillCompressionLevelItems Unfortunately the Git Plugin is required, so I'm back to blocking all confirmation dialogs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-folder-plugin] (JENKINS-27269) Credentials not usable in 'subfolders'
Jo Vandeginste resolved JENKINS-27269 as Not A Defect Credentials not usable in 'subfolders' Had nothing to do with Jenkins itself. Change By: Jo Vandeginste (13/Mar/15 1:06 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-folder-plugin] (JENKINS-27269) Credentials not usable in 'subfolders'
Jo Vandeginste commented on JENKINS-27269 Credentials not usable in 'subfolders' Confirmed: after drastically reducing the number of headers our SSO system sends to the Jetty server, everything works as expected. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27332) git-plugin no longer detects changes of branch with /
Albert Parra
commented on JENKINS-27332
git-plugin no longer detects changes of branch with /
Ok, finally i figure out what is happening.
1. compareRemoteRevisionWithImpl adds remote name to each branch got from that remote (GitSCM.java:586)
2. getPattern add */ to the branch name, if it doesn't contain * or /
// if an unqualified branch was given add a "*/" so it will match branches
// from remote repositories as the user probably intended
In our case, our branch name contains /, then */ is not added. (BranchSpec.java:117)
3. remoteName+remoteBranch is compared against our branchName, it doesn't match.
Proposed fix:
update line BranchSpec.java:126 to
builder.append("(refs/heads/|refs/remotes/|remotes/|origin/)?");
with that fix, i think that block from line 116 to 120 will be not longer needed.
hope Nicolas De Loo is watching this.
Cheers
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [testng-plugin] (JENKINS-27414) unable to restart jenkins and load testng-plugin
Daniel Beck commented on JENKINS-27414 unable to restart jenkins and load testng-plugin How are you attempting to restart Jenkins? To explain, you are running Jenkins on Windows not as a service, so restart is not supported. However, you shouldn't be shown any link or button to restart. If that's the case, that's a bug. However if you manually navigate to /restart, /safeRestart, then this isn't actually an issue. You just need to stop Jenkins and start it again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testng-plugin] (JENKINS-27414) unable to restart jenkins and load testng-plugin
Prateek Bagrecha commented on JENKINS-27414 unable to restart jenkins and load testng-plugin how do I stop Jenkins & start it again ? 1. I tried using tomcat manage apps, it did not work. 2. I tried restarting tomcat itself, it did not work. Any other option ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25270) Add option to disable configuration confirmation dialog
Daniel Beck commented on JENKINS-25270 Add option to disable configuration confirmation dialog /job/test/descriptorByName/hudson.scm.CvsRepository/fillCompressionLevelItems The CVS plugin is enabled after all. So what did you mean in your first comment responding to the suggestion to disable CVS? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25270) Add option to disable configuration confirmation dialog
Jan Mashat commented on JENKINS-25270 Add option to disable configuration confirmation dialog I enabled it for testing purposes and found that all of the above plugins are triggering the confirmation dialog. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-27415) Junit plugin fails to parse output, all tests are marjed as failed
Cristian Magherusan-Stanciu created JENKINS-27415 Junit plugin fails to parse output, all tests are marjed as failed Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 13/Mar/15 1:30 PM Description: Jobs fail all tests and are always unstable, and this error shows up when parsing the results: Failed to read test report file /var/lib/jenkins/workspace/MH5_Pipeline_02_Unit_tests/reports/client/unit/TEST-Firefox_360_Linux.nokia.mh5.adapters.IpLookup.xml org.dom4j.DocumentException: Could not load any resource bundle by com.sun.org.apache.xerces.internal.impl.msg.SAX Messages Nested exception: Could not load any resource bundle by com.sun.org.apache.xerces.internal.impl.msg.SAXMe ssages at org.dom4j.io.SAXReader.read(SAXReader.java:484) at org.dom4j.io.SAXReader.read(SAXReader.java:264) at hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:123) at hudson.tasks.junit.TestResult.parse(TestResult.java:282) at hudson.tasks.junit.TestResult.parsePossiblyEmpty(TestResult.java:228) at hudson.tasks.junit.TestResult.parse(TestResult.java:163) at hudson.tasks.junit.TestResult.parse(TestResult.java:146) at hudson.tasks.junit.TestResult.(TestResult.java:122) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:119) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:93) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2688) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) 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: java.util.MissingResourceException: Could not load any resource bundle by com.sun.org.apache.xerces.internal.impl.msg.SAXMessages at com.sun.org.apache.xerces.internal.utils.SecuritySupport$7.run(SecuritySupport.java:174) at com.sun.org.apache.xerces.internal.utils.SecuritySupport$7.run(SecuritySupport.java:166) at java.security.AccessController.doPrivileged(Native Method) at com.sun.org.apache.xerces.internal.utils.SecuritySupport.getResourceBundle(SecuritySupport.java:166) at com.sun.org.apache.xerces.internal.util.SAXMessageFormatter.formatMessage(SAXMessageFormatter.java:57) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.getProperty(AbstractSAXParser.java:2062) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.setProperty(SAXParserImpl.java:579) at org.dom4j.io.SAXHelper.setParserProperty(SAXHelper.java:34) at org.dom4j.io.SAXReader.configureReader(SAXReader.java:911) at org.dom4j.io.SAXReader.read(SAXReader.java:463) ... 18 more Nested exception: java.util.MissingResourceException: Could not load any resource bundle by com.sun.org.apache.xerces.internal.impl.msg.SAXMessages at com.sun.org.apache.xerces.internal.utils.SecuritySupport$7.run(SecuritySupport.java:174) at com.sun.org.apache.xerces.internal.utils.SecuritySupport$7.run(SecuritySupport.java:166) at java.security.AccessController.doPrivileged(Native Method) at com.sun.org.apache.xerces.internal.utils.SecuritySupport.getResourceBundle(SecuritySupport.java:166) at com.sun.org.apache.xerces.internal.util.SAXMessageFormatter.formatMessage(SAXMessageFormatter.java:57) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.getProperty(AbstractSAXParser.java:2062) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.setProperty(SAXParserImpl.java:579) at org.dom4j.io.SAXHelper.setParserProperty(SAXHelper.j
[JIRA] [testng-plugin] (JENKINS-27414) unable to restart jenkins and load testng-plugin
Daniel Beck commented on JENKINS-27414 unable to restart jenkins and load testng-plugin I tried restarting tomcat itself, it did not work. If Jenkins is hosted in Tomcat, that should work. Make sure it's not running standalone. Also, please ander the above question. What did you do to get the RestartNotSupportedException? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testng-plugin] (JENKINS-27414) unable to restart jenkins and load testng-plugin
Daniel Beck edited a comment on JENKINS-27414 unable to restart jenkins and load testng-plugin I tried restarting tomcat itself, it did not work. If Jenkins is hosted in Tomcat, that should work. Make sure it's not running standalone. Also, please answer the above question. What did you do to get the RestartNotSupportedException? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testng-plugin] (JENKINS-27414) unable to restart jenkins and load testng-plugin
Prateek Bagrecha commented on JENKINS-27414 unable to restart jenkins and load testng-plugin I used /restart and /safeRestart with in the URL, thats when I got notsupported exception. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testng-plugin] (JENKINS-27414) unable to restart jenkins and load testng-plugin
Daniel Beck resolved JENKINS-27414 as Not A Defect unable to restart jenkins and load testng-plugin There is no bug here. Figure out how Jenkins needs to be restarted on your system and do it that way. Jenkins cannot restart itself, as the error message indicates. Change By: Daniel Beck (13/Mar/15 1:46 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27084) SVN authentication fails using subversion plugin v.2.5
Rasmus Pedersen commented on JENKINS-27084 SVN authentication fails using subversion plugin v.2.5 Adding -Dsvnkit.http.methods=Basic,NTLM,Negotiate,Digest to jenkins.xml fixes the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-27415) Junit plugin fails to parse output, all tests are marked as failed
Cristian Magherusan-Stanciu updated JENKINS-27415 Junit plugin fails to parse output, all tests are marked as failed Change By: Cristian Magherusan-Stanciu (13/Mar/15 1:52 PM) Summary: Junit plugin fails to parse output, all tests are marjed marked as failed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-27084) SVN authentication fails using subversion plugin v.2.5
Björn Olsson commented on JENKINS-27084 SVN authentication fails using subversion plugin v.2.5 I'm glad I could help! / Björn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27084) SVN authentication fails using subversion plugin v.2.5
Björn Olsson resolved JENKINS-27084 as Fixed SVN authentication fails using subversion plugin v.2.5 Resolving, as the proposed workaround fixes the issue. Change By: Björn Olsson (13/Mar/15 2:02 PM) Status: Open Resolved Assignee: Björn Olsson 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-27084) SVN authentication fails using subversion plugin v.2.5
Rasmus Pedersen
commented on JENKINS-27084
SVN authentication fails using subversion plugin v.2.5
Now I'm just wondering:
Why is there a line saying lib.svnkit.http.methods Digest,Basic,NTLM,Negotiate when I go to JENKINS_HOST/systemInfo
even though I've added the -Dsvnkit.http.methods=Basic,NTLM,Negotiate,Digest }} to {{jenkins.xml?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-27084) SVN authentication fails using subversion plugin v.2.5
Rasmus Pedersen edited a comment on JENKINS-27084 SVN authentication fails using subversion plugin v.2.5 Now I'm just wondering: Why is there a line saying lib.svnkit.http.methods Digest,Basic,NTLM,Negotiate when I go to JENKINS_HOST/systemInfo even though I've added the -Dsvnkit.http.methods=Basic,NTLM,Negotiate,Digest to jenkins.xml? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slave-utilization] (JENKINS-27416) Unable to reconnect jenkins slave automatically after restart
Basma Yangui created JENKINS-27416 Unable to reconnect jenkins slave automatically after restart Issue Type: Bug Assignee: Unassigned Components: slave-utilization Created: 13/Mar/15 2:22 PM Description: I have a Jenkins master (Linux Debian) and 4 slaves (Windows 7) which are connected via JNLP. The jenkins slave service works well in each slave. However when I restart a slave machine, the connection breaks down for all the slaves and the reconnection is established again only if the Jenkins master is restarted. What should I do? Project: Jenkins Labels: windows jenkins debian slave Priority: Minor Reporter: Basma Yangui This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27416) Unable to reconnect jenkins slave automatically after restart
Daniel Beck updated JENKINS-27416 Unable to reconnect jenkins slave automatically after restart Much more information is needed to investigate this. Consider installing Support Core plugin and attaching a support bundle to this report. Also, please read: https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue Also note this is an issue tracker, not a support site. If you're looking for help, e.g. workarounds, you're in the wrong place. Change By: Daniel Beck (13/Mar/15 2:35 PM) Labels: debian jenkins slave windows Component/s: core Component/s: remoting Component/s: slave-utilization This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloverphp-plugin] (JENKINS-27417) Clover PHP Plugin Doesn't always publish
Patrick Rose created JENKINS-27417 Clover PHP Plugin Doesn't always publish Issue Type: Improvement Assignee: sogabe Components: cloverphp-plugin Created: 13/Mar/15 2:45 PM Description: If the build fails, then the clover plugin will not publish the report. Is it possible for it a config option to publish the report? I have a fairly simple build script (and I'm not sure I want to spend too much time setting up ant) which will run things like php -l and they'll make the build fail even though I've already run the test suite and the code coverage report will exist. Project: Jenkins Priority: Minor Reporter: Patrick Rose This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloverphp-plugin] (JENKINS-27417) Clover PHP Plugin Doesn't always publish
Patrick Rose closed JENKINS-27417 as Duplicate Clover PHP Plugin Doesn't always publish Duplicate of JENKINS-21046 Change By: Patrick Rose (13/Mar/15 2:48 PM) Status: Open Closed Assignee: sogabe 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] [git-plugin] (JENKINS-27332) git-plugin no longer detects changes of branch with /
Albert Parra
edited a comment on JENKINS-27332
git-plugin no longer detects changes of branch with /
Ok, finally i figure out what is happening.
1. compareRemoteRevisionWithImpl adds remote name to each branch got from that remote (GitSCM.java:586)
2. getPattern add */ to the branch name, if it doesn't contain * or /
// if an unqualified branch was given add a "*/" so it will match branches
// from remote repositories as the user probably intended
In our case, our branch name contains /, then */ is not added. (BranchSpec.java:117)
3. remoteName+remoteBranch is compared against our branchName, it doesn't match.
Proposed fix:
update line BranchSpec.java:126 to
builder.append("(refs/heads/|refs/remotes/|remotes/|origin/)?");
with that fix, i think that block from line 116 to 120 will be not longer needed.
I'm working on a branch for this.
Cheers
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [scoverage-plugin] (JENKINS-27418) NPE in scoverage plugin
Claudio B created JENKINS-27418 NPE in scoverage plugin Issue Type: Bug Assignee: Unassigned Components: scoverage-plugin Created: 13/Mar/15 3:04 PM Description: When visiting the link http://localhost:7070/jenkins/job/abuild/scoverage/ I get back the following error: javax.servlet.ServletException: java.lang.NullPointerException 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$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:723) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:563) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103) at org.apache.catalina.core.StandardEngineValve.invoke(
[JIRA] [scoverage-plugin] (JENKINS-27418) NPE in scoverage plugin
Claudio B
updated JENKINS-27418
NPE in scoverage plugin
Change By:
Claudio B
(13/Mar/15 3:06 PM)
Description:
When visiting the link http://localhost:7070/jenkins/job/abuild/scoverage/ I get back the following error:{code}javax.servlet.ServletException: java.lang.NullPointerException 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$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:723) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:563) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:861) at org.apache.coyote.http11.Http11Proto
[JIRA] [core] (JENKINS-27399) CLONE - Cancel Job and Build Number buttons appear under main feedback panel
Brian Smith commented on JENKINS-27399 CLONE - Cancel Job and Build Number buttons appear under main feedback panel It looks like this problem has gone away after we upgraded some of our plugins (and there is a tag pair before each underscore). Not sure which one it was as none of them would seem to have an effect on the main display (maybe the Claim plugin?). If needed we can go back and see which one it was but with the latest plugins and with the latest LTS release everything seems to be working. Please let me know if you would like us to try and track it down. Upgraded plugins (from what we can remember upgrading): artifact deployer plugin build pipeline claim copy artifact copy to slave credentials disk usage email extension LDAP monitoring parameterized trigger perforce SSH slaves subversion workspace cleanup This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27399) CLONE - Cancel Job and Build Number buttons appear under main feedback panel
Brian Smith edited a comment on JENKINS-27399 CLONE - Cancel Job and Build Number buttons appear under main feedback panel It looks like this problem has gone away after we upgraded some of our plugins (and there is a tag pair before each underscore now). Not sure which one it was as none of them would seem to have an effect on the main display (maybe the Claim plugin?). If needed we can go back and see which one it was but with the latest plugins and with the latest LTS release everything seems to be working. Please let me know if you would like us to try and track it down. Upgraded plugins (from what we can remember upgrading): artifact deployer plugin build pipeline claim copy artifact copy to slave credentials disk usage email extension LDAP monitoring parameterized trigger perforce SSH slaves subversion workspace cleanup This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [elastic-axis-plugin] (JENKINS-27420) Allow for "any node matching label", not just "all nodes matching label"
Jo Shields created JENKINS-27420 Allow for "any node matching label", not just "all nodes matching label" Issue Type: New Feature Assignee: Unassigned Components: elastic-axis-plugin Created: 13/Mar/15 3:28 PM Description: I have an elastic axis "label", with node label "debian-ppc64el,centos-s390x" What I want is for any 1 node matching debian-ppc64el, AND any 1 node matching centos-s390x, to be used for the build, such that the output is available at the URL http://...blabla/label=centos-s390x/ and http://...blabla/label=debian-ppc64el/ Instead, Elastic Axis has expanded my labels, created http://...blabla/label=s390xbuilder-1-hostname/ and http://...blabla/label=s390xbuilder-2-hostname/ entries, and tries to build on both machines (a waste of time/resources) Project: Jenkins Priority: Minor Reporter: Jo Shields This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-27419) dos "exit" command not functioning correctly
James Nord
created JENKINS-27419
dos "exit" command not functioning correctly
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
durable-task-plugin, workflow-plugin
Created:
13/Mar/15 3:28 PM
Description:
if you attempt to run a dos batch file that has an "exit" command within it then the task does not notice that the interpreter has terminated.
e.g. in workflow create a CPS with the following
node {
bat '''echo hello
exit 1'''
echo 'should not be seen'
}
This results in a workflow that will run forever.
Environment:
Window 8.1
Jenkins 1.580.1
Project:
Jenkins
Priority:
Major
Reporter:
James Nord
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-27084) SVN authentication fails using subversion plugin v.2.5
Björn Olsson commented on JENKINS-27084 SVN authentication fails using subversion plugin v.2.5 lib.svnkit.http.methods=Digest,Basic,NTLM,Negotiate svnkit.http.methods=Basic,NTLM,Negotiate,Digest The first part, lib. subtle difference, and I don't know what the difference is, actually. Maybe someone else has the answer? / Björn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-27419) dos "exit" command not functioning correctly
Daniel Beck commented on JENKINS-27419 dos "exit" command not functioning correctly Isn't that what the /b flag is for? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27399) CLONE - Cancel Job and Build Number buttons appear under main feedback panel
Daniel Beck resolved JENKINS-27399 as Cannot Reproduce CLONE - Cancel Job and Build Number buttons appear under main feedback panel Alright, resolving. If you have the time, try to figure out what combination of plugins and configuration is needed. Change By: Daniel Beck (13/Mar/15 3:34 PM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26034) Option to interrupt remaining branches when one branch fails
James Nord assigned JENKINS-26034 to James Nord Option to interrupt remaining branches when one branch fails Change By: James Nord (13/Mar/15 3:53 PM) Assignee: Kohsuke Kawaguchi James Nord This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy-plugin] (JENKINS-19934) Add "Job Create" permission to project roles
Simon Devineau
commented on JENKINS-19934
Add "Job Create" permission to project roles
Hello everyone,
First I would like to say thank you to Oleg and his team. This plugin is so powerfull.
About this/these bug(s), I am sorry if I did not understand everything but here is my aim.
I want a user (let's call him jobCreator) to be able to create jobs only if it respects a pattern otherwiswe it does not create it.
If the user has the global create job he can do whatever he wants (Let's call him globalCreator)
As it was said above, you need the global create job to be able to see the icon 'Create new item'.
So the jobCreator will always have both permisisons (global and job)
The globalCreator needs to have ONLY the global create permissions.
I have modified the code of RoleBasedProjectNamingStrategy to follow my scenario.
I cannot promise anything with it but if you want to check it out and update your code with, I will be glad.
Also, I am not sure the current code is working.
//firstly check global role
SortedMap> gRole = rbas.getGrantedRoles(RoleBasedAuthorizationStrategy.GLOBAL);
for (SortedMap.Entry> entry: gRole.entrySet()){
if (entry.getKey().hasPermission(Item.CREATE))
return;
}
This will always return true because gRole contains all the users with all the global permissions.
It should check the current logged user.
I am gonna patch my code to your github if you are interested and attached it to my message.
Could you please let me know about your intention.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy-plugin] (JENKINS-19934) Add "Job Create" permission to project roles
Simon Devineau updated JENKINS-19934 Add "Job Create" permission to project roles Here is the code I modified to follow my scenario Change By: Simon Devineau (13/Mar/15 4:05 PM) Attachment: RoleBasedProjectNamingStrategy.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27399) CLONE - Cancel Job and Build Number buttons appear under main feedback panel
Brian Smith edited a comment on JENKINS-27399 CLONE - Cancel Job and Build Number buttons appear under main feedback panel OK... turns out I spoke too soon again as it started happening again this morning. I think we managed to track it down as there were only two differences between what ran yesterday when I checked and this morning. We had several matrix jobs running this morning and several jobs using the "Heavy Job" plugin. Based on the debug output from the browser (attached) it looks like the Heavy Job plugin might be the culprit as it doesn't have any tags. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27399) CLONE - Cancel Job and Build Number buttons appear under main feedback panel
Brian Smith commented on JENKINS-27399 CLONE - Cancel Job and Build Number buttons appear under main feedback panel OK... turns out I spoke too soon again as it started happening again this morning. I think we managed to track it down as there were only two differences between what ran yesterday when I checked and this morning. We had several matrix jobs running this morning and several jobs using the "Heavy Job" plugin. Based on the debug output from the browser (attached) it looks like the Heavy Job plugin is the culprit as it doesn't have any tags. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27399) CLONE - Cancel Job and Build Number buttons appear under main feedback panel
Brian Smith updated JENKINS-27399 CLONE - Cancel Job and Build Number buttons appear under main feedback panel Change By: Brian Smith (13/Mar/15 4:19 PM) Attachment: JenkinsDebugOutputCapture.PNG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-26254) Jacoco plugin is too slow and occupies too much microprocessor time
Anna Fowles-Winkler commented on JENKINS-26254 Jacoco plugin is too slow and occupies too much microprocessor time We are also seeing issues where the plugin uses too much CPU and virtual memory on our Oracle Linux 6.4 server. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [heavy-job-plugin] (JENKINS-27399) CLONE - Cancel Job and Build Number buttons appear under main feedback panel
Daniel Beck updated JENKINS-27399 CLONE - Cancel Job and Build Number buttons appear under main feedback panel Seems to be correct, see: https://github.com/jenkinsci/heavy-job-plugin/blob/master/src/main/resources/hudson/plugins/heavy_job/HeavyJobProperty/ExecutableImpl/executorCell.jelly Change By: Daniel Beck (13/Mar/15 4:40 PM) Component/s: heavy-job-plugin 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] [heavy-job-plugin] (JENKINS-27399) CLONE - Cancel Job and Build Number buttons appear under main feedback panel
Daniel Beck reopened JENKINS-27399 CLONE - Cancel Job and Build Number buttons appear under main feedback panel Change By: Daniel Beck (13/Mar/15 4:40 PM) Resolution: Cannot Reproduce Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [heavy-job-plugin] (JENKINS-27399) CLONE - Cancel Job and Build Number buttons appear under main feedback panel
Daniel Beck updated JENKINS-27399 CLONE - Cancel Job and Build Number buttons appear under main feedback panel Change By: Daniel Beck (13/Mar/15 4:41 PM) Status: Reopened Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26481) Closures only executed once in Groovy CPS DSL scripts
Jesse Glick started work on JENKINS-26481 Closures only executed once in Groovy CPS DSL scripts Change By: Jesse Glick (13/Mar/15 5:26 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
