[JIRA] (JENKINS-58878) withCredentials hangs
Title: Message Title Reinhold Füreder commented on JENKINS-58878 Re: withCredentials hangs Devin Nusbaum By any chance could this fix also solve my sporadically experienced hanging pipelines in withDockerRegistry/withDockerServer context (with executor on Jenkins master *cough*)? Example thread dump: at DSL.withDockerRegistry(not currently scheduled, or running blocks) at org.jenkinsci.plugins.docker.workflow.Docker.withRegistry(Docker.groovy:40) at DSL.withEnv(Native Method) at org.jenkinsci.plugins.docker.workflow.Docker.withRegistry(Docker.groovy:39) at org.jenkinsci.plugins.docker.workflow.Docker.node(Docker.groovy:66) at org.jenkinsci.plugins.docker.workflow.Docker.withRegistry(Docker.groovy:38) at com.acme.php.phpstorm.OfflineInspection.execute(OfflineInspection.groovy:59) at acme.executePhpStormInspections(acme.groovy:256) at WorkflowScript.run(WorkflowScript:101) ... Please note, however, that it appeared as if the single or first (?) step inside such withDockerRegistry/withDockerServer contexts may sometimes actually be still executed... 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 je
[JIRA] (JENKINS-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title
Reinhold Füreder commented on JENKINS-34256
Re: Preparing Jenkins For Shutdown Hangs Running Pipelines
Devin Nusbaum Thanks, I think that ("The main change in my PR is that today, if you cancel shutdown after clicking "Prepare for shutdown", the Pipeline builds stay paused. You have to manually pause and unpause the builds to get them to resume or restart Jenkins. After my PR, canceling shutdown will unpause the builds and resume them automatically.") should actually really address one of my (many months ago) experienced problems in this concern! (Because I have a groovy init hook script that always configures Jenkins to start in so-called quiet mode...) As other users more or less diplomatically commented, there is still room for related important enhancements: maybe these can be collected and discussed and prioritised and addressed in another future sprint/story? (And I think Jenkins is still in massive use nowadays and hopefully not dead for a long time...)
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.169794.1460663849000.1208.1575531361659%40Atlassian.JIRA.
[JIRA] (JENKINS-60358) Root=null value in Template is overridden, failing sync
Title: Message Title Guy Catz commented on JENKINS-60358 Re: Root=null value in Template is overridden, failing sync Hi Karl, I'm Guy, working Shai Shapira on that. To answer your question "why your build systems are using different drives for the Perforce data". Our Windows build is comprised of a large amount of very small files (10^5). To make the cleanup faster after a build, we simply format that disk. Moreover, a big chunk of the sources (~ 30GB) are SDKs that are rarely being changed. Instead of forced-syncing it on every build, we keep it in a separated drive, (non-forced) sync it and logically combined both drive into a one partition. For that, we keep the root null. The job below is a test for that matter. Could u explain more about the workaround? How do we achieve that while still using the p4 plugin? As a solution, can you introduce a checkbox "override root path" (default checked)? Thanks 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.203377.1575437377000.1205.1575526320175%40Atlassian.JIRA.
[JIRA] (JENKINS-60358) Root=null value in Template is overridden, failing sync
Title: Message Title Guy Catz updated an issue Jenkins / JENKINS-60358 Root=null value in Template is overridden, failing sync Change By: Guy Catz Attachment: image-2019-12-05-07-54-57-196.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.203377.1575437377000.1202.1575525420422%40Atlassian.JIRA.
[JIRA] (JENKINS-60358) Root=null value in Template is overridden, failing sync
Title: Message Title Guy Catz updated an issue Jenkins / JENKINS-60358 Root=null value in Template is overridden, failing sync Change By: Guy Catz Attachment: image-2019-12-05-07-54-02-643.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.203377.1575437377000.1199.1575525360289%40Atlassian.JIRA.
[JIRA] (JENKINS-60358) Root=null value in Template is overridden, failing sync
Title: Message Title Guy Catz updated an issue Jenkins / JENKINS-60358 Root=null value in Template is overridden, failing sync Change By: Guy Catz Attachment: image-2019-12-05-07-53-02-250.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.203377.1575437377000.1196.1575525300315%40Atlassian.JIRA.
[JIRA] (JENKINS-60372) Pipeline added a new release plug-in, and added an intermediate state based on the input audit plug-in
Title: Message Title zhai junqi closed an issue as Won't Do Jenkins / JENKINS-60372 Pipeline added a new release plug-in, and added an intermediate state based on the input audit plug-in Change By: zhai junqi Status: Open Closed Resolution: Won't Do 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.203418.1575518177000.1186.1575518640311%40Atlassian.JIRA.
[JIRA] (JENKINS-60372) Pipeline added a new release plug-in, and added an intermediate state based on the input audit plug-in
Title: Message Title zhai junqi created an issue Jenkins / JENKINS-60372 Pipeline added a new release plug-in, and added an intermediate state based on the input audit plug-in Issue Type: Improvement Assignee: Unassigned Components: jira-plugin, jira-steps-plugin Created: 2019-12-05 03:56 Environment: java:1.7+,pipeline-input-step-plugin:2.8, Priority: Major Reporter: zhai junqi Using the design idea of pipeline audit plug-in, a new release plug-in is developed, which has an intermediate state more than the audit plug-in. The third-party interface can be configured globally through Jenkins to realize asynchronous interface and interface callback after audit. Add Comment
[JIRA] (JENKINS-59492) False positive CPS mismatch warning when calling a method pointer
Title: Message Title Yuxiang Zhu commented on JENKINS-59492 Re: False positive CPS mismatch warning when calling a method pointer We came across the exact same warning when calling a method via a pointer. The method is called correctly and works fine, apparently this is a false positive warning. Pointers are assigned with https://github.com/openshift/aos-cd-jobs/pull/2053/files#diff-b89f72b7074288d1245c7ece87537d33R13-R19 and called at https://github.com/openshift/aos-cd-jobs/pull/2053/files#diff-b89f72b7074288d1245c7ece87537d33R111 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.202107.1569256304000.1184.1575517260619%40Atlassian.JIRA.
[JIRA] (JENKINS-55865) Ability to add additional tags
Title: Message Title Jie Shen resolved as Done Jenkins / JENKINS-55865 Ability to add additional tags Change By: Jie Shen Status: Open Resolved Resolution: Done Released As: 1.2.0 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.197262.1548850714000.1181.1575515580347%40Atlassian.JIRA.
[JIRA] (JENKINS-55865) Ability to add additional tags
Title: Message Title Jie Shen commented on JENKINS-55865 Re: Ability to add additional tags Viktor Jozsa in the system configure, you can find the "custom tag" in the "Azure Profile Configuration" section. You just need add tags there. For JCasC, sample at https://github.com/jenkinsci/azure-vm-agents-plugin/blob/de68b3c62b06904a83c1b47a79e13377d5188508/src/test/resources/com/microsoft/azure/vmagent/test/jcasc/advanced.yaml#L6-L8. 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.197262.1548850714000.1178.1575515520175%40Atlassian.JIRA.
[JIRA] (JENKINS-60360) error occurs when 'git config --get submodule.**.url
Title: Message Title juyeon lee commented on JENKINS-60360 Re: error occurs when 'git config --get submodule.**.url Define a freestyle job that clones in-house github repository. Add the checkout option to recursively update submodules Run the jenkins job That's all. it's not a problem of source code in github repository. Because it works in Git-Bash. 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.203381.1575447656000.1176.1575512040322%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title Amila Gunathilake commented on JENKINS-59308 Re: Cobertura Code coverage all reports are showing in similar hi Federico Pellegrin it's okay no worries. And one thing do you guys have any Tutorial or any Doc with information to operate these reports and how to read these reports ? Thanks again. 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.201856.1568169015000.1174.1575511200365%40Atlassian.JIRA.
[JIRA] (JENKINS-60353) Non-mergable Pull-request Contents Get into GH Cache with False-Positive 404
Title: Message Title Karl Shultz edited a comment on JENKINS-60353 Re: Non-mergable Pull-request Contents Get into GH Cache with False-Positive 404 [~vkuklinatjoom], thanks for reporting this, and thanks for the recreate steps. I'll take a shot at this recreate in the morning. If this is the bug I'm hoping it is, this has been showing itself for a long time, and has been super annoying to try and recreate. I'm going to see if this will show itself on versions of GHBS older than 2.5.0 as well (see [JENKINS-43194|https://issues . jenkins-ci.org/browse/JENKINS-43194]). I'm pretty sure we've been chasing this since well before that release. 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.203370.1575386738000.1170.1575509460242%40Atlassian.JIRA.
[JIRA] (JENKINS-60353) Non-mergable Pull-request Contents Get into GH Cache with False-Positive 404
Title: Message Title Karl Shultz commented on JENKINS-60353 Re: Non-mergable Pull-request Contents Get into GH Cache with False-Positive 404 Vladimir Kuklin, thanks for reporting this, and thanks for the recreate steps. I'll take a shot at this recreate in the morning. If this is the bug I'm hoping it is, this has been showing itself for a long time, and has been super annoying to try and recreate. I'm going to see if this will show itself on versions of GHBS older than 2.5.0 as well. I'm pretty sure we've been chasing this since well before that release. 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.203370.1575386738000.1168.1575509400201%40Atlassian.JIRA.
[JIRA] (JENKINS-6334) Support for displaying changesets in submodule updates
Title: Message Title Tim Black edited a comment on JENKINS-6334 Re: Support for displaying changesets in submodule updates +Update+I have read [~markewaite]'s comment above and see that there are no PRs related to this issue. I'd be happy to contribute as this is a high value, low-hanging fruit in my opinion.However, I am not a java developer, and from Mark's comments this task is largely that of backfilling a void of automated tests covering submodules, to justify any _consideration_ of a PR that touches submodules. This is of course most unfortunate.I wonder if [~markewaite] still feels this way, however, since [several of the recent releases show submodule changes|[https://github.com/jenkinsci/git-plugin/releases] . | [ https://github.com/jenkinsci/git-plugin/releases] ] . +Original Comment+I have updated to [Jenkins ver. 2.190.3|https://jenkins.io/], am using Git plugin 4.0.0, Git Client Plugin 3.0.0, and have updated my multibranch pipeline job config to recursively update submodules. In the resulting build "changes" it prints the name of the changed submodule, but does not include the changelog for it. I would like to try [~eprstov]'s solution, but I do not see an "sbm" branch here: [https://github.com/jenkinsci/git-plugin/branches]. I'm guessing it's just gone as this is a year later, and my best bet is to use the 4.0.0 tag.Has anyone else made any progress to getting a PR submitted for [~eprstov] patch (wherever it is)? Thanks. 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 gr
[JIRA] (JENKINS-6334) Support for displaying changesets in submodule updates
Title: Message Title Tim Black edited a comment on JENKINS-6334 Re: Support for displaying changesets in submodule updates +Update+I have read [~markewaite]'s comment above and see that there are no PRs related to this issue. I'd be happy to contribute as this is a high value, low-hanging fruit in my opinion.However, I am not a java developer, and from Mark's comments this task is largely that of backfilling a void of automated tests covering submodules, to justify any _consideration_ of a PR that touches submodules. This is of course most unfortunate.I wonder if [~markewaite] still feels this way, however, since [several of the recent releases show submodule changes|[https://github.com/jenkinsci/git-plugin/releases] ] . |https://github.com/jenkinsci/git-plugin/releases] +Original Comment+I have updated to [Jenkins ver. 2.190.3|https://jenkins.io/], am using Git plugin 4.0.0, Git Client Plugin 3.0.0, and have updated my multibranch pipeline job config to recursively update submodules. In the resulting build "changes" it prints the name of the changed submodule, but does not include the changelog for it. I would like to try [~eprstov]'s solution, but I do not see an "sbm" branch here: [https://github.com/jenkinsci/git-plugin/branches]. I'm guessing it's just gone as this is a year later, and my best bet is to use the 4.0.0 tag.Has anyone else made any progress to getting a PR submitted for [~eprstov] patch (wherever it is)? Thanks. 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 a
[JIRA] (JENKINS-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title Friedrich Clausen commented on JENKINS-34256 Re: Preparing Jenkins For Shutdown Hangs Running Pipelines As mentioned above, in the modern world of transient agents such as Kubernetes pods, this is quite painful. Transient agents are likely to become more prevelant. 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.169794.1460663849000.1040.1575507121314%40Atlassian.JIRA.
[JIRA] (JENKINS-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title Carlton Brown commented on JENKINS-34256 Re: Preparing Jenkins For Shutdown Hangs Running Pipelines 4 years old serious usability issue, hasn't been fixed, won't be fixed because nobody cares. Jenkins is dead, use something else. 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.169794.1460663849000.973.1575505561367%40Atlassian.JIRA.
[JIRA] (JENKINS-6334) Support for displaying changesets in submodule updates
Title: Message Title Tim Black edited a comment on JENKINS-6334 Re: Support for displaying changesets in submodule updates +Update+ I have read [~markewaite]'s comment above and see that there are no PRs related to this issue. I'd be happy to contribute as this is a high value, low-hanging fruit in my opinion.However, I am not a java developer, and from Mark's comments this task is largely that of backfilling a void of automated tests covering submodules, to justify any _consideration_ of a PR that touches submodules. This is of course most unfortunate.I wonder if [~markewaite] still feels this way, however, since [several of the recent releases show submodule changes|[https://github.com/jenkinsci/git-plugin/releases]].+Original Comment+I have updated to [Jenkins ver. 2.190.3|https://jenkins.io/], am using Git plugin 4.0.0, Git Client Plugin 3.0.0, and have updated my multibranch pipeline job config to recursively update submodules. In the resulting build "changes" it prints the name of the changed submodule, but does not include the changelog for it. I would like to try Yakov [~eprstov] 's solution, but I do not see an "sbm" branch here: [https://github.com/jenkinsci/git-plugin/branches]. What reference do I need to fetch to build 'm guessing it's just gone as this ? is a year later, and my best bet is to use the 4.0.0 tag. Has anyone else made any progress to getting a PR submitted for [~eprstov] patch (wherever it is)? Thanks. 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
[JIRA] (JENKINS-38276) Increase size of text area for pipeline script code
Title: Message Title Matt Dee commented on JENKINS-38276 Re: Increase size of text area for pipeline script code Fixing this text box would really help productivity. Another user here hoping to see this delivered. 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.174439.1474032648000.909.1575501660744%40Atlassian.JIRA.
[JIRA] (JENKINS-6334) Support for displaying changesets in submodule updates
Title: Message Title Tim Black commented on JENKINS-6334 Re: Support for displaying changesets in submodule updates I have updated to Jenkins ver. 2.190.3, am using Git plugin 4.0.0, Git Client Plugin 3.0.0, and have updated my multibranch pipeline job config to recursively update submodules. In the resulting build "changes" it prints the name of the changed submodule, but does not include the changelog for it. I would like to try Yakov's solution, but I do not see an "sbm" branch here: https://github.com/jenkinsci/git-plugin/branches. What reference do I need to fetch to build this? Has anyone else made any progress to getting a PR submitted for Yakov's patch (wherever it is)? Thanks. 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.136429.1271845294000.876.1575501302188%40Atlassian.JIRA.
[JIRA] (JENKINS-6334) Support for displaying changesets in submodule updates
Title: Message Title Tim Black edited a comment on JENKINS-6334 Re: Support for displaying changesets in submodule updates I have updated to [Jenkins ver. 2.190.3|https://jenkins.io/], am using Git plugin 4.0.0, Git Client Plugin 3.0.0, and have updated my multibranch pipeline job config to recursively update submodules. In the resulting build "changes" it prints the name of the changed submodule, but does not include the changelog for it. I would like to try Yakov's solution, but I do not see an "sbm" branch here: [https://github.com/jenkinsci/git-plugin/branches]. What reference do I need to fetch to build this?Has anyone else made any progress to getting a PR submitted for Yakov's [~eprstov] patch (wherever it is)? Thanks. 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.136429.1271845294000.878.1575501302324%40Atlassian.JIRA.
[JIRA] (JENKINS-60354) Updated pipeline build step does not work with retry, catchError, or warnError
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-60354 Updated pipeline build step does not work with retry, catchError, or warnError Change By: Devin Nusbaum Summary: Updated pipeline build step does not work with retry , catchError, or warnError 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.203371.1575392042000.845.1575498180450%40Atlassian.JIRA.
[JIRA] (JENKINS-60354) Updated pipeline build step does not work with retry
Title: Message Title Devin Nusbaum commented on JENKINS-60354 Re: Updated pipeline build step does not work with retry Jesse Glick Noted in this comment that the easiest short-term fix is probably to make retry only rethrow FlowInterruptedException when there is at least one CauseOfInterruption. I did a quick investigation and I think WorkflowRun.doTerm would need to start setting a CauseOfInterruption, but didn't see any other uses that would need to be changed. He also noted that another possible fix would be to add a flag to FlowInterrupted exception to indicate actual build interruptions as opposed to otherwise-normal exceptions with a result, and have steps like retry look at that flag to decide whether to rethrow the exception. I think that would be easier than introducing new exception types as in my original idea, and a bit more robust than relying on the presence or absence of a CauseOfInterruption, although we would need to update things like the input step and have them set that flag, so it would require a bit more effort. I am also noting that catchError and warnError have the same problem as retry with the new version of build, and will ignore any errors thrown by it by default. 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.203371.1575392042000.843.1575498180238%40Atlassian
[JIRA] (JENKINS-54154) [Custom Tools Plugin] - JCasC compatibility
Title: Message Title René Scheibe commented on JENKINS-54154 Re: [Custom Tools Plugin] - JCasC compatibility The still existing issue will be handled in JENKINS-60045. 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.194783.1539929296000.841.1575496560190%40Atlassian.JIRA.
[JIRA] (JENKINS-54154) [Custom Tools Plugin] - JCasC compatibility
Title: Message Title René Scheibe resolved as Done Jenkins / JENKINS-54154 [Custom Tools Plugin] - JCasC compatibility Change By: René Scheibe Status: Reopened Resolved 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 view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194783.1539929296000.835.1575496500352%40Atlassian.JIRA.
[JIRA] (JENKINS-60103) Cannot send junit results to Octane, because there is no permission on slave to create log folder
Title: Message Title Radi Berkovich commented on JENKINS-60103 Re: Cannot send junit results to Octane, because there is no permission on slave to create log folder any updates? 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.202949.1573206476000.833.1575496200379%40Atlassian.JIRA.
[JIRA] (JENKINS-59754) Jenkins Micro Focus Application Automation Tools Plugin losing connection with Octane after running pipelines
Title: Message Title Radi Berkovich commented on JENKINS-59754 Re: Jenkins Micro Focus Application Automation Tools Plugin losing connection with Octane after running pipelines any updates? 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.202477.1570821116000.831.1575496200347%40Atlassian.JIRA.
[JIRA] (JENKINS-60371) Azure App Service plugin deploy via docker error
Title: Message Title Tim Jacomb commented on JENKINS-60371 Re: Azure App Service plugin deploy via docker error Moved from Jenkins infra project 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.201594.1567194345000.824.1575493620128%40Atlassian.JIRA.
[JIRA] (JENKINS-60371) Azure App Service plugin deploy via docker error
Title: Message Title Tim Jacomb assigned an issue to Jie Shen Jenkins / JENKINS-60371 Azure App Service plugin deploy via docker error Change By: Tim Jacomb Assignee: Jie Shen 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.201594.1567194345000.821.1575493560365%40Atlassian.JIRA.
[JIRA] (JENKINS-60371) Azure App Service plugin deploy via docker error
Title: Message Title Tim Jacomb moved an issue Jenkins / JENKINS-60371 Azure App Service plugin deploy via docker error Change By: Tim Jacomb Project: Infrastructure Jenkins Key: INFRA JENKINS - 2247 60371 Workflow: classic default workflow JNJira + In-Review Component/s: azure-app-service-plugin Component/s: azure Component/s: docker Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Devin Nusbaum commented on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile Marky Jackson Ok, if you end up with any additional information from LAUNCH_DIAGNOSTICS, or if you can figure out whether 1.30 has the same problem, feel free to add the info here. I am going to close the ticket. 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.203277.1574777832000.812.1575492900821%40Atlassian.JIRA.
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Devin Nusbaum closed an issue as Incomplete Jenkins / JENKINS-60286 durable-task v1.33 fails with agent Dockerfile Change By: Devin Nusbaum Status: Open Closed Resolution: Incomplete 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.203277.1574777832000.814.1575492901009%40Atlassian.JIRA.
[JIRA] (JENKINS-2048) java.io.FileNotFoundException: /boot.log (Permission denied)
Title: Message Title Ulli Hafner closed an issue as Won't Do I think we safely can close this bug as the affected plugin is not supported anymore. Jenkins / JENKINS-2048 java.io.FileNotFoundException: /boot.log (Permission denied) Change By: Ulli Hafner Status: Open Closed Resolution: Won't Do 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-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Marky Jackson commented on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile Devin Nusbaum at this point it appears someone upgraded a plugin which in turn upgraded 1.29 to 1.33 and that broke all the dependancies. I moved everything back to native docker calls as Jesse Glick alluded to 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.203277.1574777832000.795.1575491340151%40Atlassian.JIRA.
[JIRA] (JENKINS-60354) Updated pipeline build step does not work with retry
Title: Message Title Devin Nusbaum commented on JENKINS-60354 Re: Updated pipeline build step does not work with retry This is caused by JENKINS-49073, and difficult to fix without breaking JENKINS-44379 (unless we just revert JENKINS-49073). The cause is that Pipeline Build Step 2.10 now throws FlowInterruptedException when the build fails instead of AbortException so that it can track the result. retry ignores FlowInterruptedException for reasons discussed in JENKINS-44379 (aborting the build via an input step or the sidebar of the build should bypass retry) I'm not really sure how to fix this. I think FlowInterruptedException is overloaded with too many meanings at this point to fix it directly. One approach would be to factor out a ResultCarryingException interface, have FlowInterruptedException and some new FooException implement that interface, and then go through and switch everything that currently just uses FlowInterruptedException for a result to use ResultCarryingException when inspecting exceptions and FooException when creating them, and only use FlowInterruptedException when we only want to capture actual Pipeline interruption. 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.203371.1575392042000.793.1575491100169%40Atlassian.JIRA.
[JIRA] (JENKINS-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title Devin Nusbaum commented on JENKINS-34256 Re: Preparing Jenkins For Shutdown Hangs Running Pipelines Ferruccio Bongianni I think the intention of the message is something like how you might use wall on a multi-user Unix system, in the sense that the message is a way for admins to signify to anyone that might be using Jenkins that it will be shut down at some point (just guessing, I did not add the feature). The admin still has to actually initiate the shutdown themselves, so for admins, I agree, the message is confusing. 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.169794.1460663849000.726.1575490981334%40Atlassian.JIRA.
[JIRA] (JENKINS-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title Alex Varju commented on JENKINS-34256 Re: Preparing Jenkins For Shutdown Hangs Running Pipelines In the modern world of transient agents (e.g. Kubernetes pods) that won't exist after restart, this approach of pausing the pipeline is painful. It would sure be nice if there was a way to allow current jobs to finish while not allowing queued jobs to be started. 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.169794.1460663849000.660.1575490921480%40Atlassian.JIRA.
[JIRA] (JENKINS-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title Ferruccio Bongianni commented on JENKINS-34256 Re: Preparing Jenkins For Shutdown Hangs Running Pipelines Hi Devin, thanks for your prompt reply. It is very confusing indeed. Shouldn't the message in red saying something different than 'Jenkins is going to shut down' if that is not true (because it actually does not shut down at all, ever). Also, I haven't tried it right now, but I'm fairly confident this is exactly what happens when you update a plugin that needs Jenkins to be restarted. if you've got pipelines running it will never do until you kill those 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.169794.1460663849000.593.1575490801454%40Atlassian.JIRA.
[JIRA] (JENKINS-47007) Excessive CPU usage on pipeline "Stage View"
Title: Message Title Matt Dee commented on JENKINS-47007 Re: Excessive CPU usage on pipeline "Stage View" It's 2019, Jenkins is on 2.190.x and Stage View is still rocketing CPU usage after being on the page for a few minutes. Need to constantly close tab and re-open in a new one to keep resource utilization manageable. 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.185386.1505967785000.587.1575490380204%40Atlassian.JIRA.
[JIRA] (JENKINS-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title Devin Nusbaum commented on JENKINS-34256 Re: Preparing Jenkins For Shutdown Hangs Running Pipelines Ferruccio Bongianni Yes, it's confusing, but that's the intended behavior. Clicking "Prepare for shutdown" pauses all running Pipelines. My PR prints a message to the build log of Pipelines when this happens to make it clear that the build is paused. Once the build is paused, Jenkins can be restarted, and the Pipeline will resume after the restart. If you are only using "Prepare for shutdown" to restart Jenkins without breaking in-progress builds of non-Pipeline jobs, you can navigate to the /safeRestart URL, which is like "Prepare for shutdown" except that it automatically restarts after all non-Pipeline jobs complete. The Pipeline builds should resume after Jenkins restarts with or without my PR. The main change in my PR is that today, if you cancel shutdown after clicking "Prepare for shutdown", the Pipeline builds stay paused. You have to manually pause and unpause the builds to get them to resume or restart Jenkins. After my PR, canceling shutdown will unpause the builds and resume them automatically. 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.169794.1460663849000.584.1575490323935%40Atlassian.JIRA.
[JIRA] (JENKINS-60165) EC2-Fleet-Plugin assigns instance name (‘Jenkins’ doesn’t have label ‘nonprodslave2’; ‘user2’ lacks permission to run on ‘nonprodslave2 i-************343’) after the label. This
Title: Message Title Artem Stasiuk commented on JENKINS-60165 Re: EC2-Fleet-Plugin assigns instance name (‘Jenkins’ doesn’t have label ‘nonprodslave2’; ‘user2’ lacks permission to run on ‘nonprodslave2 i-343’) after the label. This fails the role assignment by agent labels For information place where we set Node name https://github.com/jenkinsci/ec2-fleet-plugin/blob/master/src/main/java/com/amazon/jenkins/ec2fleet/EC2FleetCloud.java#L645 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.203117.1573718238000.514.1575490260128%40Atlassian.JIRA.
[JIRA] (JENKINS-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title
Ferruccio Bongianni edited a comment on JENKINS-34256
Re: Preparing Jenkins For Shutdown Hangs Running Pipelines
I am experiencing the same problem as described in the title. This is how to I reproduce it: * Run an instance of jenkins/jenkins:lts image (which for me has version [Jenkins ver. 2.190.2|https://jenkins.io/]) * create a simple pipeline: ** {code:java}pipeline {agent anystages {stage('x') {steps {sh 'sleep 30'sh 'sleep 30'}}}} {code} * run a build of the pipeline above, then go to {{Manage Jenkins}} and click on {{Prepare for shutdown}} At this point Jenkins shows the red stripe {{Jenkins is going to shut down}} but it never does. The pipeline never proceed (in fact, it doesn't even reach the second {{sh}} if the prepare for shutdown happened during the first sleep. The pipeline hangs, and never terminate.I am currently at Jenkins world and showed the behaviour to [~bitwiseman] today.
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.169794.1460663849000.381.1575489963458%40Atlassian.JIRA.
[JIRA] (JENKINS-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title
Ferruccio Bongianni edited a comment on JENKINS-34256
Re: Preparing Jenkins For Shutdown Hangs Running Pipelines
I am experiencing the same problem as described in the title. This is how I reproduce it: * Run an instance of a container from jenkins/jenkins:lts image (which for me has version [Jenkins ver. 2.190.2|https://jenkins.io/]) * create a simple pipeline: ** {code:java}pipeline {agent anystages {stage('x') {steps {sh 'sleep 30'sh 'sleep 30'}}}} {code} * run a build of the pipeline above, then go to {{Manage Jenkins}} and click on {{Prepare for shutdown}} At this point Jenkins shows the red stripe {{Jenkins is going to shut down}} but it never does. The pipeline never proceed (in fact, it doesn't even reach the second {{sh}} if the prepare for shutdown happened during the first sleep. The pipeline hangs, and never terminate.I am currently at Jenkins world and showed the behaviour to [~bitwiseman] today.
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.169794.1460663849000.448.1575489964326%40Atlassian.JIRA.
[JIRA] (JENKINS-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title
ferruccio bongianni commented on JENKINS-34256
Re: Preparing Jenkins For Shutdown Hangs Running Pipelines
I am experiencing the same problem as described in the title. This is how to reproduce it:
Run an instance of jenkins/jenkins:lts image (which for me has version Jenkins ver. 2.190.2)
create a simple pipeline:
pipeline {
agent any
stages {
stage('x') {
steps {
sh 'sleep 30'
sh 'sleep 30'
}
}
}
}
run a build of the pipeline above, then go to Manage Jenkins and click on Prepare for shutdown
At this point Jenkins shows the red stripe Jenkins is going to shut down but it never does. The pipeline never proceed (in fact, it doesn't even reach the second sh if the prepare for shutdown happened during the first sleep. The pipeline hangs, and never terminate. I am currently at Jenkins world and showed the behaviour to Liam Newman today.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60165) EC2-Fleet-Plugin assigns instance name (‘Jenkins’ doesn’t have label ‘nonprodslave2’; ‘user2’ lacks permission to run on ‘nonprodslave2 i-************343’) after the label. This
Title: Message Title Artem Stasiuk commented on JENKINS-60165 Re: EC2-Fleet-Plugin assigns instance name (‘Jenkins’ doesn’t have label ‘nonprodslave2’; ‘user2’ lacks permission to run on ‘nonprodslave2 i-343’) after the label. This fails the role assignment by agent labels Just checked code, plugin doesn't add label to Node name, in fact node name is always just EC2 instance ID, however Jenkins users/plugins are able to change Node name after creation is that possible that you have some additional plugin which does that? 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.203117.1573718238000.309.1575489480153%40Atlassian.JIRA.
[JIRA] (JENKINS-60165) EC2-Fleet-Plugin assigns instance name (‘Jenkins’ doesn’t have label ‘nonprodslave2’; ‘user2’ lacks permission to run on ‘nonprodslave2 i-************343’) after the label. This
Title: Message Title Artem Stasiuk commented on JENKINS-60165 Re: EC2-Fleet-Plugin assigns instance name (‘Jenkins’ doesn’t have label ‘nonprodslave2’; ‘user2’ lacks permission to run on ‘nonprodslave2 i-343’) after the label. This fails the role assignment by agent labels Hi could you please specify version of your EC2 Fleet Plugin, thx 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.203117.1573718238000.303.1575489060321%40Atlassian.JIRA.
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Devin Nusbaum edited a comment on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile [~jequals5] Once you got LAUNCH_DIAGNOSTICS enabled, did the build log have any additional information? If not, can you downgrade to Durable Task Plugin 1.30 (and Pipeline: Nodes and Processes 2.34) to see if things work correctly in that version? CC [~carroll], potentially related to JENKINS-60107 , or maybe JENKINS-60054 unless that is Kubernetes-specific? 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.203277.1574777832000.305.1575489060448%40Atlassian.JIRA.
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Devin Nusbaum commented on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile Marky Jackson Once you got LAUNCH_DIAGNOSTICS enabled, did the build log have any additional information? If not, can you downgrade to Durable Task Plugin 1.30 (and Pipeline: Nodes and Processes 2.34) to see if things work correctly in that version? CC Carroll Chiou, potentially related to JENKINS-60107 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.203277.1574777832000.299.1575488640206%40Atlassian.JIRA.
[JIRA] (JENKINS-60165) EC2-Fleet-Plugin assigns instance name (‘Jenkins’ doesn’t have label ‘nonprodslave2’; ‘user2’ lacks permission to run on ‘nonprodslave2 i-************343’) after the label. This
Title: Message Title Artem Stasiuk assigned an issue to Artem Stasiuk Jenkins / JENKINS-60165 EC2-Fleet-Plugin assigns instance name (‘Jenkins’ doesn’t have label ‘nonprodslave2’; ‘user2’ lacks permission to run on ‘nonprodslave2 i-343’) after the label. This fails the role assignment by agent labels Change By: Artem Stasiuk Assignee: Chad Schmutzer Artem Stasiuk 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.203117.1573718238000.297.1575488580326%40Atlassian.JIRA.
[JIRA] (JENKINS-60363) Include TLSv1.2 instruction in P4-Plugin Doc
Title: Message Title
Krzysztof Knapik updated an issue
Jenkins / JENKINS-60363
Include TLSv1.2 instruction in P4-Plugin Doc
Change By:
Krzysztof Knapik
Include following information in Jenkins administration guide: [https://community.perforce.com/s/article/2620] For example it could be added to: [ https://www.perforce.com/manuals/jenkins/Content/P4Jenkins/credentials.html?Highlight=JCE#Connection_Issues ] {code:java}Solution2: If you have configured your Helix VCS server to have a minimum TLS version greater than v1.0 you need to start Jenkins with the additional flag '-DsecureSocketEnabledProtocols=VERSION' where 'VERSION' is a comma-separated list of accepted protocol versions . For example edit '/etc/default/jenkins' and it the falg to 'JAVA_ARGS': JAVA_ARGS="-Djava.awt.headless=true -DsecureSocketEnabledProtocols=TLSv1.2"This will need to be set on the master and every build slave.{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You receive
[JIRA] (JENKINS-51504) Dynamic downstream projects are waiting for downstream
Title: Message Title Steve Fisher commented on JENKINS-51504 Re: Dynamic downstream projects are waiting for downstream This is happening for me as well. My job was using a specific downstream project, and it would end as expected, not waiting for the downstream job to finish. But then I edited the job to use a dynamic project name in a variable. Now the job keeps running until the downstream job is finished. The Trigger Parameterized Build step is the last Post-build step in my job. The job in question and the downstream job are both running on AWS linux instances, and they are different instances. The downstream job launches a new instance when it starts. Not sure if that matters or not. Jenkins v2.205 and Parameterized Trigger plugin 2.35.2 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.190879.1527077826000.277.1575487260239%40Atlassian.JIRA.
[JIRA] (JENKINS-12783) Delete workspace before build starts ignores Exlude patterns (for directories)
Title: Message Title
Grim Reaper edited a comment on JENKINS-12783
Re: Delete workspace before build starts ignores Exlude patterns (for directories)
Updated my test server to Jenkins 2.89.4 and we are now using "Gitea" as our backend SCM.Still the same issue.Also update on the work around. Found out it wasn't working as intended. So now I shuffle files around to make it work. This is all on Linux.Steps to configure the job: # Under "Source Code management" (Git), select "Wipe out repo & force clone" under "Additional behaviours". # Under "Build Environment", note you still need to have the preSCMBuildStep plugin and check "Run buildstep before SCM runs" and add "Execute shell", then use the following to "Exclude files" (You may need to modify for your needs):{code:java}# Move build files to temp location before workspace wipels -Al "${WORKSPACE}"[ ! -d "/tmp/${BUILD_TAG}/" ] && mkdir -p "/tmp/${BUILD_TAG}/"mv -v "${WORKSPACE}"/*.build.* "${WORKSPACE}"/suppressions.xml "/tmp/${BUILD_TAG}/"ls -Al "/tmp/${BUILD_TAG}/"{code} # Under the "Build" section of your job. Add "Execute shell" and move it to the top. In the textbox add the following script commands to move your files back into the workspace:{code:java}# Move build files back to workspace before build runs mv -v "/tmp/${BUILD_TAG}"/* "${WORKSPACE}" ls -Al "${WORKSPACE}" rm -rfv "/tmp/${BUILD_TAG}/"{code}Off to try the latest and greatest Jenkins (Hopefully ) it can still build our legacy apps >.<).
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 unsubs
[JIRA] (JENKINS-12783) Delete workspace before build starts ignores Exlude patterns (for directories)
Title: Message Title
Grim Reaper commented on JENKINS-12783
Re: Delete workspace before build starts ignores Exlude patterns (for directories)
Updated my test server to Jenkins 2.89.4 and we are now using "Gitea" as our backend SCM. Still the same issue. Also update on the work around. Found out it wasn't working as intended. So now I shuffle files around to make it work. This is all on Linux. Steps to configure the job:
Under "Source Code management" (Git), select "Wipe out repo & force clone" under "Additional behaviours".
Under "Build Environment", note you still need to have the preSCMBuildStep plugin and check "Run buildstep before SCM runs" and add "Execute shell", then use the following to "Exclude files" (You may need to modify for your needs):
# Move build files to temp location before workspace wipe
ls -Al "${WORKSPACE}"
[ ! -d "/tmp/${BUILD_TAG}/" ] && mkdir -p "/tmp/${BUILD_TAG}/"
mv -v "${WORKSPACE}"/*.build.* "${WORKSPACE}"/suppressions.xml "/tmp/${BUILD_TAG}/"
ls -Al "/tmp/${BUILD_TAG}/"
Under the "Build" section of your job. Add "Execute shell" and move it to the top. In the textbox add the following script commands to move your files back into the workspace:
# Move build files back to workspace before build runs
mv -v "/tmp/${BUILD_TAG}"/* "${WORKSPACE}"
ls -Al "${WORKSPACE}"
rm -rfv "/tmp/${BUILD_TAG}/"
Off to try the latest and greatest Jenkins (Hopefully) it can still build our legacy apps >.<).
Add Comment
[JIRA] (JENKINS-2048) java.io.FileNotFoundException: /boot.log (Permission denied)
Title: Message Title Arun Shrestha commented on JENKINS-2048 Re: java.io.FileNotFoundException: /boot.log (Permission denied) Sorry. was trying to work on some bug gardening and accidentally pressed the Progress button. Is there a way to revert the changes? 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.132121.1215526231000.241.1575486540386%40Atlassian.JIRA.
[JIRA] (JENKINS-2048) java.io.FileNotFoundException: /boot.log (Permission denied)
Title: Message Title Arun Shrestha stopped work on JENKINS-2048 Change By: Arun Shrestha Status: In Progress Open 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.132121.1215526231000.231.1575486241614%40Atlassian.JIRA.
[JIRA] (JENKINS-2048) java.io.FileNotFoundException: /boot.log (Permission denied)
Title: Message Title Arun Shrestha started work on JENKINS-2048 Change By: Arun Shrestha 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.132121.1215526231000.229.1575486241487%40Atlassian.JIRA.
[JIRA] (JENKINS-2048) java.io.FileNotFoundException: /boot.log (Permission denied)
Title: Message Title Arun Shrestha updated JENKINS-2048 Jenkins / JENKINS-2048 java.io.FileNotFoundException: /boot.log (Permission denied) Change By: Arun Shrestha Status: Reopened Open 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.132121.1215526231000.211.1575486180949%40Atlassian.JIRA.
[JIRA] (JENKINS-60107) durabletask v1.33 - process apparently never started in /var/lib/jenkins/workspace/local-cloud-regression-test@tmp/durable-fa896164
Title: Message Title Devin Nusbaum commented on JENKINS-60107 Re: durabletask v1.33 - process apparently never started in /var/lib/jenkins/workspace/local-cloud-regression-test@tmp/durable-fa896164 00:00:26.617 module.redis02.vsphere_virtual_machine.vm: Destroying... [id=42068f3c-c1f8-70e9-4262-0f63e7c9c77e] 00:00:26.617 module.cassandra01.vsphere_virtual_machine.vm: Destroying... [id=4206a140-090b-3066-35ba-71c30007b204] Is this output from the script you passed to sh? If so, I am a bit curious about the timestamps. It looks like it ran for 5 hours, and then failed with "process apparently never started"? Can you confirm that downgrading to Durable Task Plugin 1.30 (you may also need to downgrade Pipeline: Nodes and Processes Plugin to 2.34 if you have already updated to 2.35) makes these problems go away? 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.202953.1573219258000.206.1575485700261%40Atlassian.JIRA.
[JIRA] (JENKINS-60107) durabletask v1.33 - process apparently never started in /var/lib/jenkins/workspace/local-cloud-regression-test@tmp/durable-fa896164
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-60107
Re: durabletask v1.33 - process apparently never started in /var/lib/jenkins/workspace/local-cloud-regression-test@tmp/durable-fa896164
{quote}00:00:26.617 module.redis02.vsphere_virtual_machine.vm: Destroying... [id=42068f3c-c1f8-70e9-4262-0f63e7c9c77e] 00:00:26.617 module.cassandra01.vsphere_virtual_machine.vm: Destroying... [id=4206a140-090b-3066-35ba-71c30007b204]{quote}Is this output from the script you passed to {{sh}}? If so, I am a bit curious about the timestamps. It looks like it ran for 5 hours, and then failed with "process apparently never started"? Can you confirm that downgrading to Durable Task Plugin 1.30 (you may will also need to downgrade Pipeline: Nodes and Processes Plugin to 2.34 if you have already updated to 2.35) makes these problems go away?
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.202953.1573219258000.208.1575485700291%40Atlassian.JIRA.
[JIRA] (JENKINS-51968) sshagent plugin broken on Windows 10 version 1803
Title: Message Title Andreas Meyer commented on JENKINS-51968 Re: sshagent plugin broken on Windows 10 version 1803 Just a suggestion: Read the path of ssh-agent from a dedicated environment variable (say JENKINS_SSH_AGENT) instead of solely relying on PATH. If JENKINS_SSH_AGENT isn't defined, fallback to the old behaviour. This way we could avoid fiddling with PATH altogether. 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.191460.1529061233000.199.1575484980191%40Atlassian.JIRA.
[JIRA] (JENKINS-60370) Pin build at timestamp
Title: Message Title Joel Brown created an issue Jenkins / JENKINS-60370 Pin build at timestamp Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2019-12-04 18:29 Labels: P4_VERIFY Priority: Minor Reporter: Joel Brown Request the ability to pin a build to a timestamp or date. Current capability is to build at a change or label. Workaround: changes are sequentially ordered by submit datetime, so you could figure out the change that represents the desired datetime. Add Comment
[JIRA] (JENKINS-57143) JNLP4 error: "Connection closed before acknowledgement sent"
Title: Message Title Jeff Thompson commented on JENKINS-57143 Re: JNLP4 error: "Connection closed before acknowledgement sent" It would be nice to get some time to see about getting some of that in. Better diagnosability would be a nice addition. Yeah, I wonder why it needs to reverse resolve. Would take some time to figure out what and why it's doing there. Thanks! 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.198893.1555967243000.195.1575483660206%40Atlassian.JIRA.
[JIRA] (JENKINS-57143) JNLP4 error: "Connection closed before acknowledgement sent"
Title: Message Title Nathan Neulinger commented on JENKINS-57143 Re: JNLP4 error: "Connection closed before acknowledgement sent" I'd also ask question of why it has to reverse resolve - i.e. why is that requirement in there in the first place. 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.198893.1555967243000.191.1575483540240%40Atlassian.JIRA.
[JIRA] (JENKINS-57143) JNLP4 error: "Connection closed before acknowledgement sent"
Title: Message Title Nathan Neulinger commented on JENKINS-57143 Re: JNLP4 error: "Connection closed before acknowledgement sent" There was near zero useful reporting server side - if the JNLP server side handler has "remote client has to resolve in DNS" at the very least reporting that explicitly in the failure logs. I can understand it not being able to necessarily make it back to the client side but at the least the server side should report it usefully in logs. (Just guessing there, but I can certainly see that possibility from JNLP4 protocol limitations.) Would be great if server side could report it in the agent status on the node page, but at the very least getting it in the logs. 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.198893.1555967243000.187.1575483480319%40Atlassian.JIRA.
[JIRA] (JENKINS-57143) JNLP4 error: "Connection closed before acknowledgement sent"
Title: Message Title Jeff Thompson commented on JENKINS-57143 Re: JNLP4 error: "Connection closed before acknowledgement sent" Any ideas what we could do to better handle this situation? Or provide better diagnostics? 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.198893.1555967243000.183.1575483300304%40Atlassian.JIRA.
[JIRA] (JENKINS-57143) JNLP4 error: "Connection closed before acknowledgement sent"
Title: Message Title Nathan Neulinger commented on JENKINS-57143 Re: JNLP4 error: "Connection closed before acknowledgement sent" Yep, almost exact same failure, with addition of it indicating that all protocols were rejected. Re-enabling JNLP3 fixed it as a test. It was just dumb luck viewing an strace of the jenkins master that I saw the hangs/failures of reverse dns lookups on the master. 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.198893.1555967243000.179.1575482880227%40Atlassian.JIRA.
[JIRA] (JENKINS-57143) JNLP4 error: "Connection closed before acknowledgement sent"
Title: Message Title Jeff Thompson commented on JENKINS-57143 Re: JNLP4 error: "Connection closed before acknowledgement sent" Nathan Neulinger, thanks for sharing your experience. It may help give others some ideas on where to investigate if they see similar problems. Were you seeing similar log messages as originally reported? If not, it might be a somewhat different issue. DNS configuration issues can cause lots of weird, problems that don't appear related. 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.198893.1555967243000.175.1575482460314%40Atlassian.JIRA.
[JIRA] (JENKINS-60368) Server Sent Events doesn't work with CORS
Title: Message Title Stefan Schletterer updated an issue Jenkins / JENKINS-60368 Server Sent Events doesn't work with CORS Change By: Stefan Schletterer We use the CORS plugin to be able to access jenkins content from an HTML REST Client. To receive status updates on our dashboard we use the Jenkins SSE Gateway plugin with the _javascript_ client.The plugin doesn't use the CORS settings from the CORS plugin. So far we have forked the repo and [hard coded CORS in *src\main\java\org\jenkinsci\plugins\ssegateway\Endpoint.java*.|https://github.com/schletti2000/sse-gateway-plugin/blob/feature-cors/src/main/java/org/jenkinsci/plugins/ssegateway/Endpoint.java]A slightly better approach would be to get the information from the cors-plugin on initialize.But shouldn't the SSE request go through the CORS Filter anyway? 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
[JIRA] (JENKINS-60368) Server Sent Events doesn't work with CORS
Title: Message Title
Stefan Schletterer updated an issue
Jenkins / JENKINS-60368
Server Sent Events doesn't work with CORS
Change By:
Stefan Schletterer
We use the CORS plugin to be able to access jenkins content from an HTML REST Client. To receive status updates on our dashboard we use the Jenkins SSE Gateway plugin with the _javascript_ client. {{ The plugin doesn't use the CORS settings from the CORS plugin. So far [ we have forked the repo and [ hard coded cors CORS in *src\main\java\org\jenkinsci\plugins\ssegateway\Endpoint.java*. | [ https://github.com/schletti2000/sse-gateway-plugin/blob/feature-cors/src/main/java/org/jenkinsci/plugins/ssegateway/Endpoint.java] ] in *src\main\java\org\jenkinsci\plugins\ssegateway\Endpoint.java*: }} {{}}{{ A slightly better approach would be to get the information from the cors-plugin on initialize. }} But shouldn't the SSE request go through the CORS Filter anyway?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received
[JIRA] (JENKINS-60368) Server Sent Events doesn't work with CORS
Title: Message Title
Stefan Schletterer updated an issue
Jenkins / JENKINS-60368
Server Sent Events doesn't work with CORS
Change By:
Stefan Schletterer
We use the CORS plugin to be able to access jenkins content from an HTML REST Client. To receive status updates on our dashboard we use the Jenkins SSE Gateway plugin with the _javascript_ client.{{The plugin doesn't use the CORS settings from the CORS plugin. So far [ we have forked the repo and hard coded cors |[https://github.com/schletti2000/sse-gateway-plugin/blob/feature-cors/src/main/java/org/jenkinsci/plugins/ssegateway/Endpoint.java]] in *src\main\java\org\jenkinsci\plugins\ssegateway\Endpoint.java*: }}{{}}{{A slightly better approach would be to get the information from the cors-plugin on initialize.}}But shouldn't the SSE request go through the CORS Filter anyway?
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.
T
[JIRA] (JENKINS-60368) Server Sent Events doesn't work with CORS
Title: Message Title
Stefan Schletterer updated an issue
Jenkins / JENKINS-60368
Server Sent Events doesn't work with CORS
Change By:
Stefan Schletterer
We use the CORS plugin to be able to access jenkins content from an HTML REST Client. To receive status updates on our dashboard we use the Jenkins SSE Gateway plugin with the _javascript_ client.{{The plugin doesn't use the CORS settings from the CORS plugin. So far we have forked the repo and hard coded cors like this in *src\main\java\org\jenkinsci\plugins\ssegateway\Endpoint.java*: }} {{public void doFilter(...)}}{{...}} {{ String origin = httpServletRequest.getHeader("Origin"); }} {{ httpServletResponse.addHeader("Access-Control-Allow-Credentials", "true");}} {{httpServletResponse.setHeader("Access-Control-Allow-Origin", origin);}} {{httpServletResponse.setHeader("Access-Control-Allow-Methods", "POST, GET, OPTIONS, PUT, DELETE, HEAD");}} {{httpServletResponse.setHeader("Access-Control-Allow-Headers", "X-PINGOTHER, LAST-EVENT-ID, Origin, X-Requested-With, Content-Type, Accept");}}{{...}}{{But much A slightly better approach would be to get the cors settings information from the cors- plugin , if it is installed and enabled: on initialize. }} cors=Jenkins.instance.pluginManager.plugins.find it.getShortName()== But shouldn ' cors-filter' t the SSE request go through the CORS Filter anyway? {{corsClass=AccessControlsFilter.class}}{{resp.addHeader("Access-Control-Allow-Methods", getDescriptor().getAllowedMethods());}}...
Add Comment
This me
[JIRA] (JENKINS-60369) Kubernetes plugin is trying to create PVC when there are no volumes specified
Title: Message Title Vladimir Mukhin created an issue Jenkins / JENKINS-60369 Kubernetes plugin is trying to create PVC when there are no volumes specified Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2019-12-04 17:03 Environment: kubernetes-plugin: 1.19.3 jenkins: 2.176.2 kuberentes: 1.13 AWS EKS Priority: Critical Reporter: Vladimir Mukhin There are no volumes specified in our Pod template. Even though, Jenkins is trying to create a PVC and fails with an access denied error. /var/log/jenkins/jenkins.log io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: POST at: https://1293c2340bb6c04946f7328ce8ca2ad7.sk1.us-east-1.eks.amazonaws.com /api/v1/namespaces/ci/persistentvolumeclaims. Message: Forbidden! User kube-aws-translator-admin doesn't have permission. persistentvolumeclaims is forbidde n: User "system:serviceaccount:ci:jenkins" cannot create resource "persistentvolumeclaims" in API group "" in the namespace "ci". at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:510) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:447) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:413) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:372) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleCreate(OperationSupport.java:241) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.handleCreate(BaseOp
[JIRA] (JENKINS-60368) Server Sent Events doesn't work with CORS
Title: Message Title
Stefan Schletterer updated an issue
Jenkins / JENKINS-60368
Server Sent Events doesn't work with CORS
Change By:
Stefan Schletterer
We use the CORS plugin to be able to access jenkins content from an HTML REST Client. To receive status updates on our dashboard we use the Jenkins SSE Gateway plugin with the _javascript_ client.{{The plugin doesn't use the CORS settings from the CORS plugin. So far we have forked the repo and hard coded cors like this in *src\main\java\org\jenkinsci\plugins\ssegateway\Endpoint.java*: }}{{public void doFilter(...)}}{{...}}{{String origin = httpServletRequest.getHeader("Origin");}}{{httpServletResponse.addHeader("Access-Control-Allow-Credentials", "true");}}{{httpServletResponse.setHeader("Access-Control-Allow-Origin", origin);}}{{httpServletResponse.setHeader("Access-Control-Allow-Methods", "POST, GET, OPTIONS, PUT, DELETE, HEAD");}}{{httpServletResponse.setHeader("Access-Control-Allow-Headers", "X-PINGOTHER, LAST-EVENT-ID, Origin, X-Requested-With, Content-Type, Accept");}}{{...}} {{But much better would be to get the cors settings from the plugin, if it is installed and enabled:}}cors=Jenkins.instance.pluginManager.plugins.find it.getShortName()=='cors-filter' {{corsClass=AccessControlsFilter.class}}{{resp.addHeader("Access-Control-Allow-Methods", getDescriptor().getAllowedMethods());}}... However, I dont know about the performance implications of querying the cors plugin on every request. Could you point me in the right direction so I can create a proper pull request?
Add Comment
[JIRA] (JENKINS-59059) Allow repository orga scan to filter on topics
Title: Message Title Noah Nordrum commented on JENKINS-59059 Re: Allow repository orga scan to filter on topics I want this too and can work on it of somebody tells me where. This thing is so abstracted out to support everything... 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.201417.1566511327000.164.1575478620176%40Atlassian.JIRA.
[JIRA] (JENKINS-60368) Server Sent Events doesn't work with CORS
Title: Message Title
Stefan Schletterer updated an issue
Jenkins / JENKINS-60368
Server Sent Events doesn't work with CORS
Change By:
Stefan Schletterer
We use the CORS plugin to be able to access jenkins content from an HTML REST Client. To receive status updates on our dashboard we use the Jenkins SSE Gateway plugin with the _javascript_ client.{{The plugin doesn't use the CORS settings from the CORS plugin. So far we have forked the repo and hard coded cors like this in *src\main\java\org\jenkinsci\plugins\ssegateway\Endpoint.java*: }}{{ {{ public void doFilter(...)}}{{...}} }} {{ {{ String origin = httpServletRequest.getHeader("Origin");}} }} {{ {{ httpServletResponse.addHeader("Access-Control-Allow-Credentials", "true");}} }} {{ {{ httpServletResponse.setHeader("Access-Control-Allow-Origin", origin);}} }} {{ {{ httpServletResponse.setHeader("Access-Control-Allow-Methods", "POST, GET, OPTIONS, PUT, DELETE, HEAD");}} }} {{ {{ httpServletResponse.setHeader("Access-Control-Allow-Headers", "X-PINGOTHER, LAST-EVENT-ID, Origin, X-Requested-With, Content-Type, Accept");}} }} {{...}} {{ }} {{But much better would be to get the cors settings from the plugin, if it is installed and enabled:}} {{ cors=Jenkins.instance.pluginManager.plugins.find { it.getShortName()=='cors-filter' }}}{{corsClass=AccessControlsFilter.class}}{{resp.addHeader("Access-Control-Allow-Methods", getDescriptor().getAllowedMethods());}}... However, I dont know about the performance implications of querying the cors plugin on every request. Could you point me in the right direction so I can create a proper pull request?
Add Comment
[JIRA] (JENKINS-60360) error occurs when 'git config --get submodule.**.url
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-60360 error occurs when 'git config --get submodule.**.url Change By: Mark Waite Assignee: Mark Waite 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.203381.1575447656000.145.1575478140218%40Atlassian.JIRA.
[JIRA] (JENKINS-60360) error occurs when 'git config --get submodule.**.url
Title: Message Title Mark Waite commented on JENKINS-60360 Re: error occurs when 'git config --get submodule.**.url I don't know why that happens. Since you did not provide enough information that anyone else could assist, I will leave this issue open for at least one day and will then close it as "cannot reproduce". If you would like to avoid this bug being closed as "cannot reproduce", please provide significantly more details to describe the problem and confirm that you have investigated the cause of the problem. Please provide a series of steps which someone else can use to duplicate the problem you are seeing. That might include steps like: Define a freestyle job that clones https://github.com/MarkEWaite/docker-lfs.git Add the checkout option to recursively update submoodules Run the Jenkins job Actual Result: Checkout fails Expected Result: Checkout succeeds 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.203381.1575447656000.134.1575478081415%40Atlassian.JIRA.
[JIRA] (JENKINS-60360) error occurs when 'git config --get submodule.**.url
Title: Message Title Mark Waite edited a comment on JENKINS-60360 Re: error occurs when 'git config --get submodule.**.url I don't know why that happens. Since you did not provide enough information that anyone else could assist, I will leave this issue open for at least one day and will then close it as "cannot reproduce". If you would like to avoid this bug being closed as "cannot reproduce", please provide significantly more details to describe the problem and confirm that you have investigated the cause of the problem. Please provide a series of steps which someone else can use to duplicate the problem you are seeing. That might include steps like:# Define a freestyle job that clones https://github.com/MarkEWaite/docker-lfs.git# Add the checkout option to recursively update submoodules# Run the Jenkins job *Actual Result*: Checkout fails*Expected Result*: Checkout succeeds 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.203381.1575447656000.143.1575478081918%40Atlassian.JIRA.
[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title Josh Watson commented on JENKINS-55220 Re: Multibranch Pipeline jobs get randomly lost Also getting this with Jenkins running on Centos 7, using nginx as a proxy. The jobs are triggered from other multi-branch pipelines (from subversion (still using it in 2019!) ) and I'm seeing mangled branches being created, for example branches/4.0 mutates from branches-4-0.v5ktnf to bbrraanncchh.lphb61._252-F44--00 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.196298.154504211.88.1575477240855%40Atlassian.JIRA.
[JIRA] (JENKINS-60368) Server Sent Events doesn't work with CORS
Title: Message Title
Stefan Schletterer updated an issue
Jenkins / JENKINS-60368
Server Sent Events doesn't work with CORS
Change By:
Stefan Schletterer
We use the CORS plugin to be able to access jenkins content from an HTML REST Client. To receive status updates on our dashboard we use the Jenkins SSE Gateway plugin with the _javascript_ client. {{ The plugin doesn't use the CORS settings from the CORS plugin. So far we have forked the repo and hard coded cors like this in *src\main\java\org\jenkinsci\plugins\ssegateway\Endpoint.java*: }} {{ {{ public void doFilter(...)}}{{...}} }} {{ {{ String origin = httpServletRequest.getHeader("Origin");}} }} {{ {{ httpServletResponse.addHeader("Access-Control-Allow-Credentials", "true");}} }} {{ {{ httpServletResponse.setHeader("Access-Control-Allow-Origin", origin);}} }} {{ {{ httpServletResponse.setHeader("Access-Control-Allow-Methods", "POST, GET, OPTIONS, PUT, DELETE, HEAD");}} }} {{ {{ httpServletResponse.setHeader("Access-Control-Allow-Headers", "X-PINGOTHER, LAST-EVENT-ID, Origin, X-Requested-With, Content-Type, Accept");}} }} {{ httpServletResponse . setHeader("Access-Control-Max-Age", "1728000"); .. }} {{ }} Better {{But much better would be to get the cors settings from the plugin , if it is installed and enabled : }} {{cors=Jenkins.instance.pluginManager.plugins.find \ {it.getShortName()=='cors-filter' }}}{{corsClass=AccessControlsFilter.class}}{{resp.addHeader("Access-Control-Allow-Methods", getDescriptor().getAllowedMethods());}} ... However, I dont know about the performance implications of querying the cors plugin on every request. Could you point me in the right direction so I can create a proper pull request?
Add Comment
[JIRA] (JENKINS-59773) Promote pluging no access to artifact in version 3.4
Title: Message Title Andrew Waltman commented on JENKINS-59773 Re: Promote pluging no access to artifact in version 3.4 I think this may be fixed in version 3.5. I was able to successfully scp an artifact using version 3.5 where it failed for me using 3.4. 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.202497.1571043091000.54.1575475560593%40Atlassian.JIRA.
[JIRA] (JENKINS-60368) Server Sent Events doesn't work with CORS
Title: Message Title
Stefan Schletterer created an issue
Jenkins / JENKINS-60368
Server Sent Events doesn't work with CORS
Issue Type:
Improvement
Assignee:
Stefan Schletterer
Components:
sse-gateway-plugin
Created:
2019-12-04 16:00
Environment:
Jenkins: 2.190.2 jenkins-sse-gateway: 1.20
Priority:
Minor
Reporter:
Stefan Schletterer
We use the CORS plugin to be able to access jenkins content from an HTML REST Client. To receive status updates on our dashboard we use the Jenkins SSE Gateway plugin with the _javascript_ client. The plugin doesn't use the CORS settings from the CORS plugin. So far we have forked the repo and hard coded cors like this in src\main\java\org\jenkinsci\plugins\ssegateway\Endpoint.java: public void doFilter(...)... String origin = httpServletRequest.getHeader("Origin");httpServletResponse.addHeader("Access-Control-Allow-Credentials", "true");httpServletResponse.setHeader("Access-Control-Allow-Origin", origin);httpServletResponse.setHeader("Access-Control-Allow-Methods", "POST, GET, OPTIONS, PUT, DELETE, HEAD");httpServletResponse.setHeader("Access-Control-Allow-Headers", "X-PINGOTHER, LAST-EVENT-ID, Origin, X-Requested-With, Content-Type, Accept");httpServletResponse.setHeader("Access-Control-Max-Age", "1728000"); Better would be to get the cors settings from the plugin: cors=Jenkins.instance.pluginManager.plugins.find {it.getShortName()=='cors-filter' } corsClass=AccessControlsFilter.classresp.addHeader("Access-Control-Allow-Methods", getDescriptor().getAllowedMethods()); However, I dont know about the performance implications of querying the cors plugin on every request.
[JIRA] (JENKINS-38781) p4 unshelve not updating changes (pipeline)
Title: Message Title
Karl Wirth commented on JENKINS-38781
Re: p4 unshelve not updating changes (pipeline)
Hi Morne Joubert - I'd like to review this one with the developers so I did the following test. P4_CHANGELIST is reported but it matches the latest changelist the workspace was synced to. For example unshelving changelist 2254:
pipeline {
agent { label 'master' }
stages {
stage("Repro") {
steps {
script {
def p4env = p4unshelve credential: 'JenkinsMaster', ignoreEmpty: false, resolve: 'at', shelf: '2254', tidy: false, workspace: manualSpec(charset: 'none', cleanup: false, name: 'jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}', pinHost: false, spec: clientSpec(allwrite: false, backup: true, changeView: '', clobber: true, compress: false, line: 'LOCAL', locked: false, modtime: false, rmdir: false, serverID: '', streamName: '', type: 'WRITABLE', view: '//depot/JENKINS-38781-UnsyncChangelist/... //jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}/... '))
echo "P4_CHANGELIST is:"
echo env.P4_CHANGELIST
echo sh(script: 'env|sort', returnStdout: true)
}
}
}
}
}
In the output:
...cut...
P4 Task: unshelve review: 2254
... p4 unshelve -f -s2254 -cdefault +//depot/JENKINS-38781-UnsyncChangelist/f1
... duration: (2ms)
P4 Task: resolve: -at
... p4 resolve -at /var/lib/jenkins/workspace/JENKINS-38781-ChangelistOnUnshelve/... +... duration: (1ms)
[Pipeline] echo
P4_CHANGELIST is:
[Pipeline] echo
2268
...cut...
What do you want P4_CHANGELIST to be set to? Note the changes are also seen in Jenkins:
Add Comment
[JIRA] (JENKINS-38781) p4 unshelve not updating changes (pipeline)
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-38781 p4 unshelve not updating changes (pipeline) Change By: Karl Wirth Attachment: image-2019-12-04-15-41-26-079.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.175181.1475750631000.47.1575474120319%40Atlassian.JIRA.
[JIRA] (JENKINS-60367) Declarative Pipeline: Allow env vars to be used in options block
Title: Message Title Marius Meyer updated an issue Jenkins / JENKINS-60367 Declarative Pipeline: Allow env vars to be used in options block Change By: Marius Meyer Summary: Declarative Pipeline: Allow env vars to be used in options block 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.203411.157547372.44.1575474000763%40Atlassian.JIRA.
[JIRA] (JENKINS-60367) Allow env vars to be used in options block
Title: Message Title
Marius Meyer created an issue
Jenkins / JENKINS-60367
Allow env vars to be used in options block
Issue Type:
Improvement
Assignee:
Unassigned
Components:
pipeline
Created:
2019-12-04 15:35
Priority:
Minor
Reporter:
Marius Meyer
I'm trying to use the lock() option in an options block of a stage. I want the lock resource to be dynamic (depending on an environment variable). For example:
environment {
BRANCH_TO_USE = get_branch_to_use()
}
stages {
stage('Lock build'){
options {
lock(resource: "lock-${env.BRANCH_TO_USE}", quantity: 1)
}
stages {
...
But the resulting string is always "lock-null". I tried it without "env." but to no avail. I would expect this to work especially since the environment variable is available in the coming stages with no problem. Is there a way to support this or a possible workaround?
Add Comment
[JIRA] (JENKINS-60366) Incomplete remote output after streaming improvement
Title: Message Title Roberto Paolillo created an issue Jenkins / JENKINS-60366 Incomplete remote output after streaming improvement Issue Type: Bug Assignee: KaiHsiang Chang Components: parameterized-remote-trigger-plugin Created: 2019-12-04 15:27 Priority: Minor Reporter: Roberto Paolillo Since this improvement reported in 3.0.9 changelog: "Stream output rather than dump it all out at the end (a625e4b)" The very last part of the remote output is not printed in local console (I suppose the part after the last polling request). Switching back to 3.0.8 solves the issue for me. Add Comment
[JIRA] (JENKINS-60107) durabletask v1.33 - process apparently never started in /var/lib/jenkins/workspace/local-cloud-regression-test@tmp/durable-fa896164
Title: Message Title
Jon Udaondo edited a comment on JENKINS-60107
Re: durabletask v1.33 - process apparently never started in /var/lib/jenkins/workspace/local-cloud-regression-test@tmp/durable-fa896164
[~dnusbaum]The issue is still there...It happened in another job while using "terraform destroy -f". The console output of the job displays the following.. {code:java}00:00:26.617 module.redis02.vsphere_virtual_machine.vm: Destroying... [id=42068f3c-c1f8-70e9-4262-0f63e7c9c77e]00:00:26.617 module.cassandra01.vsphere_virtual_machine.vm: Destroying... [id=4206a140-090b-3066-35ba-71c30007b204]00:05:18.718 process apparently never started in /var/lib/jenkins/workspace/destroy-cloud-environment@tmp/durable-3ee2246a[Pipeline] }00:05:18.748 ERROR: script returned exit code -2{code}Below that, no more output about the error is deplayed despite having "-Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true" enabled.
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.202953.1573219258000.33.1575472381041%40Atlassian.JIRA.
[JIRA] (JENKINS-60107) durabletask v1.33 - process apparently never started in /var/lib/jenkins/workspace/local-cloud-regression-test@tmp/durable-fa896164
Title: Message Title Jon Udaondo commented on JENKINS-60107 Re: durabletask v1.33 - process apparently never started in /var/lib/jenkins/workspace/local-cloud-regression-test@tmp/durable-fa896164 Devin Nusbaum The issue is still there... It happened in another job while using "terraform destroy -f". 00:00:26.617 module.redis02.vsphere_virtual_machine.vm: Destroying... [id=42068f3c-c1f8-70e9-4262-0f63e7c9c77e] 00:00:26.617 module.cassandra01.vsphere_virtual_machine.vm: Destroying... [id=4206a140-090b-3066-35ba-71c30007b204] 00:05:18.718 process apparently never started in /var/lib/jenkins/workspace/destroy-cloud-environment@tmp/durable-3ee2246a [Pipeline] } 00:05:18.748 ERROR: script returned exit code -2 Below that, no more output about the error is deplayed despite having "-Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true" enabled. 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.202953.1573219258000.30.1575472261240%40Atlassian.JIRA.
[JIRA] (JENKINS-38669) SCM (Git) Will Not Notify Pipeline Before Execution
Title: Message Title Devin Nusbaum assigned an issue to Angry Gami Jenkins / JENKINS-38669 SCM (Git) Will Not Notify Pipeline Before Execution Change By: Devin Nusbaum Assignee: Angry Gami 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.175064.1475526372000.25.1575471900419%40Atlassian.JIRA.
[JIRA] (JENKINS-38669) SCM (Git) Will Not Notify Pipeline Before Execution
Title: Message Title Devin Nusbaum updated JENKINS-38669 Jenkins / JENKINS-38669 SCM (Git) Will Not Notify Pipeline Before Execution Change By: Devin Nusbaum 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.175064.1475526372000.19.1575471841060%40Atlassian.JIRA.
[JIRA] (JENKINS-38669) SCM (Git) Will Not Notify Pipeline Before Execution
Title: Message Title Devin Nusbaum started work on JENKINS-38669 Change By: Devin Nusbaum 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.175064.1475526372000.17.1575471841010%40Atlassian.JIRA.
[JIRA] (JENKINS-60141) Excessive number of "login -s" requests
Title: Message Title Karl Wirth assigned an issue to Unassigned Jenkins / JENKINS-60141 Excessive number of "login -s" requests Change By: Karl Wirth Assignee: Karl Wirth 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.12.1575471603690%40Atlassian.JIRA.
[JIRA] (JENKINS-60141) Excessive number of "login -s" requests
Title: Message Title Karl Wirth commented on JENKINS-60141 Re: Excessive number of "login -s" requests Sample of a basic freestyle job with a manual workspace executed on a slave. Polling enabled but polling did not trigger the job. Poll Now was clicked to collect the polling P4 commands. Single Freestyle job run through the GUI: # P4 commands $ grep user- log.case | grep jenkins | wc -l 58 # P4 info or login commands $ grep user- log.case | grep jenkins | grep "login\|info" | wc -l 37 Polling for the freestyle job: # P4 Commands $ grep user log.poll | grep jenkins | wc -l 9 # P4 info or login commands $ grep user log.poll | grep jenkins | grep "login\|info" | wc -l 5 Have attached the logs for the above output. 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.6.1575471603317%40Atlassian.JIRA.
[JIRA] (JENKINS-60141) Excessive number of "login -s" requests
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60141 Excessive number of "login -s" requests Change By: Karl Wirth Labels: P4_SUPPORT P4_A P4_VERIFY jenkins plugin 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.9.1575471603443%40Atlassian.JIRA.
[JIRA] (JENKINS-60141) Excessive number of "login -s" requests
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60141 Excessive number of "login -s" requests Change By: Karl Wirth Attachment: log.case Attachment: log.poll 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.3.1575471364122%40Atlassian.JIRA.
[JIRA] (JENKINS-55865) Ability to add additional tags
Title: Message Title Viktor Jozsa commented on JENKINS-55865 Re: Ability to add additional tags I found a new line in your changelog: version 1.2.1 'Enable adding custom tags for created resources' https://github.com/jenkinsci/azure-vm-agents-plugin/blob/dev/CHANGELOG.md But I couldn't find any information for 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.197262.1548850714000.11981.1575468960241%40Atlassian.JIRA.
[JIRA] (JENKINS-60115) NullPointerException in Declarative Pipeline after upgrade from 1.3.9 to 1.4.0
Title: Message Title Liam Newman updated JENKINS-60115 Jenkins / JENKINS-60115 NullPointerException in Declarative Pipeline after upgrade from 1.3.9 to 1.4.0 Change By: Liam Newman Status: Fixed but Unreleased Closed 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.202962.1573259182000.11973.1575466261176%40Atlassian.JIRA.
