[JIRA] (JENKINS-58861) Plugin believes the quota has been reached when no nodes are present.
Title: Message Title Jie Shen commented on JENKINS-58861 Re: Plugin believes the quota has been reached when no nodes are present. Could you please provide some specific error message? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201176.1565276471000.2.1565321940238%40Atlassian.JIRA.
[JIRA] (JENKINS-58861) Plugin believes the quota has been reached when no nodes are present.
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-58861 Plugin believes the quota has been reached when no nodes are present. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201176.1565276471000.0.1565321580307%40Atlassian.JIRA.
[JIRA] (JENKINS-58846) Dependency-Check Trend chart doesn't appears on DSL pipelines jobs
Title: Message Title Steve Springett closed an issue as Duplicate Jenkins / JENKINS-58846 Dependency-Check Trend chart doesn't appears on DSL pipelines jobs Change By: Steve Springett 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201161.1565179135000.11104.1565318280447%40Atlassian.JIRA.
[JIRA] (JENKINS-58846) Dependency-Check Trend chart doesn't appears on DSL pipelines jobs
Title: Message Title Steve Springett commented on JENKINS-58846 Re: Dependency-Check Trend chart doesn't appears on DSL pipelines jobs This issue has already been reported in JENKINS-58381. Pull requests are encouraged. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201161.1565179135000.11099.1565318220251%40Atlassian.JIRA.
[JIRA] (JENKINS-58862) Github Branch Source Plugin always references https://api.github.com
Title: Message Title Vivek Pandey commented on JENKINS-58862 Re: Github Branch Source Plugin always references https://api.github.com William Gillaspy Can you describe the steps to reproduce this problem? Its not clear whether you are creating Multi-branch pipeline or GitHub org folder job using GitHub site for your GitHub enterprise server or thru some other means. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201177.1565278734000.11097.1565317140215%40Atlassian.JIRA.
[JIRA] (JENKINS-58450) CHANGE_FORK doesn't point to the user/repo when the fork name differs from the upstream name
Title: Message Title Liam Newman commented on JENKINS-58450 Re: CHANGE_FORK doesn't point to the user/repo when the fork name differs from the upstream name Jesse Glick As I've noted, PR-235 is not perfect. I agree with you that the right solution in the long term is involves fixing the underlying API/data. However, in the short term I'm inclined to take PR-235 and open a new JIRA to address the API issue when time permits. I do have concerns as noted below, but I don't think they are sufficient to block us for taking PR-235. Pros Solves definite flaw in the way the plugin exposes fork information (it is not really sufficient in all reasonable cases) Use case is uncommon but not exceptional - It is uncommon for fork repos to have different names from their roots, but it is valid and not that rare. Does not break existing cases (when repo names are the same) Changes the data stored in underlying object not just the exposed CHANGE_FORK - all consumers of origin will see the same information. Change is contained to this plugin and brings the behavior into accordance with the API as described here: https://github.com/jenkinsci/scm-api-plugin/blob/5b5e58e70489167414b77fd1a7e8a92bf7b3e68e/src/main/java/jenkins/scm/api/SCMHeadOrigin.java#L129-L152 Concerns New value format changes depending on forked repo name - old format is always owner-name, new format is owner-name/forked-repo-name, but only when the the fork repo name differs from the root. Consumers of CHANGE_FORK must now check if it contains a slash to know which format to use. Changes the data stored in underlying object not just the exposed CHANGE_FORK - despite this being valid based on the API description, all consumer of origin will be effected and will need to be tested as correctly handling this change. Related notes: CHANGE_FORK is exposed here: https://github.com/jenkinsci/branch-api-plugin/blob/c4d394415cf25b6890855a08360119313f1330d2/src/main/java/jenkins/branch/BranchNameContributor.java#L72-L74 Add Comment
[JIRA] (JENKINS-58871) Publish API documentation
Title: Message Title Daniel Peacock commented on JENKINS-58871 Re: Publish API documentation Oh, I should mention I also found this: https://jenkins.io/doc/pipeline/steps/docker-workflow/ which has nice documentation for the top-level methods of the docker object, but doesn't include documentation for other objects like Image. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201190.1565308174000.11092.1565309040058%40Atlassian.JIRA.
[JIRA] (JENKINS-58871) Publish API documentation
Title: Message Title Daniel Peacock created an issue Jenkins / JENKINS-58871 Publish API documentation Issue Type: Improvement Assignee: Unassigned Components: docker-workflow-plugin Created: 2019-08-08 23:49 Labels: documentation docker plugin Priority: Minor Reporter: Daniel Peacock This plugin has a nice tutorial, but detailed API documentation would be beneficial. I found at least a start of this in github: help.jelly. That documentation was very helpful to me, explaining the differences between run, withRun, and inside clearly and succinctly. Is that jelly file, or other API documentation, been generated and posted anywhere? If so, it should be linked from some or all of these common entry pages to give it more visibility: https://plugins.jenkins.io/docker-workflow https://jenkins.io/doc/book/pipeline/docker/ https://wiki.jenkins.io/display/JENKINS/Docker+Pipeline+Plugin https://github.com/jenkinsci/docker-workflow-plugin/blob/master/README.md If not, it would be nice to get it published. In the short-term, simply linking to that jelly file from the github README would help developers not familiar with the structure of jenkins plugin code to find it more quickly.
[JIRA] (JENKINS-58853) nexusPublisher hangs when uploading multiple large files to Nexus 3
Title: Message Title Justin Young commented on JENKINS-58853 Re: nexusPublisher hangs when uploading multiple large files to Nexus 3 Hello, thanks for raising the issue. We (Sonatype) track issues via the following Jira: https://issues.sonatype.org/projects/NEXUS. Could you open this ticket there? Cheers. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201168.1565216757000.11090.1565306340186%40Atlassian.JIRA.
[JIRA] (JENKINS-53912) Unable to use SSHCheckoutTrait
Title: Message Title Liam Newman updated JENKINS-53912 Jenkins / JENKINS-53912 Unable to use SSHCheckoutTrait Change By: Liam Newman Status: In Progress 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194446.1538670788000.11086.1565305800491%40Atlassian.JIRA.
[JIRA] (JENKINS-53912) Unable to use SSHCheckoutTrait
Title: Message Title Liam Newman started work on JENKINS-53912 Change By: Liam Newman 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194446.1538670788000.11084.1565305800464%40Atlassian.JIRA.
[JIRA] (JENKINS-38126) Credentials dropdown empty on git scm
Title: Message Title René Scheibe edited a comment on JENKINS-38126 Re: Credentials dropdown empty on git scm I can reproduce this issue with Jenkins 2.176.2, git-plugin 3.11.0, authorize-project-plugin 1.3.0 , credentials-plugin 2 . 2.1. I also checked with other SCM plugins. The credentials drop-down is correctly filled for subversion-plugin 2.12.2 and mercurial-plugin 2.8. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174282.1473669042000.11056.1565302860412%40Atlassian.JIRA.
[JIRA] (JENKINS-38126) Credentials dropdown empty on git scm
Title: Message Title René Scheibe commented on JENKINS-38126 Re: Credentials dropdown empty on git scm I can reproduce this issue with Jenkins 2.176.2, git-plugin 3.11.0, authorize-project-plugin 1.3.0. I also checked with other SCM plugins. The credentials drop-down is correctly filled for subversion-plugin 2.12.2 and mercurial-plugin 2.8. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174282.1473669042000.11039.1565302800398%40Atlassian.JIRA.
[JIRA] (JENKINS-58745) P4Groovy p4.run() does not locate credentials in folder
Title: Message Title Joel Brown assigned an issue to Joel Brown Jenkins / JENKINS-58745 P4Groovy p4.run() does not locate credentials in folder Change By: Joel Brown Assignee: Joel Brown 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201048.156461302.11037.1565302560413%40Atlassian.JIRA.
[JIRA] (JENKINS-58772) Fall-back user for Active Directory plugin does not work
Title: Message Title Chris Johnson commented on JENKINS-58772 Re: Fall-back user for Active Directory plugin does not work No activity on this? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201078.1564682674000.11034.1565300820160%40Atlassian.JIRA.
[JIRA] (JENKINS-58870) Replace HttpGet with HttpHead
Title: Message Title Natasha Stopa created an issue Jenkins / JENKINS-58870 Replace HttpGet with HttpHead Issue Type: Task Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-08-08 21:40 Labels: gsoc-2019 plugin-manager Priority: Minor Reporter: Natasha Stopa Currently, the HttpGet would be downloading the whole file and then another download of the file would occur because of the copyURLToFile. Using HttpHead would only get the headers, which should tell you if the file exists at that URL and get the redirection info. Add Comment
[JIRA] (JENKINS-58869) job DSL folderLibraries error
Title: Message Title Pedro Daniel Valero Rueda created an issue Jenkins / JENKINS-58869 job DSL folderLibraries error Issue Type: Bug Assignee: Daniel Spilker Attachments: dslError.PNG, dslMain.groovy, dslSeed.groovy Components: job-dsl-plugin, workflow-cps-global-lib-plugin Created: 2019-08-08 21:33 Environment: Environment 1: - windows Server 2012 - Jenkins 2.164.3 (stand alone ) - job-dsl-plugin 1.72 - workflow-cps-global-lib-plugin 2.14 Environment 2: - docker oficial image - jenkins 2.176.2 - job-dsl-plugin 1.74 - workflow-cps-global-lib-plugin 2.15 Labels: plugin DSL shared-groovy-libraries Priority: Minor Reporter: Pedro Daniel Valero Rueda I use a dslMain.groovy to call other dsl script, when try to use a file to setup a folder scructure and set up on some of this a shared library, a error appear when try to set de library name so the value applicable. I try too whit a single config, but the result are always the same
[JIRA] (JENKINS-58868) OOM error caused by 'yet-another-build-visualizer' plugin
Title: Message Title Gustaf Lundh commented on JENKINS-58868 Re: OOM error caused by 'yet-another-build-visualizer' plugin Hi, Would love to investigate this further, but I'm not sure how the snippet proves a memory leak in YABV. Could you give me any more details? I don't recognize the output format. Is it output from -XX:ErrorFile? What does the values 352465 3 mean? Why is it listing BuildFlowAction.summary? Do you have a heap dump of the process? Or a dump from jmap -histo? Best regards Gustaf 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201185.156529371.11008.1565294820118%40Atlassian.JIRA.
[JIRA] (JENKINS-41704) Clicking On `Cppcheck Results` From A Multi-Branch Pipeline Build Results In javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException
Title: Message Title Ruth R commented on JENKINS-41704 Re: Clicking On `Cppcheck Results` From A Multi-Branch Pipeline Build Results In javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException This is a really debilitating bug for us, we cannot update the plugin because of it so are stuck on 1.21 that has various other bugs that also impact us (but can at least be coped with unlike this one). Is there going to be an update with this fix anytime soon? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178535.1486126311000.11006.1565294702883%40Atlassian.JIRA.
[JIRA] (JENKINS-58479) Failing to retrieve teams
Title: Message Title Paul Clark assigned an issue to Sam Gleske Jenkins / JENKINS-58479 Failing to retrieve teams Change By: Paul Clark Assignee: Paul Clark Sam Gleske 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200615.1562956253000.10961.1565293860378%40Atlassian.JIRA.
[JIRA] (JENKINS-58868) OOM error caused by 'yet-another-build-visualizer' plugin
Title: Message Title Trevor Hodde created an issue Jenkins / JENKINS-58868 OOM error caused by 'yet-another-build-visualizer' plugin Issue Type: Bug Assignee: Gustaf Lundh Components: yet-another-build-visualizer-plugin Created: 2019-08-08 19:48 Environment: Jenkins 2.176.1 running on Centos 7 Labels: plugin Priority: Minor Reporter: Trevor Hodde This manifested as a Jenkins crash. I had to restart the jenkins service to bring it back up. OutOfMemory and StackOverflow Exception counts: StackOverflowErrors=4 ... Event: 4031347.470 Thread 0x7fcaa4273800 352465 3 com.axis.system.jenkins.plugins.downstream.yabv.BuildFlowAction.summary:: (9 bytes)
[JIRA] (JENKINS-58867) Jenkins with proxy doesn't work
Title: Message Title Renan Lopes updated an issue Jenkins / JENKINS-58867 Jenkins with proxy doesn't work Change By: Renan Lopes Summary: Jenkins with proxy doens doesn 't work 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201184.1565291091000.10956.1565292300177%40Atlassian.JIRA.
[JIRA] (JENKINS-58867) Jenkins with proxy doens't work
Title: Message Title Renan Lopes updated an issue Jenkins / JENKINS-58867 Jenkins with proxy doens't work Change By: Renan Lopes Environment: Jenkins 2.189 using a war WAR packageLinux Ubuntu 18.04java version 1.8.0_221 - Oracle VendorFirefox 68Corporate Environment with ProxySSL Certificate added to the default Java Keystore on $JAVA_HOME/jre/lib/security/cacerts to fix "SSL Handshake Exception" 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201184.1565291091000.10955.1565291580070%40Atlassian.JIRA.
[JIRA] (JENKINS-58867) Jenkins with proxy doens't work
Title: Message Title Renan Lopes updated an issue Jenkins / JENKINS-58867 Jenkins with proxy doens't work Change By: Renan Lopes Environment: Jenkins 2.189 using a war packageLinux Ubuntu 18.04java version 1.8.0_221 - Oracle VendorFirefox 68Corporate Environment with ProxySSL certificate Certificate added to the default Java Keystore on$JAVA_HOME/jre/lib/security/cacerts to fix "SSL Handshake Exception" 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201184.1565291091000.10954.1565291460137%40Atlassian.JIRA.
[JIRA] (JENKINS-58867) Jenkins with proxy doens't work
Title: Message Title Renan Lopes updated an issue Jenkins / JENKINS-58867 Jenkins with proxy doens't work Change By: Renan Lopes Environment: Jenkins 2.189 using a war packageLinux Ubuntu 18.04java version 1.8.0_221 - Oracle VendorFirefox 68Corporate Environment with Proxy SSL certificate added to the default Java Keystore on 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201184.1565291091000.10953.1565291400062%40Atlassian.JIRA.
[JIRA] (JENKINS-58867) Jenkins with proxy doens't work
Title: Message Title
Renan Lopes updated an issue
Jenkins / JENKINS-58867
Jenkins with proxy doens't work
Change By:
Renan Lopes
Hi.I'm trying to install & configure Jenkins in my computer using the provided .war file on [http://mirrors.jenkins.io/war/latest/jenkins.war.] I'm trying to start Jenkins with the following command:java -Dhttp.auth.preference="basic" -jar jenkins.war --httpPort=8180 --httpsKeyStore=$JAVA_HOME/jre/lib/security/cacerts --httpsCertificate=~/Documents/PCAcert.crt Jenkins starts, but it doesn't download any plugin. So it suggested to configure a proxy. I did, but it is failing as the attached screenshot shows.If I try to test with a HTTP URL (no SSL) I get this exception:{code:java}java.lang.ClassCastException: java.lang.Long cannot be cast to java.lang.Integer at org.apache.commons.httpclient.HttpMethodDirector.applyConnectionParams(HttpMethodDirector.java:360) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:404) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:178) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:404) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:330) at hudson.ProxyConfiguration$DescriptorImpl.doValidateProxy(ProxyConfiguration.java:409) 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.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$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:797) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) 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 hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at jenkins.install.SetupWizard$1.doFilter(SetupWizard.java:627) at
[JIRA] (JENKINS-58308) Warn users if plugins require higher version of Jenkins
Title: Message Title Natasha Stopa started work on JENKINS-58308 Change By: Natasha Stopa 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200416.1562109025000.10951.1565291220194%40Atlassian.JIRA.
[JIRA] (JENKINS-58821) Combine yaml and txt plugin file options
Title: Message Title Natasha Stopa updated JENKINS-58821 Jenkins / JENKINS-58821 Combine yaml and txt plugin file options Change By: Natasha Stopa 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201133.1565063146000.10948.1565291100201%40Atlassian.JIRA.
[JIRA] (JENKINS-58867) Jenkins with proxy doens't work
Title: Message Title Renan Lopes created an issue Jenkins / JENKINS-58867 Jenkins with proxy doens't work Issue Type: Bug Assignee: Unassigned Attachments: http.png, https.png Components: core Created: 2019-08-08 19:04 Environment: Jenkins 2.189 using a war package Linux Ubuntu 18.04 java version 1.8.0_221 - Oracle Vendor Firefox 68 Corporate Environment with Proxy Priority: Minor Reporter: Renan Lopes Hi. I'm trying to install & configure Jenkins in my computer using the provided .war file on http://mirrors.jenkins.io/war/latest/jenkins.war. I'm trying to start Jenkins with the following command: java -Dhttp.auth.preference="basic" -jar jenkins.war --httpPort=8180 --httpsKeyStore=$JAVA_HOME/jre/lib/security/cacerts --httpsCertificate=~/Documents/PCAcert.crt Jenkins starts, but it doesn't download any plugin. So it suggested to configure a proxy. I did, but it is failing as the attached screenshot shows. If I try to test with a HTTP URL (no SSL) I get this exception: java.lang.ClassCastException: java.lang.Long cannot be cast to java.lang.Integer at org.apache.commons.httpclient.HttpMethodDirector.applyConnectionParams(HttpMethodDirector.java:360) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:404) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:178) at
[JIRA] (JENKINS-58866) Splunk plugin not sending json files
Title: Message Title
Sophie Lan updated an issue
Jenkins / JENKINS-58866
Splunk plugin not sending json files
Change By:
Sophie Lan
There is a bug where splunk-devops-plugin doesn't send json files to Splunk.In pipeline mode, I send a json file to splunk:{{step([$class: 'SplunkArtifactNotifier', excludeFiles: '', includeFiles: 'data/jkmaster_installs.json', publishFromSlave: true, sizeLimit: '100MB', skipGlobalSplunkArchive: true])}} The console output looks like this when I run the job:*11:41:35* sending files at job level, includes:data/jkmaster_installs.json excludes:*11:41:36* sent [/home/jenkins/workspace/slan/plugin-recon/data/jkmaster_installs.json] to splunk in 1 events However when I try to find my json file in Splunk it is not there.This bug is present in splunk-devops-plugin version 1.7.2 and higher. I am able to send my json file to Splunk with version 1.7.1. I believe that this commit causes the issue: [https://github.com/splunk/splunkforjenkins/commit/10227252b7bed9576995ea0df63b395060773031]. When I take out the code from just this commit sending my json file works fine.
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
[JIRA] (JENKINS-58866) Splunk plugin not sending json files
Title: Message Title Sophie Lan created an issue Jenkins / JENKINS-58866 Splunk plugin not sending json files Issue Type: Bug Assignee: Ted Components: splunk-devops-plugin Created: 2019-08-08 18:42 Environment: splunk-devops-plugin (version 1.7.4) Priority: Minor Reporter: Sophie Lan There is a bug where splunk-devops-plugin doesn't send json files to Splunk. In pipeline mode, I send a json file to splunk: step([$class: 'SplunkArtifactNotifier', excludeFiles: '', includeFiles: 'data/jkmaster_installs.json', publishFromSlave: true, sizeLimit: '100MB', skipGlobalSplunkArchive: true]) The console output looks like this when I run the job: 11:41:35 sending files at job level, includes:data/jkmaster_installs.json excludes:11:41:36 sent [/home/jenkins/workspace/slan/plugin-recon/data/jkmaster_installs.json] to splunk in 1 events However when I try to find my json file in Splunk it is not there. This bug is present in splunk-devops-plugin version 1.7.2 and higher. I am able to send my json file to Splunk with version 1.7.1. I believe that this commit causes the issue: https://github.com/splunk/splunkforjenkins/commit/10227252b7bed9576995ea0df63b395060773031. When I take out the code from just this commit sending my json file works fine.
[JIRA] (JENKINS-58820) scan Multibranch pipeline does not detect new streams when file is branch
Title: Message Title Joel Brown commented on JENKINS-58820 Re: scan Multibranch pipeline does not detect new streams when file is branch Hi Eric Daigneault - does your company have a Perforce License? If so, I'd prefer to work with you through our Salesforce on the issue. And then update this with any conclusion. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201132.1565041263000.10908.1565289720322%40Atlassian.JIRA.
[JIRA] (JENKINS-58450) CHANGE_FORK doesn't point to the user/repo when the fork name differs from the upstream name
Title: Message Title Victor Martinez commented on JENKINS-58450 Re: CHANGE_FORK doesn't point to the user/repo when the fork name differs from the upstream name I've got a bit skeptical about the backward compatibility, as the current implementations for already provides the account|org/repo format: Bitbucket (https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/34c73ea3aeff54bc037e6f6caaffe1a7c86b6c29/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketSCMSource.java#L1146) Gitlab (https://github.com/jenkinsci/gitlab-branch-source-plugin/blob/6478e861e1b257f1e64c63db18814b578eb2d0c6/src/main/java/io/jenkins/plugins/gitlabbranchsource/GitLabMergeRequestSCMCommentEvent.java#L52-L53) The proposal of creating a new env variable will provide a misleading since CHANGE_FORK and CHANGE_FORK_FULL env variables will behave differently based on the specific branch source plugin and therefore might confuse. Besides, the API is the one which specifies what it should be done, therefore the implementation should proceed with the requirement. In other words: github-branch-source will contain two env variables: CHANGE_FORK=account CHANGE_FORK_FULL=account/repo bitbucket-branch-source: CHANGE_FORK=account/repo CHANGE_FORK_FULL=account/repo gitlab-branch-source: CHANGE_FORK=account/repo CHANGE_FORK_FULL=account/repo As the implementation is not right, it means it's required to touch even in the API to solve it which it might be awkward. For sure it's a breaking change, but people should already be aware the implementation itself should be account/repo as already noticed in the docs. So they should not be surprised about it, although adding an entry in the release notes with the implication of those changes might be enough. Besides, I've got a question, the current implementation for CHANGE_FORK is invalid when the fork name differs from the upstream name, therefore how do we encourage people to avoid using it and use CHANGE_FORK_FULL? Add Comment
[JIRA] (JENKINS-58865) Electric flow plugin does not return the json details of a REST call
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-58865 Electric flow plugin does not return the json details of a REST call Issue Type: Improvement Assignee: ElectricFlow ElectricCloud Components: electricflow-plugin Created: 2019-08-08 18:25 Priority: Minor Reporter: Alex Taylor Issue: I am trying to do a REST API call to create a electricflow job execution. When I run that REST call it will respond with a json of the ID for that execution and I want to parse that ID into a groovy variable Steps to resolve: From what I am seeing the `perform` method here: https://github.com/jenkinsci/electricflow-plugin/blob/master/src/main/java/org/jenkinsci/plugins/electricflow/ElectricFlowGenericRestApi.java#L68 does not return a value into a groovy variable. In my opinion it should be like `ReturnStdOut` on a shell step inside of a pipeline rather than just printing into the logs. This would allow other REST calls to check on the status the build using the ID which is returned Add Comment
[JIRA] (JENKINS-58864) Add UI option for project url in multibranch pipeline job
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-58864 Add UI option for project url in multibranch pipeline job Issue Type: Improvement Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-08-08 17:11 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda Suggested by Liam Newman based on GitHub Branch Source Plugin release 2.5.5. See https://github.com/jenkinsci/github-branch-source-plugin/pull/236. Improves user experience by faster fetching of projects. Add Comment
[JIRA] (JENKINS-23766) For "Invoke Top-Level Maven Targets" default to --batch-mode
Title: Message Title Steven Schlansker commented on JENKINS-23766 Re: For "Invoke Top-Level Maven Targets" default to --batch-mode Doesn't seem to be resolved as of 2.176.2, unfortunately. This would be a very nice and welcome improvement. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.156153.1405114093000.10866.1565284200208%40Atlassian.JIRA.
[JIRA] (JENKINS-38126) Credentials dropdown empty on git scm
Title: Message Title René Scheibe updated an issue Jenkins / JENKINS-38126 Credentials dropdown empty on git scm Change By: René Scheibe Component/s: credentials-plugin 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174282.1473669042000.10828.1565282400706%40Atlassian.JIRA.
[JIRA] (JENKINS-58863) Builds cannot start after upgrading
Title: Message Title Steve Todorov created an issue Jenkins / JENKINS-58863 Builds cannot start after upgrading Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-08-08 16:38 Environment: Jenkins: 2.189 Kubernetes Plugin: 1.18.1 Priority: Critical Reporter: Steve Todorov After upgrading to the latest Kubernetes plugin we have started receiving this exception and no jobs can be built: sh: cd: line 1: can't cd to /home/jenkins/workspace/abcd_master: No such file or directory sh: can't create /home/jenkins/workspace/abcd_master@tmp/durable-9ae82b18/jenkins-log.txt: nonexistent directory sh: can't create /home/jenkins/workspace/abcd_master@tmp/durable-9ae82b18/jenkins-result.txt.tmp: nonexistent directory mv: cannot stat '/home/jenkins/workspace/abcd_master@tmp/durable-9ae82b18/jenkins-result.txt.tmp': No such file or directory process apparently never started in /home/jenkins/workspace/abcd_master@tmp/durable-9ae82b18 script returned exit code -2 An agent is being allocated, the job is running on it, but for some unknown reason it can't execute anything. Nothing has changed in our docker images so this is not a permission issue (and we have enough space on the nodes so it's not that as well) Downgrading back to 1.17.3 fixes the issue and everything works just fine.
[JIRA] (JENKINS-38126) Credentials dropdown empty on git scm
Title: Message Title René Scheibe commented on JENKINS-38126 Re: Credentials dropdown empty on git scm As the usage of the "Authorize Project" plugin is now recommended on the "Manage Jenkins" page, I think many more users will hit this 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174282.1473669042000.10811.1565282340631%40Atlassian.JIRA.
[JIRA] (JENKINS-55624) Authorize Projects plugin causes no git credentials to be found with 'Run as Specific User' Strategy is set
Title: Message Title René Scheibe updated an issue Jenkins / JENKINS-55624 Authorize Projects plugin causes no git credentials to be found with 'Run as Specific User' Strategy is set Change By: René Scheibe When attempting to configure source control for a freestyle job with the Build Authorization Strategy set to 'Run as Specific User', I don't see any available git credentials.I have credentials installed and they appear when I set Build Authorization Strategy to "Run as User who Triggered Build". See attached images.However, if I set the Build Authorization Strategy to "Run as User who Triggered", configure my job with the proper credentials and then switch to "Run as specific user", everything works, but when I go to configure the job the git credentials section of the config page displays the error that the currently configured credentials cannot be found. This is an ugly workaround but it does let my job run as desired.Steps to Reproduce: * Install Authorize Project * Configure Global Security > Access Control for Builds and to allow Per-project configurable build authorization with the "Run as Specific User" and "Run as User who Triggered Build" strategies. * Add another user to the local jenkins Jenkins user database. * Create a new freestyle project. * Enable git source control and add some credentials and select those. Save the project. * Enable "Configure Build Authorization" and set the strategy to "Run as Specific User". Set this to the new user you added (in my case this was not the same as my currently logged in user but testing showed that it didn't make a difference what user I entered) * Go back to the Configure page for the job. Observe that no credentials can be found according to the error on the Git SCM section of the page and no credentials appear in the drop down menu. * Switch the projects authorization strategy to "Run as user who Triggered Build" * Go back to the Configuration page for the job. Observe that the credentials appear valid and all available credentials appear. Add Comment
[JIRA] (JENKINS-55624) Authorize Projects plugin causes no git credentials to be found with 'Run as Specific User' Strategy is set
Title: Message Title René Scheibe updated an issue Jenkins / JENKINS-55624 Authorize Projects plugin causes no git credentials to be found with 'Run as Specific User' Strategy is set Change By: René Scheibe Component/s: authorize-project-plugin 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196797.1547654507000.10791.1565281920379%40Atlassian.JIRA.
[JIRA] (JENKINS-38126) Credentials dropdown empty on git scm
Title: Message Title René Scheibe updated an issue Jenkins / JENKINS-38126 Credentials dropdown empty on git scm Change By: René Scheibe Component/s: authorize-project-plugin 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174282.1473669042000.10774.1565281740630%40Atlassian.JIRA.
[JIRA] (JENKINS-58810) Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed
Title: Message Title Thierry Montalbano commented on JENKINS-58810 Re: Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed tom peck Did not fix it for me. I deleted it and re-configured it. I still see the communication error happening now and then. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201122.1565008163000.10769.1565280720167%40Atlassian.JIRA.
[JIRA] (JENKINS-50886) Declarative pipeline with pollSCM triggers 2 builds
Title: Message Title Mark Austin edited a comment on JENKINS-50886 Re: Declarative pipeline with pollSCM triggers 2 builds I'm seeing this happen with one of my teams using the multi-branch pipeline setup. Two different people are able to trigger the problem rather easily, but I can't for the life of me reproduce it, so this leads me to question if local browser configs/plugins are contributing to the problem. Now my use case is a little different since I don't even want polling, but I've noticed that PollSCM is switched on by default with any multibranch pipeline I setup. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190011.1524103101000.10762.1565280420252%40Atlassian.JIRA.
[JIRA] (JENKINS-50886) Declarative pipeline with pollSCM triggers 2 builds
Title: Message Title Mark Austin commented on JENKINS-50886 Re: Declarative pipeline with pollSCM triggers 2 builds I'm seeing this happen with one of my teams using the multi-branch pipeline setup. Two different people are able to trigger the problem rather easily, but I can't for the life of me reproduce it, so this leads me to question if local browser configs/plugins are contributing to the 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190011.1524103101000.10755.1565280360294%40Atlassian.JIRA.
[JIRA] (JENKINS-58839) NPE in GitLabMergeRequestSCMEvent and GitLabPushSCMEvent
Title: Message Title Parichay Barpanda updated JENKINS-58839 Jenkins / JENKINS-58839 NPE in GitLabMergeRequestSCMEvent and GitLabPushSCMEvent Change By: Parichay Barpanda Status: Open 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201154.1565157334000.10753.1565279520289%40Atlassian.JIRA.
[JIRA] (JENKINS-58862) Github Branch Source Plugin always references https://api.github.com
Title: Message Title William Gillaspy created an issue Jenkins / JENKINS-58862 Github Branch Source Plugin always references https://api.github.com Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2019-08-08 15:38 Environment: Jenkins ver. 2.189, Github Branch Plugin ver. 2.5.5 Priority: Major Reporter: William Gillaspy Lost ability to choose self hosted github enterprise api URL (API endpoint field) in version 2.5.5. Expect to be able to set "API endpoint" (apiURL in the config.xml) to company's git enterprise api url via the project setup. In version 2.5.5 apiURL is always set to https://api.github.com I'm able to work around this problem by cloning existing projects. However, making a new project does not allow me to choose our locally host github enterprise server (the API endpoint field is gone in 2.5.5) so the project fails on repository scan since it's pointed to https://api.github.com by default instead of [https://git.company.com/api/v3 StartedStarted[Thu Aug 08 10:52:57 EDT 2019] Starting branch indexing...ERROR: [Thu Aug 08 10:52:57 EDT 2019] Could not update folder level actions from source 27a03b35-22a6-4d0c-a9f6-bc0dceb6e97bhudson.AbortException: Invalid scan credentials BUSINESS_USER/** (BUSINESS_USER_PASS_AS_TOKEN) to connect to https://api.github.com, skipping at org.jenkinsci.plugins.github_branch_source.Connector.checkConnectionValidity(Connector.java:553) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieveActions(GitHubSCMSource.java:1874) at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:848) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:592) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at
[JIRA] (JENKINS-58861) Plugin believes the quota has been reached when no nodes are present.
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-58861 Plugin believes the quota has been reached when no nodes are present. Issue Type: Bug Assignee: Azure DevOps Components: azure-vm-agents-plugin Created: 2019-08-08 15:01 Environment: Jenkins LTS 2.176.22 Azure VM agents plugin 1.1.1 Priority: Major Reporter: R. Tyler Croy We noticed this behavior on ci.jenkins.io where a number of agents failed to provision due to timeout errors in the Azure API. The resource group was filled with VMs but there were not corresponding agents listed in Jenkins. Looking at the logs I noticed that the instance was complaining that it could not provision more machines due to the quota, despite very few agents actually being listed under /computer. After deleting the resource group in question, Jenkins started provisioning new agents while still complaining about the quota in the logs. I have no idea what happened here, but it seemed like the Azure timeout exceptions accumulated and caused some error condition with managing the quota.
[JIRA] (JENKINS-40656) Update maven-metadata.xml after upload
Title: Message Title Lars Briem commented on JENKINS-40656 Re: Update maven-metadata.xml after upload It looks like I have the same issue with version 3.17. I upload a jar to nexus. For snapshot versions, a maven-metadata.xml file is generated in the corresponding version folder, for release versions it is not. In the folder of the artifact, there is no maven-metadata.xml file generated. This might be the reason, why I am not able to resolve dynamic versions. Is there any workaround available to fix this 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177355.148248736.10744.1565276340256%40Atlassian.JIRA.
[JIRA] (JENKINS-54854) Warning when trigger spent to much time in a cron execution
Title: Message Title Oleg Nenashev updated JENKINS-54854 Jenkins / JENKINS-54854 Warning when trigger spent to much time in a cron execution Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195849.1543224007000.10740.1565275621426%40Atlassian.JIRA.
[JIRA] (JENKINS-54854) Warning when trigger spent to much time in a cron execution
Title: Message Title Oleg Nenashev updated JENKINS-54854 Jenkins / JENKINS-54854 Warning when trigger spent to much time in a cron execution Change By: Oleg Nenashev Status: Resolved Fixed but Unreleased 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195849.1543224007000.10738.1565275621399%40Atlassian.JIRA.
[JIRA] (JENKINS-29065) CLI install plugin jobs-dsl fails
Title: Message Title Oleg Nenashev updated JENKINS-29065 Jenkins / JENKINS-29065 CLI install plugin jobs-dsl fails Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.163524.1435155666000.10735.1565275621364%40Atlassian.JIRA.
[JIRA] (JENKINS-58733) Cannot delete project
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-58733 Cannot delete project Change By: Oleg Nenashev Labels: deletion lts-candidate regression windows 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201032.1564503798000.10724.1565275560616%40Atlassian.JIRA.
[JIRA] (JENKINS-54854) Warning when trigger spent to much time in a cron execution
Title: Message Title Oleg Nenashev updated JENKINS-54854 Jenkins / JENKINS-54854 Warning when trigger spent to much time in a cron execution Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.189 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195849.1543224007000.10721.1565275560571%40Atlassian.JIRA.
[JIRA] (JENKINS-58548) scriptText URL returns extra newlines
Title: Message Title Oleg Nenashev updated JENKINS-58548 Jenkins / JENKINS-58548 scriptText URL returns extra newlines Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.189 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200698.156345283.10699.1565275502197%40Atlassian.JIRA.
[JIRA] (JENKINS-29065) CLI install plugin jobs-dsl fails
Title: Message Title Oleg Nenashev reopened an issue Jenkins / JENKINS-29065 CLI install plugin jobs-dsl fails Change By: Oleg Nenashev Resolution: Cannot Reproduce 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.163524.1435155666000.10709.1565275502866%40Atlassian.JIRA.
[JIRA] (JENKINS-29065) CLI install plugin jobs-dsl fails
Title: Message Title Oleg Nenashev updated JENKINS-29065 Some follow-ups were addressed in Jenkins 2.189 Jenkins / JENKINS-29065 CLI install plugin jobs-dsl fails Change By: Oleg Nenashev Status: Reopened Fixed but Unreleased Resolution: Fixed Released As: Jenkins 2.189 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.163524.1435155666000.10711.1565275502897%40Atlassian.JIRA.
[JIRA] (JENKINS-58733) Cannot delete project
Title: Message Title Oleg Nenashev updated JENKINS-58733 Jenkins / JENKINS-58733 Cannot delete project Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved Released As: Jenkins 2.189 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201032.1564503798000.10694.1565275440490%40Atlassian.JIRA.
[JIRA] (JENKINS-58860) Skipped parameter which is defined in a job
Title: Message Title Julien Bréda commented on JENKINS-58860 Re: Skipped parameter which is defined in a job I changed priority since the logs are growing quickly 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201175.1565270296000.10688.1565272560050%40Atlassian.JIRA.
[JIRA] (JENKINS-58860) Skipped parameter which is defined in a job
Title: Message Title Julien Bréda updated an issue Jenkins / JENKINS-58860 Skipped parameter which is defined in a job Change By: Julien Bréda Priority: Minor Major 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201175.1565270296000.10687.1565272500093%40Atlassian.JIRA.
[JIRA] (JENKINS-58799) A few collection methods need to be whitelisted
Title: Message Title Devin Nusbaum updated JENKINS-58799 PR merged, but not yet released. Jenkins / JENKINS-58799 A few collection methods need to be whitelisted Change By: Devin Nusbaum Status: Open 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201109.1564913799000.10686.1565271900284%40Atlassian.JIRA.
[JIRA] (JENKINS-58860) Skipped parameter which is defined in a job
Title: Message Title
Julien Bréda updated an issue
Jenkins / JENKINS-58860
Skipped parameter which is defined in a job
Change By:
Julien Bréda
Since my update to Jenkins version 2.176.1, I get some warnings in logs about 'Skipped parameter', which relates to SECURITY-170.The log says : {code:java}"WARNING: Skipped parameter `artifactVersion` as it is undefined on `JOB-XX`. Set `-Dhudson.model.ParametersAction.keepUndefinedParameters=true` to allow undefined parameters to be injected as environment variables or `-Dhudson.model.ParametersAction.safeParameters=[comma-separated list]` to whitelist specific parameter names, even though it represents a security breach or `-Dhudson.model.ParametersAction.keepUndefinedParameters=false` to no longer show this message."but the problem is that this job is defining such parameter. (see attachment){code} I don't want to set `-Dhudson.model.ParametersAction.keepUndefinedParameters=true` only to evict some logs.I could see this issue twice : * one time with a pipeline job : this job defines the parameter and the scripted pipeline is retrieved on SCM. This pipeline uses this parameter. * another time with a freestyle job : this job also defines the parameter and the build task is nothing more than executing a shell script on a remote SSH. This script uses the parameter.In these both cases I need the parameter and, one more time, it is clearly defined. Why are my logs spammed with such lines ?The message is maybe missleading because my jobs are very simple and I can't see what's wrong.Is that because these jobs are launched from another job (which, of course, set the parameter) ?Is that because of the old builds ? I see somewhere a guy talking about old builds AND SECURITY-170.I think the log could be improved.
Add Comment
[JIRA] (JENKINS-58860) Skipped parameter which is defined in a job
Title: Message Title
Julien Bréda updated an issue
Jenkins / JENKINS-58860
Skipped parameter which is defined in a job
Change By:
Julien Bréda
Since my update to Jenkins version 2.176.1, I get some warnings in logs about 'Skipped parameter', which relates to SECURITY-170.The log says : {code:java} "WARNING: Skipped parameter `artifactVersion` as it is undefined on `JOB-XX`. Set `-Dhudson.model.ParametersAction.keepUndefinedParameters=true` to allow undefined parameters to be injected as environment variables or `-Dhudson.model.ParametersAction.safeParameters=[comma-separated list]` to whitelist specific parameter names, even though it represents a security breach or `-Dhudson.model.ParametersAction.keepUndefinedParameters=false` to no longer show this message." but the problem is that this job is defining such parameter. (see attachment) {code} I don't want to set `-Dhudson.model.ParametersAction.keepUndefinedParameters=true` only to evict some logs.I could see this issue twice : * one time with a pipeline job : this job defines the parameter and the scripted pipeline is retrieved on SCM. This pipeline uses this parameter. * another time with a freestyle job : this job also defines the parameter and the build task is nothing more than executing a shell script on a remote SSH. This script uses the parameter.In these both cases I need the parameter and, one more time, it is clearly defined. Why are my logs spammed with such lines ?The message is maybe missleading because my jobs are very simple and I can't see what's wrong.Is that because these jobs are launched from another job (which, of course, set the parameter) ?Is that because of the old builds ? I see somewhere a guy talking about old builds AND SECURITY-170.I think the log could be improved.
Add Comment
[JIRA] (JENKINS-58860) Skipped parameter which is defined in a job
Title: Message Title Julien Bréda created an issue Jenkins / JENKINS-58860 Skipped parameter which is defined in a job Issue Type: Bug Assignee: Unassigned Attachments: JobParameter.png Components: core, pipeline Created: 2019-08-08 13:18 Environment: Jenkins v2.176.1, RedHat7, Oracle Java8 Priority: Minor Reporter: Julien Bréda Since my update to Jenkins version 2.176.1, I get some warnings in logs about 'Skipped parameter', which relates to SECURITY-170. The log says : "WARNING: Skipped parameter `artifactVersion` as it is undefined on `JOB-XX`. Set `-Dhudson.model.ParametersAction.keepUndefinedParameters=true` to allow undefined parameters to be injected as environment variables or `-Dhudson.model.ParametersAction.safeParameters=[comma-separated list]` to whitelist specific parameter names, even though it represents a security breach or `-Dhudson.model.ParametersAction.keepUndefinedParameters=false` to no longer show this message." but the problem is that this job is defining such parameter. (see attachment) I don't want to set `-Dhudson.model.ParametersAction.keepUndefinedParameters=true` only to evict some logs. I could see this issue twice : one time with a pipeline job : this job defines the parameter and the scripted pipeline is retrieved on SCM. This pipeline uses this parameter. another time with a freestyle job : this job also defines the parameter and the build task is
[JIRA] (JENKINS-58758) React Plugin Develop Boilerplate
Title: Message Title Jack Shen started work on JENKINS-58758 Change By: Jack Shen 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201062.1564665164000.10681.1565269980140%40Atlassian.JIRA.
[JIRA] (JENKINS-57434) Unable to add or edit roles
Title: Message Title Nick Johns edited a comment on JENKINS-57434 Re: Unable to add or edit roles This lead me to https://issues.jenkins-ci.org/browse/JENKINS-57154 which is resolved in https://github.com/jenkinsci/github-oauth-plugin/blob/master/CHANGELOG.md#version-033-released-aug-5-2019 . Installing this new version resolved the issue for me. [~nv035674], are you using github authentication? This might work for you! 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199247.1557753306000.10675.1565269023687%40Atlassian.JIRA.
[JIRA] (JENKINS-57434) Unable to add or edit roles
Title: Message Title Nick Johns commented on JENKINS-57434 Re: Unable to add or edit roles This lead me to https://issues.jenkins-ci.org/browse/JENKINS-57154 which is resolved in https://github.com/jenkinsci/github-oauth-plugin/blob/master/CHANGELOG.md#version-033-released-aug-5-2019 Nathan Vahrenberg, are you using github authentication? This might work for you! 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199247.1557753306000.10667.1565268960493%40Atlassian.JIRA.
[JIRA] (JENKINS-57434) Unable to add or edit roles
Title: Message Title Nick Johns edited a comment on JENKINS-57434 Re: Unable to add or edit roles WOW. By iterating through the various checkName URLs, I've found a particular role name that logs me out. Not all roles do this :Dhttps://jenkins/descriptor/com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy/checkName?value=%5Bjsmith%5D(was not originally jsmith, but something similarly simple).I need to investigate why this is happening but jeeez. Continuing to investigate today, found that I can be logged out by viewing a user (that isn't me) via the UI too:https://j5s.anaplan-np.net/users/ 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199247.1557753306000.10664.1565268361490%40Atlassian.JIRA.
[JIRA] (JENKINS-48897) Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline
Title: Message Title Kalle Niemitalo commented on JENKINS-48897 Re: Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline Because Bitbucket Server does not support SSH credentials for actions such as retrieving Jenkinsfile (without cloning the whole repository) and reporting the build status. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187695.151567000.10656.1565268360821%40Atlassian.JIRA.
[JIRA] (JENKINS-48897) Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline
Title: Message Title Morten Kristiansen commented on JENKINS-48897 Re: Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline Hi, thanks for clearing this out. But that solves only parts of it doesn't it? Why are you not allowed to use SSH credentials in "Credentials" part? I am currently using the plugin (which is awsome!) and I am using the "Bitbucket Team/Project" job. And I would like to use SSH all over. Why the limitation? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187695.151567000.10629.1565268063194%40Atlassian.JIRA.
[JIRA] (JENKINS-52090) Support arm64 architecture build of docker image
Title: Message Title Alex Earl commented on JENKINS-52090 Re: Support arm64 architecture build of docker image See https://hub.docker.com/r/jenkins4eval/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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191189.1528297958000.10624.1565267820325%40Atlassian.JIRA.
[JIRA] (JENKINS-52785) Multi Architecture Docker image
Title: Message Title Alex Earl commented on JENKINS-52785 Re: Multi Architecture Docker image This is now implemented, see https://hub.docker.com/r/jenkins4eval/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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192700.1532781509000.10620.1565267760223%40Atlassian.JIRA.
[JIRA] (JENKINS-58859) Add option to install .hpi/.jpi files and resolve dependencies
Title: Message Title Alex Earl created an issue Jenkins / JENKINS-58859 Add option to install .hpi/.jpi files and resolve dependencies Issue Type: New Feature Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-08-08 12:33 Priority: Minor Reporter: Alex Earl One use case I have seen crop up in issues for docker is installing a specific hpi/jpi file and wanting to get the dependencies resolved. This can be useful for plugins for Jenkins which may be internal to a company. Maybe a new command line option --jpis or something which takes a list of jpi files and resolves their dependencies (via download). Add Comment
[JIRA] (JENKINS-58479) Failing to retrieve teams
Title: Message Title Juha Tiensyrjä commented on JENKINS-58479 Re: Failing to retrieve teams We are experiencing the same issue. Our existing configuration stopped working yesterday, probably after upgrading the GitHub Oauth plugin to 0.33. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200615.1562956253000.10610.1565265120181%40Atlassian.JIRA.
[JIRA] (JENKINS-52816) scm poll triggers even there is no change in repository(bitbucket)
Title: Message Title Gregory Danenberg commented on JENKINS-52816 Re: scm poll triggers even there is no change in repository(bitbucket) Hi We have the same problem and did not find any solution so far. We set polling in job settings while job itself is pipeline style. Shared libraries defined with polling disabled. And jobs randomly running even if there are no pushes to git. Based on your experience, did you resolve problems you had? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192737.1533040103000.10602.1565264160437%40Atlassian.JIRA.
[JIRA] (JENKINS-58858) Configuration as Code value for securityRealm reset after rebot
Title: Message Title Tim Brown closed an issue as Not A Defect Sorry after much searching it looks like we had a script in $JENKINS_HOME which was setting the securityRealm back to HudsonPrivateSecurityRealm This was derived from http://tdongsi.github.io/blog/2017/12/30/groovy-hook-script-and-jenkins-configuration-as-code/ and used to set the admin password. Deleting this file stop this behaviour, so closing the issue. Jenkins / JENKINS-58858 Configuration as Code value for securityRealm reset after rebot Change By: Tim Brown Status: Open Closed Resolution: Not A Defect 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. To view this discussion on the web visit
[JIRA] (JENKINS-54748) Memory leak in test-results-analyzer causes Jenkins to crash
Title: Message Title Danny Smit commented on JENKINS-54748 Re: Memory leak in test-results-analyzer causes Jenkins to crash We have recently installed the Test Results Analyzer and seem to have run into this issue. Especially if the 'auto refresh' is enabled, jenkins seem to crash within a day with excessive memory usage, but also excessive CPU usage. Is there any information I can provide to help track down and resolve this 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195552.1542794187000.10592.1565261760365%40Atlassian.JIRA.
[JIRA] (JENKINS-58858) Configuration as Code value for securityRealm reset after rebot
Title: Message Title
Tim Brown edited a comment on JENKINS-58858
Re: Configuration as Code value for securityRealm reset after rebot
Sorry forgot to mention. We are running jenkins inside a container and the config files are shared through a volume mounted into the container. When I say we ose credentials on restart, I mean when we stop and start the container. I just tested doing a UI restart and got this stacktrace:{noformat}java.lang.IllegalStateException: Expected 1 instance of hudson.model.User$AllUsers but got 0 at hudson.ExtensionList.lookupSingleton(ExtensionList.java:451) at hudson.model.User$AllUsers.getInstance(User.java:1080) at hudson.model.User$AllUsers.get(User.java:1098) at hudson.model.User$AllUsers.access$100(User.java:1061) at hudson.model.User.getOrCreateById(User.java:517) at hudson.model.User.getById(User.java:615) at hudson.security.HttpSessionContextIntegrationFilter2.hasInvalidSessionSeed(HttpSessionContextIntegrationFilter2.java:87) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:60) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:90) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:90) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:540) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:524) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1701) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1345) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:480) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1668) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1247) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.Server.handle(Server.java:502) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:370) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:267) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305) at
[JIRA] (JENKINS-58362) CommandLauncher2Test.requireApproval failure due to two copies of SystemCommandLanguage
Title: Message Title Oliver Gondža commented on JENKINS-58362 Re: CommandLauncher2Test.requireApproval failure due to two copies of SystemCommandLanguage Adrien Lecharpentier, 2.176.3 is already complete and is currently being tested without this fix in it. So it will have to wait for the next line. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200477.1562336462000.10585.1565259960162%40Atlassian.JIRA.
[JIRA] (JENKINS-29065) CLI install plugin jobs-dsl fails
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-29065 CLI install plugin jobs-dsl fails Change By: Daniel Beck Labels: lts-candidate 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.163524.1435155666000.10576.1565259300402%40Atlassian.JIRA.
[JIRA] (JENKINS-58858) Configuration as Code value for securityRealm reset after rebot
Title: Message Title
Tim Brown updated an issue
Jenkins / JENKINS-58858
Configuration as Code value for securityRealm reset after rebot
Change By:
Tim Brown
We are trying to use the https://wiki.jenkins.io/display/JENKINS/Reverse+Proxy+Auth+Plugin to handle our authentication. We can get the plugin configured correctly and after that export the config as code .yaml and save it on the filesystem. The problem is when we reboot jenkins it revertes to Internal Jenkins DB users, instead of using the reverse proxy.Here is the snippet of JCasC yaml we get from exporting the config from Jenkins: ``` {code:yaml} securityRealm:reverseProxy: disableLdapEmailResolver: false forwardedUser: "X-Forwarded-User" headerGroups: "X-Forwarded-Groups" headerGroupsDelimiter: "|" inhibitInferRootDN: false updateInterval: 15 userSearch: "uid={0}" ``` {code} Marking as minor as there is a workaround (reset the value after each reset), but it would be really nice not to have to work around it :).Not 100% is this is a bug with this or the reverse auth proxy, but raising here first seemed to make sense.
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
[JIRA] (JENKINS-58548) scriptText URL returns extra newlines
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-58548 scriptText URL returns extra newlines Change By: Daniel Beck Labels: lts-candidate regression 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200698.156345283.10567.1565257620668%40Atlassian.JIRA.
[JIRA] (JENKINS-58858) Configuration as Code value for securityRealm reset after rebot
Title: Message Title Tim Brown commented on JENKINS-58858 Re: Configuration as Code value for securityRealm reset after rebot Sorry forgot to mention. We are running jenkins inside a container and the config files are shared through a volume mounted into the container. When I say we ose credentials on restart, I mean when we stop and start the container. I just tested doing a UI restart and got this stacktrace: java.lang.IllegalStateException: Expected 1 instance of hudson.model.User$AllUsers but got 0 at hudson.ExtensionList.lookupSingleton(ExtensionList.java:451) at hudson.model.User$AllUsers.getInstance(User.java:1080) at hudson.model.User$AllUsers.get(User.java:1098) at hudson.model.User$AllUsers.access$100(User.java:1061) at hudson.model.User.getOrCreateById(User.java:517) at hudson.model.User.getById(User.java:615) at hudson.security.HttpSessionContextIntegrationFilter2.hasInvalidSessionSeed(HttpSessionContextIntegrationFilter2.java:87) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:60) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:90) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:90) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:540) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:524) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1701) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1345) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:480) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1668) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1247) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.Server.handle(Server.java:502) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:370) at
[JIRA] (JENKINS-58858) Configuration as Code value for securityRealm reset after rebot
Title: Message Title
Tim Brown created an issue
Jenkins / JENKINS-58858
Configuration as Code value for securityRealm reset after rebot
Issue Type:
Bug
Assignee:
Ewelina Wilkosz
Components:
configuration-as-code-plugin
Created:
2019-08-08 09:40
Environment:
Ubuntu: 18.04 Docker: 18.09.7, build 2d0083d Jenkins: 2.176.2 Config as Code Plugin: 1.27
Priority:
Minor
Reporter:
Tim Brown
We are trying to use the https://wiki.jenkins.io/display/JENKINS/Reverse+Proxy+Auth+Plugin to handle our authentication. We can get the plugin configured correctly and after that export the config as code .yaml and save it on the filesystem. The problem is when we reboot jenkins it revertes to Internal Jenkins DB users, instead of using the reverse proxy. Here is the snippet of JCasC yaml we get from exporting the config from Jenkins: ``` securityRealm: reverseProxy: disableLdapEmailResolver: false forwardedUser: "X-Forwarded-User" headerGroups: "X-Forwarded-Groups" headerGroupsDelimiter: "|" inhibitInferRootDN: false updateInterval: 15 userSearch: "uid= {0} " ``` Marking as minor as there is a workaround (reset the value after each reset), but it would be really nice not to have to work around it . Not 100% is this is a bug with this or the reverse auth proxy, but raising here first seemed to make sense.
[JIRA] (JENKINS-58857) add safer github auth trough GitHub Plugin or through Credentials
Title: Message Title Jack Newcombe commented on JENKINS-58857 Re: add safer github auth trough GitHub Plugin or through Credentials Jenkins credentials sounds like a good bet as they can be shared between plugins. I'll look into this soon. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201172.1565256011000.10558.1565256542097%40Atlassian.JIRA.
[JIRA] (JENKINS-58857) add safer github auth trough GitHub Plugin or through Credentials
Title: Message Title Robbert Korving created an issue Jenkins / JENKINS-58857 add safer github auth trough GitHub Plugin or through Credentials Issue Type: Improvement Assignee: Jack Newcombe Attachments: Selectie_081.png Components: github-coverage-reporter-plugin Created: 2019-08-08 09:20 Environment: Jenkins ver. 2.176.2 Labels: security configuration user-experience Priority: Minor Reporter: Robbert Korving Currently the github auth token has to be copy/pasted in an input field at "Manage Jenkins" -> "Configure System". Because of this an already created token can't be reused. Github doesn't show used tokens and Jenkins doesn't show its credentials content. It can also be seen as a security risk that an access token is exposed in that screen. I would be great if this plugin can use Jenkins Credentials to set the token or even use the setting from the GitHub Plugin. I imagine everybody who want to use this plugin has the GitHub Plugin already setup.
[JIRA] (JENKINS-12480) Build step that runs multiple jobs in parallel, and blocks until all are complete
Title: Message Title Anil Thatavarthi commented on JENKINS-12480 Re: Build step that runs multiple jobs in parallel, and blocks until all are complete If I have two different parameters to be passed for two different jobs, how can I achieve this? For example, I have two jobs to be triggered in parallel and both the jobs have two different parameters to be passed, I have used "Predefined parameters", but I assume how jenkins will take the parameters for the two jobs? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.142846.132708801.10554.1565255820788%40Atlassian.JIRA.
[JIRA] (JENKINS-58362) CommandLauncher2Test.requireApproval failure due to two copies of SystemCommandLanguage
Title: Message Title Adrien Lecharpentier commented on JENKINS-58362 Re: CommandLauncher2Test.requireApproval failure due to two copies of SystemCommandLanguage Oliver Gondža Do you think this could be backported to .3 of the current LTS? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200477.1562336462000.10530.1565252520159%40Atlassian.JIRA.
[JIRA] (JENKINS-58854) Cannot configure SonarQube plugin with JCasC
Title: Message Title Joseph Petersen assigned an issue to Sonar Team Jenkins / JENKINS-58854 Cannot configure SonarQube plugin with JCasC Change By: Joseph Petersen Assignee: Ewelina Wilkosz Sonar Team 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201169.1565220198000.10527.1565250840328%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Olivier Lamy commented on JENKINS-58684 Re: Linux max task resource exhaustion after excessive timer thread creation Colin Chapman thanks a lot I will read those logs maybe it can help by chance have you tried the snapshot? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200967.156416397.10514.1565250240582%40Atlassian.JIRA.
[JIRA] (JENKINS-58839) NPE in GitLabMergeRequestSCMEvent and GitLabPushSCMEvent
Title: Message Title Christian Köberl commented on JENKINS-58839 Re: NPE in GitLabMergeRequestSCMEvent and GitLabPushSCMEvent The current develop version built by me works without issues. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201154.1565157334000.10512.1565250120189%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Colin Chapman commented on JENKINS-58684 Re: Linux max task resource exhaustion after excessive timer thread creation Hello Olivier, We don't hav that much users, I'd say max 15 concurrent users, you can see below the logs during a high threads episodes, the job that you can see on the logs is scheduled to run every 5 minutes : logs-jenkins-06.08.txt 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200967.156416397.10502.1565249641155%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Colin Chapman updated an issue Jenkins / JENKINS-58684 Linux max task resource exhaustion after excessive timer thread creation Change By: Colin Chapman Attachment: logs-jenkins-06.08.txt 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200967.156416397.10491.1565249640930%40Atlassian.JIRA.
[JIRA] (JENKINS-58848) Getting Message: Exception has been thrown by the target of an invocation message while running jobs through jenkins in remote machine
Title: Message Title Daniel Gront commented on JENKINS-58848 Re: Getting Message: Exception has been thrown by the target of an invocation message while running jobs through jenkins in remote machine Hey Stalin Vanama, Please provide about what Jenkins version are you using, plugin version, and what job step is throwing an exception. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201163.1565185944000.10488.1565247780452%40Atlassian.JIRA.
[JIRA] (JENKINS-58856) No Authorization Header for WinRM connection
Title: Message Title Christoph Niehoff created an issue Jenkins / JENKINS-58856 No Authorization Header for WinRM connection Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-08-08 06:42 Priority: Minor Reporter: Christoph Niehoff I am trying to set up a Jenkins with Windows on-demand slaves. The Windows EC2-Instances are started by the plugin, but the WinRM connection cannot be established. The logs are stuck in a "Waiting for WinRM to come up"-loop. But I can create a WinRM-connection to the instances manually using a python library. When I compare both (the connection attempt by the EC2-Plugin and the connection by the lython tool) I observe the following: the POST-request to /wsman is answered with a 401 by the Windows instance this seems to be the case because the Authorization header is completely missing in the request Is this a bug in the plugin or am I doing something wrong? Add Comment
[JIRA] (JENKINS-37862) Extract build symlink handling to a plugin
Title: Message Title Merten Schumann commented on JENKINS-37862 Re: Extract build symlink handling to a plugin good ... Thanx alot for your feedback, Jesse Glick. Merten 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174000.1472663694000.10479.1565246460304%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Olivier Lamy edited a comment on JENKINS-58684 Re: Linux max task resource exhaustion after excessive timer thread creation I wonder how many users do you have using BlueOcean UI guys when the problem happen? Anyone could use finest logging for logger : org.jenkinsci.plugins.ssegateway.sse.EventDispatcher and post the log file here?This would definitely help. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200967.156416397.10468.1565244720315%40Atlassian.JIRA.
