[JIRA] (JENKINS-57946) No notification when Jenkins fails to check out a pipeline script
Title: Message Title TOURLONNIAS Laureny commented on JENKINS-57946 Re: No notification when Jenkins fails to check out a pipeline script I actually find it very unfortunate that an error in the job falling due to GIT is not manageable. It seems very surprising that this is not planned. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.199922.1560206168000.9600.1576570980183%40Atlassian.JIRA.
[JIRA] (JENKINS-47301) JClouds aws-ec2 always tries to use default subnet
Title: Message Title Fritz Elfert updated JENKINS-47301 Released in 2.16 Jenkins / JENKINS-47301 JClouds aws-ec2 always tries to use default subnet Change By: Fritz Elfert Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.185723.1507231416000.9603.1576571160596%40Atlassian.JIRA.
[JIRA] (JENKINS-44601) Provide an option to create preemptible GCloud VM instances
Title: Message Title Fritz Elfert updated JENKINS-44601 Released in 2.16 Jenkins / JENKINS-44601 Provide an option to create preemptible GCloud VM instances Change By: Fritz Elfert Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.182456.1496305444000.9611.1576571281002%40Atlassian.JIRA.
[JIRA] (JENKINS-60499) Plugin of JCloud won't work anymore because of GCP zone changes
Title: Message Title Fritz Elfert updated JENKINS-60499 Released in 2.16 Jenkins / JENKINS-60499 Plugin of JCloud won't work anymore because of GCP zone changes Change By: Fritz Elfert Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203590.1576497582000.9613.1576571281028%40Atlassian.JIRA.
[JIRA] (JENKINS-59128) hudson.model.UpdateCenter.never = true not working
Title: Message Title Dominik Kaspar updated an issue Jenkins / JENKINS-59128 hudson.model.UpdateCenter.never = true not working Change By: Dominik Kaspar When is I start Jenkins , there is alway always a connection made to the UpdateCentre UpdateCenter . Even when i I set hudson.model.UpdateCenter.never to true . I have no internet so there is always a timeout in the log. Looks like a scheduled action which i cannot stop. {noformat} INFO: The attempt #1 to do the action check updates server failed with an allowed exception:java.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:589) at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:666) at sun.net.NetworkClient.doConnect(NetworkClient.java:175) at sun.net.www.http.HttpClient.openServer(HttpClient.java:463) at sun.net.www.http.HttpClient.openServer(HttpClient.java:558) at sun.net.www.protocol.https.HttpsClient.(HttpsClient.java:264) at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:367) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191) at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1162) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1056) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1570) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1498) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:268) at hudson.model.DownloadService.loadJSON(DownloadService.java:167) at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:189) at hudson.PluginManager.checkUpdatesServer(PluginManager.java:1766) at hudson.util.Retrier.start(Retrier.java:62) at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:1737) at jenkins.model.DownloadSettings$DailyCheck.execute(DownloadSettings.java:130) at hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:101) at java.lang.Thread.run(Thread.java:748)Aug 28, 2019 7:13:54 PM hudson.util.Retrier startINFO: Calling the listener of the allowed exception 'connect timed out' at the attempt #1 to do the action check updates serverAug 28, 2019 7:13:54 PM hudson.util.Retrier startINFO: Attempted the action check updates server for 1 time(s) with no successAug 28, 2019 7:13:54 PM hudson.PluginManager doCheckUpdatesServerSEVERE: Error checking update sites for 1 attempt(s). Last exception was: Sock
[JIRA] (JENKINS-59128) hudson.model.UpdateCenter.never = true not working
Title: Message Title Dominik Kaspar commented on JENKINS-59128 Re: hudson.model.UpdateCenter.never = true not working I also experience the same problem. Is there any way to turn off Jenkins' attempts to connect to the Update Center? We're managing plugins inside a Docker image that gets deployed to an environment without access to the public Internet. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201560.1567017266000.9617.1576572300130%40Atlassian.JIRA.
[JIRA] (JENKINS-60514) Message: "Publish Micro Focus tests result is waiting for a checkpoint on LR_AFF #42"
Title: Message Title Yaniv Katz created an issue Jenkins / JENKINS-60514 Message: "Publish Micro Focus tests result is waiting for a checkpoint on LR_AFF #42" Issue Type: Bug Assignee: Maria Narcisa Galan Components: hp-application-automation-tools-plugin Created: 2019-12-17 09:08 Environment: hp plug-in ver. 5.9 Labels: LoadRunner Priority: Critical Reporter: Yaniv Katz We are using a windows slave in order to execute LoadRunner Jenkins jobs. Those jobs do not depends on each other. However jobs that started before the other and last longer preventing later jobs to be published and finished. The later jobs are waiting on queue and issue message in their console that they are waiting to the earlier job. I.e. "Publish Micro Focus tests result is waiting for a checkpoint on LR_AFF #42" (LR_AFF - is our LoadRunner Jenkins job name). In some cases we are coming and because that the earlier job stack the other jobs waits for days (during weekend). Please fix it.
[JIRA] (JENKINS-60514) Message: "Publish Micro Focus tests result is waiting for a checkpoint on LR_AFF #42"
Title: Message Title Yaniv Katz updated an issue Jenkins / JENKINS-60514 Message: "Publish Micro Focus tests result is waiting for a checkpoint on LR_AFF #42" Change By: Yaniv Katz Environment: hp plug-in ver Jenkins version: 2 . 5 190 . 3Microfocus Application Automation Tools v5. 9 Jenkins slave: Windows 10; Jenkins Master: LinuxBuild-step: Execute Micro Focus tests from file system Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203606.1576573702000.9621.1576573860163%40Atlassian.JIRA.
[JIRA] (JENKINS-59341) patterns arg not being evaluated by the DSL plugin
Title: Message Title Oliver Gondža commented on JENKINS-59341 Re: patterns arg not being evaluated by the DSL plugin Thanks for the report! Have this syntax ever worked? Where did you get that? The DSL generated on my instance suggests something like: patterns { pattern { pattern(String value) type(String value) } } Which I have not made to work either. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201892.156834300.9624.1576575840128%40Atlassian.JIRA.
[JIRA] (JENKINS-60446) Add option to pass custom paramters from multibranch to the trigger jobs
Title: Message Title Aytunc BEKEN started work on JENKINS-60446 Change By: Aytunc BEKEN Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203523.157608026.9627.1576576320804%40Atlassian.JIRA.
[JIRA] (JENKINS-59341) patterns arg not being evaluated by the DSL plugin
Title: Message Title Oliver Gondža edited a comment on JENKINS-59341 Re: patterns arg not being evaluated by the DSL plugin Thanks for the report! Have this syntax ever worked? Where did you get that?The DSL generated on my instance suggests something like:{noformat}patterns {pattern {pattern(String value)type(String value)}} {noformat} - Which I have not made to work either. - Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201892.156834300.9632.1576576500818%40Atlassian.JIRA.
[JIRA] (JENKINS-59341) patterns arg not being evaluated by the DSL plugin
Title: Message Title Oliver Gondža commented on JENKINS-59341 Re: patterns arg not being evaluated by the DSL plugin Ok, so I have tested this syntax is accepted by job DSL plugin: publishers { cleanWs { cleanWhenAborted(true) cleanWhenFailure(true) cleanWhenNotBuilt(false) cleanWhenSuccess(true) cleanWhenUnstable(true) deleteDirs(true) notFailBuild(true) disableDeferredWipeout(true) patterns { pattern { type('EXCLUDE') pattern('.propsfile') } pattern { type('INCLUDE') pattern('.gitignore') } } } } Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201892.156834300.9634.1576576561265%40Atlassian.JIRA.
[JIRA] (JENKINS-60515) Jenkins v2.107.3 job 保存触发异常
Title: Message Title Lei Yue created an issue Jenkins / JENKINS-60515 Jenkins v2.107.3 job 保存触发异常 Issue Type: Bug Assignee: Victor Martinez Attachments: 1.png Components: jenkinslint-plugin Created: 2019-12-17 10:20 Priority: Major Reporter: Lei Yue jenkins v2.107.3 config Build after other projects are built Add Comment
[JIRA] (JENKINS-25704) Scheduled triggering stops working until restart
Title: Message Title Chandan Kumar commented on JENKINS-25704 Re: Scheduled triggering stops working until restart This is happening to my Jenkins jobs as well. I wanted to run a job at exactly 8:25 am every day with this cron _expression_: "25 8 * * *". This was working fine for months until now. Changing the exact minute to 'H' seems to help sometimes. e.g. "H 8 * * *" triggers the job, but not at the exact time I need it to trigger. That's a workaround that might work for me, but it's disappointing to not be able to debug this. Cron log is not much help: cron checking hudson.model.FreeStyleProject@505fc44a[Cleanup_Builds/my-job] with spec ‘25 8 * * *’ Dec 17, 2019 8:25:13 AM FINER hudson.triggers.Trigger did not trigger hudson.model.FreeStyleProject@505fc44a[Cleanup_Builds/my-job] Dec 17, 2019 8:25:13 AM FINE hudson.triggers.Trigger Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.159277.141647497.9651.1576579980957%40Atlassian.JIRA.
[JIRA] (JENKINS-58789) Timestamps disappear without any reason inside podTemplate
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-58789 Timestamps disappear without any reason inside podTemplate Change By: Vincent Latombe Assignee: Carlos Sanchez Vincent Latombe Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201099.1564764393000.9685.1576581480606%40Atlassian.JIRA.
[JIRA] (JENKINS-58789) Timestamps disappear without any reason inside podTemplate
Title: Message Title Vincent Latombe started work on JENKINS-58789 Change By: Vincent Latombe Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201099.1564764393000.9691.1576581480688%40Atlassian.JIRA.
[JIRA] (JENKINS-60329) Username/password credentials can not be used with git
Title: Message Title Chris Kilding commented on JENKINS-60329 Re: Username/password credentials can not be used with git The options for fixing this appear (to me at least) to be: Fix the naive credential type detection in the Git plugin. Push type detection up the chain in the credentials provider, so that by the time we instantiate the primary credential object, we already know the exact type. This eliminates the multi-type object. Decompose the multi-type object and return a single type object in the credential snapshot taker (this is a fragile solution: it would fix the Git plugin because it just so happens to snapshot credentials, but it doesn’t generalise to plugins that use credentials directly). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203338.1575027217000.9696.1576582080431%40Atlassian.JIRA.
[JIRA] (JENKINS-58789) Timestamps disappear without any reason inside podTemplate
Title: Message Title Vincent Latombe updated JENKINS-58789 Jenkins / JENKINS-58789 Timestamps disappear without any reason inside podTemplate Change By: Vincent Latombe Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201099.1564764393000.9699.1576582080504%40Atlassian.JIRA.
[JIRA] (JENKINS-60329) Username/password credentials can not be used with git
Title: Message Title Chris Kilding commented on JENKINS-60329 Re: Username/password credentials can not be used with git When I looked at option 3 - get creative with the credential snapshot taker - I found it has very strict type constraints, so I don’t think it is viable to change the returned credential type within the snapshot taker. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203338.1575027217000.9704.1576582200118%40Atlassian.JIRA.
[JIRA] (JENKINS-50181) ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile
Title: Message Title Terracota Pz commented on JENKINS-50181 Re: ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile UPDATE I'm not having the issue anymore, it was my fault: I was using github token as the private key when I created the "SSH Username with private key" credential. Instead, an RSA private key should be used (eg: as per https://help.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh ). With this, it works fine. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.189200.1521076967000.9710.1576582620325%40Atlassian.JIRA.
[JIRA] (JENKINS-56259) Allow input timeout parameter
Title: Message Title Jordan Cockles commented on JENKINS-56259 Re: Allow input timeout parameter Hi, has there been any other movement on this particular functionality? I've been looking into using pipeline as code to automate deployments and use the steps in stages approach to manage the different elements of the CI process. Having the ability to specify a timeout directly on the input option would be perfect as it appears the stage method does not accept timeout as a valid nested parameter. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.197830.1551046009000.9724.1576584180291%40Atlassian.JIRA.
[JIRA] (JENKINS-58949) If job fails in cleanup further triggering fails
Title: Message Title Paul Allen commented on JENKINS-58949 Re: If job fails in cleanup further triggering fails The P4 Trigger is a top level endpoint in Jenkins and wakes up all Subscribed Jenkins jobs, checks for changes then scheduled a build. If the previous run failed or was aborted then no changes are recorded so further polling or in this case triggers will fail. A 'Build Now' would correct the state and all would be back to normal. Ideally we could carry the previous built changes forward, or change the logic to search the previous builds. Perhaps recording the 'head' change would be enough for failed/aborted builds, but that might not be ideal in all circumstances. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201296.1565876577000.9731.1576584480575%40Atlassian.JIRA.
[JIRA] (JENKINS-59341) patterns arg not being evaluated by the DSL plugin
Title: Message Title Oliver Gondža started work on JENKINS-59341 Change By: Oliver Gondža Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201892.156834300.9734.1576585200419%40Atlassian.JIRA.
[JIRA] (JENKINS-60504) Nullpointer exception
Title: Message Title Matt Wilson commented on JENKINS-60504 Re: Nullpointer exception That could be the case. We use folder permissions quite a bit to block off certain jobs. That said, I was seeing this error myself on pretty much any job I looked at (my account has full access to all of Jenkins). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203595.1576505663000.9736.1576587781533%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Michal Kovarik commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Prometheus plugin 2.0.6 without permissive-security-plugin works. Prometheus plugin 2.0.0 and permissive-security-plugin 0.5 works. Prometheus plugin 2.0.6 and permissive-security-plugin 0.5 does not work regardless permissive-script-security.enabled setting. During startup of Jenkins there are issues with prometheus - https://issues.jenkins-ci.org/browse/JENKINS-59675?focusedCommentId=377073 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201579.156710687.9738.1576589580555%40Atlassian.JIRA.
[JIRA] (JENKINS-59675) Upgrading to 2.0.6 is causing UI issues in pipelines
Title: Message Title Michal Kovarik commented on JENKINS-59675 Re: Upgrading to 2.0.6 is causing UI issues in pipelines Seems to be duplicate of JENKINS-59145 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202368.1570259911000.9750.1576589640242%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title M McGrath commented on JENKINS-56500 Re: Declarative pipeline restricted in code size Liam Newman Still hitting this size limit issue with declarative with everything broken out into shared libraries. My code is predominantly in /vars. Templated pipelines with each stage broken out into global vars. Jenkinsfile passes pipeline params. At this point i'm starting to test breaking logic out into classes /scr, and a move to scripted pipelines. Im not fully sure how the jenkins compiles declarative apart from the 64K size limit. We really liked alot of what declarative pipelines offer, but the file size issue is a pain. Is a move to scripted the right option? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.198107.1552302995000.9764.1576589881612%40Atlassian.JIRA.
[JIRA] (JENKINS-59804) Support Multibranch Pipelines
Title: Message Title Nicholas Brown commented on JENKINS-59804 Re: Support Multibranch Pipelines For what it's worth the https://plugins.jenkins.io/cloudbees-bitbucket-branch-source plugin works very well for using Bitbucket Server with multi-branch pipelines. It uses the Bitbucket Server native webhooks support. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202534.1571228736000.9775.1576590060329%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title M McGrath commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Really need some direction on how to over come this issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.174127.1473169024000.9785.1576590243477%40Atlassian.JIRA.
[JIRA] (JENKINS-60516) Jenkins pipeline triggered for all branches on code commit in Develop branch
Title: Message Title Monali Chaudhary created an issue Jenkins / JENKINS-60516 Jenkins pipeline triggered for all branches on code commit in Develop branch Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2019-12-17 13:45 Priority: Major Reporter: Monali Chaudhary My developer is pushing the code in Dev branch of Bitbucket but in Jenkins it triggers Dev, Test, Stage and Prod pipeline though there is no changes deployed in Other branches and it simply redeploys the last commit in Test, Stage and Prod. But then why should any code push to DEV branch should trigger another pipelines. Please note that every env pipeline is only checking out respective env branch for deployment. I had raised this issue with Bitbucket community as well but they confirmed that no issues seen from Bitbucket end and suggested to check from Jenkins end. In my jenkins every pipeline is triggered based on "Build whenever a change is pushed to Bitbucket" Add Comment
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title efo plo commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script M McGrath Good news is that you can combine both types. Our project now looks like node('node') { stage('stage 1') { ... } node('node') { stage('stage 2') { ... } ... pipeline { agent {... } stages { ... } } ... node('node') { stage('stage n-1') { ... } node('node') { stage('stage n') { ... } Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.174127.1473169024000.9867.1576590662068%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title M McGrath commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script efo plo huumm, interesting. Ive already asked this over on https://issues.jenkins-ci.org/browse/JENKINS-56500 so apologies for duplication. our code is predominantly in /vars. Templated pipelines with each stage broken out into global vars. Jenkinsfile passes pipeline params. We really liked alot of what declarative pipelines offer, but the file size issue is a pain. At this point i'm starting to break logic out into classes /scr, and a move to scripted pipelines. Is a move to scripted the right option? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.174127.1473169024000.9943.1576591261843%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title M McGrath edited a comment on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script [~eplodn1] huumm, interesting.Ive already asked this over on https://issues.jenkins-ci.org/browse/JENKINS-56500 so apologies for duplication. our code is predominantly in /vars. Templated pipelines with each stage broken out into global vars. Jenkinsfile passes pipeline params. We really liked alot of what declarative pipelines offer, but the file size issue is a pain.At this point i'm starting to break logic out into classes /scr, and a move to scripted pipelines. Is a move to scripted the right option? If i break logic out into classes and try to still with declarative will i still hit size limit? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.174127.1473169024000.10019.1576591382945%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title M McGrath edited a comment on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script [~eplodn1] huumm, interesting.Ive already asked this over on https://issues.jenkins-ci.org/browse/JENKINS-56500 so apologies for duplication. our code is predominantly in /vars. Templated pipelines with each stage broken out into global vars. Jenkinsfile passes pipeline params. We really liked alot of what declarative pipelines offer, but the file size issue is a pain.At this point i'm starting to break logic out into classes /scr, and a move to scripted pipelines. Is a move to scripted the right option? If i break logic out into classes and try to still use with declarative will i still hit size limit? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.174127.1473169024000.10169.1576591411639%40Atlassian.JIRA.
[JIRA] (JENKINS-60446) Add option to pass custom paramters from multibranch to the trigger jobs
Title: Message Title Aytunc BEKEN commented on JENKINS-60446 Re: Add option to pass custom paramters from multibranch to the trigger jobs Hi, Full name parameters is released with the 1.6 version, probably It will be downloadable soon. For the other parameters thing, I need to work on it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203523.157608026.10173.1576591980226%40Atlassian.JIRA.
[JIRA] (JENKINS-58604) Full Stage View only showing one
Title: Message Title Brian J Murrell commented on JENKINS-58604 Re: Full Stage View only showing one I've seen suggestions to use Blue Ocean, but there is a crucial flaw with this: the Chuck Norris plugin does not support it. Blue Ocean is simply not a suitable replacement for Stage View. It has it's own bugs and issues. It's heavy – it can take many (very many in some cases) seconds to load, it's often "out of date" telling me that it's waiting for a stage to start when the stage is well under way having executed many steps already. Those are just the issues off the top of my head. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.200764.1563816065000.10178.1576593060219%40Atlassian.JIRA.
[JIRA] (JENKINS-60431) Cancel outdated jobs for Bitbucket Pull Requests Builder is not honored
Title: Message Title ovi craciun commented on JENKINS-60431 Re: Cancel outdated jobs for Bitbucket Pull Requests Builder is not honored ping Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203503.1576024387000.10234.1576593840047%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title efo plo commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script See the attached pipeline, here or over on #56500. If you're facing the same issue, then classes or no classes, it will still hit the limit. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.174127.1473169024000.10262.1576595642561%40Atlassian.JIRA.
[JIRA] (JENKINS-60321) Multibranch pipeline with default Jenkinsfile fails when scanning p4 streams
Title: Message Title Matthew Smeeth resolved as Fixed Fixed, it should now use the default Jenkinsfile when using the Multibranch with defaults plugin. Jenkins / JENKINS-60321 Multibranch pipeline with default Jenkinsfile fails when scanning p4 streams Change By: Matthew Smeeth Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+un
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title M McGrath commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script efo plo thanks for the replies. yes ive tested with attached pipeline and it reproduces the same issue we are seeing with our templated pipeline using shared libs. I tried out Liam Newman fix with the plugin update and JAVA_OPTS variable set but no joy We dont really want to move away from declarative but whatever if the best choice we will make needed changes. assuming when you say "classes or no classes, it will still hit the limit." are you refering to using classes combined with declarative. Would a move to scripted pipelines, broken out into shared libs be an option or will it be more of the same? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.174127.1473169024000.10348.1576598881748%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title M McGrath edited a comment on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script [~eplodn1] thanks for the replies. yes ive tested with attached pipeline and it reproduces the same issue we are seeing with our templated pipeline using shared libs.I tried out [~bitwiseman] fix with the plugin update and JAVA_OPTS variable set but no joy :(We dont original didnt really want to move away from declarative but whatever if is the best choice option we will make needed changes. assuming when you say "_classes or no classes, it will still hit the limit._" are you refering to using classes combined with declarative.Would a move to scripted pipelines, broken out into shared libs be an option or will it be more of the same? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.174127.1473169024000.10424.1576598941755%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title M McGrath edited a comment on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script [~eplodn1] thanks for the replies. yes ive tested with attached pipeline and it reproduces the same issue we are seeing with our templated pipeline using shared libs.I tried out [~bitwiseman] fix with the plugin update and JAVA_OPTS variable set but no joy :(We original didnt really want to move away from declarative but whatever is the best option we will make needed changes. assuming when you say "_classes or no classes, it will still hit the limit._" are you refering to using classes combined with declarative.Would a move to scripted pipelines, broken out into shared libs be an option or will it be more of the same? I dont want to refactor and find out after Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.174127.1473169024000.10500.1576599011163%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title M McGrath edited a comment on JENKINS-56500 Re: Declarative pipeline restricted in code size [~bitwiseman] Still hitting this size limit issue with declarative with everything broken out into shared libraries.My code is predominantly in /vars. Templated pipelines with each stage broken out into global vars. Jenkinsfile passes pipeline params. At this point i'm starting to test breaking logic out into classes /scr, and a move to scripted pipelines. Im not fully sure vey techie when it come to how the jenkins compiles declarative apart from the 64K size limit. We really liked alot of what declarative pipelines offer, but the file size issue is a pain.Is a move to scripted the right option? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.198107.1552302995000.10577.1576599300404%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title M McGrath edited a comment on JENKINS-56500 Re: Declarative pipeline restricted in code size [~bitwiseman] Still hitting this size limit issue with declarative with everything broken out into shared libraries.My code is predominantly in /vars. Templated pipelines with each stage broken out into global vars. Jenkinsfile passes pipeline params. At this point i'm starting to test breaking logic out into classes /scr, and a move to scripted pipelines. Im vey techie when it come to how jenkins compiles declarative apart from the 64K size limit. We really liked alot of what declarative pipelines offer, but the file size issue is a pain.Is a move to scripted the right option? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.198107.1552302995000.10590.1576599360922%40Atlassian.JIRA.
[JIRA] (JENKINS-60141) Excessive number of "login -s" requests
Title: Message Title Charusheela Bopardikar commented on JENKINS-60141 Re: Excessive number of "login -s" requests Refactored the code to reduce number of times login -s is called. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203002.157355793.10606.1576600260398%40Atlassian.JIRA.
[JIRA] (JENKINS-60141) Excessive number of "login -s" requests
Title: Message Title Charusheela Bopardikar started work on JENKINS-60141 Change By: Charusheela Bopardikar Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203002.157355793.10604.1576600260361%40Atlassian.JIRA.
[JIRA] (JENKINS-59484) EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory
Title: Message Title Matthew Smeeth started work on JENKINS-59484 Change By: Matthew Smeeth Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202099.1569244102000.10610.1576600860466%40Atlassian.JIRA.
[JIRA] (JENKINS-59484) EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory
Title: Message Title Matthew Smeeth assigned an issue to Matthew Smeeth Jenkins / JENKINS-59484 EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory Change By: Matthew Smeeth Assignee: Matthew Smeeth Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202099.1569244102000.10614.1576600920290%40Atlassian.JIRA.
[JIRA] (JENKINS-60141) Excessive number of "login -s" requests
Title: Message Title Charusheela Bopardikar assigned an issue to Charusheela Bopardikar Jenkins / JENKINS-60141 Excessive number of "login -s" requests Change By: Charusheela Bopardikar Assignee: Charusheela Bopardikar Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203002.157355793.10616.1576600920318%40Atlassian.JIRA.
[JIRA] (JENKINS-60457) NullPointerException in h.p.e.p.content.ScriptContent.renderTemplate
Title: Message Title Alex Earl commented on JENKINS-60457 Re: NullPointerException in h.p.e.p.content.ScriptContent.renderTemplate You don't need to use token macro to expand those tokens. You can just use the tokens like functions in the template in a groovy context <%= %> and it will be used correctly Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203535.1576141507000.10620.1576602420159%40Atlassian.JIRA.
[JIRA] (JENKINS-60479) Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run
Title: Message Title Karl Wirth commented on JENKINS-60479 Re: Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run Hi Andrew Bayer, Thanks for reporting this. Before we start, from a pure Perforce streams point of view I'd recommend against having a library stream in the same stream path as code. The code expects that streams are divergent forms of the same basic code. For example a stream may contain: //Project1Stream/Rel1/... //Project1Stream/Rel2/... //Project1Stream/Main/... //Project1Stream/Dev/... which could import //LibraryStream/main/... Alternatively if you have a deeper stream depth set you could have the two stream trees in the same depot: //StreamDepot/Project1/Rel1/... //StreamDepot/Project1/Rel2/... //StreamDepot/Project1/Main/... //StreamDepot/Project1/Dev/... //StreamDepot/Library/Main/... //StreamDepot/Library/Dev/... If you don't have this structure then there will always be outstanding changes that need to be branched between the library stream and it's parents. Now back to the problem. I tried setting this up and keep getting compilation errors: Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60479) Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run
Title: Message Title Karl Wirth edited a comment on JENKINS-60479 Re: Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run Hi [~abayer],Thanks for reporting this. Before we start, from a pure Perforce streams point of view I'd recommend against having a library stream in the same stream path as code.The code expects that streams are divergent forms of the same basic code. For example a stream may contain: {code:java}//Project1Stream/Rel1/...//Project1Stream/Rel2/...//Project1Stream/Main/...//Project1Stream/Dev/...{code} which could import{code:java}//LibraryStream/main/...{code}Alternatively if you have a deeper stream depth set you could have the two stream trees in the same depot:{code:java}//StreamDepot/Project1/Rel1/...//StreamDepot/Project1/Rel2/...//StreamDepot/Project1/Main/...//StreamDepot/Project1/Dev/...//StreamDepot/Library/Main/...//StreamDepot/Library/Dev/...{code}If you don't have this structure then there will always be outstanding changes that need to be branched between the library stream and it's parents.Now back to the problem. I tried setting this up and keep getting compilation errors: {code:java} org.jenkinsci.plugins.workflow.cps.CpsCompilationErrorsException: startup failed: /var/lib/jenkins/jobs/JENKINS-60479_Exclusions_MultiBranch/branches/main/builds/2/libs/test-pipeline/vars/lib.groovy: 8: Unknown stage section "matrix". Starting with version 0.5, steps in a stage must be in a ‘steps’ block. @ line 8, column 7. stage('Build') {code} I am on 2.176.1 so this may be a version problem. Just in case can you please send me the screenshots of the job definition to make sure I'm doing this correctly. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60479) Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run
Title: Message Title Matthew Brunton updated an issue Jenkins / JENKINS-60479 Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run Change By: Matthew Brunton Attachment: image-2019-12-17-13-37-15-881.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203564.1576265676000.10656.1576607880310%40Atlassian.JIRA.
[JIRA] (JENKINS-60479) Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run
Title: Message Title Matthew Brunton updated an issue Jenkins / JENKINS-60479 Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run Change By: Matthew Brunton Attachment: image-2019-12-17-13-40-13-460.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203564.1576265676000.10659.1576608060213%40Atlassian.JIRA.
[JIRA] (JENKINS-60479) Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run
Title: Message Title Matthew Brunton updated an issue Jenkins / JENKINS-60479 Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run Change By: Matthew Brunton Attachment: image-2019-12-17-13-41-38-310.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203564.1576265676000.10662.1576608120190%40Atlassian.JIRA.
[JIRA] (JENKINS-60479) Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run
Title: Message Title Matthew Brunton updated an issue Jenkins / JENKINS-60479 Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run Change By: Matthew Brunton Attachment: image-2019-12-17-13-43-11-090.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203564.1576265676000.10665.1576608240259%40Atlassian.JIRA.
[JIRA] (JENKINS-60482) EC2 Alternate Endpoint and Region are reset when managing jenkins configuration
Title: Message Title Heather Lemieux updated an issue Jenkins / JENKINS-60482 EC2 Alternate Endpoint and Region are reset when managing jenkins configuration Change By: Heather Lemieux Attachment: Screen Shot 2019-12-17 at 1.53.09 PM.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203569.1576277084000.10668.1576608840427%40Atlassian.JIRA.
[JIRA] (JENKINS-60479) Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run
Title: Message Title Matthew Brunton updated an issue Jenkins / JENKINS-60479 Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run Change By: Matthew Brunton Attachment: image-2019-12-17-13-55-17-110.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203564.1576265676000.10671.1576608960240%40Atlassian.JIRA.
[JIRA] (JENKINS-60479) Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run
Title: Message Title Matthew Brunton commented on JENKINS-60479 Re: Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run Thanks for responding. I'll supply screenshots of the setup I'm using to reproduce. I'm also using the Pipeline: Declarative plugin 1.5, which was recently released to add matrix support to declarative pipelines. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203564.1576265676000.10674.1576609080140%40Atlassian.JIRA.
[JIRA] (JENKINS-60482) EC2 Alternate Endpoint and Region are reset when managing jenkins configuration
Title: Message Title Kevin Flynn commented on JENKINS-60482 Re: EC2 Alternate Endpoint and Region are reset when managing jenkins configuration This is also an issue for me. We tried setting the AWS_DEFAULT_REGION env var in the Jenkins docker container, but the EC2 Plugin still can't determine the EC2 endpoint on it's own. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203569.1576277084000.10678.1576610040221%40Atlassian.JIRA.
[JIRA] (JENKINS-59973) rtUpload / rtDownload fail with HTTP 401 / 403
Title: Message Title Jesper Reenberg commented on JENKINS-59973 Re: rtUpload / rtDownload fail with HTTP 401 / 403 Ah, there might be the mismatch between my setup and yours. I wasn't aware that you were using API keys. Hopefully I will be able to test that tonight. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202777.157235158.10682.1576612140240%40Atlassian.JIRA.
[JIRA] (JENKINS-60517) Kubernetes plugin crashes with docker plugin .inside command
Title: Message Title Ivan Kurnosov created an issue Jenkins / JENKINS-60517 Kubernetes plugin crashes with docker plugin .inside command Issue Type: Bug Assignee: Unassigned Components: docker-workflow-plugin, kubernetes-plugin Created: 2019-12-17 20:42 Environment: 2.190.3 Labels: kubernetes kubernetes-plugin docker-workflow-plugin Priority: Critical Reporter: Ivan Kurnosov I have the following jenkinsfile: stage('build') { container('docker') { def tag = "${env.JOB_NAME}:${env.BUILD_ID}".toLowerCase() devTools = docker.build(tag, "--pull -f .docker/dev-tools/Dockerfile .") devTools.inside() { repository.code(this) sh 'make -f Makefile.test -j$(nproc) build-test' } } } It works as expected with kubernetes plugin v1.22.0 (previous stable) and docker pipeline plugin v1.21 (current stable). Today I installed a newer kubernetes plugin v1.22.1 and my jobs started failing with: 00:03:31.157 + docker inspect -f . 00:03:31.157 . 00:03:31.185
[JIRA] (JENKINS-60517) Kubernetes plugin crashes with docker plugin .inside command
Title: Message Title Ivan Kurnosov updated an issue Jenkins / JENKINS-60517 Kubernetes plugin crashes with docker plugin .inside command Change By: Ivan Kurnosov Environment: 2 jenkins v2 .190.3 kubernetes plugin v1.22.0docker workflow plugin v1.21 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203614.1576615322000.10707.1576615440160%40Atlassian.JIRA.
[JIRA] (JENKINS-41149) Jenkins Promotion Using Wrong Workspace, Workspace@2
Title: Message Title Sergej Kleva commented on JENKINS-41149 Re: Jenkins Promotion Using Wrong Workspace, Workspace@2 Jenkins 2.190.3 and latest Promote BUild 3.5 and the same thing is happening with @2 workspace! When want to promote build ... injecting file with variables cannot be found because it was created in workspace@1. Any solution to this nasty cycle! ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.177908.148468698.10709.1576615920174%40Atlassian.JIRA.
[JIRA] (JENKINS-41149) Jenkins Promotion Using Wrong Workspace, Workspace@2
Title: Message Title Sergej Kleva edited a comment on JENKINS-41149 Re: Jenkins Promotion Using Wrong Workspace, Workspace@2 Jenkins 2.190.3 and latest Promote BUild 3.5 and the same thing is happening with @2 workspace!When want to promote build ... injecting file with variables cannot be found because it was created in workspace@1. To recap:Job created env.props file in workspac@1, promote build want to include this file but cannot "look" into workspace@1 ..it only "see" workspace@2! So promote fail with an error "cannot find env.props" file! Any solution to this nasty cycle! ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.177908.148468698.10714.1576616100210%40Atlassian.JIRA.
[JIRA] (JENKINS-55849) cannot stop auto-scrolling in blue ocean console
Title: Message Title Micah Snyder commented on JENKINS-55849 Re: cannot stop auto-scrolling in blue ocean console Auto-scrolling and auto-open when a stage completes is tremendously annoying when viewing a larger pipeline with many parallel stages. Any change in status to one stage scrolls me to the bottom of the screen. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.197246.1548796499000.10719.1576617420208%40Atlassian.JIRA.
[JIRA] (JENKINS-60179) Plugin JSON format to match anchore-cli JSONs format
Title: Message Title Swathi Gangisetty updated JENKINS-60179 Fixed in release v1.0.21 by [PR|https://github.com/jenkinsci/anchore-container-scanner-plugin/pull/8] Jenkins / JENKINS-60179 Plugin JSON format to match anchore-cli JSONs format Change By: Swathi Gangisetty Status: Open Fixed but Unreleased Resolution: Fixed Released As: v1.0.21 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60179) Plugin JSON format to match anchore-cli JSONs format
Title: Message Title Swathi Gangisetty edited a comment on JENKINS-60179 Re: Plugin JSON format to match anchore-cli JSONs format Fixed in release v1.0.21 by [ GitHub PR 8 |https://github.com/jenkinsci/anchore-container-scanner-plugin/pull/8] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203139.1573802819000.10731.1576619640246%40Atlassian.JIRA.
[JIRA] (JENKINS-60179) Plugin JSON format to match anchore-cli JSONs format
Title: Message Title Swathi Gangisetty edited a comment on JENKINS-60179 Re: Plugin JSON format to match anchore-cli JSONs format Fixed in release v1.0.21 by [PR| [ https://github.com/jenkinsci/anchore-container-scanner-plugin/pull/8] ] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203139.1573802819000.10729.1576619640178%40Atlassian.JIRA.
[JIRA] (JENKINS-60179) Plugin JSON format to match anchore-cli JSONs format
Title: Message Title Swathi Gangisetty updated JENKINS-60179 Jenkins / JENKINS-60179 Plugin JSON format to match anchore-cli JSONs format Change By: Swathi Gangisetty Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203139.1573802819000.10733.1576619700270%40Atlassian.JIRA.
[JIRA] (JENKINS-59313) Builds are not processed when triggered manually
Title: Message Title Jon Denly edited a comment on JENKINS-59313 Re: Builds are not processed when triggered manually [~hex_sm] Any chance you can provide more information on the fix? We have the same problem and are using the authorize project plugin. EDIT: The fix for us was to add the Agent/Build permission globally for authenticated users, having it at folder level was not enough. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201863.1568191671000.10735.1576625400173%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Liam Newman commented on JENKINS-56500 Re: Declarative pipeline restricted in code size M McGrath There are reasons to move to Scripted but this is not one of them. In fact, this issue is a reason not to move to scripted. This error can occur in declarative or scripted, but I have no ability to automatically work around it scripted. Perhaps we can try this. Take the Jenkinsfile attached to this issue and try to run it on your Jenkins (without the JVM property). Make sure it encounters the error. Do what you've done before to turn on the fix. Make sure that after that the attached Jenkinsfile does not report the error. That way we can at least be sure that the fix is active on your system. "Templated pipelines with each stage broken out into global vars." - This doesn't sound like Declarative, but maybe I'm not understanding what you're meaning. Can you at least provide an example of what your pipeline looks like (even if you can show your actual pipeline)? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.198107.1552302995000.10737.1576626000497%40Atlassian.JIRA.
[JIRA] (JENKINS-54064) Gradle plugin uses legacy plugin format
Title: Message Title René Scheibe commented on JENKINS-54064 Re: Gradle plugin uses legacy plugin format Daniel Beck Thanks a lot for these very useful details. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.194683.1539463436000.10751.1576627080222%40Atlassian.JIRA.
[JIRA] (JENKINS-59973) rtUpload / rtDownload fail with HTTP 401 / 403
Title: Message Title Jesper Reenberg commented on JENKINS-59973 Re: rtUpload / rtDownload fail with HTTP 401 / 403 My test has also been conducted with Yahav Itzhak's example repo: https://github.com/yahavi/jenkins-reproducer To verify my simple setup outside of Jenkins, using my newly created API_KEY: $ curl --insecure \ > -H 'X-JFrog-Art-Api:AKCp5e3VEwLXG..vqfWiw1nUUiuEKaMuYBn' \ > -i "http://localhost/artifactory/api/search/aql" \ > -X POST \ > -H 'Content-Type:text/plain' \ > --data 'items.find({"repo": "generic-local","$or": [{"$and": [{"path": { "$match": "*"},"name": { "$match": "*"}}]}]}).include("name","repo","path","actual_md5","actual_sha1","size","type","property")' HTTP/1.1 200 OK Server: Artifactory/6.16.0 X-Artifactory-Id: b2b51933cd264b43:10d5af30:16f15b57d38:-8000 Content-Type: application/json Transfer-Encoding: chunked Date: Tue, 17 Dec 2019 22:16:13 GMT { "results" : [ { "repo" : "generic-local", "path" : ".", "name" : "hello", "type" : "file", "size" : 14, "actual_md5" : "bea8252ff4e80f41719ea13cdf007273", "actual_sha1" : "60fde9c2310b0d4cad4dab8d126b04387efba289" } ], "range" : { "start_pos" : 0, "end_pos" : 1, "total" : 1 } } Used Versions Jenkins ver. 2.190.3 Artifactory OSS 6.16.0 rev 61600900 Test matrix artifactory-jenkins-plugin Anonymous (Credentials set to '- none -') User/password User/API_KEY API_KEY (SecretText) 3.3.2 HTTP/1.1 403 Forbidden N/A (not able to select in global plugin server config) 3.3.x-SNAPSHOT (private-4272760c-reenberg) aka HAP-1219 HTTP/1.1 403 Forbidden N/A
[JIRA] (JENKINS-59973) rtUpload / rtDownload fail with HTTP 401 / 403
Title: Message Title Jesper Reenberg edited a comment on JENKINS-59973 Re: rtUpload / rtDownload fail with HTTP 401 / 403 My test has also been conducted with [~yahaviz]'s example repo: [https://github.com/yahavi/jenkins-reproducer]To verify my simple setup outside of Jenkins, using my newly created API_KEY:{code:java}$ curl --insecure \> -H 'X-JFrog-Art-Api:AKCp5e3VEwLXG..vqfWiw1nUUiuEKaMuYBn' \> -i "http://localhost/artifactory/api/search/aql" \> -X POST \> -H 'Content-Type:text/plain' \> --data 'items.find({"repo": "generic-local","$or": [{"$and": [{"path": { "$match": "*"},"name": { "$match": "*"}}]}]}).include("name","repo","path","actual_md5","actual_sha1","size","type","property")'HTTP/1.1 200 OKServer: Artifactory/6.16.0X-Artifactory-Id: b2b51933cd264b43:10d5af30:16f15b57d38:-8000Content-Type: application/jsonTransfer-Encoding: chunkedDate: Tue, 17 Dec 2019 22:16:13 GMT{"results" : [ { "repo" : "generic-local", "path" : ".", "name" : "hello", "type" : "file", "size" : 14, "actual_md5" : "bea8252ff4e80f41719ea13cdf007273", "actual_sha1" : "60fde9c2310b0d4cad4dab8d126b04387efba289"} ],"range" : { "start_pos" : 0, "end_pos" : 1, "total" : 1}}{code} h3. Used VersionsJenkins ver. 2.190.3Artifactory OSS 6.16.0 rev 61600900h3. Test matrix||artifactory-jenkins-plugin||Anonymous (Credentials set to '- none -')||User/password||User/API_KEY||API_KEY (SecretText)|||3.3.2|HTTP/1.1 403 Forbidden|(/)|(/)|N/A (not able to select in global plugin server config)||3.3.x-SNAPSHOT (private-4272760c-reenberg) aka HAP-1219|HTTP/1.1 403 Forbidden|(/)|(/)| N/A||3.4.1|HTTP/1.1 403 Forbidden|(/)|(/)|N/A||3.4.x-SNAPSHOT (private-879ba6cb-jenkins) by Yahavi Enables SecretText|HTTP/1.1 403 Forbidden *Logs* access.log: {{2019-12-17 23:31:14,749 [ACCEPTED LOGIN] for client : anonymous / 172.22.0.3.}} request.log: {{20191217233114\|23\|REQUEST\|172.22.0.3\|anonymous\|POST\|/api/search/aql\|HTTP/1.1\|403\|192}} *Note:* I assume that the anonymous user fails (even though enonymous has READ access and can download through the web interface), as JQL is used here, and thus an actual user is needed?|(/)|(/)|(x) The SecretText credentials are shown, but it fails: HTTP/1.1 401 Unauthorized *Logs* | access.log:{{2019-12-17 23:26:16,665 [DENIED LOGIN] for client : NA / 172.22.0.3.}} request.log:{{20191217232616 \ |36 \ |REQUEST \ |172.22.0.3 \ |non_authenticated_user \ |POST \ |/api/search/aql \ |HTTP/1.1 \ |401 \ |192}} *NOTE:* I have never before seen the 'non_authenticated_user', but maybe this is somewhat new? Anyways its seems that my API_KEY which was pasted as the SecretText credentials are not properly recognized. I have double checked that the API_KEY is pasted correctly.| Obviously I need to retest this with 6.12 version of Artifactory, but I doubt that is where the issue lies. [~ethorsa], I would suggest that you atleast look in the 'access.log' and 'request.log'. What I finds easiest, is to just {{tail -f ARTI_HOME/logs/*.log}}. Then add a few newlines to your terminal by pressing enter a few times, and then try your build. Assuming you don't have any other traffic to your Artifactory instance, then you will easily see anything that gets added to any of the log files. If that is not possible for you, then you would need to fetch them from the web interface, as previously mentioned. [~yahaviz], note that I tested your build, but couldn't get it to work. Maybee i derbed something?I added a new secret, in the global scope: * Secret: * ID: 'api-user_secret' * Description: 'api-user using API_KEY as secret text'
[JIRA] (JENKINS-59973) rtUpload / rtDownload fail with HTTP 401 / 403
Title: Message Title Jesper Reenberg edited a comment on JENKINS-59973 Re: rtUpload / rtDownload fail with HTTP 401 / 403 My test has also been conducted with [~yahaviz]'s example repo: [https://github.com/yahavi/jenkins-reproducer]To verify my simple setup outside of Jenkins, using my newly created API_KEY:{code:java}$ curl --insecure \> -H 'X-JFrog-Art-Api:AKCp5e3VEwLXG..vqfWiw1nUUiuEKaMuYBn' \> -i "http://localhost/artifactory/api/search/aql" \> -X POST \> -H 'Content-Type:text/plain' \> --data 'items.find({"repo": "generic-local","$or": [{"$and": [{"path": { "$match": "*"},"name": { "$match": "*"}}]}]}).include("name","repo","path","actual_md5","actual_sha1","size","type","property")'HTTP/1.1 200 OKServer: Artifactory/6.16.0X-Artifactory-Id: b2b51933cd264b43:10d5af30:16f15b57d38:-8000Content-Type: application/jsonTransfer-Encoding: chunkedDate: Tue, 17 Dec 2019 22:16:13 GMT{"results" : [ { "repo" : "generic-local", "path" : ".", "name" : "hello", "type" : "file", "size" : 14, "actual_md5" : "bea8252ff4e80f41719ea13cdf007273", "actual_sha1" : "60fde9c2310b0d4cad4dab8d126b04387efba289"} ],"range" : { "start_pos" : 0, "end_pos" : 1, "total" : 1}}{code} h3. Used VersionsJenkins ver. 2.190.3Artifactory OSS 6.16.0 rev 61600900h3. Test matrix||artifactory-jenkins-plugin||Anonymous (Credentials set to '- none -')||User/password||User/API_KEY||API_KEY (SecretText)|||3.3.2|HTTP/1.1 403 Forbidden|(/)|(/)|N/A (not able to select in global plugin server config)||3.3.x-SNAPSHOT (private-4272760c-reenberg) aka HAP-1219|HTTP/1.1 403 Forbidden|(/)|(/)| N/A||3.4.1|HTTP/1.1 403 Forbidden|(/)|(/)|N/A||3.4.x-SNAPSHOT (private-879ba6cb-jenkins) by Yahavi Enables SecretText|HTTP/1.1 403 Forbidden *Logs* access.log: {{2019-12-17 23:31:14,749 [ACCEPTED LOGIN] for client : anonymous / 172.22.0.3.}} request.log: {{20191217233114\|23\|REQUEST\|172.22.0.3\|anonymous\|POST\|/api/search/aql\|HTTP/1.1\|403\|192}} *Note:* I assume that the anonymous user fails (even though enonymous has READ access and can download through the web interface), as JQL is used here, and thus an actual user is needed?|(/)|(/)|(x) The SecretText credentials are shown, but it fails: HTTP/1.1 401 Unauthorized *Logs* access.log: {{2019-12-17 23:26:16,665 [DENIED LOGIN] for client : NA / 172.22.0.3.}} request.log: {{20191217232616\|36\|REQUEST\|172.22.0.3\|non_authenticated_user\|POST\|/api/search/aql\|HTTP/1.1\|401\|192}} *NOTE:* I have never before seen the 'non_authenticated_user', but maybe this is somewhat new? Anyways its seems that my API_KEY which was pasted as the SecretText credentials are not properly recognized. I have double checked that the API_KEY is pasted correctly.| Obviously I need to retest this with 6.12 version of Artifactory, but I doubt that is where the issue lies. [~ethorsa], I would suggest that you atleast look in the 'access.log' and 'request.log'. What I finds easiest, is to just {{tail -f ARTI_HOME/logs/*.log}}. Then add a few newlines to your terminal by pressing enter a few times, and then try your build. Assuming you don't have any other traffic to your Artifactory instance, then you will easily see anything that gets added to any of the log files. If that is not possible for you, then you would need to fetch them from the web interface, as previously mentioned. [~yahaviz], note that I tested your build, but couldn't get it to work. Maybee i derbed something?I added a new secret, in the global scope: * Secret: * ID: 'api-user_secret' * Description: 'api-user using API_KEY as secret text'
[JIRA] (JENKINS-59973) rtUpload / rtDownload fail with HTTP 401 / 403
Title: Message Title Jesper Reenberg edited a comment on JENKINS-59973 Re: rtUpload / rtDownload fail with HTTP 401 / 403 My test has also been conducted with [~yahaviz]'s example repo: [https://github.com/yahavi/jenkins-reproducer]To verify my simple setup outside of Jenkins, using my newly created API_KEY:{code:java}$ curl --insecure \> -H 'X-JFrog-Art-Api:AKCp5e3VEwLXG..vqfWiw1nUUiuEKaMuYBn' \> -i "http://localhost/artifactory/api/search/aql" \> -X POST \> -H 'Content-Type:text/plain' \> --data 'items.find({"repo": "generic-local","$or": [{"$and": [{"path": { "$match": "*"},"name": { "$match": "*"}}]}]}).include("name","repo","path","actual_md5","actual_sha1","size","type","property")'HTTP/1.1 200 OKServer: Artifactory/6.16.0X-Artifactory-Id: b2b51933cd264b43:10d5af30:16f15b57d38:-8000Content-Type: application/jsonTransfer-Encoding: chunkedDate: Tue, 17 Dec 2019 22:16:13 GMT{"results" : [ { "repo" : "generic-local", "path" : ".", "name" : "hello", "type" : "file", "size" : 14, "actual_md5" : "bea8252ff4e80f41719ea13cdf007273", "actual_sha1" : "60fde9c2310b0d4cad4dab8d126b04387efba289"} ],"range" : { "start_pos" : 0, "end_pos" : 1, "total" : 1}}{code} h3. Used VersionsJenkins ver. 2.190.3Artifactory OSS 6.16.0 rev 61600900h3. Test matrix||artifactory-jenkins-plugin||Anonymous (Credentials set to '- none -')||User/password||User/API_KEY||API_KEY (SecretText)|||3.3.2|HTTP/1.1 403 Forbidden|(/)|(/)|N/A (not able to select in global plugin server config)||3.3.x-SNAPSHOT (private-4272760c-reenberg) aka HAP-1219|HTTP/1.1 403 Forbidden|(/)|(/)| N/A||3.4.1|HTTP/1.1 403 Forbidden|(/)|(/)|N/A||3.4.x-SNAPSHOT (private-879ba6cb-jenkins) by Yahavi Enables SecretText|HTTP/1.1 403 Forbidden *Logs* access.log: {{2019-12-17 23:31:14,749 [ACCEPTED LOGIN] for client : anonymous / 172.22.0.3.}} request.log: {{20191217233114\|23\|REQUEST\|172.22.0.3\|anonymous\|POST\|/api/search/aql\|HTTP/1.1\|403\|192}} *Note:* I assume that the anonymous user fails (even though enonymous has READ access and can download through the web interface), as JQL AQL is used here, and thus an actual user is needed?|(/)|(/)|(x) The SecretText credentials are shown, but it fails: HTTP/1.1 401 Unauthorized *Logs* access.log:{{2019-12-17 23:26:16,665 [DENIED LOGIN] for client : NA / 172.22.0.3.}} request.log:{{20191217232616\|36\|REQUEST\|172.22.0.3\|non_authenticated_user\|POST\|/api/search/aql\|HTTP/1.1\|401\|192}} *NOTE:* I have never before seen the 'non_authenticated_user', but maybe this is somewhat new? Anyways its seems that my API_KEY which was pasted as the SecretText credentials are not properly recognized. I have double checked that the API_KEY is pasted correctly.| Obviously I need to retest this with 6.12 version of Artifactory, but I doubt that is where the issue lies. [~ethorsa], I would suggest that you atleast look in the 'access.log' and 'request.log'. What I finds easiest, is to just {{tail -f ARTI_HOME/logs/*.log}}. Then add a few newlines to your terminal by pressing enter a few times, and then try your build. Assuming you don't have any other traffic to your Artifactory instance, then you will easily see anything that gets added to any of the log files. If that is not possible for you, then you would need to fetch them from the web interface, as previously mentioned. [~yahaviz], note that I tested your build, but couldn't get it to work. Maybee i derbed something?I added a new secret, in the global scope: * Secret: * ID: 'api-user_secret' * Description: 'api-user using API_KEY as secret text'
[JIRA] (JENKINS-60518) java.lang.AssertionError: InstanceIdentity is missing its singleton
Title: Message Title prabhu deivam created an issue Jenkins / JENKINS-60518 java.lang.AssertionError: InstanceIdentity is missing its singleton Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-12-18 00:25 Priority: Blocker Reporter: prabhu deivam Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Gro
[JIRA] (JENKINS-60518) java.lang.AssertionError: InstanceIdentity is missing its singleton
Title: Message Title prabhu deivam updated an issue Jenkins / JENKINS-60518 java.lang.AssertionError: InstanceIdentity is missing its singleton Change By: prabhu deivam Attachment: jenkins.err.log Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203615.1576628744000.10783.1576628880066%40Atlassian.JIRA.
[JIRA] (JENKINS-60518) java.lang.AssertionError: InstanceIdentity is missing its singleton
Title: Message Title prabhu deivam updated an issue Jenkins / JENKINS-60518 java.lang.AssertionError: InstanceIdentity is missing its singleton Change By: prabhu deivam java.lang.AssertionError: InstanceIdentity is missing its singleton at org.jenkinsci.main.modules.instance_identity.InstanceIdentity.get(InstanceIdentity.java:133) at org.jenkinsci.main.modules.instance_identity.InstanceIdentityRSAProvider.getKeyPair(InstanceIdentityRSAProvider.java:23) at jenkins.model.identity.InstanceIdentityProvider$KeyTypes.get(InstanceIdentityProvider.java:161) at jenkins.model.identity.InstanceIdentityProvider$KeyTypes.getKeyPair(InstanceIdentityProvider.java:210) at jenkins.model.identity.IdentityRootAction.getUrlName(IdentityRootAction.java:42) at jenkins.model.Jenkins.getDynamic(Jenkins.java:3663) at java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:710) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:372) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:734)Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:784) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:864) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:742) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:105) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:90) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.jav
[JIRA] (JENKINS-60518) java.lang.AssertionError: InstanceIdentity is missing its singleton
Title: Message Title prabhu deivam updated an issue Jenkins / JENKINS-60518 java.lang.AssertionError: InstanceIdentity is missing its singleton Error Log 2019-12-17 23:05:58.037+ [id=1] INFO hudson.WebAppMain#contextDestroyed: Shutting down a Jenkins instance that was still starting up2019-12-17 23:05:58.037+ [id=1] INFO hudson.WebAppMain#contextDestroyed: Shutting down a Jenkins instance that was still starting upjava.lang.Throwable: reason at hudson.WebAppMain.contextDestroyed(WebAppMain.java:388) at org.eclipse.jetty.server.handler.ContextHandler.callContextDestroyed(ContextHandler.java:965) at org.eclipse.jetty.servlet.ServletContextHandler.callContextDestroyed(ServletContextHandler.java:566) at org.eclipse.jetty.server.handler.ContextHandler.stopContext(ContextHandler.java:942) at org.eclipse.jetty.servlet.ServletContextHandler.stopContext(ServletContextHandler.java:376) at org.eclipse.jetty.webapp.WebAppContext.stopWebapp(WebAppContext.java:1503) at org.eclipse.jetty.webapp.WebAppContext.stopContext(WebAppContext.java:1467) at org.eclipse.jetty.server.handler.ContextHandler.doStop(ContextHandler.java:1009) at org.eclipse.jetty.servlet.ServletContextHandler.doStop(ServletContextHandler.java:288) at org.eclipse.jetty.webapp.WebAppContext.doStop(WebAppContext.java:569) at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) at org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:178) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:199) at org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:124) at org.eclipse.jetty.server.Server.doStop(Server.java:464) at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) at winstone.Launcher.shutdown(Launcher.java:313) at winstone.Launcher.(Launcher.java:200) at winstone.Launcher.main(Launcher.java:362) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at Main._main(Main.java:375) at Main.main(Main.java:151)Exception in thread "Jenkins initialization thread" 2019-12-17 23:05:58.037+ [id=1] INFO o.e.j.s.handler.ContextHandler#doStop: Stopped w.@16d844d{Jenkins v2.190.3,/,null,UNAVAILABLE} {D:\JENKINS_HOME\war} java.lang.NoClassDefFoundError: hudson/util/HudsonFailedToLoad at hudson.WebAppMain$3.run(WebAppMain.java:247)Caused by: java.lang.ClassNotFoundException: hudson.util.HudsonFailedToLoad at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:555) at java.lang.ClassLoader.loadClass(Unknown Source) ... 1 more2019-12-17 23:05:58.069+ [id=1] INFO winstone.Logger#logInternal: Jetty shutdown successfullyjava.io.IOException: Failed to start Jetty at winstone.Launcher.(Launcher.java:189) at winstone.Launcher.main(Launcher.java:362) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at Main._main(Main.java:375) at Main.main(Main.java:151)Caused by: java.io.IOException: Failed to bind to 0.0.0.0/0.0.0.0:8080 at org.ec
[JIRA] (JENKINS-60518) java.lang.AssertionError: InstanceIdentity is missing its singleton
Title: Message Title prabhu deivam updated an issue Jenkins / JENKINS-60518 java.lang.AssertionError: InstanceIdentity is missing its singleton Change By: prabhu deivam Attachment: jenkins.err.log Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203615.1576628744000.10786.1576629120066%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-37984 org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Change By: Liam Newman Attachment: Script_Splitting.groovy Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.174127.1473169024000.10864.1576629245781%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Liam Newman commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script efo plo Um, why would you do that? That will definitely limit the effectiveness of script splitting from JENKINS-56500. See the attached pipeline, here or over on #56500. If you're facing the same issue, then classes or no classes, it will still hit the limit. I also am unclear on what you mean with this comment. Could you give an example? Finally, I'm uploading an example of a pipeline helped by script splitting. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.174127.1473169024000.10862.1576629245709%40Atlassian.JIRA.
[JIRA] (JENKINS-60518) java.lang.AssertionError: InstanceIdentity is missing its singleton
Title: Message Title prabhu deivam updated an issue Jenkins / JENKINS-60518 java.lang.AssertionError: InstanceIdentity is missing its singleton Change By: prabhu deivam *Upgraded Jenkins from 2.121 to 2.190, but few days domain user password expired. Updated the security level to false and restarted the server, after that if I click on configure global security option it throws me the below error and also the existing jobs are missing.* java.lang.AssertionError: InstanceIdentity is missing its singleton at org.jenkinsci.main.modules.instance_identity.InstanceIdentity.get(InstanceIdentity.java:133) at org.jenkinsci.main.modules.instance_identity.InstanceIdentityRSAProvider.getKeyPair(InstanceIdentityRSAProvider.java:23) at jenkins.model.identity.InstanceIdentityProvider$KeyTypes.get(InstanceIdentityProvider.java:161) at jenkins.model.identity.InstanceIdentityProvider$KeyTypes.getKeyPair(InstanceIdentityProvider.java:210) at jenkins.model.identity.IdentityRootAction.getUrlName(IdentityRootAction.java:42) at jenkins.model.Jenkins.getDynamic(Jenkins.java:3663) at java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:710) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:372) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:734)Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:784) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:864) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:742) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:105) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:90) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at
[JIRA] (JENKINS-60518) java.lang.AssertionError: InstanceIdentity is missing its singleton
Title: Message Title prabhu deivam updated an issue Jenkins / JENKINS-60518 java.lang.AssertionError: InstanceIdentity is missing its singleton Change By: prabhu deivam *Upgraded Jenkins from 2.121 to 2.190 , but few days and everything was working fine till domain user password expired. Updated changed, Then stopped the server and updated the security level to false in config.xml file and restarted the server, after that if I click on configure global security option it throws me the below error and also the existing jobs are missing.* *OS: Windows**Open JDK: 11* java.lang.AssertionError: InstanceIdentity is missing its singleton at org.jenkinsci.main.modules.instance_identity.InstanceIdentity.get(InstanceIdentity.java:133) at org.jenkinsci.main.modules.instance_identity.InstanceIdentityRSAProvider.getKeyPair(InstanceIdentityRSAProvider.java:23) at jenkins.model.identity.InstanceIdentityProvider$KeyTypes.get(InstanceIdentityProvider.java:161) at jenkins.model.identity.InstanceIdentityProvider$KeyTypes.getKeyPair(InstanceIdentityProvider.java:210) at jenkins.model.identity.IdentityRootAction.getUrlName(IdentityRootAction.java:42) at jenkins.model.Jenkins.getDynamic(Jenkins.java:3663) at java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:710) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:372) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:734) Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:784) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:864) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:742) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:105) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hu
[JIRA] (JENKINS-59973) rtUpload / rtDownload fail with HTTP 401 / 403
Title: Message Title Jesper Reenberg commented on JENKINS-59973 Re: rtUpload / rtDownload fail with HTTP 401 / 403 Yahav Itzhak, not to sidetrack this bug report, but I managed to do a TCP dump of the requests, just in case it may clarify why the SecretText failed for me. I tried to repaste the API_KEY into the SecretText credential, just to make tripple sure, that I didn't make anything wrong. Using the SecretText: POST /artifactory/api/search/aql HTTP/1.1 Authorization: Bearer AKCp5e3VEwLXGKsjPvBX6nv4CgPtGeKDsV576c5xH29viZx7DNKZpvqfWiw1nUUiuEKaMuYBn Content-Length: 192 Content-Type: text/plain; charset=ISO-8859-1 Host: artifactory:8081 Connection: Keep-Alive User-Agent: ArtifactoryBuildClient/2.13.x-SNAPSHOT Accept-Encoding: gzip,deflate items.find({"repo": "generic-local","$or": [{"$and": [{"path": { "$match": "*"},"name": { "$match": "*"}}]}]}).include("name","repo","path","actual_md5","actual_sha1","size","type","property") --- HTTP/1.1 401 Unauthorized Server: Artifactory/6.16.0 X-Artifactory-Id: b2b51933cd264b43:10d5af30:16f15b57d38:-8000 WWW-Authenticate: Basic realm="Artifactory Realm" Content-Type: application/json;charset=ISO-8859-1 Content-Length: 171 Date: Wed, 18 Dec 2019 00:42:20 GMT { "errors" : [ { "status" : 401, "message" : "Bad props auth token: basictoken=AKCp5e3VEwLXGKsjPvBX6nv4CgPtGeKDsV576c5xH29viZx7DNKZpvqfWiw1nUUiuEKaMuYBn" } ] } Using API_KEY as user/pass: POST /artifactory/api/search/aql HTTP/1.1 Content-Length: 192 Content-Type: text/plain; charset=ISO-8859-1 Host: artifactory:8081 Connection: Keep-Alive User-Agent: ArtifactoryBuildClient/2.13.x-SNAPSHOT Accept-Encoding: gzip,deflate Authorization: Basic YXBpLXVzZXI6QUtDcDVlM1ZFd0xYR0tzalB2Qlg2bnY0Q2dQdEdlS0RzVjU3NmM1eEgyOXZpWng3RE5LWnB2cWZXaXcxblVVaXVFS2FNdVlCbg== items.find({"repo": "generic-local","$or": [{"$and": [{"path": { "$match": "*"},"name": { "$match": "*"}}]}]}).include("name","repo","path","actual_md5","actual_sha1","size","type","property") --- HTTP/1.1 200 OK Server: Artifactory/6.16.0 X-Artifactory-Id: b2b51933cd264b43:10d5af30:16f15b57d38:-8000 Content-Type: application/json Transfer-Encoding: chunked Date: Wed, 18 Dec 2019 00:42:31 GMT 12e { "results" : [ { "repo" : "generic-local", "path" : ".", "name" : "hello", "type" : "file", "size" : 14, "actual_md5" : "bea8252ff4e80f41719ea13cdf007273", "actual_sha1" : "60fde9c2310b0d4cad4dab8d126b04387efba289" } ], "range" : { "start_pos" : 0, "end_pos" : 1, "total" : 1 } } Obviously, using user/pass, is the same as user/API_KEY, using the basic auth, except my super secret password POST /artifactory/api/search/aql HTTP/1.1 Content-Length: 192 Content-Type: text/plain; charset=ISO-8859-1 Host: artifactory:8081 Connection: Keep-Alive User-Agent: ArtifactoryBuildClient/2.13.x-SNAPSHOT Accept-Encoding: gzip,deflate Authorization: Basic dXNlcjpwYXNzd29yZA==
[JIRA] (JENKINS-60515) Jenkins v2.107.3 job 保存触发异常
Title: Message Title Ian Williams commented on JENKINS-60515 Re: Jenkins v2.107.3 job 保存触发异常 Could you post the error as TEXT rather than an image (I have added an image to text temporarily) ? Could you also elaborate on the description of the problem and what was occurring when error appeared? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203608.1576578047000.10951.1576630680395%40Atlassian.JIRA.
[JIRA] (JENKINS-60515) Jenkins v2.107.3 job 保存触发异常
Title: Message Title Ian Williams updated an issue Jenkins / JENKINS-60515 Jenkins v2.107.3 job 保存触发异常 Change By: Ian Williams jenkins v2.107.3 config Build after other projects are built java.lang.NullPointerException at jenkins.triggers.ReverseBuildTrigger.stop (ReverseBuildTrigger.java:196) at hudson.model.AbstractProject.submit (AbstractProject.java:1805) at hudson.model.Project.submit (Project.java:225) at hudson.model.Job.doConfigSubmit (Job.java:1354) at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:772) at java.lang.invoke.MethodHandle.invokeWithArguinents (MethodHandle.java:ô25) at org.kohsuke.stapler.Function$MethodFunction.invoke (Function.java:343) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke (RequirePOST.java:77) at org.kohsuke.stapler.PrelnvokelnterceptedFunction.invoke (PrelnvokelnterceptedFunction.java:20) at org.kohsuke.stapler.Function.bindAndlnvoke (Function.java:184) at org.kohsuke.stapler.Function.bindAndlnvokeAndServeResponse (Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.j aya :129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch (NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.trylnvoke (Stapler.jaya:715) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59973) rtUpload / rtDownload fail with HTTP 401 / 403
Title: Message Title Jesper Reenberg edited a comment on JENKINS-59973 Re: rtUpload / rtDownload fail with HTTP 401 / 403 [~yahaviz], not to sidetrack this bug report, but I managed to do a TCP dump of the requests, just in case it may clarify why the SecretText failed for me. I tried to repaste the API_KEY into the SecretText credential, just to make tripple sure, that I didn't make anything wrong. Using the SecretText:{code :java }POST /artifactory/api/search/aql HTTP/1.1Authorization: Bearer AKCp5e3VEwLXGKsjPvBX6nv4CgPtGeKDsV576c5xH29viZx7DNKZpvqfWiw1nUUiuEKaMuYBnContent-Length: 192Content-Type: text/plain; charset=ISO-8859-1Host: artifactory:8081Connection: Keep-AliveUser-Agent: ArtifactoryBuildClient/2.13.x-SNAPSHOTAccept-Encoding: gzip,deflateitems.find({"repo": "generic-local","$or": [{"$and": [{"path": { "$match": "*"},"name": { "$match": "*"}}]}]}).include("name","repo","path","actual_md5","actual_sha1","size","type","property")---HTTP/1.1 401 UnauthorizedServer: Artifactory/6.16.0X-Artifactory-Id: b2b51933cd264b43:10d5af30:16f15b57d38:-8000WWW-Authenticate: Basic realm="Artifactory Realm"Content-Type: application/json;charset=ISO-8859-1Content-Length: 171Date: Wed, 18 Dec 2019 00:42:20 GMT{ "errors" : [ {"status" : 401,"message" : "Bad props auth token: basictoken=AKCp5e3VEwLXGKsjPvBX6nv4CgPtGeKDsV576c5xH29viZx7DNKZpvqfWiw1nUUiuEKaMuYBn" } ]} {code} Using API_KEY as user/pass:{code :java }POST /artifactory/api/search/aql HTTP/1.1Content-Length: 192Content-Type: text/plain; charset=ISO-8859-1Host: artifactory:8081Connection: Keep-AliveUser-Agent: ArtifactoryBuildClient/2.13.x-SNAPSHOTAccept-Encoding: gzip,deflateAuthorization: Basic YXBpLXVzZXI6QUtDcDVlM1ZFd0xYR0tzalB2Qlg2bnY0Q2dQdEdlS0RzVjU3NmM1eEgyOXZpWng3RE5LWnB2cWZXaXcxblVVaXVFS2FNdVlCbg==items.find({"repo": "generic-local","$or": [{"$and": [{"path": { "$match": "*"},"name": { "$match": "*"}}]}]}).include("name","repo","path","actual_md5","actual_sha1","size","type","property")---HTTP/1.1 200 OKServer: Artifactory/6.16.0X-Artifactory-Id: b2b51933cd264b43:10d5af30:16f15b57d38:-8000Content-Type: application/jsonTransfer-Encoding: chunkedDate: Wed, 18 Dec 2019 00:42:31 GMT 12e{"results" : [ { "repo" : "generic-local", "path" : " . ", "name" : "hello", "type" : "file", "size" : 14, "actual_md5" : "bea8252ff4e80f41719ea13cdf007273", "actual_sha1" : "60fde9c2310b0d4cad4dab8d126b04387efba289"} ],"range" : .. { "start_pos" : 0, "end_pos" : 1, "total" : 1}} { code} Obviously, using user/pass, is the same as user/API_KEY, using the basic auth, except my super secret password :){code :java }POST /artifactory/api/search/aql HTTP/1.1Content-Length: 192Content-Type: text/plain; charset=ISO-8859-1Host: artifactory:8081Connection: Keep-AliveUser-Agent: ArtifactoryBuildClient/2.13.x-SNAPSHOTAccept-Encoding: gzip,deflateAuthorization: Basic dXNlcjpwYXNzd29yZA==items.find({"repo": "generic-local","$or": [{"$and": [{"path": { "$match": "*"},"name": { "$match": "*"}}]}]}).include("name","repo","path","actual_md5","actual_sha1","size","type","property")---HTTP/1.1 200 OKServer: Artifactory/6.16.0X-Artifactory-Id: b2b51933cd264b43:10d5af30:16f15b57d38:-8000Content-Type: application/jsonTransfer-Encoding: chunkedDate: Wed, 18 Dec 2019 00:42:53 GMT ... {code}
[JIRA] (JENKINS-60277) NullPointerExceptionat EMEJenkinsPlugin.EME_SCM(EME_SCM.java:250)
Title: Message Title Nutan Sawant commented on JENKINS-60277 Re: NullPointerExceptionat EMEJenkinsPlugin.EME_SCM(EME_SCM.java:250) This issue seems resolved itself. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203267.1574732369000.10957.1576632660063%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Brian J Murrell commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Liam Newman I think the point being made, and demonstrated with JenkinsCodeTooLarge.groovy is that even a pipeline that contains nothing except pipeline structure and calls to library functions can blow the limit on size. At some point, as the above pipeline demonstrates, you have factored out as much as you can and still blow the limit. The limit is the problem here, not how much of a pipeline has been factored away in to a library. The latter is just a band-aid, postponing of the inevitable and frankly a wasted investment if you are going to have to end up scrapping the whole thing at some point and moving to an entirely new solution that won't have such inevitable fatal limits. Hopefully the newly available matrix feature will help some people out, but there will still be people with big pipelines that are un-matrixable. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.174127.1473169024000.10959.1576632721730%40Atlassian.JIRA.
[JIRA] (JENKINS-60277) NullPointerExceptionat EMEJenkinsPlugin.EME_SCM(EME_SCM.java:250)
Title: Message Title Nutan Sawant closed an issue as Done This issue seems resolved by itself , as stopped facing this now without any changes . Jenkins / JENKINS-60277 NullPointerExceptionat EMEJenkinsPlugin.EME_SCM(EME_SCM.java:250) Change By: Nutan Sawant Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-37984 org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Change By: Liam Newman Attachment: Script_Splittingx10.groovy Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.174127.1473169024000.11044.1576634162218%40Atlassian.JIRA.
[JIRA] (JENKINS-59865) Bogus Scala Compiler warning about missing files after test failure in sbt
Title: Message Title Benjamin Cross assigned an issue to Unassigned Jenkins / JENKINS-59865 Bogus Scala Compiler warning about missing files after test failure in sbt Change By: Benjamin Cross Assignee: Benjamin Cross Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202604.1571658262000.11120.1576634700263%40Atlassian.JIRA.
[JIRA] (JENKINS-60519) Move Plugin documentation to github
Title: Message Title Ioannis Moutsatsos created an issue Jenkins / JENKINS-60519 Move Plugin documentation to github Issue Type: Improvement Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 2019-12-18 02:23 Priority: Minor Reporter: Ioannis Moutsatsos See: https://jenkins.io/blog/2019/10/21/plugin-docs-on-github/ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Liam Newman commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Brian J Murrell The latter is just a band-aid, postponing of the inevitable and frankly a wasted investment if you are going to have to end up scrapping the whole thing at some point and moving to an entirely new solution that won't have such inevitable fatal limits. I'm not understanding your statement here. There is no way to make there not be some point at which this limit is hit - it is part of the Java class file binary format. You can hit this while writing any Java program. You don't hit it because of the structure of Java encourages code practices that make it unlikely. The Script_Splitting.groovy shows that script splitting addresses this issue for Declarative Pipelines that don't use variables (which is best practice). It is effectively the same as JenkinsCodeTooLarge.groovy but without the variable declaration. Is there still a point at which you may hit the size limit? Yes, however, it is over 1000 stages (that's where I stopped), and even higher for matrix-generated stages. At which point hitting the issue isn't "inevitable" but rather highly unlikely. How big of a pipeline are you trying to run? If what you mean to say is "Well, I use variables so this doesn't help me", I understand your frustration. If you have bandwidth do contribute a solution, I'd love to chat with you about it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60520) Unable to see Failure Scan Options
Title: Message Title Gajanan Mahajan created an issue Jenkins / JENKINS-60520 Unable to see Failure Scan Options Issue Type: Bug Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2019-12-18 05:16 Priority: Minor Reporter: Gajanan Mahajan I've build failure analyzer plugin 1.24.1 installed but I cannot see - 'Failure Scan Options' in Jenkins. I'm logged in with admin user. Is there anything I need to do that option to appear? Or it this a bug with 1.24.1 version? Add Comment
[JIRA] (JENKINS-60513) Jenkins core 2.209: Warnings concerning AtomicInteger and class-filter
Title: Message Title Reinhold Füreder commented on JENKINS-60513 Re: Jenkins core 2.209: Warnings concerning AtomicInteger and class-filter IMHO caused by https://github.com/jenkinsci/jenkins/pull/4337 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203605.1576562327000.11203.1576646940051%40Atlassian.JIRA.
[JIRA] (JENKINS-60513) Jenkins core 2.209: Warnings concerning AtomicInteger and class-filter
Title: Message Title Reinhold Füreder commented on JENKINS-60513 Re: Jenkins core 2.209: Warnings concerning AtomicInteger and class-filter The list of "hudson.plugins.git.GitSCM$DescriptorImpl" entries in "Manage Old Data" keeps growing; interestingly there is still only one for "hudson.scm.SubversionSCM$DescriptorImpl"... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203605.1576562327000.11204.1576647240133%40Atlassian.JIRA.