[JIRA] (JENKINS-50732) MobileCenter Jenkin Plugin should support enforce upload application if it can't be packaged
Title: Message Title Wenbin Gao updated JENKINS-50732 Fixed by PR https://github.com/jenkinsci/hpe-application-automation-tools-plugin/pull/77. Jenkins / JENKINS-50732 MobileCenter Jenkin Plugin should support enforce upload application if it can't be packaged Change By: Wenbin Gao Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-50732) MobileCenter Jenkin Plugin should support enforce upload application if it can't be packaged
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50732 Re: MobileCenter Jenkin Plugin should support enforce upload application if it can't be packaged Code changed in jenkins User: Yafim Kazak Path: src/main/java/com/hpe/application/automation/tools/mc/Constants.java http://jenkins-ci.org/commit/hpe-application-automation-tools-plugin/8fc9cfbfd4ad99aa2121caec9e3e28ee8ab3b389 Log: Merge pull request #77 from nopainsnogains11/def_22046_jenkinsPlugin_appUpload Bug JENKINS-50732: ensure application to be uploaded even if instrumentation fails during app upload Compare: https://github.com/jenkinsci/hpe-application-automation-tools-plugin/compare/39b0160d0f86...8fc9cfbfd4ad Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50756) HTML and LRA folder not getting created after LR scenario execution with Jenkins
Title: Message Title Batami Gold assigned an issue to Ofir Shaked Jenkins / JENKINS-50756 HTML and LRA folder not getting created after LR scenario execution with Jenkins Change By: Batami Gold Assignee: Batami Gold Ofir Shaked Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50781) Shiro Plugin - Refusing to marshal org.apache.shiro.authc.credential.AllowAllCredentialsMatcher for security reasons
Title: Message Title angel liang commented on JENKINS-50781 Re: Shiro Plugin - Refusing to marshal org.apache.shiro.authc.credential.AllowAllCredentialsMatcher for security reasons Hi please see the attachment hudson.zip thanks a lot. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50781) Shiro Plugin - Refusing to marshal org.apache.shiro.authc.credential.AllowAllCredentialsMatcher for security reasons
Title: Message Title angel liang updated an issue Jenkins / JENKINS-50781 Shiro Plugin - Refusing to marshal org.apache.shiro.authc.credential.AllowAllCredentialsMatcher for security reasons Change By: angel liang Attachment: hudson.zip Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title Alex White commented on JENKINS-50833 Re: NoSuchMethodError causing Pipeline editor to not see agent settings I noticed this issue yesterday after using Pipeline and Blue Ocean for the first time and was very confused. I tried downgrading to Pipeline 2.4 from 2.5 but it still appears that `pipeline-model-definition 1.2.8` is the dependency there. I don't see a way to easily downgrade that specific dependency Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48631) Automatically remove the cache created on disk when lightweight checkout is used
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-48631 Re: Automatically remove the cache created on disk when lightweight checkout is used This is also used by branch indexing. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50756) HTML and LRA folder not getting created after LR scenario execution with Jenkins
Title: Message Title Ashwin Unnikrishnan assigned an issue to Batami Gold Jenkins / JENKINS-50756 HTML and LRA folder not getting created after LR scenario execution with Jenkins Change By: Ashwin Unnikrishnan Assignee: Yafim Kazak Batami Gold Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50805) Jenkins Blue Ocean won't show Agent when creating a Pipeline
Title: Message Title
Karl Shultz edited a comment on JENKINS-50805
Re: Jenkins Blue Ocean won't show Agent when creating a Pipeline
Many thanks for following up! We suspect root cause is actually in the {{pipeline-model-definition plugin }} plugin . [JENKINS-50833|https://issues.jenkins-ci.org/browse/JENKINS-50833] has been opened.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title Vivek Pandey commented on JENKINS-50833 Re: NoSuchMethodError causing Pipeline editor to not see agent settings Basically if users upgrade to pipeline-model-definition 1.2.8, this incompatibility will cause pipeline editor to be non-functional. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50805) Jenkins Blue Ocean won't show Agent when creating a Pipeline
Title: Message Title Karl Shultz commented on JENKINS-50805 Re: Jenkins Blue Ocean won't show Agent when creating a Pipeline Many thanks for following up! We suspect root cause is actually in the pipeline-model-definition plugin. JENKINS-50833 has been opened. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title
Karl Shultz updated an issue
Jenkins / JENKINS-50833
NoSuchMethodError causing Pipeline editor to not see agent settings
Change By:
Karl Shultz
*Summary*After taking the upgrade to Declarative 1. 28 2.8 , previously working Blue Ocean pipelines don't work correctly inside the editor. The editor still works, but the ability to change the agent type has gone missing. This was originally reported as Blue Ocean bug [JENKINS-50805|https://issues.jenkins-ci.org/browse/JENKINS-50805]. *Steps to recreate*1. Set up Blue Ocean to connect to a previously working Pipeline, or open a preexisting Pipeline.2. Launch the pipeline editor, and notice that there's no "Agent" settings available: !image-2018-04-16-18-40-00-833.png|thumbnail! 3. In the Jenkins log, you'll see the following {{InvocationTargetException}}, caused by a {{NoSuchMethodException}}: {code:none}Apr 16, 2018 10:29:19 PM org.eclipse.jetty.server.handler.ContextHandler$Context logWARNING: Error while serving http://172.18.40.95:8080/blue/rest/pipeline-metadata/agentMetadatajava.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:347) at org.kohsuke.stapler.ForwardingFunction.invoke(ForwardingFunction.java:63) at io.jenkins.blueocean.commons.stapler.TreeResponse$Processor.invoke(TreeResponse.java:43) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:686) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) 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:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:841) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:225) at
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-50833 NoSuchMethodError causing Pipeline editor to not see agent settings Change By: Karl Shultz Environment: Jenkins:- Core 2.116- Blue Ocean 1.5.0- Declarative 1. 28 2.8 - Experimental update center everything elseClient:- Fedora workstation, updated and running the latest available version of Chrome Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title Karl Shultz commented on JENKINS-50833 Re: NoSuchMethodError causing Pipeline editor to not see agent settings Setting up a link relationship between the originally-reported issue and this one. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title
Karl Shultz updated an issue
Jenkins / JENKINS-50833
NoSuchMethodError causing Pipeline editor to not see agent settings
Change By:
Karl Shultz
*Summary*After taking the upgrade to Declarative 1.28, previously working Blue Ocean pipelines don't work correctly inside the editor. The editor still works, but the ability to change the agent type has gone missing. This was originally reported as Blue Ocean bug [JENKINS-50805|https://issues.jenkins-ci.org/browse/JENKINS-50805]. *Steps to recreate*1. Set up Blue Ocean to connect to a previously working Pipeline, or open a preexisting Pipeline.2. Launch the pipeline editor, and notice that there's no "Agent" settings available: !image-2018-04-16-18-40-00-833.png|thumbnail! 3. In the Jenkins log, you'll see the following {{InvocationTargetException}}, caused by a {{NoSuchMethodException}}: {code:none}Apr 16, 2018 10:29:19 PM org.eclipse.jetty.server.handler.ContextHandler$Context logWARNING: Error while serving http://172.18.40.95:8080/blue/rest/pipeline-metadata/agentMetadatajava.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:347) at org.kohsuke.stapler.ForwardingFunction.invoke(ForwardingFunction.java:63) at io.jenkins.blueocean.commons.stapler.TreeResponse$Processor.invoke(TreeResponse.java:43) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:686) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) 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:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:841) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:225) at
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title Karl Shultz commented on JENKINS-50833 Re: NoSuchMethodError causing Pipeline editor to not see agent settings Can also be recreated via: docker run \ --rm \ -u root \ -p 8080:8080 \ -v jenkins-data:/var/jenkins_home \ -v /var/run/docker.sock:/var/run/docker.sock \ -v "$HOME":/home \ jenkinsci/blueocean Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48141) Logging framework improvements
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-48141 Logging framework improvements Change By: Vivek Pandey Sprint: Blue Ocean 1.4 - beta 3 , Blue Ocean - Candidates Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48141) Logging framework improvements
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-48141 Logging framework improvements Change By: Vivek Pandey Sprint: Blue Ocean 1.4 - beta 3 , Blue Ocean 1.6 - beta 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title Karl Shultz created an issue Jenkins / JENKINS-50833 NoSuchMethodError causing Pipeline editor to not see agent settings Issue Type: Bug Assignee: Andrew Bayer Attachments: image-2018-04-16-18-40-00-833.png Components: pipeline-model-definition-plugin Created: 2018-04-16 22:49 Environment: Jenkins: - Core 2.116 - Blue Ocean 1.5.0 - Declarative 1.28 - Experimental update center everything else Client: - Fedora workstation, updated and running the latest available version of Chrome Priority: Major Reporter: Karl Shultz Summary After taking the upgrade to Declarative 1.28, previously working Blue Ocean pipelines don't work correctly inside the editor. The editor still works, but the ability to change the agent type has gone missing. This was originally reported as Blue Ocean bug JENKINS-50805. Steps to recreate 1. Set up Blue Ocean to connect to a previously working Pipeline, or open a preexisting Pipeline. 2. Launch the pipeline editor, and notice that there's no "Agent" settings available: 3. In the Jenkins log, you'll see the following InvocationTargetException, caused by a NoSuchMethodException: Apr 16, 2018 10:29:19 PM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: Error while serving http://172.18.40.95:8080/blue/rest/pipeline-metadata/agentMetadata java.lang.reflect.InvocationTargetException at
[JIRA] (JENKINS-47929) Extensible run details tabs
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-47929 Extensible run details tabs Change By: Vivek Pandey Sprint: Blue Ocean 1.4 - beta 3, Blue Ocean 1.4 - beta 2 , Blue Ocean 1.6 - beta 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47929) Extensible run details tabs
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-47929 Extensible run details tabs Change By: Vivek Pandey Sprint: Blue Ocean 1.4 - beta 3, Blue Ocean 1.4 - beta 2 , Blue Ocean - Candidates Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47929) Extensible run details tabs
Title: Message Title Vivek Pandey assigned an issue to Ivan Meredith Jenkins / JENKINS-47929 Extensible run details tabs Change By: Vivek Pandey Assignee: Keith Zantow Ivan Meredith Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42173) Blue Ocean SDK design document - extensibility improvements
Title: Message Title Vivek Pandey assigned an issue to Ivan Meredith Jenkins / JENKINS-42173 Blue Ocean SDK design document - extensibility improvements Change By: Vivek Pandey Assignee: Keith Zantow Ivan Meredith Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47592) Blue Ocean auto-bundling can get into an infinite loop
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-47592 Blue Ocean auto-bundling can get into an infinite loop Change By: Vivek Pandey Sprint: Blue Ocean 1.4 - beta 3, Blue Ocean 1.4 - beta 2 , Blue Ocean - Candidates Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47592) Blue Ocean auto-bundling can get into an infinite loop
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-47592 Blue Ocean auto-bundling can get into an infinite loop Change By: Vivek Pandey Sprint: Blue Ocean 1.4 - beta 3, Blue Ocean 1.4 - beta 2 , Blue Ocean 1.6 - beta 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50692) Allow incrementals deployment from core
Title: Message Title Jesse Glick updated JENKINS-50692 Jenkins / JENKINS-50692 Allow incrementals deployment from core Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28471) xUnit should compare test results to last build with recorded tests for the "new" thresholds
Title: Message Title Nikolas Falco commented on JENKINS-28471 Re: xUnit should compare test results to last build with recorded tests for the "new" thresholds PR merged. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28471) xUnit should compare test results to last build with recorded tests for the "new" thresholds
Title: Message Title Nikolas Falco resolved as Fixed Jenkins / JENKINS-28471 xUnit should compare test results to last build with recorded tests for the "new" thresholds Change By: Nikolas Falco Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28471) xUnit should compare test results to last build with recorded tests for the "new" thresholds
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-28471 xUnit should compare test results to last build with recorded tests for the "new" thresholds Change By: Nikolas Falco Assignee: Alexander A Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49337) InterruptedException - Exception processing the logs
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-49337 Re: InterruptedException - Exception processing the logs Fingerprinting offers traceability across pipelines but it's not needed to trigger downstream pipelines. I don't see what could have been misleading here. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49337) InterruptedException - Exception processing the logs
Title: Message Title Cyrille Le Clerc commented on JENKINS-49337 Re: InterruptedException - Exception processing the logs Fingerprinting offers traceability across pipelines but it's not needed to trigger downstream pipelines. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50692) Allow incrementals deployment from core
Title: Message Title Jesse Glick started work on JENKINS-50692 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50028) Maven Report gadget : attached artifacts of 'pom' projects are not displayed
Title: Message Title Cyrille Le Clerc closed an issue as Fixed Jenkins / JENKINS-50028 Maven Report gadget : attached artifacts of 'pom' projects are not displayed Change By: Cyrille Le Clerc Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50832) PollSCM triggers jobs even if there are no changes jenkinsfile declarative
Title: Message Title
Luis Ibarra created an issue
Jenkins / JENKINS-50832
PollSCM triggers jobs even if there are no changes jenkinsfile declarative
Issue Type:
Bug
Assignee:
Vincent Latombe
Components:
pollscm-plugin
Created:
2018-04-16 21:18
Environment:
- Jenkins ver. 2.60.3 - Pipeline Plugin 1.2.7 - Pipeline: Multibranch 2.6
Labels:
jenkinsfile pollscm github-plugin declarative pipeline
Priority:
Blocker
Reporter:
Luis Ibarra
I'm using the github organization folder plugin to discover branches and pull requests dynamically. The discovery of new branches work as expected, but I want to reduce the time of discovering of new PR's and new commits for the specific repositories(by default is 1 day). For that I defined triggers { pollSCM('H/10 * * * *')} in the jenkinsfile(declarative) for some branches in some repos. I'm behind a firewall, so webhooks are not an option. However, the job triggers every 10 minutes in all the branches and PR's(until accepted) even if there are no changes after building once(it saves the trigger definition). According to the triggers documentation, it should run only if there are changes. I'm using this because GitSCM is not supported in the trigger definition. It would be super nice to have it in fact. Any ideas in how to deal with this would be great/
[JIRA] (JENKINS-50686) [JEP-305] Ability to publish incremental commits as Maven releases
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-50686 [JEP-305] Ability to publish incremental commits as Maven releases Change By: Jesse Glick Summary: [JEP-305] Ability to publish incremental commits as Maven releases Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50694) Draft process JEP
Title: Message Title Jesse Glick updated JENKINS-50694 Jenkins / JENKINS-50694 Draft process JEP Change By: Jesse Glick Status: In Review Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50805) Jenkins Blue Ocean won't show Agent when creating a Pipeline
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-50805 Jenkins Blue Ocean won't show Agent when creating a Pipeline Change By: Karl Shultz Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50784) "Replay" pipeline button/link is not (always?) available (anymore?)
Title: Message Title Jesse Glick commented on JENKINS-50784 Re: "Replay" pipeline button/link is not (always?) available (anymore?) Note that you could trigger a background load if and when someone calls getOrNull (but return null for now). Whether or not that is too late depends on the caller. In the case of Replay, it would mean that the action would not initially appear in the sidebar, but then it would appear in the context menu a moment later. For PipelineTimings and JobPropertyStep, this would not really help—in both cases it probably makes more sense to just use get and block if necessary. And I think the originally suggested change to ReplayAction (+ its index.jelly) would be desirable anyway—more transparent to have the link always be there, and if it cannot be used, explain why. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50805) Jenkins Blue Ocean won't show Agent when creating a Pipeline
Title: Message Title Christopher Francisco commented on JENKINS-50805 Re: Jenkins Blue Ocean won't show Agent when creating a Pipeline 1. I was using the repo in the tutorial, I literally just forked it and that was it. (https://github.com/jenkins-docs/creating-a-pipeline-in-blue-ocean) 2. no Jenkinsfile in it 3. First time setting up Jenkins on my own, so N/A Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50805) Jenkins Blue Ocean won't show Agent when creating a Pipeline
Title: Message Title Elia Zammuto commented on JENKINS-50805 Re: Jenkins Blue Ocean won't show Agent when creating a Pipeline a) I Created the Repos within this version, so they started as empty one b) N/A c) This was the first version I Installed So, Fresh New Install Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50805) Jenkins Blue Ocean won't show Agent when creating a Pipeline
Title: Message Title Karl Shultz commented on JENKINS-50805 Re: Jenkins Blue Ocean won't show Agent when creating a Pipeline Christopher Francisco, Elia Zammuto, and Jens Villadsen - thanks for reporting. Can you tell us more about the repositories you're connecting to? Are they empty repositories? If they're not empty, do they already have Jenkinsfiles created inside of them? Did these repositories work correctly with previous versions of Jenkins and/or Blue Ocean? I'll also take the liberty of adding this bug to the blueocean-pipeline-editor component. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50805) Jenkins Blue Ocean won't show Agent when creating a Pipeline
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-50805 Jenkins Blue Ocean won't show Agent when creating a Pipeline Change By: Karl Shultz Component/s: blueocean-pipeline-editor-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50784) "Replay" pipeline button/link is not (always?) available (anymore?)
Title: Message Title Jesse Glick commented on JENKINS-50784 Re: "Replay" pipeline button/link is not (always?) available (anymore?) Also, the following calls to getOrNull should be reviewed to see whether they will still produce reasonable behavior given the lazy-loading change: https://github.com/jenkinsci/workflow-cps-plugin/blob/9b0848c4efd71f051c653fc288492a2d70a84e58/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java#L1779 (arguably a regression) https://github.com/jenkinsci/workflow-cps-plugin/blob/41ac59c8f0878645ee5d697cdf8f37ce88c68a7d/src/main/java/org/jenkinsci/plugins/workflow/cps/RunningFlowActions.java#L51 (I think this one is fine) https://github.com/jenkinsci/workflow-multibranch-plugin/blob/dd6fbd2c1fdba58bc0a8b0404b72304beb3e09be/src/main/java/org/jenkinsci/plugins/workflow/multibranch/JobPropertyStep.java#L104 (looks like a regression) https://github.com/jenkinsci/parallel-test-executor-plugin/blob/89aad65707343dc98339b006fa4fe07ba1fe58b0/src/main/java/org/jenkinsci/plugins/parallel_test_executor/ParallelTestExecutor.java#L170 (probably fine) https://github.com/jenkinsci/junit-realtime-test-reporter-plugin/blob/b929d6924439f4c31775c704d3d83f8b052533a5/src/test/java/org/jenkinsci/plugins/junitrealtimetestreporter/RealtimeJUnitStepTest.java#L218 (probably fine) https://github.com/jenkinsci/throttle-concurrent-builds-plugin/blob/d105bb791364f3d8bfe42dcad448b14f9b0ed8b7/src/main/java/hudson/plugins/throttleconcurrents/ThrottleJobProperty.java#L327 (probably fine) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50784) "Replay" pipeline button/link is not (always?) available (anymore?)
Title: Message Title Jesse Glick commented on JENKINS-50784 Re: "Replay" pipeline button/link is not (always?) available (anymore?) I am not sure what the concerns surrounding corner cases are, but if the issue is simply that for a build which was loaded from disk (not started in this session) for which we did not independently load the FlowExecution, that ReplayAction.isEnabled is returning false because WorkflowRun.Owner.getOrNull is returning null for reasons of laziness, then the fix is simple: make the action enabled whenever we have a FlowExecutionOwner, and if and when the user invokes the action, then call get() (blocking), check RUN_SCRIPTS for non-sandbox mode, and provide some sort of UI notification if these preconditions are not met. Could all happen in ReplayAction/index.jelly in fact. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50820) Rerun button gone in Blue Ocean UI
Title: Message Title Sam Van Oort closed an issue as Duplicate Same root cause with fetching the execution and getting a null! Jenkins / JENKINS-50820 Rerun button gone in Blue Ocean UI Change By: Sam Van Oort Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Adam Daughterson commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline An acceptable workaround would be a flag to opt out of the workspace name mangling in either the Jenkinsfile or the multibranch configuration. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50784) "Replay" pipeline button/link is not (always?) available (anymore?)
Title: Message Title Jesse Glick commented on JENKINS-50784 Re: "Replay" pipeline button/link is not (always?) available (anymore?) Sam Van Oort when referring to other issues, just paste in the ID, not the link, or JIRA will not properly provide tool tips. So: JENKINS-50199 and JENKINS-49686 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50776) Default selected item doesn't always honor exactly Default Value
Title: Message Title Boguslaw Klimas updated JENKINS-50776 Release 0.9.2 Jenkins / JENKINS-50776 Default selected item doesn't always honor exactly Default Value Change By: Boguslaw Klimas Status: In Review Resolved Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50820) Rerun button gone in Blue Ocean UI
Title: Message Title Karl Shultz commented on JENKINS-50820 Re: Rerun button gone in Blue Ocean UI kutzi - do the `Replay` and `Rebuild` buttons still appear when you look at the same jobs in the Classic UI? Or maybe only one, but not both? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50776) Default selected item doesn't always honor exactly Default Value
Title: Message Title Boguslaw Klimas updated JENKINS-50776 Jenkins / JENKINS-50776 Default selected item doesn't always honor exactly Default Value Change By: Boguslaw Klimas Status: Closed In Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49727) Add optional parameter to specify the number of items the list will display
Title: Message Title Boguslaw Klimas resolved as Fixed Release 0.9.2 Jenkins / JENKINS-49727 Add optional parameter to specify the number of items the list will display Change By: Boguslaw Klimas Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-50776) Default selected item doesn't always honor exactly Default Value
Title: Message Title Boguslaw Klimas closed an issue as Fixed Release 0.9.2 Jenkins / JENKINS-50776 Default selected item doesn't always honor exactly Default Value Change By: Boguslaw Klimas Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50784) "Replay" pipeline button/link is not (always?) available (anymore?)
Title: Message Title Sam Van Oort commented on JENKINS-50784 Re: "Replay" pipeline button/link is not (always?) available (anymore?) Comment 2: the behavior of the ExecutionPromise is poorly defined with regards to loading the execution after a restart of Jenkins AFAICT. And in general there's not a sensible way to distinguish the following cases: 1. FlowExecution is null because we're just beginning the Run and it hasn't been created yet 2. FlowExecution is null because something went horribly wrong and it had to be trashed I'm also wondering if this may relate somehow to https://issues.jenkins-ci.org/browse/JENKINS-50199 and https://issues.jenkins-ci.org/browse/JENKINS-49686 in some vague way since it seems to open up a possibility that the Owner.get() method might be failing to invoke the FlowExecution.onLoad. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49596) User session memory leak
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-49596
Re: User session memory leak
[~marcmac] Based on the [README|https://github.com/jenkinsci/winstone/blob/master/README.md#command-line-options] I think you want to pass {{ \ --sessionEviction=foo}} in addition to {{ \ --sessionTimeout=foo}}.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49596) User session memory leak
Title: Message Title Devin Nusbaum commented on JENKINS-49596 Re: User session memory leak marc macintyre Based on the README I think you want to pass -sessionEviction=foo in addition to -sessionTimeout=foo. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50784) "Replay" pipeline button/link is not (always?) available (anymore?)
Title: Message Title Sam Van Oort edited a comment on JENKINS-50784 Re: "Replay" pipeline button/link is not (always?) available (anymore?) So, as best I can determine:1. WorkflowRun.Owner#getOrNull() is pretty much incompatible with lazy loading of the FlowExecution-- either we violate its premise of not blocking (in which case, why bother with it) or we accept bogus nulls when lazy load hasn't happened. We *may* consider switching consumers of that API to blocking calls maybe (it is only used a tiny number of places). 2. The WorkflowRun.executionPromise field can be null freely since it is only initialized on first run... we could solve this with a lazy-initialization on the getter, but that really mandates synchronization and I cannot determine which of 3 objects we should be synchronizing on (the run, the copyLogsGuard, or LOADING_RUNS). NPEs that could be thrown within getOrNull when loading the build are, um, swallowed if your log level is >FINE (it only logs them). 3. We could add null checks for the executionPromise in the first few places it's touched, and have getOrNull take advantage of that 4. WorkflowRun#getExecutionPromise is (aside from the Owner.getOrNull) exclusively used in tests to wait until the run begins. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45480) GIT Build with Parameters is not listing branches
Title: Message Title Boguslaw Klimas updated an issue Jenkins / JENKINS-45480 GIT Build with Parameters is not listing branches Change By: Boguslaw Klimas Labels: ssh_error Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50784) "Replay" pipeline button/link is not (always?) available (anymore?)
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-50784 "Replay" pipeline button/link is not (always?) available (anymore?) Change By: Sam Van Oort Labels: regression Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49596) User session memory leak
Title: Message Title marc macintyre commented on JENKINS-49596 Re: User session memory leak Prior to this fix, I'd been setting --sessionTimeout=N in my java options to extend the session. Is there an equivalent way to set the eviction policy to longer than 30 minutes, or is my only option to add a groovy script to JENKINS_HOME/init.groovy.d? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50784) "Replay" pipeline button/link is not (always?) available (anymore?)
Title: Message Title Sam Van Oort commented on JENKINS-50784 Re: "Replay" pipeline button/link is not (always?) available (anymore?) So, as best I can determine: 1. WorkflowRun.Owner#getOrNull() is pretty much incompatible with lazy loading of the FlowExecution-- either we violate its premise of not blocking (in which case, why bother with it) or we accept bogus nulls when lazy load hasn't happened. We may consider switching consumers of that API to blocking calls maybe (it is only used a tiny number of places). 2. The WorkflowRun.executionPromise field can be null freely since it is only initialized on first run... we could solve this with a lazy-initialization on the getter, but that really mandates synchronization and I cannot determine which of 3 objects we should be synchronizing on (the run, the copyLogsGuard, or LOADING_RUNS). NPEs that could be thrown within getOrNull when loading the build are, um, swallowed if your log level is >FINE (it only logs them). 3. We could add null checks for the executionPromise in the first few places it's touched, and have getOrNull 4. WorkflowRun#getExecutionPromise is (aside from the Owner.getOrNull) exclusively used in tests to wait until the run begins. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Adam Daughterson edited a comment on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
After upgrade to this crufty new version of pipeline, all multibranch pipelines using older (eg no declarative pipeline stuffs like pipeline\{} agent\{} etc) syntax have now a useless name for the git repo, and first part of the name is truncated instead of the ending. Setting jenkins.branch.WorkspaceLocatorImpl.PATH_MAX=0 has no noticeable effect. Combining new and old syntax does not appear to get beyond carving a workspace, and attempting to set workspace via customWorkspace doesn't work at all.Who approved this disruptive myopic change? Way to break everything...
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Adam Daughterson commented on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
After upgrade to this crufty new version of pipeline, all multibranch pipelines using older (eg no declarative pipeline stuffs like pipeline{} agent{} etc) syntax have now a useless name for the git repo, and first part of the name is truncated instead of the ending. Setting jenkins.branch.WorkspaceLocatorImpl.PATH_MAX=0 has no noticeable effect. Combining new and syntax does not appear to get beyond carving a workspace, and attempting to set workspace via customWorkspace doesn't work at all. Who approved this disruptive myopic change? Way to break everything...
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49098) Job DSL Plugin extended email trigger send-to list cannot be emptied
Title: Message Title Namikaze Minato commented on JENKINS-49098 Re: Job DSL Plugin extended email trigger send-to list cannot be emptied Nevermind, it was released in 1.68 and I have waited two months for nothing ^^' Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49098) Job DSL Plugin extended email trigger send-to list cannot be emptied
Title: Message Title Namikaze Minato edited a comment on JENKINS-49098 Re: Job DSL Plugin extended email trigger send-to list cannot be emptied @ [~daspilker] This , this was not released in 1.69, do you plan to release it in 1.70?Minato Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49098) Job DSL Plugin extended email trigger send-to list cannot be emptied
Title: Message Title Namikaze Minato edited a comment on JENKINS-49098 Re: Job DSL Plugin extended email trigger send-to list cannot be emptied [~daspilker] This was not released in 1.69, do you plan to release it in 1.70?Minato Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49098) Job DSL Plugin extended email trigger send-to list cannot be emptied
Title: Message Title Namikaze Minato commented on JENKINS-49098 Re: Job DSL Plugin extended email trigger send-to list cannot be emptied This was not released in 1.69, do you plan to release it in 1.70? Minato Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50815) beside GIT_BRANCH also expose it as BRANCH
Title: Message Title Andrew Bayer commented on JENKINS-50815 Re: beside GIT_BRANCH also expose it as BRANCH It's worth considering adding some backup heuristics in Declarative - i.e., if env.BRANCH is undefined, check env.GIT_BRANCH, etc... Will need to think about this. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50791) Got "Ambiguous method overloading" for trampoline()
Title: Message Title Andrew Bayer commented on JENKINS-50791 Re: Got "Ambiguous method overloading" for trampoline() So the problem here, at least initially, isn't the trampolining - it's ambiguity on types. I found this, which suggested changing from number * theFactorial to number * (theFactorial ?: 1), at which point the error went away. But! TrampolineClosure isn't going to work in CPS Pipeline code in general - pretty much anything that nests a Closure#call invocation inside a class that's defined outside of the Pipeline code (i.e., TrampolineClosure and its calls to original.call(...) is going to result in confusion. This'll work fine in a @NonCPS-annotated method, though. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30744) multibranch issues if branch contains /
Title: Message Title Varun Reddy commented on JENKINS-30744 Re: multibranch issues if branch contains / I am currently using the Branching strategy to include - instead of / . But the default behavior in setting up git flow branches are / . Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50216) Google Auth Plugin is incompatible with Jenkins 2.102+
Title: Message Title Oleg Nenashev updated JENKINS-50216 Jenkins / JENKINS-50216 Google Auth Plugin is incompatible with Jenkins 2.102+ Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50216) Google Auth Plugin is incompatible with Jenkins 2.102+
Title: Message Title Oleg Nenashev commented on JENKINS-50216 Re: Google Auth Plugin is incompatible with Jenkins 2.102+ I have created a fix proposal in https://github.com/jenkinsci/google-oauth-plugin/pull/15, needs reviews Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50785) when stage and input stage both is not work
Title: Message Title Andrew Bayer commented on JENKINS-50785 Re: when stage and input stage both is not work Also, input is evaluated before when, so input will always be evaluated. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50791) Got "Ambiguous method overloading" for trampoline()
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-50791 Got "Ambiguous method overloading" for trampoline() Change By: Andrew Bayer Component/s: workflow-cps-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50595) build history disappeared after upgrade to 2.107.1
Title: Message Title Thomas Frearson commented on JENKINS-50595 Re: build history disappeared after upgrade to 2.107.1 going to this latest release, yes. I used the "upgrade automatically". for the last release though, I switched from the weekly builds to the Stable build. I'm wondering if I had an issue somewhere in that process. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17228) Fail build when subversion workspace is locked
Title: Message Title Nick Owens commented on JENKINS-17228 Re: Fail build when subversion workspace is locked Please fix this or at least add a toggle to svn settings so you can choose to either "just fail", or "get fresh workspace" if the error is SVNErrorCode.WC_LOCKED Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50595) build history disappeared after upgrade to 2.107.1
Title: Message Title Jennifer schuch commented on JENKINS-50595 Re: build history disappeared after upgrade to 2.107.1 I'll find out by tomorrow morning. Those jobs are scheduled to run this evening. I'll update tomorrow. For this update, I had selected their 'upgrade automatically'. Is this how you updated? I'm wondering if it's an issue via their war, instead of using their windows installer package. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50830) Update plugin meet Socket Time Exception
Title: Message Title Joseph Petersen assigned an issue to Unassigned Jenkins / JENKINS-50830 Update plugin meet Socket Time Exception Change By: Joseph Petersen Assignee: Joseph Petersen Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50830) Update plugin meet Socket Time Exception
Title: Message Title Joseph Petersen updated an issue Jenkins / JENKINS-50830 Update plugin meet Socket Time Exception Change By: Joseph Petersen Component/s: _unsorted Component/s: accurev-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50830) Update plugin meet Socket Time Exception
Title: Message Title Joseph Petersen edited a comment on JENKINS-50830 Re: Update plugin meet Socket Time Exception Not sure I can help, the stacktrace you given me points to the update center. Nothing here is related to Accurev plugin Seems more like something you should post on jenkins user mailing list: [ https://groups.google.com/forum/#!forum/jenkinsci-users ] Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50830) Update plugin meet Socket Time Exception
Title: Message Title Joseph Petersen closed an issue as Cannot Reproduce Jenkins / JENKINS-50830 Update plugin meet Socket Time Exception Change By: Joseph Petersen Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50830) Update plugin meet Socket Time Exception
Title: Message Title Joseph Petersen commented on JENKINS-50830 Re: Update plugin meet Socket Time Exception Not sure I can help, the stacktrace you given me points to the update center. Seems more like something you should post on jenkins user mailing list: https://groups.google.com/forum/#!forum/jenkinsci-users Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50595) build history disappeared after upgrade to 2.107.1
Title: Message Title Thomas Frearson commented on JENKINS-50595 Re: build history disappeared after upgrade to 2.107.1 decided to purge build history of impacted build jobs and start anew Did this work? Do the affected builds now have a build history? I have a few job that are being affected and may have to do the same. I'm not sure how those build.xml files stopped being created in each build. That's the correlation I noticed though, is that jobs with accurate build history had a build.xml file in each build dir, job with disappearing history didn't have one. I'm surprised that no one else has reported this issue, not sure what to do next short of re-deploying the build master to see if that fixes it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50830) Update plugin meet Socket Time Exception
Title: Message Title
Joseph Petersen updated an issue
Jenkins / JENKINS-50830
Update plugin meet Socket Time Exception
Change By:
Joseph Petersen
After install Jenkins to my PC then login to local Jenkins with created profile.when I update the plugin then meet the issue as below: {code:java} java.net.SocketTimeoutException: connect timed out at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source) at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source) at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source) at java.net.AbstractPlainSocketImpl.connect(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at sun.net.NetworkClient.doConnect(Unknown Source) at sun.net.www.http.HttpClient.openServer(Unknown Source) at sun.net.www.http.HttpClient.openServer(Unknown Source) at sun.net.www.http.HttpClient.(Unknown Source) at sun.net.www.http.HttpClient.New(Unknown Source) at sun.net.www.http.HttpClient.New(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getHeaderField(Unknown Source) at java.net.URLConnection.getHeaderFieldLong(Unknown Source) at java.net.URLConnection.getContentLengthLong(Unknown Source) at java.net.URLConnection.getContentLength(Unknown Source) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1126) Caused: java.net.SocketTimeoutException: connect timed out at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection$10.run(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection$10.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.net.www.protocol.http.HttpURLConnection.getChainedException(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1139) Caused: java.io.IOException: Failed to load http://updates.jenkins-ci.org/download/plugins/script-security/1.43/script-security.hpi to C:\Users\Administrator.LG-20171104SUTB\.jenkins\plugins\script-security.jpi.tmp at
[JIRA] (JENKINS-47978) Lightweight checkout not working for branches that contain forward slash '/'
Title: Message Title
Anna Tikhonova edited a comment on JENKINS-47978
Re: Lightweight checkout not working for branches that contain forward slash '/'
The workaround is to put 'refs/heads/feature/test' in Branch Specifier field of Git SCM. Not 'feature/test', not '*/feature/test'. You have to specify your git ref at full as this is the only supported case. See the breaking code in git-plugin (src/main/java//jenkins/plugins/git/GitSCMFileSystem.java):{code:java}@Extension(ordinal = Short.MIN_VALUE)public static class BuilderImpl extends SCMFileSystem.Builder { @Override public boolean supports(SCM source) {return source instanceof GitSCM && ((GitSCM) source).getUserRemoteConfigs().size() == 1 && ((GitSCM) source).getBranches().size() == 1 && ((GitSCM) source).getBranches().get(0).getName().matches( "^((\\Q" + Constants.R_HEADS + "\\E.*)|([^/]+)|(\\*/[^/*]+(/[^/*]+)*))$"// HERE !!); // we only support where the branch spec is obvious{code}I think this simple implementation is good and the only issue here is the match failing silently. Probably, this method should put a warning to the Console explaining why lightweight checkout failed.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47978) Lightweight checkout not working for branches that contain forward slash '/'
Title: Message Title
Anna Tikhonova edited a comment on JENKINS-47978
Re: Lightweight checkout not working for branches that contain forward slash '/'
The workaround is to put 'refs/heads/feature/test' in Branch Specifier field of Git SCM. Not 'feature/test', not '*/feature/test'. You have to specify your git ref at full as this is the only supported case. See the breaking code in git-plugin (src/main/java//jenkins/plugins/git/GitSCMFileSystem.java):{code:java}@Extension(ordinal = Short.MIN_VALUE)public static class BuilderImpl extends SCMFileSystem.Builder { @Override public boolean supports(SCM source) {return source instanceof GitSCM && ((GitSCM) source).getUserRemoteConfigs().size() == 1 && ((GitSCM) source).getBranches().size() == 1 && ((GitSCM) source).getBranches().get(0).getName().matches( "^((\\Q" + Constants.R_HEADS + "\\E.*)|([^/]+)|(\\*/[^/*]+(/[^/*]+)*))$"// HERE !!); // we only support where the branch spec is obvious{code} I think this simple implementation is good and the only issue here is the match failing silently. Probably, this method should put a warning to the Console why lightweight checkout failed.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50635) NUnit plugin does not fail build on test-runner error
Title: Message Title Alex Earl commented on JENKINS-50635 Re: NUnit plugin does not fail build on test-runner error Would it be possible for you to enable the option to save the JUnit files that are generated and then upload the resulting JUnit file? The current XSLT transform should actually work for the case of setting it to unstable, so I want to see what the resulting transform creates. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50595) build history disappeared after upgrade to 2.107.1
Title: Message Title Jennifer schuch commented on JENKINS-50595 Re: build history disappeared after upgrade to 2.107.1 nothing is being reported in the system logs. appears that the config.xml upgraded to 1.1, i reverted back my installation of Jenkins to the previous version I had on this server. Build history seems to now be 'lost'. decided to purge build history of impacted build jobs and start anew. there is/are no build.xml files located in root of directory of impacted build jobs. build.xml does exist in build number directories of jobs not impacted by this issue. how would these build.xml files 'disappear'? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45997) BitBucket PRs failing to checkout on initial run after PR updated with new commits
Title: Message Title Aleksey Smyrnov commented on JENKINS-45997 Re: BitBucket PRs failing to checkout on initial run after PR updated with new commits I've faced same problem today - but with GitHub and it's Pull Requests: Pull request #339 updated 16:23:22 Connecting to https://api.github.com using botaccount/** (botaccount-github-userpass) Checking out git g...@github.com:team/project.git into /var/jenkins_home/workspace/team_unilanding_PR-339-QD7W5G5UCQBK3XJQYNPM6GQDRVGPY6TQABV6SD4RWHXU2EDQR65A@script to read Jenkinsfile > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url g...@github.com:team/project.git # timeout=10 Fetching without tags Fetching upstream changes from g...@github.com:team/project.git > git --version # timeout=10 using GIT_SSH to set credentials botaccount-github-ssh-key > git fetch --no-tags --progress g...@github.com:team/project.git +refs/pull/339/head:refs/remotes/origin/PR-339 +refs/heads/master:refs/remotes/origin/master Merging remotes/origin/master commit bb79fa5bd122fa0fac4608d10a9ccd41dc2e72f7 into PR head commit dc38ea253251ca79a4587c20b25b425ede135de7 > git config core.sparsecheckout # timeout=10 > git checkout -f dc38ea253251ca79a4587c20b25b425ede135de7 GitHub has been notified of this commit’s build result hudson.plugins.git.GitException: Command "git checkout -f dc38ea253251ca79a4587c20b25b425ede135de7" returned status code 128: stdout: stderr: fatal: reference is not a tree: dc38ea253251ca79a4587c20b25b425ede135de7 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1996) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$800(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:2295) Caused: hudson.plugins.git.GitException: Could not checkout dc38ea253251ca79a4587c20b25b425ede135de7 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:2319) at jenkins.plugins.git.MergeWithGitSCMExtension.checkout(MergeWithGitSCMExtension.java:146) at jenkins.plugins.git.MergeWithGitSCMExtension.decorateRevisionToBuild(MergeWithGitSCMExtension.java:112) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:1068) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1161) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:143) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:120) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:295) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Finished: FAILURE Only closing old PR and re-creating it can solve this problem. Need this fix for GitHub.
[JIRA] (JENKINS-50730) NoClassDefFound errors in Cloud Slaves
Title: Message Title
Emmanuel Costa edited a comment on JENKINS-50730
Re: NoClassDefFound errors in Cloud Slaves
We are observing the same bug on our production system,{code:java}2018-04-16 16:16:34.028:INFO:osjs.Server:main: Started @1199ms16:16:34.028 INFO - Selenium Server is up and runningApr 16, 2018 4:16:34 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Apr 16, 2018 4:16:34 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful Agent address: jenkins. bankin . io XXX Agent port: Identity: 62:69:42:d7:6c:31:25:9d:ab:7e:97:4f:de:36:2a:b1Apr 16, 2018 4:16:34 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingApr 16, 2018 4:16:34 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to jenkins. bankin XXX . io XX :Apr 16, 2018 4:16:34 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectApr 16, 2018 4:16:34 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: Remote identity confirmed: 62:69:42:d7:6c:31:25:9d:ab:7e:97:4f:de:36:2a:b1Apr 16, 2018 4:16:34 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: ConnectedApr 16, 2018 4:29:51 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: TerminatedApr 16, 2018 4:30:01 PM hudson.remoting.jnlp.Main$CuiListener errorSEVERE: jenkins/slaves/restarter/JnlpSlaveRestarterInstallerjava.lang.NoClassDefFoundError: jenkins/slaves/restarter/JnlpSlaveRestarterInstallerat jenkins.slaves.restarter.JnlpSlaveRestarterInstaller$FindEffectiveRestarters$1.onReconnect(JnlpSlaveRestarterInstaller.java:97)at hudson.remoting.EngineListenerSplitter.onReconnect(EngineListenerSplitter.java:49)at hudson.remoting.Engine.innerRun(Engine.java:643)at hudson.remoting.Engine.run(Engine.java:451)Caused by: java.lang.ClassNotFoundException: jenkins.slaves.restarter.JnlpSlaveRestarterInstallerat java.net.URLClassLoader.findClass(URLClassLoader.java:381)at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:157)at java.lang.ClassLoader.loadClass(ClassLoader.java:424)at java.lang.ClassLoader.loadClass(ClassLoader.java:357)... 4 more{code}
Add Comment
[JIRA] (JENKINS-50730) NoClassDefFound errors in Cloud Slaves
Title: Message Title Emmanuel Costa commented on JENKINS-50730 Re: NoClassDefFound errors in Cloud Slaves We are observing the same bug on our production system, 2018-04-16 16:16:34.028:INFO:osjs.Server:main: Started @1199ms 16:16:34.028 INFO - Selenium Server is up and running Apr 16, 2018 4:16:34 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping] Apr 16, 2018 4:16:34 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Agent discovery successful Agent address: jenkins.bankin.io Agent port: Identity: 62:69:42:d7:6c:31:25:9d:ab:7e:97:4f:de:36:2a:b1 Apr 16, 2018 4:16:34 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking Apr 16, 2018 4:16:34 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to jenkins.bankin.io: Apr 16, 2018 4:16:34 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Trying protocol: JNLP4-connect Apr 16, 2018 4:16:34 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Remote identity confirmed: 62:69:42:d7:6c:31:25:9d:ab:7e:97:4f:de:36:2a:b1 Apr 16, 2018 4:16:34 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connected Apr 16, 2018 4:29:51 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Terminated Apr 16, 2018 4:30:01 PM hudson.remoting.jnlp.Main$CuiListener error SEVERE: jenkins/slaves/restarter/JnlpSlaveRestarterInstaller java.lang.NoClassDefFoundError: jenkins/slaves/restarter/JnlpSlaveRestarterInstaller at jenkins.slaves.restarter.JnlpSlaveRestarterInstaller$FindEffectiveRestarters$1.onReconnect(JnlpSlaveRestarterInstaller.java:97) at hudson.remoting.EngineListenerSplitter.onReconnect(EngineListenerSplitter.java:49) at hudson.remoting.Engine.innerRun(Engine.java:643) at hudson.remoting.Engine.run(Engine.java:451) Caused by: java.lang.ClassNotFoundException: jenkins.slaves.restarter.JnlpSlaveRestarterInstaller at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:157) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 4 more Add Comment
[JIRA] (JENKINS-47978) Lightweight checkout not working for branches that contain forward slash '/'
Title: Message Title
Anna Tikhonova commented on JENKINS-47978
Re: Lightweight checkout not working for branches that contain forward slash '/'
The workaround is to put 'refs/heads/feature/test' in Branch Specifier field of Git SCM. Not 'feature/test', not '*/feature/test'. You have to specify your git ref at full as this is the only supported case. See the breaking code in git-plugin (src/main/java//jenkins/plugins/git/GitSCMFileSystem.java):
@Extension(ordinal = Short.MIN_VALUE)
public static class BuilderImpl extends SCMFileSystem.Builder {
@Override
public boolean supports(SCM source) {
return source instanceof GitSCM
&& ((GitSCM) source).getUserRemoteConfigs().size() == 1
&& ((GitSCM) source).getBranches().size() == 1
&& ((GitSCM) source).getBranches().get(0).getName().matches(
"^((\\Q" + Constants.R_HEADS + "\\E.*)|([^/]+)|(\\*/[^/*]+(/[^/*]+)*))$"// HERE !!
);
// we only support where the branch spec is obvious
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50831) ssh_exchange_identification connection reset by peer
Title: Message Title Rodrigo Porto commented on JENKINS-50831 Re: ssh_exchange_identification connection reset by peer Hi, Thank you very much for the information, Regards Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50831) ssh_exchange_identification connection reset by peer
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-50831 ssh_exchange_identification connection reset by peer Change By: Mark Waite Summary: ssh_key_exchange ssh_exchange_identification connection reset by peer Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48933) Unstoppable Multibranch Pipeline Scan
Title: Message Title David Taylor commented on JENKINS-48933 Re: Unstoppable Multibranch Pipeline Scan Having this exact same issue. No updates? It's been a few months Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50831) ssh_key_exchange connection reset by peer
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-50831 ssh_key_exchange connection reset by peer Change By: Mark Waite Summary: Repository is not reachable ssh_key_exchange connection reset by peer Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50831) Repository is not reachable
Title: Message Title Mark Waite resolved as Not A Defect The log file shows: using GIT_SSH to set credentials > git fetch --tags --progress my_repository +refs/heads/*:refs/remotes/origin/* ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "git fetch --tags --progress my_repository +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: ssh_exchange_identification: read: Connection reset by peer fatal: Could not read from remote repository. The ssh server on your git host is closing the connection. It could be due to any number of network connection issues between the agent running that pod template and the ssh server on your git host. It is very, very rare that those types of issues are bugs. Please use the Internet Relay Chat or the Jenkins users mailing list to request help with authentication and connectivity issues. There are many more people monitoring those lists than there are people who monitor bug reports submitted to the git plugin Jenkins / JENKINS-50831 Repository is not reachable Change By: Mark Waite Status: Open Resolved Resolution: Not A Defect Add Comment
[JIRA] (JENKINS-50831) Repository is not reachable
Title: Message Title
Rodrigo Porto updated an issue
Jenkins / JENKINS-50831
Repository is not reachable
Change By:
Rodrigo Porto
Hi everyone,I have an issue with *Kubernetes Plugin* and *Jenkins Slave*. If I build a simple pipeline, everything works, for example:{code:java}node {git branch: 'master',credentialsId: ‘crediantials-number’,url: my_repository}{code}However, if I try to build a pipeline via *Kubernetes Plugin*, for example:{code:java}def label = "test"podTemplate(label: label) { node(label) { stage('Deploy Test on Kubernetes') { git branch: 'master', credentialsId: ‘crediantials-number’, url: my_repository } }}{code}I receive the next error:{code:java} at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Thread.java:748) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.47.0.152/10.47.0.152:34226 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1737) at hudson.remoting.UserResponse.retrieve(UserRequest.java:313) at hudson.remoting.Channel.call(Channel.java:952) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43){code} I attach some files in order to provide further information.Thanks in advance,Regards
Add Comment
[JIRA] (JENKINS-50831) Repository is not reachable
Title: Message Title
Rodrigo Porto updated an issue
Jenkins / JENKINS-50831
Repository is not reachable
Change By:
Rodrigo Porto
Hi everyone,I have an issue with *Kubernetes Plugin* and *Jenkins Slave*. If I build a simple pipeline, everything works, for example:{code:java}node {git branch: 'master',credentialsId: ‘crediantials-number’,url: my_repository}{code}However, if I try to build a pipeline via *Kubernetes Plugin*, for example:{code:java}def label = "test"podTemplate(label: label) { node(label) { stage('Deploy Test on Kubernetes') { git branch: 'master', credentialsId: ‘crediantials-number’, url: my_repository } }}{code}I receive the next error:{code:java} at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Thread.java:748) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.47.0.152/10.47.0.152:34226 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1737) at hudson.remoting.UserResponse.retrieve(UserRequest.java:313) at hudson.remoting.Channel.call(Channel.java:952) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43){code} I attach a file some files in order to provide further information.Thanks in advance,Regards
Add Comment
[JIRA] (JENKINS-40717) Enable authentication using Kubernetes service account token
Title: Message Title Nitin Padalia edited a comment on JENKINS-40717 Re: Enable authentication using Kubernetes service account token Hi [~csanchez] I am not able to see any token value which I can provide using this plugin.It is automatically creating some token value. I am using latest version of kubernetes-credentials-plugin.I Jenkins master is outside of Kubernetes cluster. Am I doing something wrong? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50831) Repository is not reachable
Title: Message Title Rodrigo Porto updated an issue Jenkins / JENKINS-50831 Repository is not reachable Change By: Rodrigo Porto Attachment: jenkins.log Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
