[JIRA] (JENKINS-52922) slave is getting disconnected in the middle of the job
Title: Message Title sumanthnath gangavarapu commented on JENKINS-52922 Re: slave is getting disconnected in the middle of the job We are using below SSH slave and Windows Slaves plugins to connect with the slaves. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52922) slave is getting disconnected in the middle of the job
Title: Message Title sumanthnath gangavarapu updated an issue Jenkins / JENKINS-52922 slave is getting disconnected in the middle of the job Change By: sumanthnath gangavarapu Attachment: image-2018-08-08-10-59-23-440.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-37934) NTLM Authentication No Matter What
Title: Message Title Mark Waite updated JENKINS-37934 A fix was also included in JGit to allow NTLM authentication to be used more reliably on Windows. The JGit version with the fix is included in git client plugin 3.0.0-beta5. Jenkins / JENKINS-37934 NTLM Authentication No Matter What Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-29644) Branch parameter ignored when a non-parameterized branch is also monitored
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-29644 Branch parameter ignored when a non-parameterized branch is also monitored Change By: Mark Waite Summary: can't use build triggers along with branch Branch parameterignored when a non-parameterized branch is also monitored Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-35648) Aborting thread doing git operation leaves repository in unclean state
Title: Message Title Mark Waite updated JENKINS-35648 Jenkins / JENKINS-35648 Aborting thread doing git operation leaves repository in unclean state Change By: Mark Waite Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25353) Git operations fail due to "dead", but lingering lock file
Title: Message Title Mark Waite updated JENKINS-25353 Jenkins / JENKINS-25353 Git operations fail due to "dead", but lingering lock file Change By: Mark Waite Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25353) Git operations fail due to "dead", but lingering lock file
Title: Message Title Mark Waite updated JENKINS-25353 Jenkins / JENKINS-25353 Git operations fail due to "dead", but lingering lock file Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25353) Git operations fail due to "dead", but lingering lock file
Title: Message Title Mark Waite updated JENKINS-25353 Jenkins / JENKINS-25353 Git operations fail due to "dead", but lingering lock file Change By: Mark Waite Status: Reopened Open Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-35648) Aborting thread doing git operation leaves repository in unclean state
Title: Message Title Mark Waite updated JENKINS-35648 Jenkins / JENKINS-35648 Aborting thread doing git operation leaves repository in unclean state Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-47652) "Another git process seems to be running in this repository" when Jenkins is the only thing using workspaces
Title: Message Title Mark Waite updated JENKINS-47652 Jenkins / JENKINS-47652 "Another git process seems to be running in this repository" when Jenkins is the only thing using workspaces Change By: Mark Waite Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-47652) "Another git process seems to be running in this repository" when Jenkins is the only thing using workspaces
Title: Message Title Mark Waite updated JENKINS-47652 Jenkins / JENKINS-47652 "Another git process seems to be running in this repository" when Jenkins is the only thing using workspaces Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Mark Waite updated JENKINS-48258 Jenkins / JENKINS-48258 git client plugin occasionally fails with "text file busy" error Change By: Mark Waite Status: Reopened Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52078) Git fails to fetch from private repo when credentials manager enabled
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-52078 Git fails to fetch from private repo when credentials manager enabled Change By: Mark Waite Summary: Github plugins Git fails to fetch from private repo when credentials manager enabled Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52798) Platform labeler plugin does not recognize Alpine linux
Title: Message Title Mark Waite updated JENKINS-52798 Jenkins / JENKINS-52798 Platform labeler plugin does not recognize Alpine linux Change By: Mark Waite Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52798) Platform labeler plugin does not recognize Alpine linux
Title: Message Title Mark Waite updated JENKINS-52798 Released in platformlabeler 2.1 released 30 July 2018. Jenkins / JENKINS-52798 Platform labeler plugin does not recognize Alpine linux Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52798) Platform labeler plugin does not recognize Alpine linux
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-52798 Platform labeler plugin does not recognize Alpine linux Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52856) Pipeline checkout stage fails with "java.io.IOException: Unable to serialize"
Title: Message Title Mark Waite commented on JENKINS-52856 Re: Pipeline checkout stage fails with "java.io.IOException: Unable to serialize" Can you provide enough details that someone else can duplicate the problem? Have you tried the git client plugin 3.0.0-beta5, since it includes a change which resolves another case of "serialization of anonymous classes" as noted in f7126b1ec13f74f612d0413febb20f5f83eb0508. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52927) Manager Jenkins >> Configure Global Security >> Matrix Based Security - Not able to Submit
Title: Message Title Upen Rajkumar updated an issue Jenkins / JENKINS-52927 Manager Jenkins >> Configure Global Security >> Matrix Based Security - Not able to Submit Change By: Upen Rajkumar Attachment: PastedGraphic-16.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52927) Manager Jenkins >> Configure Global Security >> Matrix Based Security - Not able to Submit
Title: Message Title Upen Rajkumar updated an issue Jenkins / JENKINS-52927 Manager Jenkins >> Configure Global Security >> Matrix Based Security - Not able to Submit Change By: Upen Rajkumar When I try to submit a change Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52927) Manager Jenkins >> Configure Global Security >> Matrix Based Security - Not able to Submit
Title: Message Title
Upen Rajkumar updated an issue
Jenkins / JENKINS-52927
Manager Jenkins >> Configure Global Security >> Matrix Based Security - Not able to Submit
Change By:
Upen Rajkumar
When I try to submit a change under Matrix Auth Table, below error pops up. Aug 07, 2018 6:08:35 PM hudson.init.impl.InstallUncaughtExceptionHandler$1 reportExceptionWARNING: nulljavax.servlet.ServletException: This page expects a form submission but had only {}at org.kohsuke.stapler.RequestImpl.getSubmittedForm(RequestImpl.java:1013)at hudson.security.GlobalSecurityConfiguration.doConfigure(GlobalSecurityConfiguration.java:101)at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343)at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:52)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.Stapler.invoke(Stapler.java:649)at org.kohsuke.stapler.Stapler.service(Stapler.java:238)at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135)at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:47)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:59)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:138)at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49)at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)at
[JIRA] (JENKINS-52927) Manager Jenkins >> Configure Global Security >> Matrix Based Security - Not able to Submit
Title: Message Title Upen Rajkumar created an issue Jenkins / JENKINS-52927 Manager Jenkins >> Configure Global Security >> Matrix Based Security - Not able to Submit Issue Type: Bug Assignee: Daniel Beck Components: matrix-auth-plugin Created: 2018-08-08 04:20 Environment: Jenkins 2.73.1 OEL7 Linux 64. Jenkins war under tomcat Priority: Blocker Reporter: Upen Rajkumar Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this
[JIRA] (JENKINS-52856) Pipeline checkout stage fails with "java.io.IOException: Unable to serialize"
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-52856 Pipeline checkout stage fails with "java.io.IOException: Unable to serialize" Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52926) "Git Build Data" should not appear more than once in the side menu for pipeline builds
Title: Message Title Mark Waite commented on JENKINS-52926 Re: "Git Build Data" should not appear more than once in the side menu for pipeline builds Thanks for the further explanation. You might perform the merge once, stash the result, then unstash it on each of the other platforms, rather than performing the merge on every platform. As another alternative, you might perform the checkout once on every platform, perform the merge on one, generate a patch of the merge result, stash the patch, and unstash the patch on each of the targets. You said: using the hash is not a good idea for deduplicating what code is being built The SHA-1 hash is the most natural choice to decide if something has changed. Performing the same merge on multiple agents is not a use case that the plugin is ready to handle. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52828) Add slave suffix command
Title: Message Title Tomonori Iida commented on JENKINS-52828 Re: Add slave suffix command Pull Request: https://github.com/jenkinsci/ec2-plugin/pull/297 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52174) parameter of type run not added to params
Title: Message Title Jarrad Whitaker edited a comment on JENKINS-52174 Re: parameter of type run not added to params See bludgeon-level PR at [https://github.com/jenkinsci/jenkins/pull/3578] .Can't find docs on how you go about making API changes (maybe that means you never do? eep), but as a sanity check, I cannot find any usages of `getValue()` on a `RunParameterValue` by using github search on the jenkinsci organization. (Searched for `RunParameterValue` and manually inspected usages. I guess it's still possible that someone could use ParameterValue.getValue instanceof Run...).Edit: also searched for "instanceof Run" "ParameterValue" with no relevant results.Is this approach with worth pursuing? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52174) parameter of type run not added to params
Title: Message Title Jarrad Whitaker edited a comment on JENKINS-52174 Re: parameter of type run not added to params See bludgeon-level PR at [https://github.com/jenkinsci/jenkins/pull/3578] .Can't find docs on how you go about making API changes (maybe that means you never do? eep), but as a sanity check, I cannot find any usages of `getValue()` on a `RunParameterValue` by using github search on the jenkinsci organization. (Searched for `RunParameterValue` and manually inspected usages. I guess it's still possible that someone could use ParameterValue.getValue instanceof Run...). Edit: also searched for "instanceof Run" "ParameterValue" with no relevant results. Is this approach with pursuing? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52926) "Git Build Data" should not appear more than once in the side menu for pipeline builds
Title: Message Title trejkaz commented on JENKINS-52926 Re: "Git Build Data" should not appear more than once in the side menu for pipeline builds The job is a pipeline job. Multiple checkouts do get performed, but I think that's a necessity? Otherwise, I don't understand how code would get from the node coordinating the build to each of the individual nodes doing the build. The hash built is different every time a separate node is spun off, because the merge gets performed again and git hashes are essentially random numbers, rather than actual hashes of the content. The multiple hashes reflect the random number each merge generated when the build for that node was performed. When I'm essentially saying is that using the hash is not a good idea for deduplicating what code is being built, because when a merge has occurred, the number is not usable in any way. If you replaced that information with enough information to actually reproduce the build, and then deduplicated on that, I think all the items would deduplicate properly. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52174) parameter of type run not added to params
Title: Message Title Jarrad Whitaker commented on JENKINS-52174 Re: parameter of type run not added to params See bludgeon-level PR at https://github.com/jenkinsci/jenkins/pull/3578 . Can't find docs on how you go about making API changes (maybe that means you never do? eep), but as a sanity check, I cannot find any usages of `getValue()` on a `RunParameterValue` by using github search on the jenkinsci organization. (Searched for `RunParameterValue` and manually inspected usages. I guess it's still possible that someone could use ParameterValue.getValue instanceof Run...). Is this approach with pursuing? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52919) Client secret not masked in build log when using withCredentials([azureServicePrincipal(id)])
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-52919 Client secret not masked in build log when using withCredentials([azureServicePrincipal(id)]) Change By: Jie Shen Assignee: Azure DevOps Jie Shen Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52926) "Git Build Data" should not appear more than once in the side menu for pipeline builds
Title: Message Title Mark Waite edited a comment on JENKINS-52926 Re: "Git Build Data" should not appear more than once in the side menu for pipeline builds Can you provide detailed steps to duplicate the problem? The sample you've provided almost looks like multiple checkout operations are being performed (and I doubt that is what you're actually doing in your build). Are the SHA-1 hashes in the git build data from the preceding builds? Since you indicate that the list continues to grow, it seems likely that they are somehow recording the history of the SHA-1's built by that job.Is the job a Pipeline job or a Freestyle job?If it is a Pipeline job, is it using a Pipeline shared library? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52171) Gitlab plugin uncompatible with Jira plugin in pipeline
Title: Message Title Owen Mehegan commented on JENKINS-52171 Re: Gitlab plugin uncompatible with Jira plugin in pipeline Matej Dro can you please test this patched version of the plugin? It should fix this. http://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/gitlab-plugin/1.5.10-SNAPSHOT/gitlab-plugin-1.5.10-20180808.012800-1.hpi Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52926) "Git Build Data" should not appear more than once in the side menu for pipeline builds
Title: Message Title Mark Waite commented on JENKINS-52926 Re: "Git Build Data" should not appear more than once in the side menu for pipeline builds Can you provide detailed steps to duplicate the problem? The sample you've provided almost looks like multiple checkout operations are being performed (and I doubt that is what you're actually doing in your build). Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52926) "Git Build Data" should not appear more than once in the side menu for pipeline builds
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-52926 "Git Build Data" should not appear more than once in the side menu for pipeline builds Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52704) After update of parent pom, build failure: jenkins/util/SystemProperties must not be used
Title: Message Title HaiTong Wu commented on JENKINS-52704 Re: After update of parent pom, build failure: jenkins/util/SystemProperties must not be used Because the velocity of allocation and releasing nodes is too slow, I modify the code of mesos plugin (v0.13.1). It was built OK. Now I want to update mesos plugin version to 0.17, so I merge my modification to source code of v0,17. But it can't be built. I just used the original pom file in mesos plugin source code. Why it built ok in v0.13.2, but no ok in v0.17? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52926) "Git Build Data" should not appear more than once in the side menu for pipeline builds
Title: Message Title trejkaz created an issue Jenkins / JENKINS-52926 "Git Build Data" should not appear more than once in the side menu for pipeline builds Issue Type: Improvement Assignee: Mark Waite Attachments: Screen Shot 2018-08-08 at 9.34.41 am.png, Screen Shot 2018-08-08 at 9.34.50 am.png, Screen Shot 2018-08-08 at 9.34.58 am.png Components: git-plugin Created: 2018-08-08 00:41 Priority: Minor Reporter: trejkaz Currently, for pipeline builds, every time the pipeline runs on a new node and merges the branch you're building with master, you get an extra "Git Build Data" entry in the sidebar, even though you're building exactly the same thing. The individual screens show different revisions being built:But actually, these are the same PR branch, merged with the same master branch. In this situation, I would expect a single entry, and I would expect the linked page to list the branches which were merged, not to show the commit hash of the merge result. The merge result is literally impossible to access after the build has completed anyway, so there is no point having this information at all.
[JIRA] (JENKINS-52862) Synchronization issue in pipeline SSE event publishing
Title: Message Title Vivek Pandey updated JENKINS-52862 Released in blueocean 1.5.2 and 1.7.2. Jenkins / JENKINS-52862 Synchronization issue in pipeline SSE event publishing Change By: Vivek Pandey Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52862) Synchronization issue in pipeline SSE event publishing
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-52862 Synchronization issue in pipeline SSE event publishing Change By: Vivek Pandey Summary: Performance fix Synchronization issue in pipeline event SSE publisher event publishing Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52862) Performance fix in pipeline event SSE publisher
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-52862 Performance fix in pipeline event SSE publisher Change By: Vivek Pandey Summary: Peformance issue at java.util.WeakHashMap.get(WeakHashMap.java:403) Performance fix in pipeline event SSE publisher Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52174) parameter of type run not added to params
Title: Message Title Jarrad Whitaker commented on JENKINS-52174 Re: parameter of type run not added to params Erp that's a bit of a kuldge. Is it possible to just make a Run parameter serializable? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49050) I can view my sequential declarative pipeline stages in the pipeline visualization plugin
Title: Message Title Chad Bercea commented on JENKINS-49050 Re: I can view my sequential declarative pipeline stages in the pipeline visualization plugin Nicolae Pascu I really like the idea of no longer combining the top most stage name with the name of the "stack". In cases where this happens, what would we name that "parent"? Just curious. Otherwise this looks exactly like what we talked about. Nice! Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-51928) Timeout is caught by the most internal try-catch, but should be caught by the try-catch that surrounds the timeout step
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-51928 Timeout is caught by the most internal try-catch, but should be caught by the try-catch that surrounds the timeout step Change By: Andrew Bayer Component/s: workflow-basic-steps-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-51958) Basic pipeline job Configuration： "Build periodically" is same with "Poll SCM"
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-51958 Basic pipeline job Configuration： "Build periodically" is same with "Poll SCM" Change By: Andrew Bayer Component/s: workflow-job-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52053) Jenkins stash failed after npm install
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-52053 Jenkins stash failed after npm install Change By: Andrew Bayer Component/s: workflow-basic-steps-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52053) Jenkins stash failed after npm install
Title: Message Title Andrew Bayer stopped work on JENKINS-52053 Change By: Andrew Bayer Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52142) Default values in closures are not work
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-52142 Default values in closures are not work Change By: Andrew Bayer Component/s: workflow-cps-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52174) parameter of type run not added to params
Title: Message Title Andrew Bayer updated JENKINS-52174 Regrettably, we can only include parameters in params if they're serializable - and a Run is not serializable. So we have to skip it and not add anything for that parameter. Sorry. Jenkins / JENKINS-52174 parameter of type run not added to params Change By: Andrew Bayer Status: Open Fixed but Unreleased Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52174) parameter of type run not added to params
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-52174 parameter of type run not added to params Change By: Andrew Bayer Component/s: workflow-cps-plugin Component/s: workflow-cps-global-lib-plugin Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52174) parameter of type run not added to params
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-52174 parameter of type run not added to params Change By: Andrew Bayer Component/s: workflow-cps-global-lib-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52209) [Cancelling nested steps due to timeout] aborts a job prematurely
Title: Message Title Andrew Bayer commented on JENKINS-52209 Re: [Cancelling nested steps due to timeout] aborts a job prematurely Could you attach your Jenkinsfile? Thanks. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52209) [Cancelling nested steps due to timeout] aborts a job prematurely
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-52209 [Cancelling nested steps due to timeout] aborts a job prematurely Change By: Andrew Bayer Component/s: pipeline-model-definition-plugin Component/s: core Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52216) Pull Request and pipeline agent
Title: Message Title Andrew Bayer commented on JENKINS-52216 Re: Pull Request and pipeline agent That is deeply weird - I can't reproduce it. Any chance you could zip/tar up the build directories for a build that does the right thing and one that does the wrong thing? I'm talking about the directories like JENKINS_HOME/jobs/repo-name/jobs/branch-name/builds/123. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52216) Pull Request and pipeline agent
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-52216 Pull Request and pipeline agent Change By: Andrew Bayer Component/s: pipeline-model-definition-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52376) Trigger a build by tagging an existing commit
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-52376 Trigger a build by tagging an existing commit Change By: Andrew Bayer Component/s: workflow-job-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52388) Unable to skip Declarative: Checkout SCM when restart from stage
Title: Message Title Andrew Bayer commented on JENKINS-52388 Re: Unable to skip Declarative: Checkout SCM when restart from stage Hmm, interesting. In general, we work with the assumption that any changes to the workspace would need be to be stashed (and then unstashed in the restarted stage) to be preserved, so I'm not sure whether this fits...lemme think on it. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52388) Unable to skip Declarative: Checkout SCM when restart from stage
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-52388 Unable to skip Declarative: Checkout SCM when restart from stage Change By: Andrew Bayer Assignee: Andrew Bayer Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52388) Unable to skip Declarative: Checkout SCM when restart from stage
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-52388 Unable to skip Declarative: Checkout SCM when restart from stage Change By: Andrew Bayer Component/s: pipeline-model-definition-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52859) ps: unrecognized option: p
Title: Message Title Andrew Bayer resolved as Duplicate Jenkins / JENKINS-52859 ps: unrecognized option: p Change By: Andrew Bayer Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52925) postbuildscript-plugin is unable to limit execution on matrix parent only
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-52925 postbuildscript-plugin is unable to limit execution on matrix parent only Change By: Rick Liu Attachment: Selection_021.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52925) postbuildscript-plugin is unable to limit execution on matrix parent only
Title: Message Title Rick Liu closed an issue as Not A Defect I just found a separate postbuild step called "Execute Scripts on Matrix": this allowed "Matrix target" selection for: MATRIX AXES BOTH Jenkins / JENKINS-52925 postbuildscript-plugin is unable to limit execution on matrix parent only Change By: Rick Liu Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-31096) Unicode characters in console logs do not print correctly in Workflow builds
Title: Message Title Jesse Glick updated JENKINS-31096 Released. Please check the plugin wikis for changelog information—it is important to update all four affected plugins. Jenkins / JENKINS-31096 Unicode characters in console logs do not print correctly in Workflow builds Change By: Jesse Glick Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52925) postbuildscript-plugin is unable to limit execution on matrix parent only
Title: Message Title Rick Liu created an issue Jenkins / JENKINS-52925 postbuildscript-plugin is unable to limit execution on matrix parent only Issue Type: Bug Assignee: Daniel Heid Attachments: Selection_019.png, Selection_020.png Components: postbuildscript-plugin Created: 2018-08-07 21:48 Environment: Ubuntu 16.04 Jenkins core: 2.107.3 postbuildscript-plugin: upgraded from 0.17 to 2.7.0 Priority: Critical Reporter: Rick Liu I just upgraded the plugin from 0.17 to the latest 2.7.0. For a matrix job (multi-configuration job), back in 0.17, I was able to select "Execute script on": MATRIX - executed for matrix parent job only AXES - executed for each matrix axes jobs BOTH - executed for both matrix parent and axes jobs But in 2.7.0, I don't see such configuration anymore. I see only "Execution is limited to": Master Slave Both When selecting "Master", the execution still runs for both matrix parent and axes jobs.
[JIRA] (JENKINS-46636) `dir` does not change working directory for contained steps
Title: Message Title Umesh Sharma commented on JENKINS-46636 Re: `dir` does not change working directory for contained steps Any updates or solution to this issue Docker version is older than 17.12, working directory will be /var/jenkins_home/workspace/gsilva-pro_master-FNQGFOZNCGYYR7K4UGJOX5A6UTRZHRZ2ZIJHDRTUJOUALWVMZQJA not /var/jenkins_home/workspace/gsilva-pro_master-FNQGFOZNCGYYR7K4UGJOX5A6UTRZHRZ2ZIJHDRTUJOUALWVMZQJA/web-ui Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-47891) Bitbucket branch source plugin does not understand the new Bitbucket webhooks
Title: Message Title Tom Wieczorek commented on JENKINS-47891 Re: Bitbucket branch source plugin does not understand the new Bitbucket webhooks I'm currently working on native webhook support for Bitbucket Server here: https://github.com/jenkinsci/bitbucket-branch-source-plugin/compare/master...yieldlab:native-webhooks Not yet complete, hence no open Pull Request, but it's partially working already. Maybe this helps already. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52924) Durable Task 1.23 broke bash scripting on Windows agents via Cygwin
Title: Message Title
John Zila updated an issue
Jenkins / JENKINS-52924
Durable Task 1.23 broke bash scripting on Windows agents via Cygwin
Change By:
John Zila
To connect my Windows agent machines, I essentially followed this guide (modified to handle auto-scaling spot fleets via the ec2-fleet-plugin): [ https:// support go .cloudbees.com/ hc docs / en cloudbees - us documentation / articles/222978868 admin - How-to-Connect-to-Remote-SSH-Slaves-] cje/agents/#_configuring_windows_agents Until 1.22, this worked great. Since 1.23, I now get this:{noformat}[client\go] Running shell scriptps: unknown option -- oTry `ps --help' for more information.+ go list ./...+ grep -v github.com/keybase/client/go/bind+ xargs go vetwrapper script does not seem to be touching the log file in c:\Jenkins\workspace/client/master/6615\go/src/github.com/keybase/client\go@tmp\durable-8945eeb6(JENKINS-48300: if on a laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=300) {noformat}The failing line of my Jenkinsfile is here: [https://github.com/keybase/client/blob/aa1fc347042cafba8cf8f48a40bed59e8bce60dd/Jenkinsfile#L309]I believe this has something to do with the fix to the infinite log problem in JENKINS-37575.In the meantime, I've reverted to 1.22, and it's working again.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
[JIRA] (JENKINS-52924) Durable Task 1.23 broke bash scripting on Windows agents via Cygwin
Title: Message Title
John Zila updated an issue
Jenkins / JENKINS-52924
Durable Task 1.23 broke bash scripting on Windows agents via Cygwin
Change By:
John Zila
To connect my Windows agent machines, I essentially followed this guide (modified to handle auto-scaling spot fleets via the ec2-fleet-plugin): [https://support.cloudbees.com/hc/en-us/articles/222978868-How-to-Connect-to-Remote-SSH-Slaves-]Until 1.22, this worked great. Since 1.23, I now get this:{noformat}[client\go] Running shell scriptps: unknown option -- oTry `ps --help' for more information.+ go list ./...+ grep -v github.com/keybase/client/go/bind+ xargs go vetwrapper script does not seem to be touching the log file in c:\Jenkins\workspace/client/master/6615\go/src/github.com/keybase/client\go@tmp\durable-8945eeb6(JENKINS-48300: if on a laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=300) {noformat}The failing line of my Jenkinsfile is here: [https://github.com/keybase/client/blob/aa1fc347042cafba8cf8f48a40bed59e8bce60dd/Jenkinsfile#L309]I believe this has something to do with the fix to the infinite log problem in JENKINS-37575. In the meantime, I've reverted to 1.22, and it's working again.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-44836) Docker inspect failing on FROM statements with ARG
Title: Message Title Jeff Kwan commented on JENKINS-44836 Re: Docker inspect failing on FROM statements with ARG Similar issue: If the first line ends with a line continuation character instead of the image tag, it blows up too: FROM \ mycentos:mytag You get: java.io.IOException: Cannot retrieve .Id from 'docker inspect \' Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52924) Durable Task 1.23 broke bash scripting on Windows agents via Cygwin
Title: Message Title John Zila created an issue Jenkins / JENKINS-52924 Durable Task 1.23 broke bash scripting on Windows agents via Cygwin Issue Type: Bug Assignee: Unassigned Components: durable-task-plugin Created: 2018-08-07 20:11 Priority: Major Reporter: John Zila To connect my Windows agent machines, I essentially followed this guide (modified to handle auto-scaling spot fleets via the ec2-fleet-plugin): https://support.cloudbees.com/hc/en-us/articles/222978868-How-to-Connect-to-Remote-SSH-Slaves- Until 1.22, this worked great. Since 1.23, I now get this: [client\go] Running shell script ps: unknown option -- o Try `ps --help' for more information. + go list ./... + grep -v github.com/keybase/client/go/bind + xargs go vet wrapper script does not seem to be touching the log file in c:\Jenkins\workspace/client/master/6615\go/src/github.com/keybase/client\go@tmp\durable-8945eeb6 (JENKINS-48300: if on a laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=300) The failing line of my Jenkinsfile is here: https://github.com/keybase/client/blob/aa1fc347042cafba8cf8f48a40bed59e8bce60dd/Jenkinsfile#L309 I believe this has something to do with the fix to the infinite log problem in JENKINS-37575.
[JIRA] (JENKINS-52847) durable-task plugin v1.23 misbehaves on BusyBox agents
Title: Message Title Devin Nusbaum updated JENKINS-52847 This should be fixed in durable-task 1.24. Jenkins / JENKINS-52847 durable-task plugin v1.23 misbehaves on BusyBox agents Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: durable-task 1.24 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-33232) Not working in internal network.
Title: Message Title John Wu commented on JENKINS-33232 Re: Not working in internal network. Has anyone found a solution / workaround for this problem? Please share it out. Thanks. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52636) Gerrit triggered jobs getting delayed
Title: Message Title Hugo Ares updated an issue Jenkins / JENKINS-52636 Gerrit triggered jobs getting delayed Change By: Hugo Ares Component/s: pipeline Component/s: script-security-plugin Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52636) Gerrit triggered jobs getting delayed
Title: Message Title Hugo Ares commented on JENKINS-52636 Re: Gerrit triggered jobs getting delayed Scott Hebert Any chance you have time to fix this Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52906) jira-plugin: FAILED TO EXPORT hudson.plugins.jira.JiraProjectProperty
Title: Message Title Nicolas De Loof commented on JENKINS-52906 Re: jira-plugin: FAILED TO EXPORT hudson.plugins.jira.JiraProjectProperty Incompatibility comes from conflicting accessors : public void setSites(JiraSite site) vs public JiraSite[] getSites() The later return an array, while the former takes a single argument (and actually don't set value, but add to internal list. CasC can't introspect the data type and fail to read current value. one could imagine to introduce DescriptorImpl#setSites(Sites[]), but doing so CasC won't be able to distinguish the two set methods :'( Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49076) Cannot set custom PATH inside docker container
Title: Message Title Rong Shen commented on JENKINS-49076 Re: Cannot set custom PATH inside docker container Thank you Paul Theunissen! Let me have a try Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-37099) Null value passed through ParametersAction causes all jobs to throw StackTrace
Title: Message Title Mitch McLaughlin updated JENKINS-37099 Jenkins / JENKINS-37099 Null value passed through ParametersAction causes all jobs to throw StackTrace Change By: Mitch McLaughlin Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-37099) Null value passed through ParametersAction causes all jobs to throw StackTrace
Title: Message Title Mitch McLaughlin updated JENKINS-37099 Jenkins / JENKINS-37099 Null value passed through ParametersAction causes all jobs to throw StackTrace Change By: Mitch McLaughlin Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-37099) Null value passed through ParametersAction causes all jobs to throw StackTrace
Title: Message Title Mitch McLaughlin commented on JENKINS-37099 Re: Null value passed through ParametersAction causes all jobs to throw StackTrace Looks like this has been fixed already Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52923) Error Signal Description not displayed in Blue Ocean
Title: Message Title
Jakub Pawlinski updated an issue
Jenkins / JENKINS-52923
Error Signal Description not displayed in Blue Ocean
Change By:
Jakub Pawlinski
When running Declarative Pipeline in below particular case error signal does not display any descriptions. The only place to find it (and its there properly expanded) is the end of console output.{code:java}stage ('Pipeline-PR') {when {changeRequest()_expression_ { env.CHANGE_TARGET == 'master' || env.CHANGE_TARGET == 'develop' }}steps {script {def version = bat(script: "@set library.componentPipeline.version", returnStdout: true).split("=",2).last().trim()if (version != 'master') {error "Pull request targeting ${env.CHANGE_TARGET} cannot be based on ${version} branch of component pipeline, should be based on master!"}}}}{code}shows only as:!image-2018-08-07-18-17-57-087.png! !image-2018-08-07-18-19-01-833.png!
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-52923) Error Signal Description not displayed in Blue Ocean
Title: Message Title Jakub Pawlinski updated an issue Jenkins / JENKINS-52923 Error Signal Description not displayed in Blue Ocean Change By: Jakub Pawlinski Attachment: image-2018-08-07-18-19-01-833.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52923) Error Signal Description not displayed in Blue Ocean
Title: Message Title
Jakub Pawlinski updated an issue
Jenkins / JENKINS-52923
Error Signal Description not displayed in Blue Ocean
Change By:
Jakub Pawlinski
When running Declarative Pipeline in below particular case error signal does not display any descriptions. The only place to find it (and its there properly expanded) is the end of console output.{code:java}stage ('Pipeline-PR') {when {changeRequest()_expression_ { env.CHANGE_TARGET == 'master' || env.CHANGE_TARGET == 'develop' }}steps {script {def version = bat(script: "@set library.componentPipeline.version", returnStdout: true).split("=",2).last().trim()if (version != 'master') {error "Pull request targeting ${env.CHANGE_TARGET} cannot be based on ${version} branch of component pipeline, should be based on master!"}}}}{code}shows only as:!image-2018-08-07-18-17- 35 57 - 341 087 .png!
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-52923) Error Signal Description not displayed in Blue Ocean
Title: Message Title Jakub Pawlinski updated an issue Jenkins / JENKINS-52923 Error Signal Description not displayed in Blue Ocean Change By: Jakub Pawlinski Attachment: image-2018-08-07-18-17-57-087.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52923) Error Signal Description not displayed in Blue Ocean
Title: Message Title Jakub Pawlinski updated an issue Jenkins / JENKINS-52923 Error Signal Description not displayed in Blue Ocean Change By: Jakub Pawlinski Attachment: image-2018-08-07-18-17-35-341.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52923) Error Signal Description not displayed in Blue Ocean
Title: Message Title Jakub Pawlinski updated an issue Jenkins / JENKINS-52923 Error Signal Description not displayed in Blue Ocean Change By: Jakub Pawlinski Attachment: image-2018-08-07-18-17-28-500.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52923) Error Signal Description not displayed in Blue Ocean
Title: Message Title Jakub Pawlinski updated an issue Jenkins / JENKINS-52923 Error Signal Description not displayed in Blue Ocean Change By: Jakub Pawlinski Attachment: image-2018-08-07-18-17-28-500.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52923) Error Signal Description not displayed in Blue Ocean
Title: Message Title Jakub Pawlinski updated an issue Jenkins / JENKINS-52923 Error Signal Description not displayed in Blue Ocean Change By: Jakub Pawlinski Attachment: image-2018-08-07-18-17-35-341.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52923) Error Signal Description not displayed in Blue Ocean
Title: Message Title
Jakub Pawlinski updated an issue
Jenkins / JENKINS-52923
Error Signal Description not displayed in Blue Ocean
Change By:
Jakub Pawlinski
When defining a running Declarative Pipeline which declares an {{environment}} directive in below particular case error signal descriptions are does not expandible in Blue Ocean view display any descriptions . declarative-pipeline-error-signal-example-with-env-var:{code:java}pipeline {agent noneenvironment {EXAMPLE_VARIABLE = 'This is an example variable'}stages {stage The only place to find it ( 'Error Example' and its there properly expanded ) {steps {error "This is an error example using declarative pipeline"{code}Note that when looking at Blue Ocean output that the error description is not expandible:!declarative-pipeline-error-signal-example-with-env-var end of console output . png! The issue is not reproduced when using Scripted Pipeline.scripted-pipeline-with-env-var: {code:java} node {withEnv(['EXAMPLE_VARIABLE="this is an example variable"']) { stage(' Error Example Pipeline-PR ') { error "This is an example error message using scripted pipeline"}}} when { code} Error is expandible in Blue Ocean: changeRequest() !scripted-pipeline-with- _expression_ { env -var . png! Looking at the console logs in the Declarative Pipeline example.declarative-pipeline-error-signal-example-with-env-var.log:{quote}blueocean.js:18586 Browser configuration of @jenkins-cd/logging is explained at https://tfennelly.github.io/jenkins-js-logging/index.html#browser-configjenkins-js-extension.js:47602 [Violation] Added non-passive event listener to a scroll-blocking CHANGE_TARGET == ' wheel master ' event || env . Consider marking event handler as CHANGE_TARGET == ' passive develop ' to make the page more responsive. } blueocean.js:2752 Uncaught TypeError: Cannot read property 'indexOf' of undefined } at trimRestUrl (blueocean.js:2752) steps { at getPrefetchedDataFuture (blueocean.js:2762) script { at request def version = bat ( blueocean.js script : 2629) at DeDupeCallTracker "@set library . dedupe (blueocean componentPipeline . js version", returnStdout : 7920 true ) at dedupe (blueocean . js:7943) at Object.rawFetch split ( blueocean.js:2659 "=",2 ) at Object . fetch last ( blueocean.js:2737 ) at jenkins-js-extension . js:50210 at invokeFunc trim ( jenkins-js-extension.js:7887 ) at trailingEdge if ( jenkins-js-extension.js:7934 version != 'master' ) { trimRestUrl @ blueocean.js:2752getPrefetchedDataFuture @ blueocean.js:2762 error "Pull request @ blueocean targeting ${env . js:2629 CHANGE_TARGET} cannot be based on ${version} branch of component pipeline, should be based on master!" dedupe @ blueocean.js:7920 } dedupe @ blueocean.js:7943 } rawFetch @ blueocean.js:2659 } fetch @ blueocean.js:2737 }{code} (anonymous) @ jenkins-js-extension.js shows only as : 50210
[JIRA] (JENKINS-52923) Error Signal Description not displayed in Blue Ocean
Title: Message Title Jakub Pawlinski updated an issue Jenkins / JENKINS-52923 Error Signal Description not displayed in Blue Ocean Change By: Jakub Pawlinski Summary: CLONE - Error Signal Description not expandible displayed in Blue Ocean when using Declarative Pipeline and Environment Variables Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52923) Error Signal Description not displayed in Blue Ocean
Title: Message Title Jakub Pawlinski updated an issue Jenkins / JENKINS-52923 Error Signal Description not displayed in Blue Ocean Change By: Jakub Pawlinski Environment: Jenkins===Version details--- * Version: `2.60.1` * Mode:WAR * Url: http://127.0.0.1:8080 * Servlet container - Specification: 3.1 - Name: `jetty/9.2.z-SNAPSHOT` * Java - Home: `/usr/lib/jvm/java-8-oracle/jre` - Vendor: Oracle Corporation - Version: 1.8.0_131 - Maximum memory: 1.52 GB (1629487104) - Allocated memory: 797.50 MB (836239360) - Free memory: 269.19 MB (282262896) - In-use memory:528.31 MB (553976464) - GC strategy: ParallelGCRelevant plugins:blueocean:1.1.6:not-pinnedblueocean-autofavorite:1.0.0:not-pinnedblueocean-commons:1.1.6:not-pinnedblueocean-config:1.1.6:not-pinnedblueocean-dashboard:1.1.6:not-pinnedblueocean-display-url:2.0:not-pinnedblueocean-events:1.1.6:not-pinnedblueocean-git-pipeline:1.1.6:not-pinnedblueocean-github-pipeline:1.1.6:not-pinnedblueocean-i18n:1.1.6:not-pinnedblueocean-jwt:1.1.6:not-pinnedblueocean-personalization:1.1.6:not-pinnedblueocean-pipeline-api-impl:1.1.6:not-pinnedblueocean-pipeline-editor:0.2.0:not-pinnedblueocean-pipeline-scm-api:1.1.6:not-pinnedblueocean-rest:1.1.6:not-pinnedblueocean-rest-impl:1.1.6:not-pinnedblueocean-web:1.1.6:not-pinnedpipeline-build-step:2.5:not-pinnedpipeline-classpath:0.1.0:not-pinnedpipeline-github-lib:1.0:not-pinnedpipeline-graph-analysis:1.4:not-pinnedpipeline-input-step:2.8:not-pinnedpipeline-maven:2.5.0:not-pinnedpipeline-milestone-step:1.3.1:not-pinnedpipeline-model-api:1.1.6:not-pinnedpipeline-model-declarative-agent:1.1.1:not-pinnedpipeline-model-definition:1.1.6:not-pinnedpipeline-model-extensions:1.1.6:not-pinnedpipeline-rest-api:2.8:not-pinnedpipeline-stage-step:2.2:not-pinnedpipeline-stage-tags-metadata:1.1.6:not-pinnedpipeline-stage-view:2.8:not-pinnedpipeline-utility-steps:1.3.0:not-pinnedworkflow-aggregator:2.5:not-pinnedworkflow-api:2.17:not-pinnedworkflow-basic-steps:2.5:not-pinnedworkflow-cps:2.36:not-pinnedworkflow-cps-checkpoint:2.4:not-pinnedworkflow-cps-global-lib:2.8:not-pinnedworkflow-durable-task-step:2.12:not-pinnedworkflow-job:2.12.1:not-pinnedworkflow-multibranch:2.16:not-pinnedworkflow-scm-step:2.6:not-pinnedworkflow-step-api:2.11:not-pinnedworkflow-support:2.14:not-pinned Add Comment
[JIRA] (JENKINS-52923) Error Signal Description not displayed in Blue Ocean
Title: Message Title Jakub Pawlinski updated an issue Jenkins / JENKINS-52923 Error Signal Description not displayed in Blue Ocean Change By: Jakub Pawlinski Priority: Critical Major Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52923) CLONE - Error Signal Description not expandible in Blue Ocean when using Declarative Pipeline and Environment Variables
Title: Message Title Jakub Pawlinski created an issue Jenkins / JENKINS-52923 CLONE - Error Signal Description not expandible in Blue Ocean when using Declarative Pipeline and Environment Variables Issue Type: Bug Assignee: Andrew Bayer Components: blueocean-plugin Created: 2018-08-07 17:10 Environment: Jenkins === Version details --- * Version: `2.60.1` * Mode: WAR * Url: http://127.0.0.1:8080 * Servlet container - Specification: 3.1 - Name: `jetty/9.2.z-SNAPSHOT` * Java - Home: `/usr/lib/jvm/java-8-oracle/jre` - Vendor: Oracle Corporation - Version: 1.8.0_131 - Maximum memory: 1.52 GB (1629487104) - Allocated memory: 797.50 MB (836239360) - Free memory: 269.19 MB (282262896) - In-use memory: 528.31 MB (553976464) - GC strategy: ParallelGC Relevant plugins: blueocean:1.1.6:not-pinned blueocean-autofavorite:1.0.0:not-pinned blueocean-commons:1.1.6:not-pinned blueocean-config:1.1.6:not-pinned blueocean-dashboard:1.1.6:not-pinned blueocean-display-url:2.0:not-pinned blueocean-events:1.1.6:not-pinned blueocean-git-pipeline:1.1.6:not-pinned blueocean-github-pipeline:1.1.6:not-pinned blueocean-i18n:1.1.6:not-pinned blueocean-jwt:1.1.6:not-pinned blueocean-personalization:1.1.6:not-pinned blueocean-pipeline-api-impl:1.1.6:not-pinned blueocean-pipeline-editor:0.2.0:not-pinned blueocean-pipeline-scm-api:1.1.6:not-pinned blueocean-rest:1.1.6:not-pinned blueocean-rest-impl:1.1.6:not-pinned blueocean-web:1.1.6:not-pinned pipeline-build-step:2.5:not-pinned pipeline-classpath:0.1.0:not-pinned pipeline-github-lib:1.0:not-pinned pipeline-graph-analysis:1.4:not-pinned pipeline-input-step:2.8:not-pinned pipeline-maven:2.5.0:not-pinned pipeline-milestone-step:1.3.1:not-pinned pipeline-model-api:1.1.6:not-pinned pipeline-model-declarative-agent:1.1.1:not-pinned pipeline-model-definition:1.1.6:not-pinned pipeline-model-extensions:1.1.6:not-pinned pipeline-rest-api:2.8:not-pinned pipeline-stage-step:2.2:not-pinned pipeline-stage-tags-metadata:1.1.6:not-pinned pipeline-stage-view:2.8:not-pinned pipeline-utility-steps:1.3.0:not-pinned workflow-aggregator:2.5:not-pinned workflow-api:2.17:not-pinned workflow-basic-steps:2.5:not-pinned workflow-cps:2.36:not-pinned workflow-cps-checkpoint:2.4:not-pinned workflow-cps-global-lib:2.8:not-pinned workflow-durable-task-step:2.12:not-pinned workflow-job:2.12.1:not-pinned workflow-multibranch:2.16:not-pinned workflow-scm-step:2.6:not-pinned workflow-step-api:2.11:not-pinned workflow-support:2.14:not-pinned
[JIRA] (JENKINS-52623) environment variables like COMMIT_ID, GIT_BRANCH etc are not published to kuberenetes agent
Title: Message Title Carlos Sanchez updated JENKINS-52623 Jenkins / JENKINS-52623 environment variables like COMMIT_ID, GIT_BRANCH etc are not published to kuberenetes agent Change By: Carlos Sanchez Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-50892) Pipeline jobs stuck after restart
Title: Message Title
Damien Merlin commented on JENKINS-50892
Re: Pipeline jobs stuck after restart
Hi, I noticed an issue with this fix, it generates errors message on my windows nodes ( where I use cygwin ) :
[e:\jenkins\workspace\test-node-windows-ps] Running shell script ps: unknown option – o Try `ps --help' for more information.
So my troubles are with code :
cmd = String.format("pid=$$;{{
Unknown macro: { while *ps -o pid -p $pid* | grep -q $pid && [ -d '%s' -a \! -f '%s' ]; do touch '%s'; sleep 3; done }
}}& jsc=%s; %s=$jsc '%s' > '%s' 2> '%s'; echo $? > '%s.tmp'; mv '%s.tmp' '%s'; wait",
On cygwin I would expect : ps -p $pid
{{$ ps -p 12588}} PID PPID PGID WINPID TTY UID STIME COMMAND 12588 10484 12588 1836 pty1 1053975 09:58:55 /usr/bin/bash
Because following code is not working
$ ps -o pid -p 12588 ps: unknown option – o Try `ps --help' for more information.
This code seems fine for debian jessie for example :
$ ps -o pid -p 102008 {{ PID}} 102008
So that's explain my error message and so the fix is not working for cygwin configuration. Should me re-open this defect or create a new defect ?
Add Comment
[JIRA] (JENKINS-52868) Windows packaging embeds 32bit Java, and it makes process management malfunctional on 64bit systems
Title: Message Title Kohsuke Kawaguchi commented on JENKINS-52868 Re: Windows packaging embeds 32bit Java, and it makes process management malfunctional on 64bit systems Cool, you are way ahead of me! Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52868) Windows packaging embeds 32bit Java, and it makes process management malfunctional on 64bit systems
Title: Message Title Oleg Nenashev commented on JENKINS-52868 Re: Windows packaging embeds 32bit Java, and it makes process management malfunctional on 64bit systems Generally we have an ongoing discussion in https://groups.google.com/forum/#!topic/jenkins-platform-sig/K2Vrl5fHh6A Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52906) jira-plugin: FAILED TO EXPORT hudson.plugins.jira.JiraProjectProperty
Title: Message Title Nicolas De Loof updated an issue Jenkins / JENKINS-52906 jira-plugin: FAILED TO EXPORT hudson.plugins.jira.JiraProjectProperty Change By: Nicolas De Loof *please check the following issue over at [github|https://github.com/jenkinsci/configuration-as-code-plugin/issues/409]*: [https://github.com/jenkinsci/configuration-as-code-plugin/issues/409]seems like the getter/setters are taking and returning different objects. *proposal*: - "To keep binary compatibility you could introduce a new property get/setUrls()" to access sites Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52868) Windows packaging embeds 32bit Java, and it makes process management malfunctional on 64bit systems
Title: Message Title Oleg Nenashev commented on JENKINS-52868 Re: Windows packaging embeds 32bit Java, and it makes process management malfunctional on 64bit systems Kohsuke Kawaguchi Yes, it changed. 64bit is widely used now, especially on the server side. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52868) Windows packaging embeds 32bit Java, and it makes process management malfunctional on 64bit systems
Title: Message Title Kohsuke Kawaguchi commented on JENKINS-52868 Re: Windows packaging embeds 32bit Java, and it makes process management malfunctional on 64bit systems The last time I checked, which is admittedly years ago, bulk of the Windows users were still running 32bit Windows. Did that situation change? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52922) slave is getting disconnected in the middle of the job
Title: Message Title sumanthnath gangavarapu commented on JENKINS-52922 Re: slave is getting disconnected in the middle of the job Jenkins version: 2.134 Jenkins Master installed in Linux Jenkins Slave installed in Windows Below is the Jenkins slave properties window. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52922) slave is getting disconnected in the middle of the job
Title: Message Title sumanthnath gangavarapu updated an issue Jenkins / JENKINS-52922 slave is getting disconnected in the middle of the job Change By: sumanthnath gangavarapu Attachment: image-2018-08-07-21-45-04-675.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52922) slave is getting disconnected in the middle of the job
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-52922 slave is getting disconnected in the middle of the job Change By: Oleg Nenashev Component/s: remoting Component/s: slave-squatter-plugin Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52922) slave is getting disconnected in the middle of the job
Title: Message Title Oleg Nenashev assigned an issue to Jeff Thompson Jenkins / JENKINS-52922 slave is getting disconnected in the middle of the job Change By: Oleg Nenashev Assignee: Jeff Thompson Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
