[JIRA] (JENKINS-54260) Fails when notifying for merged PR build
Title: Message Title Sean MacKay created an issue Jenkins / JENKINS-54260 Fails when notifying for merged PR build Issue Type: Bug Assignee: Antonio Mansilla Components: bitbucket-build-status-notifier-plugin Created: 2018-10-25 23:11 Priority: Minor Reporter: Sean MacKay Flagged as minor because one workaround is just not to merge your PRs before building (losing the functionality of testing the merge result also builds). There may also be a way to tell the jenkinsfile to only notify if it's not a merged PR build. The Bitbucket Build Status Notifier Plugin fails when building a PR with the "Merging the pull request with the current target branch revision" PR policy, with the following error: [Bitbucket] Notifying pull request build result [Bitbucket] Build result notified Also: java.lang.Exception: None or multiple repos java.lang.Exception: None or multiple repos at org.jenkinsci.plugins.bitbucket.scm.GitScmAdapter.getCommitRepoMap(GitScmAdapter.java:53) at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper.createBuildStatusResources(BitbucketBuildStatusHelper.java:87) at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper.createBuildStatusResources(BitbucketBuildStatusHelper.java:140) at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper.notifyBuildStatus(BitbucketBuildStatusHelper.java:231) at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifierStep$Execution.run(BitbucketBuildStatusNotifierStep.java:206) at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifierStep$Execution.run(BitbucketBuildStatusNotifierStep.java:152) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at
[JIRA] (JENKINS-41147) bitbucket-build-status-notifier-plugin fails for multiple Git repo
Title: Message Title Sean MacKay commented on JENKINS-41147 Re: bitbucket-build-status-notifier-plugin fails for multiple Git repo I get this error when merging my PR branches together before running the build. I think the notifier does not know which branch to send notifications for since it's a merged commit that isn't in the bitbucket remote. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51091) Make test results available on currentBuild
Title: Message Title
Sean MacKay commented on JENKINS-51091
Re: Make test results available on currentBuild
Interesting, so do none of the test results pages in normal or Blue Ocean UI function without the junit plugin? Or is the way the data is eventually saved into the finished build just even harder to access? I assumed the workaround with AbstractTestResultAction pulled the results from the same final location which both nunit and junit post to, but I haven't tested to confirm so I'm not sure. And that's interesting. I assume you could use it in a scripting pipeline like this. Does the same work in Declarative pipeline?
def results = junit '*.xml';
sh "echo ${results.getFailCount()}"
Unfortunately the `nunit` plugin doesn't seem to behave the same way (I use both). Yet it still posts the results to the same final place, so those results should still be available from one location regardless of which plugin posts there. That's why I assumed there would be a way to read them, but I don't know enough about the architecture in place to really be sure of anything. I'll do some testing and see if I can at least confirm what the behaviour of each approach is.
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
[JIRA] (JENKINS-51091) Make test results available on currentBuild
Title: Message Title Sean MacKay created an issue Jenkins / JENKINS-51091 Make test results available on currentBuild Issue Type: New Feature Assignee: Unassigned Components: pipeline Created: 2018-05-02 20:05 Priority: Minor Reporter: Sean MacKay Currently, as described here, the only way to get the archived test results in a Pipeline job is through the currentBuild.rawBuild object and pulling an AbstractTestResultAction out of it to read test results. This involved whitelisting several external methods. This is a lot of work to try and say, generate a slack message saying "Build BUILD failed, X/Y tests failed". How hard would it be to define a property on the currentBuild Global Variable live this: currentBuild.testResult.failCount ? Add Comment
[JIRA] (JENKINS-47179) Can't use milestone with parallel stages in Declarative
Title: Message Title Sean MacKay edited a comment on JENKINS-47179 Re: Can't use milestone with parallel stages in Declarative I'm just bumping up against this as well. I'm trying to set up deployments in a Declarative Pipeline. Really I just need some logic to go "If `develop`, then `DevServer`, if `release/*` then `stagingServer`. Multiple `when` calls don't work in a stage, so I switch to a `parallel` block where each path has a `when` and only one should ever execute. Putting the `milestone` before `parallel` could work (as long as different branches don't cancel each other), but a milestone in each deployment branch would be more ideal. Is there some other way I could structure my "If this branch deploy here" logic to avoid `parallel` altogether? edit: Just using a `script` step might be the easiest way to do what I need. 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-47179) Can't use milestone with parallel stages in Declarative
Title: Message Title Sean MacKay commented on JENKINS-47179 Re: Can't use milestone with parallel stages in Declarative I'm just bumping up against this as well. I'm trying to set up deployments in a Declarative Pipeline. Really I just need some logic to go "If `develop`, then `DevServer`, if `release/*` then `stagingServer`. Multiple `when` calls don't work in a stage, so I switch to a `parallel` block where each path has a `when` and only one should ever execute. Putting the `milestone` before `parallel` could work (as long as different branches don't cancel each other), but a milestone in each deployment branch would be more ideal. Is there some other way I could structure my "If this branch deploy here" logic to avoid `parallel` altogether? 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-27039) Option for input or stage step to cancel older executions
Title: Message Title Sean MacKay updated JENKINS-27039 Jenkins / JENKINS-27039 Option for input or stage step to cancel older executions Change By: Sean MacKay Status: Resolved In 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-42692) When git fetch fails in Scan Multibranch Pipeline fails, the job never stops
Title: Message Title Sean MacKay updated an issue Jenkins / JENKINS-42692 When git fetch fails in Scan Multibranch Pipeline fails, the job never stops I'm going to downgrade to minor because solving the underlying issrom preventing the use of Jenkins. Change By: Sean MacKay Priority: Major Minor 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-42692) When git fetch fails in Scan Multibranch Pipeline fails, the job never stops
Title: Message Title Sean MacKay commented on JENKINS-42692 Re: When git fetch fails in Scan Multibranch Pipeline fails, the job never stops You appear to be correct. The job not terminating correctly appears to be the crux of the issue. For completeness sake, the cause of my timeout above was the Git Credential Manager for windows attempting to pop up a username and password dialogue box, but being unable to do so as jenkins runs as the LOCAL_SYSTEM account on windows which does not have desktop access (even with it granted in the services config apparently). In the past I'd gotten around this popup by using a tool to spawn a cmd.exe process as LOCAL_SYSTEM but accessible by myself, then made the git checkout request and handled the dialog myself so it would be saved for Jenkins to use. However, it seems that expires. I removed git and reinstalled without the Git Credential Manager and the Jenkins credential config seems to work. So the error causing this error to occur has been solved for me, but the Jenkins job not ending correctly after an error is still a frustrating experience that can happen. 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-42692) When git fetch fails in Scan Multibranch Pipeline fails, the job never stops
Title: Message Title
Sean MacKay updated an issue
Jenkins / JENKINS-42692
When git fetch fails in Scan Multibranch Pipeline fails, the job never stops
Change By:
Sean MacKay
When running the `Scan Multibranch Pipeline` step of my multibranch pipeline (where I believe it fetches the branches to determine which contain a jenkinsfile and have not yet been run) The git fetch command is timing out. (This is probably a credentials or git plugin issue, and not the cause of this bug).The bug is that when I get the `ERROR: Timeout after 10 minutes` there is then an `ERROR: Failed to join a process` error, and that seems to lock the Build Executor threads. Preventing Jenkins from restarting even with the /restart url, and instead forcing me to kill the Java process before having it happen all over again. From /job/MYPipeline/indexing/console{noformat}Started by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timer[Sat Mar 11 12:14:25 EST 2017] Starting branch indexing...Setting origin to https://u...@bitbucket.org/TEAM/PROJECT.git > D:\Git\cmd\git.exe config remote.origin.url https://u...@bitbucket.org/TEAM/PROJECT.git # timeout=10Fetching & pruning origin...Fetching upstream changes from origin > D:\Git\cmd\git.exe --version # timeout=10using GIT_ASKPASS to set credentials MY_CREDENTIALS > D:\Git\cmd\git.exe fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* --pruneERROR: Timeout after 10 minutesERROR: Failed to join a processorg.jvnet.winp.WinpException: Failed to read RT_USER_PROCESS_PARAMETERS error=299 at envvar-cmdline.cpp:151 at org.jvnet.winp.Native.getCmdLineAndEnvVars(Native Method) at org.jvnet.winp.WinProcess.parseCmdLineAndEnvVars(WinProcess.java:126) at org.jvnet.winp.WinProcess.getCommandLine(WinProcess.java:102) at hudson.util.ProcessTree$Windows$1.getArguments(ProcessTree.java:444) at hudson.plugins.msbuild.MsBuildKillingVeto.vetoProcessKilling(MsBuildKillingVeto.java:56) at hudson.util.ProcessTree$OSProcess.getVeto(ProcessTree.java:242) at hudson.util.ProcessTree$Windows$1.killRecursively(ProcessTree.java:425) at hudson.util.ProcessTree.killAll(ProcessTree.java:145) at hudson.Proc$LocalProc.destroy(Proc.java:380) at hudson.Proc$LocalProc.kill(Proc.java:372) at hudson.Proc$1.run(Proc.java:159) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source){noformat} And from the other failing task:{noformat}Started by timer[Sat Mar 11 11:59:00 EST 2017] Starting branch indexing... > D:\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10Setting origin to https://u...@bitbucket.org/TEAM/PROJECT.git > D:\Git\cmd\git.exe config remote.origin.url
[JIRA] (JENKINS-42692) When git fetch fails in Scan Multibranch Pipeline fails, the job never stops
Title: Message Title
Sean MacKay updated an issue
Jenkins / JENKINS-42692
When git fetch fails in Scan Multibranch Pipeline fails, the job never stops
Change By:
Sean MacKay
When running the `Scan Multibranch Pipeline` step of my multibranch pipeline (where I believe it fetches the branches to determine which contain a jenkinsfile and have not yet been run) The git fetch command is timing out. (This is probably a credentials or git plugin issue, and not the cause of this bug).The bug is that when I get the `ERROR: Timeout after 10 minutes` there is then an `ERROR: Failed to join a process` error, and that seems to lock the Build Executor threads. Preventing Jenkins from restarting even with the /restart url, and instead forcing me to kill the Java process before having it happen all over again. From /job/MYPipeline/indexing/console {noformat}Started by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timer[Sat Mar 11 12:14:25 EST 2017] Starting branch indexing...Setting origin to https://u...@bitbucket.org/TEAM/PROJECT.git > D:\Git\cmd\git.exe config remote.origin.url https://u...@bitbucket.org/TEAM/PROJECT.git # timeout=10Fetching & pruning origin...Fetching upstream changes from origin > D:\Git\cmd\git.exe --version # timeout=10using GIT_ASKPASS to set credentials MY_CREDENTIALS > D:\Git\cmd\git.exe fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* --pruneERROR: Timeout after 10 minutesERROR: Failed to join a processorg.jvnet.winp.WinpException: Failed to read RT_USER_PROCESS_PARAMETERS error=299 at envvar-cmdline.cpp:151 at org.jvnet.winp.Native.getCmdLineAndEnvVars(Native Method) at org.jvnet.winp.WinProcess.parseCmdLineAndEnvVars(WinProcess.java:126) at org.jvnet.winp.WinProcess.getCommandLine(WinProcess.java:102) at hudson.util.ProcessTree$Windows$1.getArguments(ProcessTree.java:444) at hudson.plugins.msbuild.MsBuildKillingVeto.vetoProcessKilling(MsBuildKillingVeto.java:56) at hudson.util.ProcessTree$OSProcess.getVeto(ProcessTree.java:242) at hudson.util.ProcessTree$Windows$1.killRecursively(ProcessTree.java:425) at hudson.util.ProcessTree.killAll(ProcessTree.java:145) at hudson.Proc$LocalProc.destroy(Proc.java:380) at hudson.Proc$LocalProc.kill(Proc.java:372) at hudson.Proc$1.run(Proc.java:159) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source){noformat}!Locked_threads.png!When I went in to check today the job had been running for 4 days 4 hours.
[JIRA] (JENKINS-42692) When git fetch fails in Scan Multibranch Pipeline fails, the job never stops
Title: Message Title
Sean MacKay updated an issue
Jenkins / JENKINS-42692
When git fetch fails in Scan Multibranch Pipeline fails, the job never stops
Change By:
Sean MacKay
When running the `Scan Multibranch Pipeline` step of my multibranch pipeline (where I believe it fetches the branches to determine which contain a jenkinsfile and have not yet been run) The git fetch command is timing out. (This is probably a credentials or git plugin issue, and not the cause of this bug).The bug is that when I get the `ERROR: Timeout after 10 minutes` there is then an `ERROR: Failed to join a process` error, and that seems to lock the Build Executor threads. Preventing Jenkins from restarting even with the /restart url, and instead forcing me to kill the Java process before having it happen all over again. {noformat}Started by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timerStarted by timer[Sat Mar 11 12:14:25 EST 2017] Starting branch indexing...Setting origin to https://u...@bitbucket.org/TEAM/PROJECT.git > D:\Git\cmd\git.exe config remote.origin.url https://u...@bitbucket.org/TEAM/PROJECT.git # timeout=10Fetching & pruning origin...Fetching upstream changes from origin > D:\Git\cmd\git.exe --version # timeout=10using GIT_ASKPASS to set credentials MY_CREDENTIALS > D:\Git\cmd\git.exe fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* --pruneERROR: Timeout after 10 minutesERROR: Failed to join a processorg.jvnet.winp.WinpException: Failed to read RT_USER_PROCESS_PARAMETERS error=299 at envvar-cmdline.cpp:151 at org.jvnet.winp.Native.getCmdLineAndEnvVars(Native Method) at org.jvnet.winp.WinProcess.parseCmdLineAndEnvVars(WinProcess.java:126) at org.jvnet.winp.WinProcess.getCommandLine(WinProcess.java:102) at hudson.util.ProcessTree$Windows$1.getArguments(ProcessTree.java:444) at hudson.plugins.msbuild.MsBuildKillingVeto.vetoProcessKilling(MsBuildKillingVeto.java:56) at hudson.util.ProcessTree$OSProcess.getVeto(ProcessTree.java:242) at hudson.util.ProcessTree$Windows$1.killRecursively(ProcessTree.java:425) at hudson.util.ProcessTree.killAll(ProcessTree.java:145) at hudson.Proc$LocalProc.destroy(Proc.java:380) at hudson.Proc$LocalProc.kill(Proc.java:372) at hudson.Proc$1.run(Proc.java:159) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source){noformat}!Locked_threads.png!When I went in to check today the job had been running for 4 days 4 houors hours .
[JIRA] (JENKINS-42692) When git fetch fails in Scan Multibranch Pipeline fails, the job never stops
Title: Message Title Sean MacKay created an issue Jenkins / JENKINS-42692 When git fetch fails in Scan Multibranch Pipeline fails, the job never stops Issue Type: Bug Assignee: Matthew DeTullio Attachments: Locked_threads.png Components: core, multi-branch-project-plugin, pipeline-multibranch-defaults-plugin Created: 2017/Mar/11 6:18 PM Environment: Jenkins 2.32.2 LTS Windows Server 2012 R2 BitBucket Plugin 1.1.5 Blue Ocean Beta 1.0.0-b25 Pipeline 2.5 Pipeline Multibranch 2.14 Labels: Pipeline git-client Priority: Major Reporter: Sean MacKay When running the `Scan Multibranch Pipeline` step of my multibranch pipeline (where I believe it fetches the branches to determine which contain a jenkinsfile and have not yet been run) The git fetch command is timing out. (This is probably a credentials or git plugin issue, and not the cause of this bug). The bug is that when I get the `ERROR: Timeout after 10 minutes` there is then an `ERROR: Failed to join a process` error, and that seems to lock the Build Executor threads. Preventing Jenkins from restarting even with the /restart url, and instead forcing me to kill the Java process before having it happen all over again. Started
[JIRA] (JENKINS-38973) Multibranch-Pipeline Not Honoring Git Timeout
Title: Message Title Sean MacKay commented on JENKINS-38973 Re: Multibranch-Pipeline Not Honoring Git Timeout This is suddenly an issue for me. I'm not sure the timeout is the culprit, as it used to clone fine, but now some problem with the git fetch does cause the timeout to expire. Additionally, this doesn't read as a failure on the git fetch for the multibranch pipeline project, it just stays locked on this git fetch process preventing other jobs from running. Perhaps this is another issue that should have a new bug opened? 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.
