[JIRA] (JENKINS-49759) Can't create temp file in Kubernetes Plugin Pipeline
Title: Message Title Carlos Sanchez commented on JENKINS-49759 Re: Can't create temp file in Kubernetes Plugin Pipeline I'm actually quite surprised it works at all. From my understanding createTempFile runs on the agent container, and because the filesystem is shared you could see the file in all the containers. So it would work when outside the container step. Inside container you can execute commands, but that's all you can do because it uses kubectl exec Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44420) ERROR: Error fetching remote repo 'origin' if workspace path includes '%' char
Title: Message Title sajid yar commented on JENKINS-44420 Re: ERROR: Error fetching remote repo 'origin' if workspace path includes '%' char Mark Waite I am getting this error while I am building a .NET project having git as a source control explorer. I am using git version 2.16.1.windows.4 of git and using updated Jenkins version. Here is the complete log while I am building a project. I don't know what's happening behind the scene. Started by user anonymous [EnvInject] - Loading node environment variables. Building in workspace C:\Users\sajid.yar\.jenkins\workspace\RiskManagerDev > C:\Program Files\Git\bin\git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > C:\Program Files\Git\bin\git config remote.origin.url https://github.com/envolvevision/RiskManager.git timeout=10 Fetching upstream changes from https://github.com/envolvevision/RiskManager.git > C:\Program Files\Git\bin\git --version # timeout=10 using GIT_ASKPASS to set credentials > C:\Program Files\Git\bin\git fetch --tags --progress https://github.com/envolvevision/RiskManager.git +refs/heads/:refs/remotes/origin/ ERROR: Timeout after 10 minutes ERROR: Error fetching remote repo 'origin' hudson.plugins.git.GitException: Failed to fetch from https://github.com/envolvevision/RiskManager.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:862) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1129) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1160) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1203) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1727) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Caused by: hudson.plugins.git.GitException: Command "C:\Program Files\Git\bin\git fetch --tags --progress https://github.com/envolvevision/RiskManager.git +refs/heads/:refs/remotes/origin/" returned status code -1: stdout: stderr: remote: Counting objects: 4418, done. remote: Compressing objects: 0% (1/2000) remote: Compressing objects: 1% (20/2000) remote: Compressing objects: 2% (40/2000) remote: Compressing objects: 3% (60/2000) remote: Compressing objects: 4% (80/2000) remote: Compressing objects: 5% (100/2000) remote: Compressing objects: 6% (120/2000) remote: Compressing objects: 7% (140/2000) remote: Compressing objects: 8% (160/2000) remote: Compressing objects: 9% (180/2000) remote: Compressing objects: 10% (200/2000) remote: Compressing objects: 11% (220/2000) remote: Compressing objects: 12% (240/2000) remote: Compressing objects: 13% (260/2000) remote: Compressing objects: 14% (280/2000) remote: Compressing objects: 15% (300/2000) remote: Compressing objects: 16% (320/2000) remote: Compressing objects: 17% (340/2000) remote: Compressing objects: 18% (360/2000) remote: Compressing objects: 19% (380/2000) remote: Compressing objects: 20% (400/2000) remote: Compressing objects: 21% (420/2000) remote: Compressing objects: 22% (440/2000) remote: Compressing objects: 23% (460/2000) remote: Compressing objects: 24% (480/2000) remote: Compressing objects: 25% (500/2000) remote: Compressing objects: 26% (520/2000) remote: Compressing objects:
[JIRA] (JENKINS-49679) Return value unpacking in pipelinescript causes function to execute twice.
Title: Message Title Uli Hierl commented on JENKINS-49679 Re: Return value unpacking in pipelinescript causes function to execute twice. Wow, that was quick. Thank you for your effort! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39010) Comment Added event does not work
Title: Message Title Björn Pedersen commented on JENKINS-39010 Re: Comment Added event does not work Ry Jones: I think this actually excpected behaviour: The plugin filters it's own comments to avoid trigger-loops. One solution: use the gerrit ssh cli to post the review 'DO BUILD 1' with another account to force triggering, or just trigger the other job directly (there are different ways to do that in jenkins...) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49707) Pipeline hangs: "The channel is closing down or has closed down"
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49707 Pipeline hangs: "The channel is closing down or has closed down" Change By: Oleg Nenashev Component/s: _unsorted Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49707) Pipeline hangs: "The channel is closing down or has closed down"
Title: Message Title Oleg Nenashev commented on JENKINS-49707 Re: Pipeline hangs: "The channel is closing down or has closed down" Please provide the following info: Support bundle for the timeframe of the outage: https://wiki.jenkins.io/display/JENKINS/Support+Core+Plugin Agent threaddump dump for the timeframe of the outage Agent filesystem log for the time of the outage You can find some pointers here: https://speakerdeck.com/onenashev/day-of-jenkins-2017-dealing-with-agent-connectivity-issues?slide=51 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49760) SSL Error in Github API connection
Title: Message Title Saul Alonso closed an issue as Duplicate Jenkins / JENKINS-49760 SSL Error in Github API connection Change By: Saul Alonso Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49761) SSL Error in Github API connection
Title: Message Title Saul Alonso updated an issue Jenkins / JENKINS-49761 SSL Error in Github API connection Change By: Saul Alonso Since crypto removal of github.com (https://githubengineering.com/crypto-removal-notice/) , when trying to connect to github API, causes SSL error in connection. Full trace:Feb 27, 2018 7:41:00 AM org.jenkinsci.plugins.ghprb.GhprbRootAction$2 runSEVERE: Unable to handle PR# 344 for repo: java.lang.Error: org.kohsuke.github.HttpException: Server returned HTTP response code: -1, message: 'null' for URL: [ https://api.github.com/repos//pulls/344/files ] at org.kohsuke.github.Requester$PagingIterator.fetch(Requester.java:516) at org.kohsuke.github.Requester$PagingIterator.hasNext(Requester.java:481) at org.kohsuke.github.PagedIterator.fetch(PagedIterator.java:44) at org.kohsuke.github.PagedIterator.hasNext(PagedIterator.java:32) at org.jenkinsci.plugins.ghprb.GhprbPullRequest.containsWatchedPaths(GhprbPullRequest.java:439) at org.jenkinsci.plugins.ghprb.GhprbPullRequest.tryBuild(GhprbPullRequest.java:502) at org.jenkinsci.plugins.ghprb.GhprbPullRequest.check(GhprbPullRequest.java:198) at org.jenkinsci.plugins.ghprb.GhprbRepository.onPullRequestHook(GhprbRepository.java:394) at org.jenkinsci.plugins.ghprb.GhprbTrigger.handlePR(GhprbTrigger.java:746) at org.jenkinsci.plugins.ghprb.GhprbRootAction$2.run(GhprbRootAction.java:257)Caused by: org.kohsuke.github.HttpException: Server returned HTTP response code: -1, message: 'null' for URL: [ https://api.github.com/repos/Telefonica/vamps/pulls/344/files ] at org.kohsuke.github.Requester.parse(Requester.java:633) at org.kohsuke.github.Requester.parse(Requester.java:594) at org.kohsuke.github.Requester.access$200(Requester.java:73) at org.kohsuke.github.Requester$PagingIterator.fetch(Requester.java:505) ... 9 moreCaused by: javax.net.ssl.SSLException: Received fatal alert: protocol_version at sun.security.ssl.Alerts.getSSLException(Alerts.java:208) at sun.security.ssl.Alerts.getSSLException(Alerts.java:154) at sun.security.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:2023) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1125) at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387) at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1513) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) at
[JIRA] (JENKINS-43673) Need new trigger for Parameterized Trigger Plugin: Failed but not still failing
Title: Message Title Michael M. commented on JENKINS-43673 Re: Need new trigger for Parameterized Trigger Plugin: Failed but not still failing I would really like to have this trigger. I want to trigger an action when a periodic test fails the first time. It is clear in the next test runs that the test again will fail unless, I have fixed the bug. It would be very helpful for me to have this trigger. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49761) SSL Error in Github API connection
Title: Message Title Saul Alonso created an issue Jenkins / JENKINS-49761 SSL Error in Github API connection Issue Type: Bug Assignee: Unassigned Components: github-api-plugin Created: 2018-02-27 06:41 Environment: Red Hat Enterprise Linux 7.3, Jenkins 2.89.4, Github API Plugin 1.90 Priority: Major Reporter: Saul Alonso Since crypto removal of github.com, when trying to connect to github API, causes SSL error in connection. Full trace: Feb 27, 2018 7:41:00 AM org.jenkinsci.plugins.ghprb.GhprbRootAction$2 run SEVERE: Unable to handle PR# 344 for repo: java.lang.Error: org.kohsuke.github.HttpException: Server returned HTTP response code: -1, message: 'null' for URL: https://api.github.com/repos//pulls/344/files at org.kohsuke.github.Requester$PagingIterator.fetch(Requester.java:516) at org.kohsuke.github.Requester$PagingIterator.hasNext(Requester.java:481) at org.kohsuke.github.PagedIterator.fetch(PagedIterator.java:44) at org.kohsuke.github.PagedIterator.hasNext(PagedIterator.java:32) at org.jenkinsci.plugins.ghprb.GhprbPullRequest.containsWatchedPaths(GhprbPullRequest.java:439) at org.jenkinsci.plugins.ghprb.GhprbPullRequest.tryBuild(GhprbPullRequest.java:502) at org.jenkinsci.plugins.ghprb.GhprbPullRequest.check(GhprbPullRequest.java:198) at org.jenkinsci.plugins.ghprb.GhprbRepository.onPullRequestHook(GhprbRepository.java:394) at org.jenkinsci.plugins.ghprb.GhprbTrigger.handlePR(GhprbTrigger.java:746) at org.jenkinsci.plugins.ghprb.GhprbRootAction$2.run(GhprbRootAction.java:257) Caused by: org.kohsuke.github.HttpException: Server returned HTTP response code: -1, message: 'null' for URL: https://api.github.com/repos/Telefonica/vamps/pulls/344/files at org.kohsuke.github.Requester.parse(Requester.java:633) at
[JIRA] (JENKINS-49760) SSL Error in Github API connection
Title: Message Title Saul Alonso created an issue Jenkins / JENKINS-49760 SSL Error in Github API connection Issue Type: Bug Assignee: Unassigned Components: github-api-plugin Created: 2018-02-27 06:40 Environment: Red Hat Enterprise Linux 7.3, Jenkins 2.89.4, Github API Plugin 1.90 Priority: Major Reporter: Saul Alonso Since crypto removal of github.com, when trying to connect to github API, causes SSL error in connection. Full trace: Add Comment
[JIRA] (JENKINS-43673) Need new trigger for Parameterized Trigger Plugin: Failed but not still failing
Title: Message Title Michael M. updated an issue Jenkins / JENKINS-43673 Need new trigger for Parameterized Trigger Plugin: Failed but not still failing Change By: Michael M. Priority: Minor Trivial Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41600) Parallel step running forever if too much console output is logged
Title: Message Title mishal shah commented on JENKINS-41600 Re: Parallel step running forever if too much console output is logged Joerg Schwaerzler Did you find a workaround for this issue? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48776) Not able to trigger builds
Title: Message Title kgiloo commented on JENKINS-48776 Re: Not able to trigger builds any update on this one? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27963) Please add support for jenkins pipeline plugin to publish-over-ssh
Title: Message Title Tapio Reijonen commented on JENKINS-27963 Re: Please add support for jenkins pipeline plugin to publish-over-ssh Very quickly tested this 1.19 and seams to work OK in pipeline and freestyle jobs. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44483) Large console logs cause infinite loops in slave
Title: Message Title mishal shah commented on JENKINS-44483 Re: Large console logs cause infinite loops in slave is there any workaround to this issue? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45080) Blue Ocean displays wrong step time
Title: Message Title Surya Bharath Bommadevara started work on JENKINS-45080 Change By: Surya Bharath Bommadevara Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45080) Blue Ocean displays wrong step time
Title: Message Title Surya Bharath Bommadevara stopped work on JENKINS-45080 Change By: Surya Bharath Bommadevara Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40109) Compilation error in shared library/global variable produces java.io.NotSerializableException org.codehaus.groovy.control.ErrorCollector
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-40109 Compilation error in shared library/global variable produces java.io.NotSerializableException org.codehaus.groovy.control.ErrorCollector Change By: Vivek Pandey Sprint: Pipeline - Candidates Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40117) Type java.lang$Enum not present when updating 2.6 to 2.7
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-40117 Type java.lang$Enum not present when updating 2.6 to 2.7 Change By: Vivek Pandey Sprint: Pipeline - Candidates March 2018 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27092) create a step to abort the build with a NOT_BUILT status
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-27092 create a step to abort the build with a NOT_BUILT status Change By: Vivek Pandey Sprint: Pipeline - Candidates March 2018 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27092) create a step to abort the build with a NOT_BUILT status
Title: Message Title Vivek Pandey assigned an issue to Andrew Bayer Jenkins / JENKINS-27092 create a step to abort the build with a NOT_BUILT status Change By: Vivek Pandey Assignee: Andrew Bayer Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48644) First step in Pipeline does not have a description
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-48644 First step in Pipeline does not have a description Change By: Vivek Pandey Sprint: Pipeline - December March 2018 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34433) Pipeline locks not signalled on manual unreserving of resources
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-34433 Pipeline locks not signalled on manual unreserving of resources Change By: Vivek Pandey Sprint: Pipeline - December March 2018 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48491) NPE in CpsThreadGroup.run & IOOBE in CpsThreadGroup.readResolve
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-48491 NPE in CpsThreadGroup.run & IOOBE in CpsThreadGroup.readResolve Change By: Vivek Pandey Sprint: Pipeline - December March 2018 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46809) Allow sequencial stages inside parallel in Declarative syntax
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-46809 Allow sequencial stages inside parallel in Declarative syntax Change By: Vivek Pandey Sprint: Pipeline - December March 2018 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43194) Lightweight checkout for PR merge jobs
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-43194 Lightweight checkout for PR merge jobs Change By: Vivek Pandey Sprint: Blue Ocean 1.4 - beta 2, Pipeline - December March 2018 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46354) Retry in Declarative options skips retried stages due to earlier failure
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-46354 Retry in Declarative options skips retried stages due to earlier failure Change By: Vivek Pandey Sprint: Declarative - 1.2, Pipeline - December March 2018 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46174) Error cloning remote from PR at first try
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-46174 Error cloning remote from PR at first try Change By: Vivek Pandey Sprint: Pipeline - December March 2018 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48303) Review SCM, Branch, Bitbucket and Github branch source PRs
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-48303 Review SCM, Branch, Bitbucket and Github branch source PRs Change By: Vivek Pandey Sprint: Pipeline - December March 2018 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40912) Add verbose option to stash/unstash to get list of files
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-40912 Add verbose option to stash/unstash to get list of files Change By: Vivek Pandey Sprint: Pipeline - October, Pipeline - December March 2018 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32000) durable-task 1.7 breaks workflow bat steps
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-32000 durable-task 1.7 breaks workflow bat steps Change By: Vivek Pandey Sprint: Pipeline - December March 2018 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45455) Restarting stages
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-45455 Restarting stages Change By: Vivek Pandey Sprint: Pipeline - December March 2018 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29840) when workflow uses multiple git repos the "git build data" and "tags" become next to useless.
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-29840 when workflow uses multiple git repos the "git build data" and "tags" become next to useless. Change By: Vivek Pandey Sprint: Pipeline - October, Pipeline - December March 2018 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47174) Optimize incidental persistence calls during pipeline execution
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-47174 Optimize incidental persistence calls during pipeline execution Change By: Vivek Pandey Sprint: Pipeline - October, Pipeline - December March 2018 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43995) Individual Pipeline steps and stages/blocks should have Result statuses
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-43995 Individual Pipeline steps and stages/blocks should have Result statuses Change By: Vivek Pandey Sprint: Pipeline - July/August, Pipeline - October, Pipeline - December March 2018 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39489) Loading pipeline builds is expensive because they store scripts
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-39489 Loading pipeline builds is expensive because they store scripts Change By: Vivek Pandey Sprint: Pipeline - October, Pipeline - December March 2018 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47520) Probable race condition in deleting/loading branches of a multibranch project
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-47520 Probable race condition in deleting/loading branches of a multibranch project Change By: Vivek Pandey Sprint: Pipeline - October, Pipeline - December March 2018 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38381) Optimize log handling in Pipeline and Durable Task
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-38381 Optimize log handling in Pipeline and Durable Task Change By: Vivek Pandey Sprint: Pipeline - October, Pipeline - December March 2018 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26313) Workflow script fails if CPS-transformed methods are called from constructors
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-26313 Workflow script fails if CPS-transformed methods are called from constructors Change By: Vivek Pandey Sprint: Pipeline - March 2018 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45334) REGRESSION "input parameter not support go to classic link" does not work
Title: Message Title Nicolae Pascu started work on JENKINS-45334 Change By: Nicolae Pascu Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49759) Can't create temp file in Kubernetes Plugin Pipeline
Title: Message Title
Michael MacFadden updated an issue
Jenkins / JENKINS-49759
Can't create temp file in Kubernetes Plugin Pipeline
Change By:
Michael MacFadden
We are having an issue where we can not create a temp file in a build pipeline within a PodTemplate. Oddly inserting a random 'sh' command before the creation of the temp file solved the problem. Here is the code that fails: {code:java} import hudson.FilePath;import jenkins.model.Jenkins;def label = "mynode"podTemplate( label: label, nodeSelector: "kops.k8s.io/instancegroup=jenkins-workers", containers: [containerTemplate(name: 'kubectl', image: 'lachlanevenson/k8s-kubectl:v1.9.3', command: 'cat', ttyEnabled: true)]) { node(label) {container("kubectl") { def workspace = new FilePath(Jenkins.getInstance().getComputer(env.NODE_NAME).getChannel(), env.WORKSPACE); workspace.createTempFile("test", ".txt") sh "ls -al"} }}{code} The full log is attached, but essentially we get the following exception:{code:java}Caused: java.io.IOException: Failed to create a temp file on /home/jenkins/workspace/folder/test-jobat hudson.FilePath.createTempFile(FilePath.java:1330){code}Oddly, if we add a "sh" command before the creation of the temp file the job succeeds. The following code works:{code:java} import hudson.FilePath;import jenkins.model.Jenkins;def label = "mynode"podTemplate( label: label, nodeSelector: "kops.k8s.io/instancegroup=jenkins-workers", containers: [containerTemplate(name: 'kubectl', image: 'lachlanevenson/k8s-kubectl:v1.9.3', command: 'cat', ttyEnabled: true)]) { node(label) {container("kubectl") { sh "ls -al" // This added code somehow makes this pipeline succeed. def workspace = new FilePath(Jenkins.getInstance().getComputer(env.NODE_NAME).getChannel(), env.WORKSPACE); workspace.createTempFile("test", ".txt") sh "ls -al"} }}{code}It does not seem to matter what the "sh" command before the temp file creation is. We have used "pwd", "echo $HOME", etc. and they all have the same effect of making the pipeline work. Of course both sh "ls -al" commands were put in there as debugging steps, and it just so happened that the first one accidentally made the pipeline work.
Add Comment
[JIRA] (JENKINS-49759) Can't create temp file in Kubernetes Plugin Pipeline
Title: Message Title
Michael MacFadden created an issue
Jenkins / JENKINS-49759
Can't create temp file in Kubernetes Plugin Pipeline
Issue Type:
Bug
Assignee:
Carlos Sanchez
Attachments:
failure.log
Components:
kubernetes-plugin
Created:
2018-02-27 03:55
Environment:
Kuberetes 1.8 Jenkins 2.107 Kubernetes Plugin: 1.2.1 Java Version: 1.8.0_151 Jenkins Master running in Docker Container in k8s
Labels:
pipeline slave kubernetes-plugin
Priority:
Major
Reporter:
Michael MacFadden
We are having an issue where we can not create a temp file in a build pipeline within a PodTemplate. Oddly inserting a random 'sh' command before the creation of the temp file solved the problem. Here is the code that fails:
import hudson.FilePath;
import jenkins.model.Jenkins;
def label = "mynode"
podTemplate(
label: label,
nodeSelector: "kops.k8s.io/instancegroup=jenkins-workers",
containers: [containerTemplate(name: 'kubectl', image: 'lachlanevenson/k8s-kubectl:v1.9.3', command: 'cat', ttyEnabled: true)]) {
node(label) {
container("kubectl") {
def workspace = new FilePath(Jenkins.getInstance().getComputer(env.NODE_NAME).getChannel(), env.WORKSPACE);
[JIRA] (JENKINS-49757) Git clone triggers fetch twice
Title: Message Title
Mark Waite edited a comment on JENKINS-49757
Re: Git clone triggers fetch twice
I think I see the same behavior in the log file of my jobs. I have a [Freestyle job|https://github.com/MarkEWaite/docker-lfs/blob/lts-with-plugins/ref/jobs/Bugs-Individual/jobs/JENKINS-48064-Fisheye-url-validator-ignored/config.xml] configured which generates the following log output:{noformat}> git init /home/beemarkwaite/mark-pc2.markwaite.net-agent/workspace/Bugs-Individual/JENKINS-48064-Fisheye-url-validator-ignored # timeout=10Fetching upstream changes from https://github.com/aeshell/aesh.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/aeshell/aesh.git +refs/heads/master:refs/remotes/origin/master +refs/heads/0.56.1:refs/remotes/origin/0.56.1 > git config remote.origin.url https://github.com/aeshell/aesh.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/master:refs/remotes/origin/master # timeout=10 > git config --add remote.origin.fetch +refs/heads/0.56.1:refs/remotes/origin/0.56.1 # timeout=10 > git config remote.origin.url https://github.com/aeshell/aesh.git # timeout=10Fetching upstream changes from https://github.com/aeshell/aesh.git > git fetch --tags --progress https://github.com/aeshell/aesh.git +refs/heads/master:refs/remotes/origin/master +refs/heads/0.56.1:refs/remotes/origin/0.56.1{noformat}That seems to show that shows two calls are made to {{git fetch}}. Since {{git fetch}} is an incremental operation, I'm not planning to make any change in this area of the code. The second fetch operation is not free, but it is usually very lightweight, since it will only request changes made since the preceding fetch.For the sake of precision, your earlier comments are not describing the implementation of the code. You said:bq. The first link is part of the Git-client clone step, it triggers the git-plugin CloneCommand (second link) to perform the clone operations. And afterwards, the Git-client plugin performs a fetch.As far as I can tell, that's not the way the code works. The git client plugin does not call the git plugin. It does not have any dependency on the git plugin and does not know about the git plugin implementation. The git client plugin provides an API that is called by the git plugin.The stack trace you provided shows two calls to {{git fetch}}, but the two calls are using different credentials. I'm assuming that the difference in credentials is because you edited the log output to remove identifying information.
Add Comment
[JIRA] (JENKINS-49757) Git clone triggers fetch twice
Title: Message Title Mark Waite commented on JENKINS-49757 Re: Git clone triggers fetch twice I think I see the same behavior in the log file of my jobs. I have a Freestyle job configured which generates the following log output: > git init /home/beemarkwaite/mark-pc2.markwaite.net-agent/workspace/Bugs-Individual/JENKINS-48064-Fisheye-url-validator-ignored # timeout=10 Fetching upstream changes from https://github.com/aeshell/aesh.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/aeshell/aesh.git +refs/heads/master:refs/remotes/origin/master +refs/heads/0.56.1:refs/remotes/origin/0.56.1 > git config remote.origin.url https://github.com/aeshell/aesh.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/master:refs/remotes/origin/master # timeout=10 > git config --add remote.origin.fetch +refs/heads/0.56.1:refs/remotes/origin/0.56.1 # timeout=10 > git config remote.origin.url https://github.com/aeshell/aesh.git # timeout=10 Fetching upstream changes from https://github.com/aeshell/aesh.git > git fetch --tags --progress https://github.com/aeshell/aesh.git +refs/heads/master:refs/remotes/origin/master +refs/heads/0.56.1:refs/remotes/origin/0.56.1 That seems to show that two calls are made to git fetch. Since git fetch is an incremental operation, I'm not planning to make any change in this area of the code. The second fetch operation is not free, but it is usually very lightweight, since it will only request changes made since the preceding fetch. For the sake of precision, your earlier comments are not describing the implementation of the code. You said: The first link is part of the Git-client clone step, it triggers the git-plugin CloneCommand (second link) to perform the clone operations. And afterwards, the Git-client plugin performs a fetch. As far as I can tell, that's not the way the code works. The git client plugin does not call the git plugin. It does not have any dependency on the git plugin and does not know about the git plugin implementation. The git client plugin provides an API that is called by the git plugin. The stack trace you provided shows two calls to git fetch, but the two calls are using different credentials. I'm assuming that the difference in credentials is because you edited the log output to remove identifying information. Add Comment
[JIRA] (JENKINS-46940) Build pipeline plugin duplicates static linked jobs in view
Title: Message Title heidi huang started work on JENKINS-46940 Change By: heidi huang Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46940) Build pipeline plugin duplicates static linked jobs in view
Title: Message Title heidi huang stopped work on JENKINS-46940 Change By: heidi huang Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49757) Git clone triggers fetch twice
Title: Message Title sam leung edited a comment on JENKINS-49757 Re: Git clone triggers fetch twice [~markewaite]The second link is part of the GITSCM step, it triggers the git-client-plugin's CloneCommand (first link) to perform the clone operation. And afterwards, the GITSCM step performs a fetch once the CloneCommand Completes.However, within the CloneCommand (first link) itself, a fetch command was already done. see GitSCM#1140 on the call from GITSCM into CloneCommand,see CliGitAPIImpl#609 inside CloneCommand for the first fetch.see GitSCM#1153 for the second fetch Thanks a lot for looking into this Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49757) Git clone triggers fetch twice
Title: Message Title sam leung updated an issue Jenkins / JENKINS-49757 Git clone triggers fetch twice Change By: sam leung When performing a git clone operation,git-client and git-plugin both triggers a git fetch. Below are the two lines of code running in the same git clone command both doing fetches. The first second link is part of the Git-client clone GITSCM step, it triggers the git- client- plugin 's CloneCommand ( second first link) to perform the clone operations operation . And afterwards, the Git-client plugin GITSCM step performs a fetch once cloneCommand the CloneCommand Completes.However, within the cloneCommand CloneCommand ( second first link) itself, a fetch command was already done. [https://github.com/jenkinsci/git-client-plugin/blob/4241e818dbe27fb78093094f29ebcd2203166610/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L609] [https://github.com/jenkinsci/git-plugin/blob/cb58c74efafafd08bc03bba2787997c6a0272df0/src/main/java/hudson/plugins/git/GitSCM.java#L1153] I am aware there are needs to support for git clone to fetch all refs first - - JENKINS-31393- - . The suggestion provided in that ticket was to use "honor git refspec", so shouldn't "honor git refspec" skip the first fetch here? Thanks,Sam Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49757) Git clone triggers fetch twice
Title: Message Title sam leung edited a comment on JENKINS-49757 Re: Git clone triggers fetch twice [~markewaite]The first second link is part of the Git-client clone GITSCM step, it triggers the git- client- plugin 's CloneCommand ( second first link) to perform the clone operations operation . And afterwards, the Git-client plugin GITSCM step performs a fetch once the CloneCommand Completes .However, within the cloneCommand CloneCommand ( second first link) itself, a fetch command was already done. Thanks a lot for looking into this Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49757) Git clone triggers fetch twice
Title: Message Title sam leung edited a comment on JENKINS-49757 Re: Git clone triggers fetch twice [~markewaite]The first link is part of the Git-client clone step, it triggers the git-plugin CloneCommand (second link) to perform the clone operations. And afterwards, the Git-client plugin performs a fetch once cloneCommand Completes .However, within the cloneCommand (second link) itself, a fetch command was already done. Thanks a lot for looking into this Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49757) Git clone triggers fetch twice
Title: Message Title sam leung updated an issue Jenkins / JENKINS-49757 Git clone triggers fetch twice Change By: sam leung When performing a git clone operation,git-client and git-plugin both triggers a git fetch. Below are the two lines of code running in the same git clone command both doing fetches. The first link is part of the Git-client clone step, it triggers the git-plugin CloneCommand (second link) to perform the clone operations. And afterwards, the Git-client plugin performs a fetch once cloneCommand Completes.However, within the cloneCommand (second link) itself, a fetch command was already done. [https://github.com/jenkinsci/git-client-plugin/blob/4241e818dbe27fb78093094f29ebcd2203166610/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L609] [https://github.com/jenkinsci/git-plugin/blob/cb58c74efafafd08bc03bba2787997c6a0272df0/src/main/java/hudson/plugins/git/GitSCM.java#L1153] I am aware there are needs to support for git clone to fetch all refs first - JENKINS-31393 - . The suggestion provided in that ticket was to use "honor git refspec", so shouldn't "honor git refspec" skip the first fetch here? Thanks,Sam Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49757) Git clone triggers fetch twice
Title: Message Title sam leung commented on JENKINS-49757 Re: Git clone triggers fetch twice Mark Waite The first link is part of the Git-client clone step, it triggers the git-plugin CloneCommand (second link) to perform the clone operations. And afterwards, the Git-client plugin performs a fetch once cloneCommand Completes. However, within the cloneCommand (second link) itself, a fetch command was already done. Thanks a lot for looking into this Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49757) Git clone triggers fetch twice
Title: Message Title sam leung edited a comment on JENKINS-49757 Re: Git clone triggers fetch twice If you look at the first link. It's calling the fetchcommand.execute directly and skipping all the fetchCommand decorator decorators . Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49757) Git clone triggers fetch twice
Title: Message Title sam leung commented on JENKINS-49757 Re: Git clone triggers fetch twice If you look at the first link. It's calling the fetchcommand.execute directly and skipping all the fetchCommand decorator. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49757) Git clone triggers fetch twice
Title: Message Title
sam leung commented on JENKINS-49757
Re: Git clone triggers fetch twice
Hi, The clone itself isn't being performed twice, however it's triggering fetch twice. Both fetches are being trigger by the same Clone operation. Once by the git-plugin after doing a clone, and once more by the git-client-plugin after calling the git-plugin to do the clone. Below is the log output
00:06:32 Cloning repository ssh://[git project]
00:06:32 > /usr/bin/git init /var/lib/jenkins/workspace/workspace # timeout=10
00:06:32 Fetching upstream changes from ssh://[git project]
00:06:32 > /usr/bin/git --version # timeout=10
00:06:32 using GIT_SSH to set credentials Gerrit SSH Key
00:06:32 > /usr/bin/git fetch --tags --progress ssh://[git project] +refs/heads/*:refs/remotes/origin/* # timeout=20
00:07:49 > /usr/bin/git config remote.origin.url ssh://[git project] # timeout=10
00:07:49 > /usr/bin/git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
00:07:49 > /usr/bin/git config remote.origin.url ssh://[git project] # timeout=10
00:07:49 Fetching upstream changes from ssh://[git project]
00:07:49 using GIT_SSH to set credentials fpajenkins Gerrit SSH Key
00:07:49 > /usr/bin/git fetch --tags --progress ssh://[git project] refs/changes/14/3174614/2 # timeout=20
00:08:18 > /usr/bin/git rev-parse cc8266a2cecb79d475d5c3b1dbaa5b2ea3171400^{commit} # timeout=10
00:08:18 Checking out Revision cc8266a2cecb79d475d5c3b1dbaa5b2ea3171400 (detached)
00:08:18 > /usr/bin/git config core.sparsecheckout # timeout=10
00:08:18 > /usr/bin/git config core.sparsecheckout true # timeout=10
00:08:18 > /usr/bin/git read-tree -mu HEAD # timeout=10
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49686) NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead
Title: Message Title Sam Van Oort assigned an issue to Sam Van Oort Jenkins / JENKINS-49686 NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead Change By: Sam Van Oort Assignee: Sam Van Oort Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49758) when passing in ref_spec with build parameters, the exact string "$REF_SPEC" is used rather then the value
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-49758 when passing in ref_spec with build parameters, the exact string "$REF_SPEC" is used rather then the value Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49754) Streams other than StdOut getting returned when using returnStdOut on PowerShell Step
Title: Message Title Jared Kauppila commented on JENKINS-49754 Re: Streams other than StdOut getting returned when using returnStdOut on PowerShell Step Gabriel Loewen It looks like durable-task-plugin#51 modified the streams output so everything is redirecting to 1 rather than everything else getting written to the result file. https://github.com/jenkinsci/durable-task-plugin/pull/51/files#diff-2ee2c814de2b034e34d312e8b7276e45L111 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49757) Git clone triggers fetch twice
Title: Message Title Mark Waite edited a comment on JENKINS-49757 Re: Git clone triggers fetch twice I appreciate the analysis very much.Unfortunately, the analysis doesn't seem (to me) like evidence of a bug. The git plugin (your second link) uses the git client plugin (your first link) to perform the fetch. I don't see from your description that there are two fetch operations are being performed for each repository being cloned.Please provide log output which shows two fetches being performed.Since you've provided those call sites, I assume you could also include stack traces to show that a clone is being performed twice. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49757) Git clone triggers fetch twice
Title: Message Title Mark Waite commented on JENKINS-49757 Re: Git clone triggers fetch twice I appreciate the analysis very much. Unfortunately, the analysis doesn't seem (to me) like evidence of a bug. The git plugin (your second link) uses the git client plugin (your first link) to perform the fetch. I don't see from your description that there are two fetch operations are being performed for each repository being cloned. Please provide log output which shows two fetches being performed. Since you've provided those call sites, I assume you could also include stack traces to show that a clone is being performed twice. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49707) Pipeline hangs: "The channel is closing down or has closed down"
Title: Message Title Jon B commented on JENKINS-49707 Re: Pipeline hangs: "The channel is closing down or has closed down" i just changed the JIRA "component" field for this to "remoting". Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49758) when passing in ref_spec with build parameters, the exact string "$REF_SPEC" is used rather then the value
Title: Message Title sam leung created an issue Jenkins / JENKINS-49758 when passing in ref_spec with build parameters, the exact string "$REF_SPEC" is used rather then the value Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2018-02-27 03:00 Priority: Minor Reporter: sam leung To replicate: 1) create a job and pass in refspec as build parameter e.g. "$GIT_REFSPEC" 2) use the parameter "$GIT_REFSPEC" as the SCM configuration for git-plugin 3) The build will use the exact string "$GIT_REFSPEC" rather than the actual value of $GIT_REFSPEC for the fetch operation. For example: 01:26:08 using GIT_SSH to set credentials Gerrit SSH Key 01:26:08 > /usr/bin/git fetch --no-tags --progress ssh://[github-project-url] $GIT_REFSPEC --depth=2 01:31:43 > /usr/bin/git config remote.origin.url ssh://[github-project-url] # timeout=10 01:31:43 > /usr/bin/git config --add remote.origin.fetch $GIT_REFSPEC # timeout=10 I believe the .toString in this line is causing this problem: https://github.com/jenkinsci/git-client-plugin/blob/4241e818dbe27fb78093094f29ebcd2203166610/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L617 Add Comment
[JIRA] (JENKINS-49757) Git clone triggers fetch twice
Title: Message Title Mark Waite edited a comment on JENKINS-49757 Re: Git clone triggers fetch twice I appreciate the analysis very much.Unfortunately, the analysis doesn't seem (to me) like evidence of a bug. The git plugin (your second link) uses the git client plugin (your first link) to perform the fetch. I don't see from your description that there are two fetch operations are being performed for each repository being cloned.Please provide log output which shows two fetches being performed.Since you've provided those call sites, I assume you could also include stack traces to show that a clone is being performed twice. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49707) Pipeline hangs: "The channel is closing down or has closed down"
Title: Message Title Jon B updated an issue Jenkins / JENKINS-49707 Pipeline hangs: "The channel is closing down or has closed down" Change By: Jon B Component/s: remoting Component/s: workflow-durable-task-step-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42460) EnvInject-Permission not shown/maintainable (after restart) correctly
Title: Message Title Amir Zarrinkafsh commented on JENKINS-42460 Re: EnvInject-Permission not shown/maintainable (after restart) correctly Happy to provide any additional detail if required, however Alvin Huang sums up the steps rather succinctly. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49707) Pipeline hangs: "The channel is closing down or has closed down"
Title: Message Title Jon B commented on JENKINS-49707 Re: Pipeline hangs: "The channel is closing down or has closed down" Oleg Nenashev Should this be redesignated a remoting bug? I'm not sure how to unblock my pipelines that are hanging from this issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49757) Git clone triggers fetch twice
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-49757 Git clone triggers fetch twice Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49756) InvocationTargetException when connecting to Bitbucket server with an empty repo
Title: Message Title
Karl Shultz updated an issue
Jenkins / JENKINS-49756
InvocationTargetException when connecting to Bitbucket server with an empty repo
Change By:
Karl Shultz
*Summary:*After upgrading to 1.5-beta-1, I've seen twice now an InvocationTargetException when attempting connecting to a Bitbucket server to which I'd previously connected.*Frequency of Occurrence:* Seen twice in a row 100% reproducible so far .*Steps to recreate:*0. Optional: assuming you've got filesystem access to your Jenkins server, run {{tail -f /var/log/jenkins/jenkins.log}} so you can monitor the Jenkins log in real time.1. Given an existing Jenkins installation with BO 1.4.x installed, take the 1.5.0-beta-1 upgrade. The Jenkins instance should be already connected to a Bitbucket server.2. Create an empty repository on this same Bitbucket server, using the flow in the BBS UI. Make no commits to it - my thinking was that I could build the repo from nothing, using the edtor. It'll look something like this when you're done: !image-2018-02-26-21-46-22-268.png|thumbnail! 3. Create a new pipeline, and pick the "Project" in which you created the new repo. In my case this project is called "February." Tthe loading wheel will get stuck at this loading wheel for many minutes: !image-2018-02-26-21-48-01-159.png|thumbnail! 4. Take a look at the output from the Jenkins log you started tailing in step 0, and you'll see the InvocationTargetException being thrown:{code:none}Feb 27, 2018 2:47:26 AM io.jenkins.blueocean.commons.stapler.export.ExportInterceptor$1 getValueWARNING: Failed to get "repositories" from a io.jenkins.blueocean.blueocean_bitbucket_pipeline.BitbucketRepositoryContainerjava.lang.reflect.InvocationTargetException at io.jenkins.blueocean.commons.stapler.export.MethodProperty.getValue(MethodProperty.java:74) at io.jenkins.blueocean.commons.stapler.export.ExportInterceptor$1.getValue(ExportInterceptor.java:46) at io.jenkins.blueocean.commons.stapler.Export$BlueOceanExportInterceptor.getValue(Export.java:167) at io.jenkins.blueocean.commons.stapler.export.Property.writeTo(Property.java:136) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:228) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Model.writeTo(Model.java:199) at io.jenkins.blueocean.commons.stapler.Export.writeOne(Export.java:148) at io.jenkins.blueocean.commons.stapler.Export.serveExposedBean(Export.java:139) at io.jenkins.blueocean.commons.stapler.Export.doJson(Export.java:79) at io.jenkins.blueocean.commons.stapler.TreeResponse$Processor$1.generateResponse(TreeResponse.java:48) at org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(HttpResponseRenderer.java:124) at org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(HttpResponseRenderer.java:69) at org.kohsuke.stapler.Function.renderResponse(Function.java:136) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:119) at
[JIRA] (JENKINS-49757) Git clone triggers fetch twice
Title: Message Title sam leung updated an issue Jenkins / JENKINS-49757 Git clone triggers fetch twice Change By: sam leung When performing a git clone operation,git-client and git-plugin both triggers a git fetch. Below are the two lines of code running in the same git clone command both doing fetches.[https://github.com/jenkinsci/git-client-plugin/blob/4241e818dbe27fb78093094f29ebcd2203166610/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L609] [https://github.com/jenkinsci/git-plugin/blob/cb58c74efafafd08bc03bba2787997c6a0272df0/src/main/java/hudson/plugins/git/GitSCM.java#L1153] I am aware there are needs to support for git clone to fetch all refs first [ JENKINS-31393 |https://issues . jenkins-ci.org/browse/JENKINS-31393]. The suggestion provided in that ticket was to use "honor git refspec", so shouldn't "honor git refspec" skip the first fetch here? Thanks,Sam Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are
[JIRA] (JENKINS-49756) InvocationTargetException when connecting to Bitbucket server with an empty repo
Title: Message Title Karl Shultz created an issue Jenkins / JENKINS-49756 InvocationTargetException when connecting to Bitbucket server with an empty repo Issue Type: Bug Assignee: Unassigned Attachments: image-2018-02-26-21-46-22-268.png, image-2018-02-26-21-48-01-159.png Components: blueocean-plugin Created: 2018-02-27 02:51 Environment: Jenkins: Core 2.109 with BO 1.5.0-beta-1 All other plugins at experimental update center levels Priority: Major Reporter: Karl Shultz Summary: After upgrading to 1.5-beta-1, I've seen twice now an InvocationTargetException when attempting connecting to a Bitbucket server to which I'd previously connected. Frequency of Occurrence: Seen twice in a row. Steps to recreate: 0. Optional: assuming you've got filesystem access to your Jenkins server, run tail -f /var/log/jenkins/jenkins.log so you can monitor the Jenkins log in real time. 1. Given an existing Jenkins installation with BO 1.4.x installed, take the 1.5.0-beta-1 upgrade. The Jenkins instance should be already connected to a Bitbucket server. 2. Create an empty repository on this same Bitbucket server, using the flow in the BBS UI. Make no commits to it - my thinking was that I could build the repo from nothing, using the edtor. It'll look something like this when you're done: 3. Create a new pipeline, and pick the "Project" in which you created the new repo. In my case this project is called "February." Tthe loading wheel will get stuck at this loading wheel for many minutes: 4. Take a look at the output from the Jenkins log you started tailing in step 0, and
[JIRA] (JENKINS-49757) Git clone triggers fetch twice
Title: Message Title sam leung created an issue Jenkins / JENKINS-49757 Git clone triggers fetch twice Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2018-02-27 02:52 Priority: Major Reporter: sam leung When performing a git clone operation, git-client and git-plugin both triggers a git fetch. Below are the two lines of code running in the same git clone command both doing fetches. https://github.com/jenkinsci/git-client-plugin/blob/4241e818dbe27fb78093094f29ebcd2203166610/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L609 https://github.com/jenkinsci/git-plugin/blob/cb58c74efafafd08bc03bba2787997c6a0272df0/src/main/java/hudson/plugins/git/GitSCM.java#L1153 I am aware there are needs to support for git clone to fetch all refs first JENKINS-31393. The suggestion provided was to use "honor git refspec", so shouldn't "honor git refspec" skip the first fetch here? Thanks, Sam Add Comment
[JIRA] (JENKINS-47952) Browser back behaviour for result screen is broken
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-47952 Browser back behaviour for result screen is broken Change By: Vivek Pandey Sprint: Blue Ocean 1.4 - beta 3, Blue Ocean 1.4 - beta 5 , Blue Ocean 1.5 - beta 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1
Title: Message Title Jean-Paul G edited a comment on JENKINS-48300 Re: Pipeline shell step aborts prematurely with ERROR: script returned exit code -1 The folder jenkins/jobs with the log being on the master, should the JVM parameter -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=300 be set on the master JVM (in the start script) or on each slave node JVM (in the node configuration) ? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1
Title: Message Title Jean-Paul G commented on JENKINS-48300 Re: Pipeline shell step aborts prematurely with ERROR: script returned exit code -1 The folder jenkins/jobs with the log being on the master, should the JVM parameter -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=300 set on the master (in the start script) or on each slave node (in the node configuration) ? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49755) Jenkins does work with Parameterized Trigger Plugin 2.35
Title: Message Title robert knox created an issue Jenkins / JENKINS-49755 Jenkins does work with Parameterized Trigger Plugin 2.35 Issue Type: Bug Assignee: Unassigned Components: plugin-usage-plugin Created: 2018-02-27 01:11 Environment: Host on Ubuntu 14.04.5 LTS Jenkins 2.89.4 does work with /Parameterized+Trigger+Plugin 2.35 Priority: Blocker Reporter: robert knox I have read other bugs indicating that this combination of Jenkins 2.89 and the Parameterized+Trigger+Plugin 2.35 does not pass params from one job to another. The response is always: things have changed and that the downstream job now needs to define the param as well. I have done that. The combination does not work and it block builds on our system. Add Comment
[JIRA] (JENKINS-38383) StackOverflow when loading a large pipeline job
Title: Message Title Sam Van Oort updated JENKINS-38383 Jenkins / JENKINS-38383 StackOverflow when loading a large pipeline job Change By: Sam Van Oort Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38383) StackOverflow when loading a large pipeline job
Title: Message Title Sam Van Oort started work on JENKINS-38383 Change By: Sam Van Oort Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35708) EC2 Plugin: Ability to round robin EC2 availability zones
Title: Message Title Levi Lovelock commented on JENKINS-35708 Re: EC2 Plugin: Ability to round robin EC2 availability zones Any progress or workarounds here? This hurts when using instances that have lower availability (i.e. graphics instances) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44729) Optimize git clones via shared reference repo for multi branch builds of same repository
Title: Message Title Tristan Lewis commented on JENKINS-44729 Re: Optimize git clones via shared reference repo for multi branch builds of same repository Any update on the PR that Chris Williams linked? My team would love to have the git plugin handle managing reference repos on each node for us to keep disk usage down as well as speed up clones of newly-created branches. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49746) Regex returns more matches than it should if errors are close together
Title: Message Title David van Laatum assigned an issue to Alex Earl Jenkins / JENKINS-49746 Regex returns more matches than it should if errors are close together Change By: David van Laatum Component/s: token-macro-plugin Component/s: email-ext-plugin Assignee: David van Laatum Alex Earl Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33639) Unable to connect TFS server with The SOAP endpoint could not be contacted
Title: Message Title Andrew Gray reopened an issue This issue is occurring intermittently with v5.126 of the tfs plugin. Visual studio has no issue checking in code but the tfs-plugin fails to poll tfs or checkout (if build started manually) Jenkins / JENKINS-33639 Unable to connect TFS server with The SOAP endpoint could not be contacted Change By: Andrew Gray Resolution: Done Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this
[JIRA] (JENKINS-47395) Github Server must have /api/v3 appended
Title: Message Title Nicolae Pascu closed an issue as Fixed Jenkins / JENKINS-47395 Github Server must have /api/v3 appended Change By: Nicolae Pascu Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47395) Github Server must have /api/v3 appended
Title: Message Title Nicolae Pascu commented on JENKINS-47395 Re: Github Server must have /api/v3 appended Cyrille Le Clerc Karl Shultz The fix was not cherry picked from master to the 1.4 release branch and that is why the bug is still present in 1.4.2. I cherry picked it via a PR today and it will be present in the next release. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47395) Github Server must have /api/v3 appended
Title: Message Title Nicolae Pascu resolved as Fixed Jenkins / JENKINS-47395 Github Server must have /api/v3 appended Change By: Nicolae Pascu Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46785) Add a way to disable all reporters (and selectively enable a few)
Title: Message Title Cyrille Le Clerc commented on JENKINS-46785 Re: Add a way to disable all reporters (and selectively enable a few) Fixed in pipeline-maven-3.4.0-beta-1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46785) Add a way to disable all reporters (and selectively enable a few)
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-46785 Add a way to disable all reporters (and selectively enable a few) Change By: Cyrille Le Clerc Summary: add Add a way to disable all reporters (and selectively enable a few) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49708) withMaven option to skip ALL reporters
Title: Message Title Cyrille Le Clerc closed an issue as Duplicate Jenkins / JENKINS-49708 withMaven option to skip ALL reporters Change By: Cyrille Le Clerc Status: Open Closed Assignee: Alvaro Lobato Cyrille Le Clerc Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46785) add a way to disable all reporters (and selectively enable a few)
Title: Message Title
Cyrille Le Clerc commented on JENKINS-46785
Re: add a way to disable all reporters (and selectively enable a few)
Sample:
node {
stage ('Build') {
git "https://github.com/cyrille-leclerc/my-jar.git"
// disable all publishers
withMaven(maven: 'maven-3.5.2', publisherStrategy: 'EXPLICIT') {
sh "mvn dependency:go-offline"
}
withMaven(maven: 'maven-3.5.2') {
sh "mvn clean deploy"
}
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42129) Closure delegate idiom fails attempting to call .DefaultGroovyMethods.invokeMethod(Object, String, Object)
Title: Message Title
pixman20 edited a comment on JENKINS-42129
Re: Closure delegate idiom fails attempting to call .DefaultGroovyMethods.invokeMethod(Object, String, Object)
[~abayer], I don't think the original issue in the description was resolved, only the later example in the comments.In the original example attached (copied below), the "sh" line is getting this error as shown in the description{code:java}@Library('myPipelineLib') _emailBreaks {mailingList = 'u...@example.com'node('master') {git 'https://git.example.org/user/pipeline-build-failures.git'//sh 'true'sh 'might fail' // <-- Causes: Scripts not permitted to use staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods invokeMethod java.lang.Object java.lang.String java.lang.Object}}{code}Looking at the emailBreaks shared pipeline function, I'm not sure how your previous solution applies (I could easily just be missing it){code:java}def call(Closure body) {currentBuild.result = 'SUCCESS'def config = [:]body.resolveStrategy = Closure.DELEGATE_FIRSTbody.delegate = configcatchError {body() // <-- Running the closure here delegates to config, but seems to make anything available in the owner's scope because a script approval problem}...} {code}I have the exact same situation as this, error and all. I can workaround it (painfully so), by explicitly defining the object containing the function that's being invoked. For example, using the above example, changing "sh" to either "this.sh" or "steps.sh" would work probably work (it was fixed in my case by adding the global library name) For some reason, when letting the scope with the defined function be found implicitly, the script approval part gets angry :(
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42129) Closure delegate idiom fails attempting to call .DefaultGroovyMethods.invokeMethod(Object, String, Object)
Title: Message Title
pixman20 commented on JENKINS-42129
Re: Closure delegate idiom fails attempting to call .DefaultGroovyMethods.invokeMethod(Object, String, Object)
Andrew Bayer, I don't think the original issue in the description was resolved, only the later example in the comments. In the original example attached (copied below), the "sh" line is getting this error as shown in the description
@Library('myPipelineLib') _
emailBreaks {
mailingList = 'u...@example.com'
node('master') {
git 'https://git.example.org/user/pipeline-build-failures.git'
//sh 'true'
sh 'might fail' // <-- Causes: Scripts not permitted to use staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods invokeMethod java.lang.Object java.lang.String java.lang.Object
}
}
Looking at the emailBreaks shared pipeline function, I'm not sure how your previous solution applies (I could easily just be missing it)
def call(Closure body) {
currentBuild.result = 'SUCCESS'
def config = [:]
body.resolveStrategy = Closure.DELEGATE_FIRST
body.delegate = config
catchError {
body() // <-- Running the closure here delegates to config, but seems to make the owner's scope because a script approval problem
}
...
}
I have the exact same situation as this, error and all. I can workaround it (painfully so), by explicitly defining the object containing the function that's being invoked. For example, using the above example, changing "sh" to either "this.sh" or "steps.sh" would work probably work (it was fixed in my case by adding the global library name) For some reason, when letting the scope with the defined function be found implicitly, the script approval part gets angry
Add Comment
[JIRA] (JENKINS-49332) Jenkins unable to manage webhooks of Github organization
Title: Message Title
Adam BH edited a comment on JENKINS-49332
Re: Jenkins unable to manage webhooks of Github organization
Same message after upgrading to Github plugin 1.29.Also Enterprise Github instance.Manage web hooks in Github pull request builder: DisabledManage hooks under github server: DisabledError messages persist after disabling both manage web hook check boxes.Work around: I downgraded back to the last version I used, 1.28.1, which got rid of the message spam. Jenkins+Github worked even when I got the error messages, except things seemed a bit slower.Here is a full stack trace from the error I got on 1.29, server, org, and repo names removed: { { code:java} org.jenkinsci.plugins.github.webhook.WebhookManager$2 applyNullSafeWARNING: Failed to add GitHub webhook for GitHubRepositoryName[host=github.XXX.com,username=orgName,repository=repoName]java.lang.NullPointerException: There is no credentials with admin access to manage hooks on GitHubRepositoryName[host=github.XXX.com,username=orgName,repository=repoName] at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:231) at org.jenkinsci.plugins.github.webhook.WebhookManager$2.applyNullSafe(WebhookManager.java:179) at org.jenkinsci.plugins.github.webhook.WebhookManager$2.applyNullSafe(WebhookManager.java:175) at org.jenkinsci.plugins.github.util.misc.NullSafeFunction.apply(NullSafeFunction.java:18) at com.google.common.collect.Iterators$8.next(Iterators.java:812) at com.google.common.collect.Iterators$7.computeNext(Iterators.java:648) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at com.google.common.collect.Iterators$7.computeNext(Iterators.java:647) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at com.google.common.collect.Lists.newArrayList(Lists.java:138) at com.google.common.collect.Lists.newArrayList(Lists.java:119) at org.jenkinsci.plugins.github.util.FluentIterableWrapper.toList(FluentIterableWrapper.java:147) at org.jenkinsci.plugins.github.webhook.WebhookManager$1.run(WebhookManager.java:127) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:119) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) {code } } The error messages appeared every time my github organizations were scanning, every 2 minutes. Again, I did not have manage hooks enabled for my github server or pull request builder configurations.I generated a brand new github token for jenkins, which I made sure had the right permissions, but the errors persisted after saving it (and then restarting jenkins for good measure). The funny thing was Github reported the token was 'never used' after the errors were being thrown - it only said the token was used once I went back to Jenkins configuration and hit the 'test connection' to github button. Related possibly considering the 'null' parts of the stacktrace.
[JIRA] (JENKINS-17809) Problem executing commands on Windows over SSH
Title: Message Title Alex Earl commented on JENKINS-17809 Re: Problem executing commands on Windows over SSH Thanks for following up after 5 years! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49332) Jenkins unable to manage webhooks of Github organization
Title: Message Title
Adam BH edited a comment on JENKINS-49332
Re: Jenkins unable to manage webhooks of Github organization
Same message after upgrading to Github plugin 1.29.Also Enterprise Github instance.Manage web hooks in Github pull request builder: DisabledManage hooks under github server: DisabledError messages persist after disabling both manage web hook check boxes.Work around: I downgraded back to the last version I used, 1.28.1, which got rid of the message spam. Jenkins+Github worked even when I got the error messages, except things seemed a bit slower.Here is a full stack trace from the error I got on 1.29, server, org, and repo names removed: ``` {{ org.jenkinsci.plugins.github.webhook.WebhookManager$2 applyNullSafeWARNING: Failed to add GitHub webhook for GitHubRepositoryName[host=github.XXX.com,username=orgName,repository=repoName]java.lang.NullPointerException: There is no credentials with admin access to manage hooks on GitHubRepositoryName[host=github.XXX.com,username=orgName,repository=repoName] at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:231) at org.jenkinsci.plugins.github.webhook.WebhookManager$2.applyNullSafe(WebhookManager.java:179) at org.jenkinsci.plugins.github.webhook.WebhookManager$2.applyNullSafe(WebhookManager.java:175) at org.jenkinsci.plugins.github.util.misc.NullSafeFunction.apply(NullSafeFunction.java:18) at com.google.common.collect.Iterators$8.next(Iterators.java:812) at com.google.common.collect.Iterators$7.computeNext(Iterators.java:648) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at com.google.common.collect.Iterators$7.computeNext(Iterators.java:647) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at com.google.common.collect.Lists.newArrayList(Lists.java:138) at com.google.common.collect.Lists.newArrayList(Lists.java:119) at org.jenkinsci.plugins.github.util.FluentIterableWrapper.toList(FluentIterableWrapper.java:147) at org.jenkinsci.plugins.github.webhook.WebhookManager$1.run(WebhookManager.java:127) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:119) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) }} ``` The error messages appeared every time my github organizations were scanning, every 2 minutes. Again, I did not have manage hooks enabled for my github server or pull request builder configurations.I generated a brand new github token for jenkins, which I made sure had the right permissions, but the errors persisted after saving it (and then restarting jenkins for good measure). The funny thing was Github reported the token was 'never used' after the errors were being thrown - it only said the token was used once I went back to Jenkins configuration and hit the 'test connection' to github button. Related possibly considering the 'null' parts of the stacktrace.
[JIRA] (JENKINS-49332) Jenkins unable to manage webhooks of Github organization
Title: Message Title Adam BH commented on JENKINS-49332 Re: Jenkins unable to manage webhooks of Github organization Same message after upgrading to Github plugin 1.29. Also Enterprise Github instance. Manage web hooks in Github pull request builder: Disabled Manage hooks under github server: Disabled Error messages persist after disabling both manage web hook check boxes. Work around: I downgraded back to the last version I used, 1.28.1, which got rid of the message spam. Jenkins+Github worked even when I got the error messages, except things seemed a bit slower. Here is a full stack trace from the error I got on 1.29, server, org, and repo names removed: ``` org.jenkinsci.plugins.github.webhook.WebhookManager$2 applyNullSafe WARNING: Failed to add GitHub webhook for GitHubRepositoryName[host=github.XXX.com,username=orgName,repository=repoName] java.lang.NullPointerException: There is no credentials with admin access to manage hooks on GitHubRepositoryName[host=github.XXX.com,username=orgName,repository=repoName] at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:231) at org.jenkinsci.plugins.github.webhook.WebhookManager$2.applyNullSafe(WebhookManager.java:179) at org.jenkinsci.plugins.github.webhook.WebhookManager$2.applyNullSafe(WebhookManager.java:175) at org.jenkinsci.plugins.github.util.misc.NullSafeFunction.apply(NullSafeFunction.java:18) at com.google.common.collect.Iterators$8.next(Iterators.java:812) at com.google.common.collect.Iterators$7.computeNext(Iterators.java:648) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at com.google.common.collect.Iterators$7.computeNext(Iterators.java:647) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at com.google.common.collect.Lists.newArrayList(Lists.java:138) at com.google.common.collect.Lists.newArrayList(Lists.java:119) at org.jenkinsci.plugins.github.util.FluentIterableWrapper.toList(FluentIterableWrapper.java:147) at org.jenkinsci.plugins.github.webhook.WebhookManager$1.run(WebhookManager.java:127) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:119) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) ``` The error messages appeared every time my github organizations were scanning, every 2 minutes. Again, I did not have manage hooks enabled for my github server or pull request builder configurations. I generated a brand new github token for jenkins, which I made sure had the right permissions, but the errors persisted after saving it (and then restarting jenkins for good measure). The funny thing was Github reported the token was 'never used' after the errors were being thrown - it only said the token was used once I went back to Jenkins configuration and hit the 'test connection' to github button. Related possibly considering the 'null' parts of the stacktrace.
[JIRA] (JENKINS-40912) Add verbose option to stash/unstash to get list of files
Title: Message Title Andrew Bayer commented on JENKINS-40912 Re: Add verbose option to stash/unstash to get list of files Ok, this sucker is back in the "I dunno what to do" state. There's continued uncertainty as to what exactly Sparkle Pony and everyone else would actually like - my PRs switch stash and unstash to return a list of the files affected - does that meet your requirements? Or would you prefer logging the files with a verbose option? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40912) Add verbose option to stash/unstash to get list of files
Title: Message Title Andrew Bayer stopped work on JENKINS-40912 Change By: Andrew Bayer Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40912) Add verbose option to stash/unstash to get list of files
Title: Message Title Andrew Bayer updated JENKINS-40912 Jenkins / JENKINS-40912 Add verbose option to stash/unstash to get list of files Change By: Andrew Bayer Status: In Review Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43073) Old syntax not honored for explicit single required parameter taking struct
Title: Message Title Andrew Bayer resolved as Duplicate This was actually a dupe of JENKINS-38169, which was fixed in workflow-cps 2.17. Jenkins / JENKINS-43073 Old syntax not honored for explicit single required parameter taking struct Change By: Andrew Bayer Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-46785) add a way to disable all reporters (and selectively enable a few)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-46785 Re: add a way to disable all reporters (and selectively enable a few) Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/MavenPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/MavenPublisherStrategy.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/MavenSpyLogProcessor.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/WithMavenStep.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/WithMavenStepExecution.java jenkins-plugin/src/main/resources/org/jenkinsci/plugins/pipeline/maven/WithMavenStep/config.jelly jenkins-plugin/src/main/resources/org/jenkinsci/plugins/pipeline/maven/WithMavenStep/help-publisherStrategy.html jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/MavenPublisherStrategyTest.java jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/MavenPublisherTest.java jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/WithMavenStepTest.java http://jenkins-ci.org/commit/pipeline-maven-plugin/1d0617207186decf257afc2d8b08ad454c319109 Log: JENKINS-46785 Strategy to enable / disable publishers in pipelines Compare: https://github.com/jenkinsci/pipeline-maven-plugin/compare/586c9f75a5f3...1d0617207186 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
