[JIRA] (JENKINS-57082) Azure Deployment in Jenkins pipeline ignores Git config and searches for Linux git command
Title: Message Title Matthias Lischka commented on JENKINS-57082 Re: Azure Deployment in Jenkins pipeline ignores Git config and searches for Linux git command Hi, thx for the quick reply. "https://jenkins/computer/[BuildAgent]/configure". Set "(Git) Default" to "C:\Program Files\Git\bin\git.exe". Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-44869) Activity tabs Run id column should expand to fit value
Title: Message Title Reinhold Füreder updated an issue Jenkins / JENKINS-44869 Activity tabs Run id column should expand to fit value Change By: Reinhold Füreder Attachment: screenshot-now.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Oleg Nenashev commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. This is something I missed during the installer review for Java 11 GA.It somehow worked on my test machine, likely a clean environment issue Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57096 The latest debian installers 2.164+ do not work with java 11. Change By: Oleg Nenashev Labels: java11 java11-compatibility jenkins Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57083) Mouse over in diagrams only works for first diagram
Title: Message Title Christian Treczoks commented on JENKINS-57083 Re: Mouse over in diagrams only works for first diagram yes, you're right. I created a test-job where I removed all the stage-definitions and then the problem disappeared, all diagrams are working. What do you mean by "the bug has been resolved in HEAD"? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57097) [pipeline] can not update the Jenkinsfile from a gerrit commit
Title: Message Title chen hb created an issue Jenkins / JENKINS-57097 [pipeline] can not update the Jenkinsfile from a gerrit commit Issue Type: Improvement Assignee: Unassigned Components: pipeline Created: 2019-04-18 05:28 Priority: Minor Reporter: chen hb We use Gerrit to manage the Jenkinsfile, update the Jenkinsfile from the gerrit repo, unfortunately, the plugin cannot update the Jenkinsfile from a gerrit commit, so it is hard to debug the Jenkinsfile, the commit must be merged then debug the Jenkinsfile, it is not friendly. Add Comment
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Joe Mihalich created an issue Jenkins / JENKINS-57096 The latest debian installers 2.164+ do not work with java 11. Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: core, packaging Created: 2019-04-18 05:20 Environment: lilnux Labels: jenkins Priority: Major Reporter: Joe Mihalich it's hard to believe i'm the only one experiencing this. The debian package installer is completely broken for java 11 starting with the supported 2.164.x releases. When installing on Ubuntu 18.04 with (in my case) openjdk-11-jdk installed, you get the following error: Unpacking jenkins (2.164.2) ... Setting up jenkins (2.264.2) ... Job for jenkins.service failed because the control process exited with error code. See "systemctl status jenkins.service" and "journalctl -xe" for details. invoke-rc.d: initscript jenkins, action "start" failed. ● jenkins.service - LSB: Start Jenkins at boot time Loaded: loaded (/etc/init.d/jenkins; generated) Active: failed (Result: exit-code) since Thu 2019-04-18 04:47:26 UTC; 5ms ago Docs: man:systemd-sysv-generator(8) Process: 9040 ExecStart=/etc/init.d/jenkins start (code=exited, status=1/FAILURE)Apr 18 04:47:26 ip-10-0-109-178 systemd[1]: Starting LSB: Start Jenkins at boot time... Apr 18 04:47:26 ip-10-0-109-178 jenkins[9040]: Found an incorrect Java version Apr 18 04:47:26 ip-10-0-109-178 jenkins[9040]: Java version found:
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title
Joe Mihalich updated an issue
Jenkins / JENKINS-57096
The latest debian installers 2.164+ do not work with java 11.
Change By:
Joe Mihalich
it's hard to believe i'm the only one experiencing this. The debian package installer is completely broken for java 11 starting with the supported 2.164.x releases. When installing on Ubuntu 18.04 with (in my case) openjdk-11-jdk installed, you get the following error: {code:java}Unpacking jenkins (2.164.2) ...Setting up jenkins (2.264.2) ...Job for jenkins.service failed because the control process exited with error code.See "systemctl status jenkins.service" and "journalctl -xe" for details.invoke-rc.d: initscript jenkins, action "start" failed.● jenkins.service - LSB: Start Jenkins at boot time Loaded: loaded (/etc/init.d/jenkins; generated) Active: failed (Result: exit-code) since Thu 2019-04-18 04:47:26 UTC; 5ms ago Docs: man:systemd-sysv-generator(8) Process: 9040 ExecStart=/etc/init.d/jenkins start (code=exited, status=1/FAILURE)Apr 18 04:47:26 ip-10-0-109-178 systemd[1]: Starting LSB: Start Jenkins at boot time...Apr 18 04:47:26 ip-10-0-109-178 jenkins[9040]: Found an incorrect Java versionApr 18 04:47:26 ip-10-0-109-178 jenkins[9040]: Java version found:Apr 18 04:47:26 ip-10-0-109-178 jenkins[9040]: openjdk version "11.0.2" 2019-01-15Apr 18 04:47:26 ip-10-0-109-178 jenkins[9040]: OpenJDK Runtime Environment (build 11.0.2+9-Ubuntu-3ubuntu118.04.3)Apr 18 04:47:26 ip-10-0-109-178 jenkins[9040]: OpenJDK 64-Bit Server VM (build 11.0.2+9-Ubuntu-3ubuntu118.04.3, mixed mode, sharing)Apr 18 04:47:26 ip-10-0-109-178 jenkins[9040]: AbortingApr 18 04:47:26 ip-10-0-109-178 systemd[1]: jenkins.service: Control process exited, code=exited status=1Apr 18 04:47:26 ip-10-0-109-178 systemd[1]: jenkins.service: Failed with result 'exit-code'.Apr 18 04:47:26 ip-10-0-109-178 systemd[1]: Failed to start LSB: Start Jenkins at boot time.{code}inspection of the jenkins init script in /etc/init.d/jenkins reveals the isssue:{code:java}JAVA_ALLOWED_VERSION="18" ... # Work out the JAVA version we are working with:JAVA_VERSION=$($JAVA -version 2>&1 | sed -n ';s/.* version "\(.*\)\.\(.*\)\..*"/\1\2/p;')if [ "$JAVA_VERSION" = "$JAVA_ALLOWED_VERSION" ]; thenecho "Correct java version found" >&2elseecho "Found an incorrect Java version" >&2echo "Java version found:" >&2echo $($JAVA -version) >&2echo "Aborting" >&2exit 1fi{code}Obviously the first problem is you're only allowing version 18. The second problem is, the value of JAVA_VERSION after that command with java 11 installed is: "110 2019-01-15". So that command is completely broken for java 11.With this busted, there's no 'official' way for me to install this on Ubuntu right now.
[JIRA] (JENKINS-57095) Validate#check should be case insensitive
Title: Message Title Stuart Rowe commented on JENKINS-57095 Re: Validate#check should be case insensitive https://github.com/jenkinsci/p4-plugin/pull/96 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57095) Validate#check should be case insensitive
Title: Message Title Stuart Rowe commented on JENKINS-57095 Re: Validate#check should be case insensitive https://github.com/jenkinsci/p4-plugin/pull/96 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57095) Validate#check should be case insensitive
Title: Message Title Stuart Rowe started work on JENKINS-57095 Change By: Stuart Rowe Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57095) Validate#check should be case insensitive
Title: Message Title Stuart Rowe assigned an issue to Stuart Rowe Jenkins / JENKINS-57095 Validate#check should be case insensitive Change By: Stuart Rowe Assignee: Stuart Rowe Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57095) Validate#check should be case insensitive
Title: Message Title Stuart Rowe created an issue Jenkins / JENKINS-57095 Validate#check should be case insensitive Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2019-04-18 02:08 Environment: p4-plugin 1.9.6 Priority: Minor Reporter: Stuart Rowe Perforce is inconsistent with the casing in filespec status messages that the server returns. As an example, different teams that I work with have seen p4 merge commands return the following messages depending on the p4 server version and/or merge options provides. all revision(s) already integrated. All revision(s) already integrated. It would be simple to update the Validate#check method to lowercase both the filespec status messages and messages in the ignore list.
[JIRA] (JENKINS-57082) Azure Deployment in Jenkins pipeline ignores Git config and searches for Linux git command
Title: Message Title Jie Shen commented on JENKINS-57082 Re: Azure Deployment in Jenkins pipeline ignores Git config and searches for Linux git command How do you configure git for your agent? I am trying to reproduce your issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57082) Azure Deployment in Jenkins pipeline ignores Git config and searches for Linux git command
Title: Message Title Azure DevOps started work on JENKINS-57082 Change By: Azure DevOps Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-56788) VM without disk space aren't remove from the available pool
Title: Message Title Jie Shen resolved as Cannot Reproduce Jenkins / JENKINS-56788 VM without disk space aren't remove from the available pool Change By: Jie Shen Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57082) Azure Deployment in Jenkins pipeline ignores Git config and searches for Linux git command
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-57082 Azure Deployment in Jenkins pipeline ignores Git config and searches for Linux git command Change By: Jie Shen Assignee: Azure DevOps Jie Shen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57094) Add option to fail build if unshelve changelist does not exists
Title: Message Title Jean-Christian Imbeault created an issue Jenkins / JENKINS-57094 Add option to fail build if unshelve changelist does not exists Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2019-04-18 01:14 Environment: Jenkins ver. 2.135 p4-plugin ver. 1.9.6 Labels: plugin p4-plugin p4 Priority: Minor Reporter: Jean-Christian Imbeault I'd like to request adding an option the the Perforce: Unshelve build step to fail the build if the unshelve changelist does not exist. Perhaps a checkbox with "Fail build if unshelve changelist does not exist" Currently the console output looks like this when unshelving using a shelve list that does not exists. p4 unshelve -f -s252595 -cdefault No such file(s). For our workflow it would be an error for the build to pass if there were no shelved files.
[JIRA] (JENKINS-47881) Declarative Pipeline: add option to set environment variables based on user passed boolean parameter in the environment directive
Title: Message Title Daniel Mladek commented on JENKINS-47881 Re: Declarative Pipeline: add option to set environment variables based on user passed boolean parameter in the environment directive Any update on its status? I mean as suggested by Andrew Bayer it is working as of Jenkins v. 2.150.3, so it looks like it has been released. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57093) Declarative directive generator fails with NPE in case of Parameterized Scheduler Plugin
Title: Message Title
Sergey Zhemzhitsky updated an issue
Jenkins / JENKINS-57093
Declarative directive generator fails with NPE in case of Parameterized Scheduler Plugin
Change By:
Sergey Zhemzhitsky
Here is what happens in case of generating a snippet for Parameterized Scheduler by Declarative Directive Generator!image-2019-04-18-01-37-56-041.png|width=835,height=417!... and here is the stacktrace{code:java|title=NullPointerException at ParameterParser.java:50 |collapse=true }java.lang.NullPointerException at org.jenkinsci.plugins.parameterizedscheduler.ParameterParser.checkSanity(ParameterParser.java:50) at org.jenkinsci.plugins.parameterizedscheduler.DescriptorImpl.doCheckParameterizedSpecification(DescriptorImpl.java:64) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:537) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739)Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:789) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:282) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:458) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:282) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:282) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:282) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668) 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:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at
[JIRA] (JENKINS-57093) Declarative directive generator fails with NPE in case of Parameterized Scheduler Plugin
Title: Message Title
Sergey Zhemzhitsky updated an issue
Jenkins / JENKINS-57093
Declarative directive generator fails with NPE in case of Parameterized Scheduler Plugin
Change By:
Sergey Zhemzhitsky
Here is what happens in case of generating a snippet for Parameterized Scheduler by Declarative Directive Generator!image-2019-04-18-01-37-56-041.png |width=835,height=417 !... and here is the stacktrace{code: collapse=true java |title=NullPointerException at ParameterParser.java:50}java.lang.NullPointerException at org.jenkinsci.plugins.parameterizedscheduler.ParameterParser.checkSanity(ParameterParser.java:50) at org.jenkinsci.plugins.parameterizedscheduler.DescriptorImpl.doCheckParameterizedSpecification(DescriptorImpl.java:64) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:537) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739)Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:789) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:282) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:458) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:282) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:282) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:282) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668) 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:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at
[JIRA] (JENKINS-57093) Declarative directive generator fails with NPE in case of Parameterized Scheduler Plugin
Title: Message Title Sergey Zhemzhitsky created an issue Jenkins / JENKINS-57093 Declarative directive generator fails with NPE in case of Parameterized Scheduler Plugin Issue Type: Bug Assignee: Baptiste Mathus Attachments: image-2019-04-18-01-37-56-041.png Components: parameterized-scheduler-plugin Created: 2019-04-17 22:42 Environment: Jenkins 2.161 Parameterized Scheduler 0.6.3 Priority: Major Reporter: Sergey Zhemzhitsky Here is what happens in case of generating a snippet for Parameterized Scheduler by Declarative Directive Generator ... and here is the stacktrace NullPointerException at ParameterParser.java:50 java.lang.NullPointerException at org.jenkinsci.plugins.parameterizedscheduler.ParameterParser.checkSanity(ParameterParser.java:50) at org.jenkinsci.plugins.parameterizedscheduler.DescriptorImpl.doCheckParameterizedSpecification(DescriptorImpl.java:64) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at
[JIRA] (JENKINS-57083) Mouse over in diagrams only works for first diagram
Title: Message Title Ulli Hafner assigned an issue to Ulli Hafner Can you disable the stage view and check if the charts are working correctly? Jenkins / JENKINS-57083 Mouse over in diagrams only works for first diagram Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57083) Mouse over in diagrams only works for first diagram
Title: Message Title Ulli Hafner assigned an issue to Unassigned I think this is a bug in the stage view (from the wiki it seems that the bug has been resolved in HEAD). Jenkins / JENKINS-57083 Mouse over in diagrams only works for first diagram Change By: Ulli Hafner Component/s: pipeline-stage-view-plugin Component/s: warnings-ng-plugin Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57092) Error connecting slave using SSH Plugin
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-57092 Re: Error connecting slave using SSH Plugin Could you attach the whole Agent log (http://jenkins.example.com/computer/NODENAME/log)? Did you check the troubleshooting guide? In order to have the whole context I need the info I describe at Common info needed to troubleshooting a bug Did you check the SSHD service logs? try to increase the verbosity by setting `LogLevel VERBOSE` or `LogLevel DEBUG1` on your /etc/ssh/sshd_config file and see Logging_and_Troubleshooting Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57092) Error connecting slave using SSH Plugin
Title: Message Title Shane Kirk created an issue Jenkins / JENKINS-57092 Error connecting slave using SSH Plugin Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: ssh-slaves-plugin Created: 2019-04-17 21:30 Environment: Jenkins Version 2.150.3 SSH Slaves Plugin - 1.29.4 OpenJDK 1.8.0_171 - Master OpenJDK 1.8.0_191 - Slave Red Hat Enterprise Linux Server release 7.4 - Master Red Hat Enterprise Linux Server release 7.3 - Slave Priority: Minor Reporter: Shane Kirk Apr 17, 2019 2:16:23 PM INFO hudson.remoting.SynchronousCommandTransport$ReaderThread run When attempting to connect a slave using "Launch Agent via SSH" getting the following error. [04/17/19 16:27:27] [SSH] Checking java version of /u01/app/jenkinswork/jdk/bin/java [04/17/19 16:27:28] [SSH] /u01/app/jenkinswork/jdk/bin/java -version returned 1.8.0_191. [04/17/19 16:27:28] [SSH] Starting sftp client. [04/17/19 16:27:28] [SSH] Copying latest remoting.jar... [04/17/19 16:27:28] [SSH] Copied 776,717 bytes. Expanded the channel window size to 4MB [04/17/19 16:27:28] [SSH] Starting agent process: cd "/u01/app/jenkinswork" && /u01/app/jenkinswork/jdk/bin/java -jar remoting.jar -workDir /u01/app/jenkinswork Apr 17, 2019 4:27:28 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using /u01/app/jenkinswork/remoting as a remoting work directory Both error and output logs will be printed to /u01/app/jenkinswork/remoting <===[JENKINS REMOTING CAPACITY]===>channel started Remoting version: 3.27 This is a Unix agent Evacuated stdout Slave JVM has not reported exit code. Is it still running? [04/17/19 16:27:33] Launch failed - cleaning up connection [04/17/19 16:27:33] [SSH] Connection closed. ERROR: Connection terminated java.io.EOFException at
[JIRA] (JENKINS-55754) ERROR: Failed to upload files java.io.IOException: Expecting Ant GLOB pattern, but saw 'C:\Program Files (x86)\Jenkins\workspace\CD Gateway API\publish.zip'
Title: Message Title Shannon Kerr commented on JENKINS-55754 Re: ERROR: Failed to upload files java.io.IOException: Expecting Ant GLOB pattern, but saw 'C:\Program Files (x86)\Jenkins\workspace\CD Gateway API\publish.zip' Did you try using a relative rather than absolute path? I was getting this until I changed to a path relative to the workspace directory. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55353) Upgrade Jenkins core to 2.138.4
Title: Message Title Ivan Fernandez Calvo updated JENKINS-55353 Jenkins / JENKINS-55353 Upgrade Jenkins core to 2.138.4 Change By: Ivan Fernandez Calvo Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-53733) % Character in Password Created Error in User Creation
Title: Message Title Daniel Beck closed an issue as Duplicate Fixed as JENKINS-56856 in weeklies and proposed for LTS backporting. Jenkins / JENKINS-53733 % Character in Password Created Error in User Creation Change By: Daniel Beck Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-53733) % Character in Password Created Error in User Creation
Title: Message Title
Andrew Figueroa edited a comment on JENKINS-53733
Re: % Character in Password Created Error in User Creation
Reproduced with Jenkins 2.164.2 on Windows with the following password: g6%xTIS9N8*3 Edit: I would argue that this is a minor issue since it is easy to circumvent by using a password that does not contain a % character. Stack trace:{{java.lang.IllegalArgumentException: Not valid encoding '%xT'}} \ {{ at org.eclipse.jetty.util.UrlEncoded.decodeHexByte(UrlEncoded.java:889)}} \ {{ at org.eclipse.jetty.util.UrlEncoded.decodeUtf8To(UrlEncoded.java:522)}} \ {{ at org.eclipse.jetty.util.UrlEncoded.decodeTo(UrlEncoded.java:577)}} \ {{ at org.eclipse.jetty.server.Request.extractFormParameters(Request.java:551)}} \ {{ at org.eclipse.jetty.server.Request.extractContentParameters(Request.java:475)}} \ {{ at org.eclipse.jetty.server.Request.getParameters(Request.java:386)}}{{Caused: org.eclipse.jetty.http.BadMessageException: 400: Unable to parse form content}} \ {{ at org.eclipse.jetty.server.Request.getParameters(Request.java:390)}} \ {{ at org.eclipse.jetty.server.Request.getParameterNames(Request.java:1049)}} \ {{ at javax.servlet.ServletRequestWrapper.getParameterNames(ServletRequestWrapper.java:212)}} \ {{ at org.kohsuke.stapler.RequestImpl.getParameterNames(RequestImpl.java:190)}} \ {{ at org.kohsuke.stapler.RequestImpl.bindParameters(RequestImpl.java:387)}} \ {{ at org.kohsuke.stapler.RequestImpl.bindParameters(RequestImpl.java:383)}} \ {{ at hudson.security.HudsonPrivateSecurityRealm$SignupInfo.(HudsonPrivateSecurityRealm.java:596)}} \ {{ at hudson.security.HudsonPrivateSecurityRealm.validateAccountCreationForm(HudsonPrivateSecurityRealm.java:405)}} \ {{ at hudson.security.HudsonPrivateSecurityRealm.createAccountFromSetupWizard(HudsonPrivateSecurityRealm.java:325)}} \ {{ at jenkins.install.SetupWizard.doCreateAdminUser(SetupWizard.java:259)}} \ {{ at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source)}} \ {{ at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)}} \ {{ at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408)}} \ {{ at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77)}} \ {{ at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26)}} \ {{ at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212)}} \ {{ at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145)}} \ {{ at org.kohsuke.stapler.MetaClass data-model-type="hudson.model.Hudson" id="jenkins" class="yui-skin-sam two-column jenkins-2.164.2" data-version="2.164.2"1.doDispatch(MetaClass.java:537)}} \ {{ at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)}} \ {{ at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739)}}{{Caused: javax.servlet.ServletException}} \ {{ at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:789)}} \ {{ at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870)}} \ {{ at org.kohsuke.stapler.MetaClass>.doDispatch(MetaClass.java:221)}} \ {{ at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)}} \ {{ at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739)}} \ {{ at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870)}} \ {{ at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668)}} \ {{ 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:865)}} \ {{ at
[JIRA] (JENKINS-57091) Error cloning remote repo origin
Title: Message Title Rukmani Devi Sundarraj created an issue Jenkins / JENKINS-57091 Error cloning remote repo origin Issue Type: Task Assignee: Unassigned Components: core Created: 2019-04-17 19:27 Environment: Jenkin-2.121.1, git 3.9.1 , git-client 2.7.2, git-server 1.7 , github 1.29.2 , github-api 1.92 , windows -os Priority: Critical Reporter: Rukmani Devi Sundarraj Below is the error message thrown when building the project,can someone help me on this Wiping out workspace first.Cloning the remote Git repositoryHonoring refspec on initial cloneCloning repository > /opt/bitnami/git/bin/git init /opt/bitnami/apps/jenkins/jenkins_home/jobs/dmt-preproduction/workspace # timeout=10Fetching upstream changes from > /opt/bitnami/git/bin/git --version # timeout=10using GIT_ASKPASS to set credentials > /opt/bitnami/git/bin/git fetch --tags --progress +refs/heads/:refs/remotes/origin/ # timeout=20ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "/opt/bitnami/git/bin/git fetch --tags --progress +refs/heads/:refs/remotes/origin/" returned status code 128:stdout: stderr: remote: Counting objects: 70117, done. Receiving objects: 0% (1/70117) Receiving objects: 1% (702/70117) Receiving objects: 2% (1403/70117) Receiving objects: 3% (2104/70117) Receiving objects: 4% (2805/70117) Receiving objects: 5% (3506/70117) Receiving objects: 6% (4208/70117) Receiving objects: 7% (4909/70117) Receiving objects: 8% (5610/70117) Receiving objects: 9% (6311/70117) Receiving objects: 10% (7012/70117) Receiving objects: 11% (7713/70117) Receiving objects: 12% (8415/70117) Receiving objects: 13% (9116/70117) Receiving objects: 14% (9817/70117) Receiving objects: 15% (10518/70117)
[JIRA] (JENKINS-53733) % Character in Password Created Error in User Creation
Title: Message Title
Andrew Figueroa commented on JENKINS-53733
Re: % Character in Password Created Error in User Creation
Reproduced with Jenkins 2.164.2 on Windows with the following password: g6%xTIS9N8*3 Stack trace: java.lang.IllegalArgumentException: Not valid encoding '%xT' {{ at org.eclipse.jetty.util.UrlEncoded.decodeHexByte(UrlEncoded.java:889)}} {{ at org.eclipse.jetty.util.UrlEncoded.decodeUtf8To(UrlEncoded.java:522)}} {{ at org.eclipse.jetty.util.UrlEncoded.decodeTo(UrlEncoded.java:577)}} {{ at org.eclipse.jetty.server.Request.extractFormParameters(Request.java:551)}} {{ at org.eclipse.jetty.server.Request.extractContentParameters(Request.java:475)}} {{ at org.eclipse.jetty.server.Request.getParameters(Request.java:386)}} Caused: org.eclipse.jetty.http.BadMessageException: 400: Unable to parse form content {{ at org.eclipse.jetty.server.Request.getParameters(Request.java:390)}} {{ at org.eclipse.jetty.server.Request.getParameterNames(Request.java:1049)}} {{ at javax.servlet.ServletRequestWrapper.getParameterNames(ServletRequestWrapper.java:212)}} {{ at org.kohsuke.stapler.RequestImpl.getParameterNames(RequestImpl.java:190)}} {{ at org.kohsuke.stapler.RequestImpl.bindParameters(RequestImpl.java:387)}} {{ at org.kohsuke.stapler.RequestImpl.bindParameters(RequestImpl.java:383)}} {{ at hudson.security.HudsonPrivateSecurityRealm$SignupInfo.(HudsonPrivateSecurityRealm.java:596)}} {{ at hudson.security.HudsonPrivateSecurityRealm.validateAccountCreationForm(HudsonPrivateSecurityRealm.java:405)}} {{ at hudson.security.HudsonPrivateSecurityRealm.createAccountFromSetupWizard(HudsonPrivateSecurityRealm.java:325)}} {{ at jenkins.install.SetupWizard.doCreateAdminUser(SetupWizard.java:259)}} {{ at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source)}} {{ at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)}} {{ at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408)}} {{ at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77)}} {{ at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26)}} {{ at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212)}} {{ at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145)}} {{ at org.kohsuke.stapler.MetaClass data-model-type="hudson.model.Hudson" id="jenkins" class="yui-skin-sam two-column jenkins-2.164.2" data-version="2.164.2"1.doDispatch(MetaClass.java:537)}} {{ at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)}} {{ at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739)}} Caused: javax.servlet.ServletException {{ at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:789)}} {{ at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870)}} {{ at org.kohsuke.stapler.MetaClass>.doDispatch(MetaClass.java:221)}} {{ at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)}} {{ at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739)}} {{ at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870)}} {{ at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668)}} {{ 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:865)}} {{ at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655)}} {{ at hudson.util.PluginServletFilter data-model-type="hudson.model.Hudson" id="jenkins" class="yui-skin-sam two-column jenkins-2.164.2" data-version="2.164.2".doFilter(PluginServletFilter.java:154)}} {{ at
[JIRA] (JENKINS-49946) input step cannot access environment blocks
Title: Message Title Ben Wolin commented on JENKINS-49946 Re: input step cannot access environment blocks I have this problem also. Would really like to have a way to use the environment in inputs Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54998) Stash and archive should resolve symlinks
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-54998 Stash and archive should resolve symlinks Change By: Jesse Glick Component/s: core Component/s: workflow-basic-steps-plugin Component/s: pipeline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54998) Stash and archive should refuse symlinks
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-54998 Stash and archive should refuse symlinks Change By: Jesse Glick Summary: Stash and archive should resolve refuse symlinks Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57052) The Validate check method should be case insensitive
Title: Message Title Daniel Beck deleted an issue Jenkins / JENKINS-57052 The Validate check method should be case insensitive This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57051) The Validate check method should be case insensitive
Title: Message Title Daniel Beck deleted an issue Jenkins / JENKINS-57051 The Validate check method should be case insensitive This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57053) Validate.check should be case insensitive
Title: Message Title Daniel Beck deleted an issue Jenkins / JENKINS-57053 Validate.check should be case insensitive This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57048) Validate#check should be case insensitive
Title: Message Title Daniel Beck deleted an issue Jenkins / JENKINS-57048 Validate#check should be case insensitive This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57049) Validate.check should be case insensitive
Title: Message Title Daniel Beck deleted an issue Jenkins / JENKINS-57049 Validate.check should be case insensitive This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57050) The Validate.check method should be case insensitive
Title: Message Title Daniel Beck deleted an issue Jenkins / JENKINS-57050 The Validate.check method should be case insensitive This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54998) Stash and archive should resolve symlinks
Title: Message Title Jesse Glick reopened an issue Presence of symlinks or other special files in the input should just be treated as an error. Jenkins / JENKINS-54998 Stash and archive should resolve symlinks Change By: Jesse Glick Resolution: Duplicate Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57059) Stack Traces with complex file names cannot be deserialized by XStream
Title: Message Title Daniel Beck deleted an issue Jenkins / JENKINS-57059 Stack Traces with complex file names cannot be deserialized by XStream This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57062) Stack Traces with complex file names cannot be deserialized by XStream
Title: Message Title Daniel Beck deleted an issue Jenkins / JENKINS-57062 Stack Traces with complex file names cannot be deserialized by XStream This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57066) Stack Traces with complex file names cannot be deserialized by XStream
Title: Message Title Daniel Beck deleted an issue Jenkins / JENKINS-57066 Stack Traces with complex file names cannot be deserialized by XStream This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57063) Stack Traces with complex file names cannot be deserialized by XStream
Title: Message Title Daniel Beck deleted an issue Jenkins / JENKINS-57063 Stack Traces with complex file names cannot be deserialized by XStream This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57060) Stack Traces with complex file names cannot be deserialized by XStream
Title: Message Title Daniel Beck deleted an issue Jenkins / JENKINS-57060 Stack Traces with complex file names cannot be deserialized by XStream This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57065) Stack Traces with complex file names cannot be deserialized by XStream
Title: Message Title Daniel Beck deleted an issue Jenkins / JENKINS-57065 Stack Traces with complex file names cannot be deserialized by XStream This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57058) Stack Traces with complex file names cannot be deserialized by XStream
Title: Message Title Daniel Beck deleted an issue Jenkins / JENKINS-57058 Stack Traces with complex file names cannot be deserialized by XStream This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57064) Stack Traces with complex file names cannot be deserialized by XStream
Title: Message Title Daniel Beck deleted an issue Jenkins / JENKINS-57064 Stack Traces with complex file names cannot be deserialized by XStream This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57067) Stack Traces with complex file names cannot be deserialized by XStream
Title: Message Title Daniel Beck deleted an issue Jenkins / JENKINS-57067 Stack Traces with complex file names cannot be deserialized by XStream This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57061) Stack Traces with complex file names cannot be deserialized by XStream
Title: Message Title Daniel Beck deleted an issue Jenkins / JENKINS-57061 Stack Traces with complex file names cannot be deserialized by XStream This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57032) List of JIRA projects should expire
Title: Message Title Daniel Beck deleted an issue Jenkins / JENKINS-57032 List of JIRA projects should expire This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52781) tar function is breaking symlinks
Title: Message Title Jesse Glick reopened an issue Pierre Beitz the Shelve plugin could probably work around this issue by excluding known symlink filenames from its patternset. Jenkins / JENKINS-52781 tar function is breaking symlinks Change By: Jesse Glick Resolution: Won't Fix Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52781) tar function is breaking symlinks
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-52781 tar function is breaking symlinks Change By: Jesse Glick Component/s: shelve-project-plugin Component/s: core Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57057) List of Jira projects should be refreshed periodically
Title: Message Title Daniel Beck deleted an issue Jenkins / JENKINS-57057 List of Jira projects should be refreshed periodically This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57047) List of Jira Issues Should Expire
Title: Message Title Daniel Beck deleted an issue Jenkins / JENKINS-57047 List of Jira Issues Should Expire This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57034) List of JIRA projects should expire
Title: Message Title Daniel Beck deleted an issue Jenkins / JENKINS-57034 List of JIRA projects should expire This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57045) List of Jira Issues Should Expire
Title: Message Title Daniel Beck deleted an issue Jenkins / JENKINS-57045 List of Jira Issues Should Expire This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57055) List of Jira projects should expire periodically
Title: Message Title Daniel Beck deleted an issue Jenkins / JENKINS-57055 List of Jira projects should expire periodically This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57056) List of Jira projects should expire periodically
Title: Message Title Daniel Beck deleted an issue Jenkins / JENKINS-57056 List of Jira projects should expire periodically This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57033) List of JIRA projects should expire
Title: Message Title Daniel Beck deleted an issue Jenkins / JENKINS-57033 List of JIRA projects should expire This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57054) List of Jira projects should expire periodically
Title: Message Title Daniel Beck deleted an issue Jenkins / JENKINS-57054 List of Jira projects should expire periodically This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55560) stashing a symlink to a directory resolves the symlink instead of stashing it
Title: Message Title Jesse Glick updated JENKINS-55560 Jenkins / JENKINS-55560 stashing a symlink to a directory resolves the symlink instead of stashing it Change By: Jesse Glick Resolution: Fixed Status: Fixed but Unreleased Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55560) stashing a symlink to a directory resolves the symlink instead of stashing it
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-55560 stashing a symlink to a directory resolves the symlink instead of stashing it Change By: Jesse Glick Status: Reopened Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-44239) IIS Reverse Proxy: It appears that your reverse proxy set up is broken
Title: Message Title RENEESH KOTTAKKALATHIL commented on JENKINS-44239 Re: IIS Reverse Proxy: It appears that your reverse proxy set up is broken Terry Lacy Did you get this to fix? I'm running into the same problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49051) Add event field to BranchEventCause
Title: Message Title Liam Newman commented on JENKINS-49051 Re: Add event field to BranchEventCause Yuri Goikhman This point of this would be to reduce network bandwidth right? Network connection would still be needed for some data sooner or later. This change will require additional changes to derived classes to make it useful. You mention the bitbucket plugin. Have you considered implementing the desired changes locally there to see how they go? I understand this change would have benefits for other scm plugins, but it might be worth it to workout the kinks within the context of a single plugin before changing the upstream classes/apis. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57090) Some Java 8 artifacts return 404 on download
Title: Message Title Devin Nusbaum edited a comment on JENKINS-57090 Re: Some Java 8 artifacts return 404 on download This is probably related to Oracle changing the license for Java 8 as of the April 16, 2019 release of JDK 8u211 and JDK 8u212 (or maybe for earlier versions, but I'm not sure) . In short, using Oracle JDK 8u211 and newer for non-personal use cases is a violation of the license agreement unless you are paying Oracle for some other license , see the warning [here|https://www . oracle.com/technetwork/java/javaee/downloads/jdk8-downloads-2133151.html] for details. Using the JDK inside of Jenkins probably does not qualify as personal use according to the FAQ [here|https://www.oracle.com/technetwork/java/javase/overview/oracle-jdk-faqs.html].So, while maybe some crawler or plugin update could fix this, I don't think it would make sense to do so. You should switch to using OpenJDK builds from your OS package manager or something like https://adoptopenjdk.net/. Updating this plugin to download from AdoptOpenJDK sounds like a good RFE, but I have no plans to work on it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57090) Some Java 8 artifacts return 404 on download
Title: Message Title Devin Nusbaum assigned an issue to Unassigned Jenkins / JENKINS-57090 Some Java 8 artifacts return 404 on download Change By: Devin Nusbaum Assignee: Devin Nusbaum Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57090) Some Java 8 artifacts return 404 on download
Title: Message Title Devin Nusbaum commented on JENKINS-57090 Re: Some Java 8 artifacts return 404 on download This is probably related to Oracle changing the license for Java 8 as of the April 16, 2019 release of JDK 8u211 and JDK 8u212. In short, using Oracle JDK 8u211 and newer for non-personal use cases is a violation of the license agreement unless you are paying Oracle for some other license. Using the JDK inside of Jenkins probably does not qualify as personal use according to the FAQ here. So, while maybe some crawler or plugin update could fix this, I don't think it would make sense to do so. You should switch to using OpenJDK builds from your OS package manager or something like https://adoptopenjdk.net/. Updating this plugin to download from AdoptOpenJDK sounds like a good RFE, but I have no plans to work on it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57089) Tag fails with merge before build triggered by GitLab
Title: Message Title
Ken Overly updated an issue
Jenkins / JENKINS-57089
Tag fails with merge before build triggered by GitLab
Change By:
Ken Overly
Building a tag fails when 'merge before build' is configured. Build is triggered by a push to GitLab. The console output indicates a merge is attempted, however I believe it should be the same as when a new branch is pushed - which just checks out the revision.Here's what I see when a new branch is pushed:{noformat}[EnvInject] - Loading node environment variables.[EnvInject] - Preparing an environment for the build.[EnvInject] - Keeping Jenkins system variables.[EnvInject] - Keeping Jenkins build variables.[EnvInject] - Evaluating the Groovy script content[EnvInject] - Injecting contributions.Building on master in workspace C:\jenkins\workspace\merge_test[EnvInject] - Unset unresolved 'USERNAME' variable.[WS-CLEANUP] Deleting project workspace...[WS-CLEANUP] Deferred wipeout is used...[WS-CLEANUP] Doneusing credential f8a5a716-639d-4483-af01-f054e9ccbcc5Cloning the remote Git repositoryCloning repository g...@st-gitlab.apsautobag.com:APS/test_jenkins.git > git.exe init C:\jenkins\workspace\merge_test # timeout=10Fetching upstream changes from g...@st-gitlab.apsautobag.com:APS/test_jenkins.git > git.exe --version # timeout=10using GIT_SSH to set credentials Repository authentication for GitLab > git.exe fetch --tags --force --progress g...@st-gitlab.apsautobag.com:APS/test_jenkins.git +refs/heads/*:refs/remotes/origin/* > git.exe config remote.origin.url g...@st-gitlab.apsautobag.com:APS/test_jenkins.git # timeout=10 > git.exe config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git.exe config remote.origin.url g...@st-gitlab.apsautobag.com:APS/test_jenkins.git # timeout=10Fetching upstream changes from g...@st-gitlab.apsautobag.com:APS/test_jenkins.gitusing GIT_SSH to set credentials Repository authentication for GitLab > git.exe fetch --tags --force --progress g...@st-gitlab.apsautobag.com:APS/test_jenkins.git +refs/heads/*:refs/remotes/origin/* +refs/merge-requests/*/head:refs/remotes/origin/merge-requests/* +refs/tags/*:refs/remotes/origin/tags/* > git.exe rev-parse "remotes/origin/develop^{commit}" # timeout=10 > git.exe branch -a -v --no-abbrev --contains e41c8438b086f1aded8dc8e6f94227915fe846ed # timeout=10Checking out Revision e41c8438b086f1aded8dc8e6f94227915fe846ed (origin/develop) > git.exe config core.sparsecheckout # timeout=10 > git.exe checkout -f e41c8438b086f1aded8dc8e6f94227915fe846edCommit message: "Test change"First time build. Skipping changelog.[merge_test] $ cmd /c call C:\Windows\TEMP\jenkins8458950606275891551.bat{noformat}Here's what happens when a tag is pushed:{noformat}[EnvInject] - Loading node environment variables.[EnvInject] - Preparing an environment for the build.[EnvInject] - Keeping Jenkins system variables.[EnvInject] - Keeping Jenkins build variables.[EnvInject] - Evaluating the Groovy script content[EnvInject] - Injecting contributions.Building on master in workspace
[JIRA] (JENKINS-57090) Some Java 8 artifacts return 404 on download
Title: Message Title
Owen Wood updated an issue
Jenkins / JENKINS-57090
Some Java 8 artifacts return 404 on download
Change By:
Owen Wood
We've noted that some of the JDK 8 artifacts return 404.For example:{noformat}Installing JDK jdk-8u202-oth-JPR Downloading JDK from https://download.oracle.com/otn-pub/java/jdk/8u202-b08/1961070e4c9b4e26a04e7f5a083f551e/jdk-8u202-linux-x64.tar.gz FATAL: command execution failed java.io.IOException: Failed to request https://download.oracle.com/otn-pub/java/jdk/8u202-b08/1961070e4c9b4e26a04e7f5a083f551e/jdk-8u202-linux-x64.tar.gz?AuthParam= 1555471069_b10c8d4cbccf39e1a71d85ff3f9fc4c1 X exit code=404 at hudson.tools.JDKInstaller.locate(JDKInstaller.java:492) at hudson.tools.JDKInstaller.performInstallation(JDKInstaller.java:150) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:72) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:109) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:206) at hudson.model.JDK.forNode(JDK.java:148) at hudson.model.AbstractProject.getEnvironment(AbstractProject.java:341) at hudson.model.Run.getEnvironment(Run.java:2374) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:872) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:102) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1816) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Build step 'Execute shell' marked build as failure Finished: FAILURE{noformat}We've noticed that JDK 7 artifacts seem fine.We've noticed that some JDK 8 artifacts still work. 8u202 and 8u201 give 404. 8u192 seem to download just fine (for example).
Add Comment
[JIRA] (JENKINS-57089) Tag fails with merge before build triggered by GitLab
Title: Message Title
Ken Overly updated an issue
Jenkins / JENKINS-57089
Tag fails with merge before build triggered by GitLab
Change By:
Ken Overly
Building a tag fails when 'merge before build' is configured. Build is triggered by a push to GitLab. The console output indicates a merge is attempted, however I believe it should be the same as when a new branch is pushed - which just checks out the revision.Here's what I see when a new branch is pushed:{noformat}[EnvInject] - Loading node environment variables.[EnvInject] - Preparing an environment for the build.[EnvInject] - Keeping Jenkins system variables.[EnvInject] - Keeping Jenkins build variables.[EnvInject] - Evaluating the Groovy script content[EnvInject] - Injecting contributions.Building on master in workspace C:\jenkins\workspace\merge_test[EnvInject] - Unset unresolved 'USERNAME' variable.[WS-CLEANUP] Deleting project workspace...[WS-CLEANUP] Deferred wipeout is used...[WS-CLEANUP] Doneusing credential f8a5a716-639d-4483-af01-f054e9ccbcc5Cloning the remote Git repositoryCloning repository g...@st-gitlab.apsautobag.com:APS/test_jenkins.git > git.exe init C:\jenkins\workspace\merge_test # timeout=10Fetching upstream changes from g...@st-gitlab.apsautobag.com:APS/test_jenkins.git > git.exe --version # timeout=10using GIT_SSH to set credentials Repository authentication for GitLab > git.exe fetch --tags --force --progress g...@st-gitlab.apsautobag.com:APS/test_jenkins.git +refs/heads/*:refs/remotes/origin/* > git.exe config remote.origin.url g...@st-gitlab.apsautobag.com:APS/test_jenkins.git # timeout=10 > git.exe config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git.exe config remote.origin.url g...@st-gitlab.apsautobag.com:APS/test_jenkins.git # timeout=10Fetching upstream changes from g...@st-gitlab.apsautobag.com:APS/test_jenkins.gitusing GIT_SSH to set credentials Repository authentication for GitLab > git.exe fetch --tags --force --progress g...@st-gitlab.apsautobag.com:APS/test_jenkins.git +refs/heads/*:refs/remotes/origin/* +refs/merge-requests/*/head:refs/remotes/origin/merge-requests/* +refs/tags/*:refs/remotes/origin/tags/* > git.exe rev-parse "remotes/origin/develop^{commit}" # timeout=10 > git.exe branch -a -v --no-abbrev --contains e41c8438b086f1aded8dc8e6f94227915fe846ed # timeout=10Checking out Revision e41c8438b086f1aded8dc8e6f94227915fe846ed (origin/develop) > git.exe config core.sparsecheckout # timeout=10 > git.exe checkout -f e41c8438b086f1aded8dc8e6f94227915fe846edCommit message: "Test change"First time build. Skipping changelog.[merge_test] $ cmd /c call C:\Windows\TEMP\jenkins8458950606275891551.bat{noformat}Here's what happens when a tag is pushed:{noformat}[EnvInject] - Loading node environment variables.[EnvInject] - Preparing an environment for the build.[EnvInject] - Keeping Jenkins system variables.[EnvInject] - Keeping Jenkins build variables.[EnvInject] - Evaluating the Groovy script content[EnvInject] - Injecting contributions.Building on master in workspace
[JIRA] (JENKINS-57090) Some Java 8 artifacts return 404 on download
Title: Message Title Owen Wood created an issue Jenkins / JENKINS-57090 Some Java 8 artifacts return 404 on download Issue Type: Bug Assignee: Devin Nusbaum Components: jdk-tool-plugin Created: 2019-04-17 18:01 Priority: Minor Reporter: Owen Wood We've noted that some of the JDK 8 artifacts return 404. For example: Installing JDK jdk-8u202-oth-JPR Downloading JDK from https://download.oracle.com/otn-pub/java/jdk/8u202-b08/1961070e4c9b4e26a04e7f5a083f551e/jdk-8u202-linux-x64.tar.gz FATAL: command execution failed java.io.IOException: Failed to request https://download.oracle.com/otn-pub/java/jdk/8u202-b08/1961070e4c9b4e26a04e7f5a083f551e/jdk-8u202-linux-x64.tar.gz?AuthParam=1555471069_b10c8d4cbccf39e1a71d85ff3f9fc4c1 exit code=404 at hudson.tools.JDKInstaller.locate(JDKInstaller.java:492) at hudson.tools.JDKInstaller.performInstallation(JDKInstaller.java:150) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:72) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:109) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:206) at hudson.model.JDK.forNode(JDK.java:148) at hudson.model.AbstractProject.getEnvironment(AbstractProject.java:341) at hudson.model.Run.getEnvironment(Run.java:2374) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:872) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:102) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at
[JIRA] (JENKINS-56976) WAIT ERROR even though when JESINTERFACELEVEL is 2
Title: Message Title Alexander Shcherbakov updated an issue Jenkins / JENKINS-56976 WAIT ERROR even though when JESINTERFACELEVEL is 2 Change By: Alexander Shcherbakov Attachment: zos-connector-2.2.1-JESINTERFACELEVEL1-SNAPSHOT.hpi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-56976) WAIT ERROR even though when JESINTERFACELEVEL is 2
Title: Message Title Alexander Shcherbakov commented on JENKINS-56976 Re: WAIT ERROR even though when JESINTERFACELEVEL is 2 I've uploaded new version with some hacks for JESINTERFACELEVEL=1. For your setup kindly try this one (don't forget to check the box with JESINTERFACELEVEL=1). Post the logs here, please. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-56976) WAIT ERROR even though when JESINTERFACELEVEL is 2
Title: Message Title Alexander Shcherbakov updated an issue Jenkins / JENKINS-56976 WAIT ERROR even though when JESINTERFACELEVEL is 2 Change By: Alexander Shcherbakov Attachment: zos-connector-2.2.1-JESINTERFACELEVEL1-SNAPSHOT.hpi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-56976) WAIT ERROR even though when JESINTERFACELEVEL is 2
Title: Message Title Alexander Shcherbakov updated an issue Jenkins / JENKINS-56976 WAIT ERROR even though when JESINTERFACELEVEL is 2 Change By: Alexander Shcherbakov Attachment: zos-connector-2.2.1-JESINTERFACELEVEL1-SNAPSHOT.hpi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54522) Host JDK Tool Plugin download failing
Title: Message Title
Owen Wood updated an issue
Jenkins / JENKINS-54522
Host JDK Tool Plugin download failing
Change By:
Owen Wood
I'm on jdk-tool:1.1 and Jenkins 2.138.2. I've configured JDK10 in Global Tools per the attached screenshot. When running a job that uses it, I get:{noformat}Installing JDK jdk-10.0.2-oth-JPRDownloading JDK from http://download.oracle.com/otn-pub/java/jdk/10.0.2+13/19aef61b38124481863b1413dce1855f/jdk-10.0.2_linux-x64_bin.tar.gz[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinejava.io.IOException: Failed to request https://download.oracle.com/otn-pub/java/jdk/10.0.2+13/19aef61b38124481863b1413dce1855f/jdk-10.0.2_linux-x64_bin.tar.gz?AuthParam=1541612216_106847a9a60b4e512bb6e81d31a78d22 exit code=404{noformat}I believe these URLs should be:[http://download.oracle.com/otn|http://download.oracle.com/otn-pub/java/jdk/10.0.2+13/19aef61b38124481863b1413dce1855f/jdk-10.0.2_linux-x64_bin.tar.gz]instead of:[http://download.oracle.com/otn-pub|http://download.oracle.com/otn-pub/java/jdk/10.0.2+13/19aef61b38124481863b1413dce1855f/jdk-10.0.2_linux-x64_bin.tar.gz]I've tried using other installer methods such as Extract *.zip/ \ *.tar.gz and also the Custom Tool plugin instead, but these lack the authentication-handling needed to download JDK from Oracle.If the "Install from java.sun.com" method is currently broken, how are people using the official JDK with Jenkins? Doesn't seem to be a public docker image for it. Is everyone using openjdk instead? Or maintaining their own jdk docker images?
Add Comment
[JIRA] (JENKINS-57089) Tag fails with merge before build triggered by GitLab
Title: Message Title
Ken Overly updated an issue
Jenkins / JENKINS-57089
Tag fails with merge before build triggered by GitLab
Change By:
Ken Overly
Building a tag fails when 'merge before build' is configured. Build is triggered by a push to GitLab. The console output indicates a merge is attempted, however I believe it should be the same as when a new branch is pushed - which just checks out the revision.Here's what I see when a new branch is pushed:{noformat}[EnvInject] - Loading node environment variables.[EnvInject] - Preparing an environment for the build.[EnvInject] - Keeping Jenkins system variables.[EnvInject] - Keeping Jenkins build variables.[EnvInject] - Evaluating the Groovy script content[EnvInject] - Injecting contributions.Building on master in workspace C:\jenkins\workspace\merge_test[EnvInject] - Unset unresolved 'USERNAME' variable.[WS-CLEANUP] Deleting project workspace...[WS-CLEANUP] Deferred wipeout is used...[WS-CLEANUP] Doneusing credential f8a5a716-639d-4483-af01-f054e9ccbcc5Cloning the remote Git repositoryCloning repository g...@st-gitlab.apsautobag.com:APS/test_jenkins.git > git.exe init C:\jenkins\workspace\merge_test # timeout=10Fetching upstream changes from g...@st-gitlab.apsautobag.com:APS/test_jenkins.git > git.exe --version # timeout=10using GIT_SSH to set credentials Repository authentication for GitLab > git.exe fetch --tags --force --progress g...@st-gitlab.apsautobag.com:APS/test_jenkins.git +refs/heads/*:refs/remotes/origin/* > git.exe config remote.origin.url g...@st-gitlab.apsautobag.com:APS/test_jenkins.git # timeout=10 > git.exe config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git.exe config remote.origin.url g...@st-gitlab.apsautobag.com:APS/test_jenkins.git # timeout=10Fetching upstream changes from g...@st-gitlab.apsautobag.com:APS/test_jenkins.gitusing GIT_SSH to set credentials Repository authentication for GitLab > git.exe fetch --tags --force --progress g...@st-gitlab.apsautobag.com:APS/test_jenkins.git +refs/heads/*:refs/remotes/origin/* +refs/merge-requests/*/head:refs/remotes/origin/merge-requests/* +refs/tags/*:refs/remotes/origin/tags/* > git.exe rev-parse "remotes/origin/develop^{commit}" # timeout=10 > git.exe branch -a -v --no-abbrev --contains e41c8438b086f1aded8dc8e6f94227915fe846ed # timeout=10Checking out Revision e41c8438b086f1aded8dc8e6f94227915fe846ed (origin/develop) > git.exe config core.sparsecheckout # timeout=10 > git.exe checkout -f e41c8438b086f1aded8dc8e6f94227915fe846edCommit message: "Test change"First time build. Skipping changelog.[merge_test] $ cmd /c call C:\Windows\TEMP\jenkins8458950606275891551.bat{noformat}Here's what happens when a tag is pushed:{noformat}[EnvInject] - Loading node environment variables.[EnvInject] - Preparing an environment for the build.[EnvInject] - Keeping Jenkins system variables.[EnvInject] - Keeping Jenkins build variables.[EnvInject] - Evaluating the Groovy script content[EnvInject] - Injecting contributions.Building on master in workspace
[JIRA] (JENKINS-57089) Tag fails with merge before build triggered by GitLab
Title: Message Title
Ken Overly updated an issue
Jenkins / JENKINS-57089
Tag fails with merge before build triggered by GitLab
Change By:
Ken Overly
Building a tag fails when 'merge before build' is configured. Build is triggered by a push to GitLab. The console output indicates a merge is attempted, however I believe it should be the same as when a new branch is pushed which just checks out the revision.Here's what I see when a new branch is pushed:{noformat}[EnvInject] - Loading node environment variables.[EnvInject] - Preparing an environment for the build.[EnvInject] - Keeping Jenkins system variables.[EnvInject] - Keeping Jenkins build variables.[EnvInject] - Evaluating the Groovy script content[EnvInject] - Injecting contributions.Building on master in workspace C:\jenkins\workspace\merge_test[EnvInject] - Unset unresolved 'USERNAME' variable.[WS-CLEANUP] Deleting project workspace...[WS-CLEANUP] Deferred wipeout is used...[WS-CLEANUP] Doneusing credential f8a5a716-639d-4483-af01-f054e9ccbcc5Cloning the remote Git repositoryCloning repository g...@st-gitlab.apsautobag.com:APS/test_jenkins.git > git.exe init C:\jenkins\workspace\merge_test # timeout=10Fetching upstream changes from g...@st-gitlab.apsautobag.com:APS/test_jenkins.git > git.exe --version # timeout=10using GIT_SSH to set credentials Repository authentication for GitLab > git.exe fetch --tags --force --progress g...@st-gitlab.apsautobag.com:APS/test_jenkins.git +refs/heads/*:refs/remotes/origin/* > git.exe config remote.origin.url g...@st-gitlab.apsautobag.com:APS/test_jenkins.git # timeout=10 > git.exe config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git.exe config remote.origin.url g...@st-gitlab.apsautobag.com:APS/test_jenkins.git # timeout=10Fetching upstream changes from g...@st-gitlab.apsautobag.com:APS/test_jenkins.gitusing GIT_SSH to set credentials Repository authentication for GitLab > git.exe fetch --tags --force --progress g...@st-gitlab.apsautobag.com:APS/test_jenkins.git +refs/heads/*:refs/remotes/origin/* +refs/merge-requests/*/head:refs/remotes/origin/merge-requests/* +refs/tags/*:refs/remotes/origin/tags/* > git.exe rev-parse "remotes/origin/develop^{commit}" # timeout=10 > git.exe branch -a -v --no-abbrev --contains e41c8438b086f1aded8dc8e6f94227915fe846ed # timeout=10Checking out Revision e41c8438b086f1aded8dc8e6f94227915fe846ed (origin/develop) > git.exe config core.sparsecheckout # timeout=10 > git.exe checkout -f e41c8438b086f1aded8dc8e6f94227915fe846edCommit message: "Test change"First time build. Skipping changelog.[merge_test] $ cmd /c call C:\Windows\TEMP\jenkins8458950606275891551.bat{noformat}Here's what happens when a tag is pushed:{noformat}[EnvInject] - Loading node environment variables.[EnvInject] - Preparing an environment for the build.[EnvInject] - Keeping Jenkins system variables.[EnvInject] - Keeping Jenkins build variables.[EnvInject] - Evaluating the Groovy script content[EnvInject] - Injecting contributions.Building on master in workspace
[JIRA] (JENKINS-49567) Automatically support docker networks in pipelines with multiple containers
Title: Message Title
Ryan Desmond edited a comment on JENKINS-49567
Re: Automatically support docker networks in pipelines with multiple containers
This would be great, particularly with the deprecation of the {{--link}} option in docker.An alternative that would be a more purposeful with a sidecar pattern would be to have a function that surrounds any docker calls and switches each from the default network to a local one:{code:java}docker.withNetwork { docker.image('sidecar').withRun() { c-> docker.image('main').inside() { // do something with host "${c.name}" } }}{code} Currently, I have a function that works around this: {code:java}def withDockerNetwork(Closure inner) {try {networkId = UUID.randomUUID().toString()sh "docker network create ${networkId}"inner.call(networkId)} finally {sh "docker network rm ${networkId}"}}{code}{code:java}withDockerNetwork{ n -> docker.image('sidecar').withRun("--network ${n} --name sidecar") { c-> docker.image('main').inside("--network ${n}") { // do something with host "sidecar" } }} {code} (note that the names have to be globally unique, so they have to be generated)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-57012) Allow folder scope credential for Jira connection
Title: Message Title Mathieu Delrocq closed an issue as Duplicate Jenkins / JENKINS-57012 Allow folder scope credential for Jira connection Change By: Mathieu Delrocq Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57089) Tag fails with merge before build triggered by GitLab
Title: Message Title
Ken Overly updated an issue
Jenkins / JENKINS-57089
Tag fails with merge before build triggered by GitLab
Change By:
Ken Overly
Building a tag fails when 'merge before build' is configured. Build is triggered by a push to GitLab. The console output indicates merge is attempted, however I believe it should be the same as when a new branch is pushed which just checks out the revision.Here's what I see when a new branch is pushed:{noformat}[EnvInject] - Loading node environment variables.[EnvInject] - Preparing an environment for the build.[EnvInject] - Keeping Jenkins system variables.[EnvInject] - Keeping Jenkins build variables.[EnvInject] - Evaluating the Groovy script content[EnvInject] - Injecting contributions.Building on master in workspace C:\jenkins\workspace\merge_test[EnvInject] - Unset unresolved 'USERNAME' variable.[WS-CLEANUP] Deleting project workspace...[WS-CLEANUP] Deferred wipeout is used...[WS-CLEANUP] Doneusing credential f8a5a716-639d-4483-af01-f054e9ccbcc5Cloning the remote Git repositoryCloning repository g...@st-gitlab.apsautobag.com:APS/test_jenkins.git > git.exe init C:\jenkins\workspace\merge_test # timeout=10Fetching upstream changes from g...@st-gitlab.apsautobag.com:APS/test_jenkins.git > git.exe --version # timeout=10using GIT_SSH to set credentials Repository authentication for GitLab > git.exe fetch --tags --force --progress g...@st-gitlab.apsautobag.com:APS/test_jenkins.git +refs/heads/*:refs/remotes/origin/* > git.exe config remote.origin.url g...@st-gitlab.apsautobag.com:APS/test_jenkins.git # timeout=10 > git.exe config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git.exe config remote.origin.url g...@st-gitlab.apsautobag.com:APS/test_jenkins.git # timeout=10Fetching upstream changes from g...@st-gitlab.apsautobag.com:APS/test_jenkins.gitusing GIT_SSH to set credentials Repository authentication for GitLab > git.exe fetch --tags --force --progress g...@st-gitlab.apsautobag.com:APS/test_jenkins.git +refs/heads/*:refs/remotes/origin/* +refs/merge-requests/*/head:refs/remotes/origin/merge-requests/* +refs/tags/*:refs/remotes/origin/tags/* > git.exe rev-parse "remotes/origin/develop^{commit}" # timeout=10 > git.exe branch -a -v --no-abbrev --contains e41c8438b086f1aded8dc8e6f94227915fe846ed # timeout=10Checking out Revision e41c8438b086f1aded8dc8e6f94227915fe846ed (origin/develop) > git.exe config core.sparsecheckout # timeout=10 > git.exe checkout -f e41c8438b086f1aded8dc8e6f94227915fe846edCommit message: "Test change"First time build. Skipping changelog.[merge_test] $ cmd /c call C:\Windows\TEMP\jenkins8458950606275891551.bat{noformat}Here's what happens when a tag is pushed:{noformat}[EnvInject] - Loading node environment variables.[EnvInject] - Preparing an environment for the build.[EnvInject] - Keeping Jenkins system variables.[EnvInject] - Keeping Jenkins build variables.[EnvInject] - Evaluating the Groovy script content[EnvInject] - Injecting contributions.Building on master in workspace
[JIRA] (JENKINS-57089) Tag fails with merge before build triggered by GitLab
Title: Message Title
Ken Overly updated an issue
Jenkins / JENKINS-57089
Tag fails with merge before build triggered by GitLab
Change By:
Ken Overly
Building a tag fails when 'merge before build' is configured. Build is triggered by a push to GitLab. The console output indicates merge is attempted, however I believe it should be the same as when a new branch is pushed which just checks out the revision.Here's what I see when a new branch is pushed:{noformat}[EnvInject] - Loading node environment variables.[EnvInject] - Preparing an environment for the build.[EnvInject] - Keeping Jenkins system variables.[EnvInject] - Keeping Jenkins build variables.[EnvInject] - Evaluating the Groovy script content[EnvInject] - Injecting contributions.Building on master in workspace C:\jenkins\workspace\merge_test[EnvInject] - Unset unresolved 'USERNAME' variable.[WS-CLEANUP] Deleting project workspace...[WS-CLEANUP] Deferred wipeout is used...[WS-CLEANUP] Doneusing credential f8a5a716-639d-4483-af01-f054e9ccbcc5Cloning the remote Git repositoryCloning repository g...@st-gitlab.apsautobag.com:APS/test_jenkins.git > git.exe init C:\jenkins\workspace\merge_test # timeout=10Fetching upstream changes from g...@st-gitlab.apsautobag.com:APS/test_jenkins.git > git.exe --version # timeout=10using GIT_SSH to set credentials Repository authentication for GitLab > git.exe fetch --tags --force --progress g...@st-gitlab.apsautobag.com:APS/test_jenkins.git +refs/heads/*:refs/remotes/origin/* > git.exe config remote.origin.url g...@st-gitlab.apsautobag.com:APS/test_jenkins.git # timeout=10 > git.exe config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git.exe config remote.origin.url g...@st-gitlab.apsautobag.com:APS/test_jenkins.git # timeout=10Fetching upstream changes from g...@st-gitlab.apsautobag.com:APS/test_jenkins.gitusing GIT_SSH to set credentials Repository authentication for GitLab > git.exe fetch --tags --force --progress g...@st-gitlab.apsautobag.com:APS/test_jenkins.git +refs/heads/*:refs/remotes/origin/* +refs/merge-requests/*/head:refs/remotes/origin/merge-requests/* +refs/tags/*:refs/remotes/origin/tags/* > git.exe rev-parse "remotes/origin/develop^{commit}" # timeout=10 > git.exe branch -a -v --no-abbrev --contains e41c8438b086f1aded8dc8e6f94227915fe846ed # timeout=10Checking out Revision e41c8438b086f1aded8dc8e6f94227915fe846ed (origin/develop) > git.exe config core.sparsecheckout # timeout=10 > git.exe checkout -f e41c8438b086f1aded8dc8e6f94227915fe846edCommit message: "Test change"First time build. Skipping changelog.[merge_test] $ cmd /c call C:\Windows\TEMP\jenkins8458950606275891551.bat{noformat}Here's what happens when a tag is pushed:{noformat}[EnvInject] - Loading node environment variables.[EnvInject] - Preparing an environment for the build.[EnvInject] - Keeping Jenkins system variables.[EnvInject] - Keeping Jenkins build variables.[EnvInject] - Evaluating the Groovy script content[EnvInject] - Injecting contributions.Building on master in workspace
[JIRA] (JENKINS-25503) Use setsid instead of nohup
Title: Message Title Jesse Glick commented on JENKINS-25503 Re: Use setsid instead of nohup The advantages of Golang for this purpose are clear: small size; fast startup; static linking to minimize the chance of divergent runtime behaviors; access to platform-dependent system APIs like this one; and of course the availability of cross-compilation so we could have a Dockerized build process creating binaries for all supported platforms (whatever subset of go tool dist list) at once. There will however still be some exotic platforms not supported by Golang, such as z/OS, and probably some cases where sh is being used in a semi-POSIX environment like Cygwin that might choke on lower-level calls. So I think the current shell wrapper still needs to be available as a fallback (not sure how you decide when to use it) and given some smoke test coverage, though it could be stripped of all its advanced features like PID tracking. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57089) Tag fails with merge before build triggered by GitLab
Title: Message Title
Ken Overly updated an issue
Jenkins / JENKINS-57089
Tag fails with merge before build triggered by GitLab
Change By:
Ken Overly
Building a tag fails when 'merge before build' is configured. Build is triggered by a push to GitLab. The console output indicates merge is attempted, however I believe it should be the same as when a new branch is pushed which just checks out the revision.Here's what a I see when a new branch is pushed:{noformat}[EnvInject] - Loading node environment variables.[EnvInject] - Preparing an environment for the build.[EnvInject] - Keeping Jenkins system variables.[EnvInject] - Keeping Jenkins build variables.[EnvInject] - Evaluating the Groovy script content[EnvInject] - Injecting contributions.Building on master in workspace C:\jenkins\workspace\merge_test[EnvInject] - Unset unresolved 'USERNAME' variable.[WS-CLEANUP] Deleting project workspace...[WS-CLEANUP] Deferred wipeout is used...[WS-CLEANUP] Doneusing credential f8a5a716-639d-4483-af01-f054e9ccbcc5Cloning the remote Git repositoryCloning repository g...@st-gitlab.apsautobag.com:APS/test_jenkins.git > git.exe init C:\jenkins\workspace\merge_test # timeout=10Fetching upstream changes from g...@st-gitlab.apsautobag.com:APS/test_jenkins.git > git.exe --version # timeout=10using GIT_SSH to set credentials Repository authentication for GitLab > git.exe fetch --tags --force --progress g...@st-gitlab.apsautobag.com:APS/test_jenkins.git +refs/heads/*:refs/remotes/origin/* > git.exe config remote.origin.url g...@st-gitlab.apsautobag.com:APS/test_jenkins.git # timeout=10 > git.exe config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git.exe config remote.origin.url g...@st-gitlab.apsautobag.com:APS/test_jenkins.git # timeout=10Fetching upstream changes from g...@st-gitlab.apsautobag.com:APS/test_jenkins.gitusing GIT_SSH to set credentials Repository authentication for GitLab > git.exe fetch --tags --force --progress g...@st-gitlab.apsautobag.com:APS/test_jenkins.git +refs/heads/*:refs/remotes/origin/* +refs/merge-requests/*/head:refs/remotes/origin/merge-requests/* +refs/tags/*:refs/remotes/origin/tags/* > git.exe rev-parse "remotes/origin/develop^{commit}" # timeout=10 > git.exe branch -a -v --no-abbrev --contains e41c8438b086f1aded8dc8e6f94227915fe846ed # timeout=10Checking out Revision e41c8438b086f1aded8dc8e6f94227915fe846ed (origin/develop) > git.exe config core.sparsecheckout # timeout=10 > git.exe checkout -f e41c8438b086f1aded8dc8e6f94227915fe846edCommit message: "Test change"First time build. Skipping changelog.[merge_test] $ cmd /c call C:\Windows\TEMP\jenkins8458950606275891551.bat{noformat}Here's what happens when a tag is pushed:{noformat}[EnvInject] - Loading node environment variables.[EnvInject] - Preparing an environment for the build.[EnvInject] - Keeping Jenkins system variables.[EnvInject] - Keeping Jenkins build variables.[EnvInject] - Evaluating the Groovy script content[EnvInject] - Injecting contributions.Building on master in workspace
[JIRA] (JENKINS-57089) Tag fails with merge before build triggered by GitLab
Title: Message Title Ken Overly created an issue Jenkins / JENKINS-57089 Tag fails with merge before build triggered by GitLab Issue Type: Bug Assignee: Mark Waite Attachments: image-2019-04-17-11-57-04-847.png Components: git-plugin, gitlab-plugin Created: 2019-04-17 15:57 Environment: Jenkins 2.164.1 Git client 2.7.6 Git plugin 3.9.3 GitLab Plugin 1.5.11 Priority: Critical Reporter: Ken Overly Building a tag fails when 'merge before build' is configured. Build is triggered by a push to GitLab. The console output indicates merge is attempted, however I believe it should be the same as when a new branch is pushed which just checks out the revision. Here's what a see when a new branch is pushed: [EnvInject] - Loading node environment variables. [EnvInject] - Preparing an environment for the build. [EnvInject] - Keeping Jenkins system variables. [EnvInject] - Keeping Jenkins build variables. [EnvInject] - Evaluating the Groovy script content [EnvInject] - Injecting contributions. Building on master in workspace C:\jenkins\workspace\merge_test [EnvInject] - Unset unresolved 'USERNAME' variable. [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Deferred wipeout is used... [WS-CLEANUP] Done using credential f8a5a716-639d-4483-af01-f054e9ccbcc5 Cloning the remote Git repository Cloning repository g...@st-gitlab.apsautobag.com:APS/test_jenkins.git > git.exe init
[JIRA] (JENKINS-35401) Need equivalent to mvn release:prepare
Title: Message Title Steve Hill closed an issue as Won't Do Closing this as out of scope for the gradle-jpi-plugin. There are several options for replacing the maven-release-plugin to suite different needs. nebula.release is another option not already listed. Consider raising this with the Gradle team for the guide Migrating Builds From Apache Maven I don't know which is the best way to go. I'd suggest starting with a popular option and seeing if it meets your needs. One reason there are so many options is because the needs of versioning can vary quite a lot with the delivery workflow. Jenkins / JENKINS-35401 Need equivalent to mvn release:prepare Change By: Steve Hill Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) --
[JIRA] (JENKINS-57088) Optional load message content from file
Title: Message Title Vyacheslav Kryuchenko created an issue Jenkins / JENKINS-57088 Optional load message content from file Issue Type: New Feature Assignee: Anton Potsyus Components: icq-notification-plugin Created: 2019-04-17 15:46 Priority: Minor Reporter: Vyacheslav Kryuchenko I think the ability to load message content from a file would be very useful. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57025) github user incorrectly constructed, org name being assumed
Title: Message Title John Mellor commented on JENKINS-57025 Re: github user incorrectly constructed, org name being assumed It would appear that projects with a dedicated config seem to work ok. However, projects that inherit their config from the parent organization folder always get it wrong, and the hook pulls fail. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-48812) Developer guide for gradle-jpi-plugin
Title: Message Title Steve Hill started work on JENKINS-48812 Change By: Steve Hill Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-48812) Developer guide for gradle-jpi-plugin
Title: Message Title
Steve Hill commented on JENKINS-48812
Re: Developer guide for gradle-jpi-plugin
Hi Jeremy Marshall, We're using the standard maven-publish gradle plugin for this. Running the publishToMavenLocal task will publish the project locally. To consume your locally-published plugin, it'd just be a matter of adding a buildscript dependency and the mavenLocal() repository.
buildscript {
repositories { mavenLocal() }
dependencies {
classpath 'org.jenkins-ci.tools:gradle-jpi-plugin:'
}
}
Composite builds are also a great option if you're looking to iterate quickly without publishing. Does this help? I'm happy to link out to gradle's guides for development, but hesitant to introduce a full developer guide. We're trying to leverage the standard tooling as much as possible so we can rely on gradle's docs - which are much more likely to be kept up-to-date than our own. I recognize this issue was opened quite a long time ago and may no longer be relevant. I'll mark it as resolved if I don't hear back in a week or so.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-52272) Bitbucket branch source plugin doesn't update correctly the list of repositories
Title: Message Title Carroll Chiou edited a comment on JENKINS-52272 Re: Bitbucket branch source plugin doesn't update correctly the list of repositories In the Unable to reproduce bug with current behavior on Master, the master. Bitbucket cache is has been disabled , so the list of repos is updated correctly by default since 2 . 2.1. To reproduce the problem and verify the correct caching behavior, the following was done:# Enable the cache of Bitbucket endpoints in global config# Create a new multibranch project and add Bitbucket branch source # * * Confirmed the list of repos is showing correctly# Create a new Bitbucket repo# Create another multibranch project and add Bitbucket branch source # * * Confirmed that the newest Bitbucket repo was *not* show in the repo list# Disabled cache of Bitbucket endpoints# Go back to the lastest multibranch project and add Bitbucket branch source # * * Confirmed that the newest Bitbucket repo is showing and the list of repos is correct # Similar verification was also done by waiting for the Bitbucket cache period to expire and reloading the Bitbucket repositories list. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-56994) Provide User-Managed Service Identity support
Title: Message Title daniele vottero updated an issue Jenkins / JENKINS-56994 Provide User-Managed Service Identity support Change By: daniele vottero Attachment: screenshot.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-56994) Provide User-Managed Service Identity support
Title: Message Title daniele vottero updated an issue Jenkins / JENKINS-56994 Provide User-Managed Service Identity support Change By: daniele vottero Attachment: Screenshot 2019-04-17 at 16.12.40.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57085) Stack Traces with complex file names cannot be deserialized by XStream
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-57085
Stack Traces with complex file names cannot be deserialized by XStream
Change By:
Devin Nusbaum
Not sure about component, might be groovy-cps, might be upstream Groovy, might be upstream XStream, but nice to have tracking ticket here anyway. Marked as core for now assuming we'd need to backport a fix from some upstream library.*Problem:*If XStream is used to deserialize a {{StackTraceElement}} containing a complex file name, such as the following one seen in a stack trace in a Declarative Pipeline, the exception will be unable to be deserialized:{noformat}org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.delegateAndExecute(jar:file:/Users/dnusbaum/.m2/repository/org/jenkinsci/plugins/pipeline-model-definition/1.3.7/pipeline-model-definition-1.3.7.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:134){noformat}The file name for this example is:{noformat}jar:file:/Users/dnusbaum/.m2/repository/org/jenkinsci/plugins/pipeline-model-definition/1.3.7/pipeline-model-definition-1.3.7.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy{noformat}Example exception: {noformat}com.thoughtworks.xstream.converters.ConversionException: Could not parse StackTraceElement : org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.delegateAndExecute(jar:file:/Users/dnusbaum/.m2/repository/org/jenkinsci/plugins/pipeline-model-definition/1.3.7/pipeline-model-definition-1.3.7.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy:134) Debugging information class : java.lang.StackTraceElementrequired-type : java.lang.StackTraceElementconverter-type : com.thoughtworks.xstream.converters.SingleValueConverterWrapperwrapped-converter : com.thoughtworks.xstream.converters.extended.StackTraceElementConverterpath: /Tag/actions/wf.a.ErrorAction/error/stackTrace/trace[26]line number : 46class[1]: [Ljava.lang.StackTraceElement;converter-type[1] : com.thoughtworks.xstream.converters.collections.ArrayConverterclass[2]: hudson.AbortExceptionconverter-type[2] : com.thoughtworks.xstream.converters.extended.ThrowableConverterclass[3]: org.jenkinsci.plugins.workflow.actions.ErrorActionconverter-type[3] : com.thoughtworks.xstream.converters.reflection.ReflectionConverterclass[4]: [Lhudson.model.Action;class[5]: org.jenkinsci.plugins.workflow.support.storage.SimpleXStreamFlowNodeStorage$Tagversion : 1.4.7-jenkins-1--- at com.thoughtworks.xstream.converters.extended.StackTraceElementConverter.fromString(StackTraceElementConverter.java:93) at com.thoughtworks.xstream.converters.SingleValueConverterWrapper.fromString(SingleValueConverterWrapper.java:41) at com.thoughtworks.xstream.converters.SingleValueConverterWrapper.unmarshal(SingleValueConverterWrapper.java:49){noformat}The reason this happens is that
[JIRA] (JENKINS-52272) Bitbucket branch source plugin doesn't update correctly the list of repositories
Title: Message Title Carroll Chiou updated JENKINS-52272 Cache is disabled by default in 2.2.12 Jenkins / JENKINS-52272 Bitbucket branch source plugin doesn't update correctly the list of repositories Change By: Carroll Chiou Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52272) Bitbucket branch source plugin doesn't update correctly the list of repositories
Title: Message Title Carroll Chiou updated JENKINS-52272 Jenkins / JENKINS-52272 Bitbucket branch source plugin doesn't update correctly the list of repositories Change By: Carroll Chiou Resolution: Fixed Status: Resolved In Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55202) Performance Signature Plugin: JAXB API is missing with Java 11
Title: Message Title Adrien Lecharpentier commented on JENKINS-55202 Re: Performance Signature Plugin: JAXB API is missing with Java 11 Raphael Pionke I don't know what change in the classpath or how the class are loaded, but in step-by-step debug of the test you added, I'm going through methods of Retrofit lib that I didn't see in the "real case" usage. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
