[JIRA] (JENKINS-57566) Default security prohibits ResultAction's getResult
Title: Message Title David Wright commented on JENKINS-57566 Re: Default security prohibits ResultAction's getResult Thank you, that would be great! I think a list of actions would be most practical. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199480.1558369817000.2493.1578296880535%40Atlassian.JIRA.
[JIRA] (JENKINS-56740) Artifacts bigger than 5GB can't be uploaded to S3
Title: Message Title D Stanhope commented on JENKINS-56740 Re: Artifacts bigger than 5GB can't be uploaded to S3 Here's a generalised version: Copy-ToAwsS3.psm1 Documentation is in the file. Note that you'll probably want to find a different way of handling credentials than what that file implements, or at least switch to using PowerShell Secure Strings Hope that helps! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198381.1553514809000.2489.1578295200139%40Atlassian.JIRA.
[JIRA] (JENKINS-60641) IllegalArgumentException: No script is provided
Title: Message Title Ronny Borchert created an issue Jenkins / JENKINS-60641 IllegalArgumentException: No script is provided Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-01-06 07:18 Priority: Minor Reporter: Ronny Borchert After updating jenkins.war from 2.210 to 2.212 jenkins is not booting up properly. It looks like that mainly user configs of users which are not in company anymore, but also a few users which are still here. I didn't test 2.211! error from log: 2020-01-06 06:31:41.056+ [id=26] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Finalizing set up2020-01-06 06:31:41.056+ [id=26] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Finalizing set upjava.lang.IllegalArgumentException: No script is provided at hudson.util.spring.BeanBuilder.parse(BeanBuilder.java:130) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm.createSecurityComponents(ActiveDirectorySecurityRealm.java:340) at hudson.security.SecurityRealm.getSecurityComponents(SecurityRealm.java:487) at hudson.security.HudsonFilter.reset(HudsonFilter.java:138) at jenkins.model.Jenkins.setSecurityRealm(Jenkins.java:2590) at jenkins.model.Jenkins$16.run(Jenkins.java:3287) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1142) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)2020-01-06 06:31:41.056+ [id=18] SEVERE hudson.util.BootFailure#publish: Failed to initialize Jenkinsjava.lang.IllegalArgumentException: No script is provided at hudson.util.spring.BeanBuilder.parse(BeanBuilder.java:130) at
[JIRA] (JENKINS-56740) Artifacts bigger than 5GB can't be uploaded to S3
Title: Message Title D Stanhope updated an issue Jenkins / JENKINS-56740 Artifacts bigger than 5GB can't be uploaded to S3 Change By: D Stanhope Attachment: Copy-ToAwsS3.psm1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198381.1553514809000.2485.1578294900269%40Atlassian.JIRA.
[JIRA] (JENKINS-50331) JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen
Title: Message Title Owen Mehegan commented on JENKINS-50331 Re: JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen Jason Prickett I assigned this ticket to you because you've made sone of the most recent commits to this plugin, whereas the 'redsolo' user this was assigned to has not been active in this Jira instance since 2014. I hope that's OK. If you or one of the other current maintainers of the plugin should be made the default assignee for new issues, let me know and I can change that setting. CloudBees Support has received a case from a customer who is affected by this bug, so I was hoping to get some attention on it, since we do not maintain this plugin. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189378.1521699501000.2475.1578283860373%40Atlassian.JIRA.
[JIRA] (JENKINS-35432) Scheduled builds crash after running for more than 8 hours
Title: Message Title Owen Mehegan assigned an issue to Jason Prickett Jenkins / JENKINS-35432 Scheduled builds crash after running for more than 8 hours Change By: Owen Mehegan Assignee: Kellie Jos Jason Prickett Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.171228.146531923.2461.1578283628817%40Atlassian.JIRA.
[JIRA] (JENKINS-50331) JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen
Title: Message Title Owen Mehegan assigned an issue to Jason Prickett Jenkins / JENKINS-50331 JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen Change By: Owen Mehegan Assignee: redsolo Jason Prickett Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189378.1521699501000.2449.1578283500689%40Atlassian.JIRA.
[JIRA] (JENKINS-41664) Blue Ocean fails to load in MS Edge (Eventsource)
Title: Message Title Ning Zhang commented on JENKINS-41664 Re: Blue Ocean fails to load in MS Edge (Eventsource) This issue is reproduced again. MS edge: Microsoft Edge 41.16299.1480.0 Microsoft EdgeHTML 16.16299 BlueOcean: 1.21.0 · Core 2.190.1 Should I create one new ticket? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178492.1486049772000.2437.1578277500321%40Atlassian.JIRA.
[JIRA] (JENKINS-60412) Additional behavior "Discover open changes" not working for using Gerrit as SCM in Jenkins Shared Library configuration
Title: Message Title Felipe Santos commented on JENKINS-60412 Re: Additional behavior "Discover open changes" not working for using Gerrit as SCM in Jenkins Shared Library configuration Checked, everything works fine without having to specify any Refspec, just by using the addiotional behavior "Discover open changes" Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203469.1575926699000.2434.1578275940119%40Atlassian.JIRA.
[JIRA] (JENKINS-60364) Environment variables not being set when Gerrit 2.14
Title: Message Title Felipe Santos commented on JENKINS-60364 Re: Environment variables not being set when Gerrit 2.14 I think this Issue can be closed now, don't you think? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203387.1575461562000.2432.1578274200218%40Atlassian.JIRA.
[JIRA] (JENKINS-60624) Repo not maintained anymore?
Title: Message Title Callum Pember closed an issue as Fixed Jenkins / JENKINS-60624 Repo not maintained anymore? Change By: Callum Pember Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203857.1578001388000.2430.1578270720200%40Atlassian.JIRA.
[JIRA] (JENKINS-60624) Repo not maintained anymore?
Title: Message Title Callum Pember resolved as Fixed Jenkins / JENKINS-60624 Repo not maintained anymore? Change By: Callum Pember Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203857.1578001388000.2428.1578270600179%40Atlassian.JIRA.
[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title ilya s commented on JENKINS-44930 Re: Allow sh to return exit status, stdout and stderr all at once Here's my use case for this: aws ecr describe-repositories --repository-names foo I want to check if a Docker repository exists. On success, this command returns a JSON blob in stdout. On failure, it returns a string into stderr. As of right now, what should be a simple case of pattern-matching on the stderr content when exit code != 0 turns into something completely different. I've not yet came to a solution, but it's disappointing that what looks like shell invocation step behaves nothing like the shell in practice. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183003.149756330.2426.1578268383396%40Atlassian.JIRA.
[JIRA] (JENKINS-57931) Add more information about gerrit change
Title: Message Title Luca Domenico Milanesio commented on JENKINS-57931 Re: Add more information about gerrit change The compatibility with Gerrit v2.14 should be fixed with the plugin v0.4.x, you could try even now Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199905.1560152908000.2326.1578258660231%40Atlassian.JIRA.
[JIRA] (JENKINS-57931) Add more information about gerrit change
Title: Message Title Mariusz Markowski commented on JENKINS-57931 Re: Add more information about gerrit change Sorry for not responding. We were using Gerrit 2.14 but now switched to 2.16. We still use old version of the Gerrit Trigger Plugin. When we upgrade to newest version I will confirm if all variables are available. Thank you for help. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199905.1560152908000.2324.1578256500283%40Atlassian.JIRA.
[JIRA] (JENKINS-48975) Jenkins build using TOPIC
Title: Message Title Luca Domenico Milanesio commented on JENKINS-48975 Re: Jenkins build using TOPIC I believe this is more a problem on the multi-branch pipeline concept in Jenkins: where would the Jenkinsfile be stored? one repo? both? Where would you fetch the pipelines from? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187789.1516132931000.2320.1578252600111%40Atlassian.JIRA.
[JIRA] (JENKINS-49897) gerrit-plugin pr branch names are incorrectly name
Title: Message Title Luca Domenico Milanesio commented on JENKINS-49897 Re: gerrit-plugin pr branch names are incorrectly name What would be the point of re-triggering a build for an obsolete patch-set? Can you point me to the statistics that would be useful if we would keep the same job for the same change? (URL of the feature you would have the associated benefits?) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.11.1520103505000.2315.1578252540160%40Atlassian.JIRA.
[JIRA] (JENKINS-54214) NPE when no credentials provided on Gerrit SCM URL for Declarative Pipeline
Title: Message Title Luca Domenico Milanesio resolved as Fixed This should be working now. Jenkins / JENKINS-54214 NPE when no credentials provided on Gerrit SCM URL for Declarative Pipeline Change By: Luca Domenico Milanesio Status: Open Resolved Resolution: Fixed Released As: 0.4.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message
[JIRA] (JENKINS-54721) Show changelog messages for review changes
Title: Message Title Luca Domenico Milanesio commented on JENKINS-54721 Re: Show changelog messages for review changes Yes, agreed. So that when you go to BueOcean to the list of PRs (changes) you'll have a bit more context. Thanks for the suggestion, good idea indeed. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195523.1542709555000.2311.1578252300112%40Atlassian.JIRA.
[JIRA] (JENKINS-55037) Allow configuration/filtering of detected Changes
Title: Message Title Luca Domenico Milanesio commented on JENKINS-55037 Re: Allow configuration/filtering of detected Changes If you look at the latest version (0.4.1) the WIP state is in the list of environment variables available to the job: https://github.com/jenkinsci/gerrit-code-review-plugin/blob/master/BUILD.md Would that be enough to cover your use-case? I would also add a trait for skipping WIP changes altogether, WDYT? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196079.1544027495000.2309.1578252240259%40Atlassian.JIRA.
[JIRA] (JENKINS-57931) Add more information about gerrit change
Title: Message Title Luca Domenico Milanesio commented on JENKINS-57931 Re: Add more information about gerrit change Ping? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199905.1560152908000.2306.1578252060145%40Atlassian.JIRA.
[JIRA] (JENKINS-58547) Gerrit Branches are not fetched (got http 404)
Title: Message Title Luca Domenico Milanesio commented on JENKINS-58547 Re: Gerrit Branches are not fetched (got http 404) Ping? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200697.156345034.2304.1578252000179%40Atlassian.JIRA.
[JIRA] (JENKINS-58958) Use the same Jenkins workspace on a Change basis
Title: Message Title Luca Domenico Milanesio commented on JENKINS-58958 Re: Use the same Jenkins workspace on a Change basis Generally speaking, yes. However, this plugin uses the multi-branch pipeline which has a 1:1 representation between a child job and a branch. Because the branch is different, then the job is different. Does that makes sense? For reusing cached results of past builds, have you looked at Bazel? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201305.1565917678000.2302.1578251940190%40Atlassian.JIRA.
[JIRA] (JENKINS-60301) Cancel builds on new patch sets
Title: Message Title Luca Domenico Milanesio commented on JENKINS-60301 Re: Cancel builds on new patch sets Yes, I did a bit of research and I came to the same conclusion: this is something for the computed-folder-plugin rather than the gerrit-code-review plugin. It should be reported and resolved there, as the strategy for stopping the job when it becomes orphan should be done in that class. WDYT? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203296.1574859139000.2298.1578251820165%40Atlassian.JIRA.
[JIRA] (JENKINS-60638) Fix jiraTransitionIssue code samples in documentation
Title: Message Title Arjun Gopisetty assigned an issue to Naresh Rayapati Jenkins / JENKINS-60638 Fix jiraTransitionIssue code samples in documentation Change By: Arjun Gopisetty Assignee: Arjun Gopisetty Naresh Rayapati Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203875.1578171274000.2292.1578249180626%40Atlassian.JIRA.
[JIRA] (JENKINS-60638) Fix jiraTransitionIssue code samples in documentation
Title: Message Title Arjun Gopisetty updated JENKINS-60638 Jenkins / JENKINS-60638 Fix jiraTransitionIssue code samples in documentation Change By: Arjun Gopisetty Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203875.1578171274000.2296.1578249180721%40Atlassian.JIRA.
[JIRA] (JENKINS-60638) Fix jiraTransitionIssue code samples in documentation
Title: Message Title Arjun Gopisetty updated JENKINS-60638 Jenkins / JENKINS-60638 Fix jiraTransitionIssue code samples in documentation Change By: Arjun Gopisetty Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203875.1578171274000.2294.1578249180680%40Atlassian.JIRA.
[JIRA] (JENKINS-60473) Docker pipeline: 'absolute path' error when running linux container under windows host
Title: Message Title
Eric Schneider edited a comment on JENKINS-60473
Re: Docker pipeline: 'absolute path' error when running linux container under windows host
[~bobby013]Thank you for the detailed notes. When I run your pipeline example, it does work for me. I need to figure out what's different in your environment.The path that you bolded is correct. If you look at the "docker run" command in the log, you can see that the workspace path from the Windows host is being mounted via a volume to that path in the Linux container. The path is translated into something Linux-friendly. For example: C:\this\path becomes /c/this/path. Even though your path is is Windows-y, it doesn't really matter. The path can be arbitrary.What's unfortunate is that the sh command doesn't output the command it runs into the job log. It's difficult to capture. I'm including directions here in case you want to try. Navigate to "Managed Jenkins" > "System Log" > "Add new log recorder". Give it any name and click "OK". Under "Loggers" add "hudson" and "org.jenkinsci.plugins". Ensure that the log level is "ALL" for both. Save the recorder. This should open the log. Run your test job and right when it gets to the 'sh' step, refresh the log. Search the output for "docker" and see if you can find the "docker exec" line in the log. It can be hard to capture, since the log only shows a small number of lines. Here's an example from my log:{ noformat code:java }docker exec --env BUILD_DISPLAY_NAME=#4 --env BUILD_ID=4 --env BUILD_NUMBER=4 --env BUILD_TAG=jenkins-Parenthesis Test (wee)-4 --env BUILD_URL=http://example.com/job/Parenthesis%20Test%20(wee)/4/ --env CLASSPATH= --env EXECUTOR_NUMBER=2 --env HUDSON_HOME=/var/lib/jenkins --env HUDSON_SERVER_COOKIE=a78bfd62731ccf0a --env HUDSON_URL=http://example.com/ --env JENKINS_NODE_COOKIE=06d630b9-7764-43ee-85e0-eb9a26bcc2d2 --env JENKINS_SERVER_COOKIE=please-do-not-kill-me --env JENKINS_URL=http://example.com/ --env JOB_BASE_NAME=Parenthesis Test (wee) --env JOB_DISPLAY_URL=http://example.com/job/Parenthesis%20Test%20(wee)/display/redirect --env JOB_NAME=Parenthesis Test (wee) --env JOB_URL=http://example.com/job/Parenthesis%20Test%20(wee)/ --env NODE_LABELS=localhost master --env NODE_NAME=master --env RUN_CHANGES_DISPLAY_URL=http://example.com/job/Parenthesis%20Test%20(wee)/4/display/redirect?page=changes --env RUN_DISPLAY_URL=http://example.com/job/Parenthesis%20Test%20(wee)/4/display/redirect --env STAGE_NAME=Test --env WORKSPACE=/var/lib/jenkins/workspace/Parenthesis Test (wee) --env library.migration-library.version=master 63c3793d8f3730cafcc37fb3e495d25ec8e520d12cf9a599342697fc64616393 nohup sh -c ({ while [ -d '/var/lib/jenkins/workspace/Parenthesis Test (wee)@tmp/durable-11d2bcc9' -a \! -f '/var/lib/jenkins/workspace/Parenthesis Test (wee)@tmp/durable-11d2bcc9/jenkins-result.txt' ]; do touch '/var/lib/jenkins/workspace/Parenthesis Test (wee)@tmp/durable-11d2bcc9/jenkins-log.txt'; sleep 3; done } & jsc=durable-27a2324005ef9d26531c4508bfcb22d4; JENKINS_SERVER_COOKIE=$jsc 'sh' -xe '/var/lib/jenkins/workspace/Parenthesis Test (wee)@tmp/durable-11d2bcc9/script.sh' > '/var/lib/jenkins/workspace/Parenthesis Test (wee)@tmp/durable-11d2bcc9/jenkins-log.txt' 2>&1; echo $? > '/var/lib/jenkins/workspace/Parenthesis Test (wee)@tmp/durable-11d2bcc9/jenkins-result.txt.tmp'; mv '/var/lib/jenkins/workspace/Parenthesis Test (wee)@tmp/durable-11d2bcc9/jenkins-result.txt.tmp' '/var/lib/jenkins/workspace/Parenthesis Test (wee)@tmp/durable-11d2bcc9/jenkins-result.txt'; wait) >&- 2>&- & { noformat code }This would be the command where the job gets stuck and needs to be troubleshooted. You can try running this manually on
[JIRA] (JENKINS-60473) Docker pipeline: 'absolute path' error when running linux container under windows host
Title: Message Title
Eric Schneider commented on JENKINS-60473
Re: Docker pipeline: 'absolute path' error when running linux container under windows host
Robert Hecker Thank you for the detailed notes. When I run your pipeline example, it does work for me. I need to figure out what's different in your environment. The path that you bolded is correct. If you look at the "docker run" command in the log, you can see that the workspace path from the Windows host is being mounted via a volume to that path in the Linux container. The path is translated into something Linux-friendly. For example: C:\this\path becomes /c/this/path. Even though your path is is Windows-y, it doesn't really matter. The path can be arbitrary. What's unfortunate is that the sh command doesn't output the command it runs into the job log. It's difficult to capture. I'm including directions here in case you want to try. Navigate to "Managed Jenkins" > "System Log" > "Add new log recorder". Give it any name and click "OK". Under "Loggers" add "hudson" and "org.jenkinsci.plugins". Ensure that the log level is "ALL" for both. Save the recorder. This should open the log. Run your test job and right when it gets to the 'sh' step, refresh the log. Search the output for "docker" and see if you can find the "docker exec" line in the log. It can be hard to capture, since the log only shows a small number of lines. Here's an example from my log:
docker exec --env BUILD_DISPLAY_NAME=#4 --env BUILD_ID=4 --env BUILD_NUMBER=4 --env BUILD_TAG=jenkins-Parenthesis Test (wee)-4 --env BUILD_URL=http://example.com/job/Parenthesis%20Test%20(wee)/4/ --env CLASSPATH= --env EXECUTOR_NUMBER=2 --env HUDSON_HOME=/var/lib/jenkins --env HUDSON_SERVER_COOKIE=a78bfd62731ccf0a --env HUDSON_URL=http://example.com/ --env JENKINS_NODE_COOKIE=06d630b9-7764-43ee-85e0-eb9a26bcc2d2 --env JENKINS_SERVER_COOKIE=please-do-not-kill-me --env JENKINS_URL=http://example.com/ --env JOB_BASE_NAME=Parenthesis Test (wee) --env JOB_DISPLAY_URL=http://example.com/job/Parenthesis%20Test%20(wee)/display/redirect --env JOB_NAME=Parenthesis Test (wee) --env JOB_URL=http://example.com/job/Parenthesis%20Test%20(wee)/ --env NODE_LABELS=localhost master --env NODE_NAME=master --env RUN_CHANGES_DISPLAY_URL=http://example.com/job/Parenthesis%20Test%20(wee)/4/display/redirect?page=changes --env RUN_DISPLAY_URL=http://example.com/job/Parenthesis%20Test%20(wee)/4/display/redirect --env STAGE_NAME=Test --env WORKSPACE=/var/lib/jenkins/workspace/Parenthesis Test (wee) --env library.migration-library.version=master 63c3793d8f3730cafcc37fb3e495d25ec8e520d12cf9a599342697fc64616393 nohup sh -c ({ while [ -d '/var/lib/jenkins/workspace/Parenthesis Test (wee)@tmp/durable-11d2bcc9' -a \! -f '/var/lib/jenkins/workspace/Parenthesis Test (wee)@tmp/durable-11d2bcc9/jenkins-result.txt' ]; do touch '/var/lib/jenkins/workspace/Parenthesis Test (wee)@tmp/durable-11d2bcc9/jenkins-log.txt'; sleep 3; done } & jsc=durable-27a2324005ef9d26531c4508bfcb22d4; JENKINS_SERVER_COOKIE=$jsc 'sh' -xe '/var/lib/jenkins/workspace/Parenthesis Test (wee)@tmp/durable-11d2bcc9/script.sh' > '/var/lib/jenkins/workspace/Parenthesis Test (wee)@tmp/durable-11d2bcc9/jenkins-log.txt' 2>&1; echo $? > '/var/lib/jenkins/workspace/Parenthesis Test (wee)@tmp/durable-11d2bcc9/jenkins-result.txt.tmp'; mv '/var/lib/jenkins/workspace/Parenthesis Test (wee)@tmp/durable-11d2bcc9/jenkins-result.txt.tmp' '/var/lib/jenkins/workspace/Parenthesis Test
[JIRA] (JENKINS-60412) Additional behavior "Discover open changes" not working for using Gerrit as SCM in Jenkins Shared Library configuration
Title: Message Title Luca Domenico Milanesio commented on JENKINS-60412 Re: Additional behavior "Discover open changes" not working for using Gerrit as SCM in Jenkins Shared Library configuration Felipe Santos can you check again now with v0.4.1? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203469.1575926699000.2280.1578247920122%40Atlassian.JIRA.
[JIRA] (JENKINS-60638) Fix jiraTransitionIssue code samples in documentation
Title: Message Title
Arjun Gopisetty updated an issue
Jenkins / JENKINS-60638
Fix jiraTransitionIssue code samples in documentation
Change By:
Arjun Gopisetty
The [Releasing a project?|[https://jenkinsci.github.io/jira-steps-plugin/getting-started/examples/release_project/]] example and [the project homepage|[https://jenkinsci.github.io/jira-steps-plugin/]] code examples contains the following lines:{code:java}def transitionInput = [transition: [name: 'Close']]jiraTransitionIssue idOrKey: issueKey, input: transitionInput{code} {code:java} def transitionInput = [ transition: [ name: 'Close'] ] jiraTransitionIssue idOrKey: 'RELEASE-999', input: transitionInput, site: 'YOURJIRASITE'{code} However, this is not valid for the Jira API endpoint: [https://developer.atlassian.com/cloud/jira/platform/rest/v2/#api-rest-api-2-issue-issueIdOrKey-transitions-post.|https://developer.atlassian.com/cloud/jira/platform/rest/v2/#api-rest-api-2-issue-issueIdOrKey-transitions-post] The *IssueTransition* parameter only takes the ID of the issue transition. The documentation needs to be corrected so the function call works.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60638) Fix jiraTransitionIssue code samples in documentation
Title: Message Title Arjun Gopisetty updated an issue Jenkins / JENKINS-60638 Fix jiraTransitionIssue code samples in documentation Change By: Arjun Gopisetty Summary: Example on "Releasing a project" is incorrect Fix jiraTransitionIssue code samples in documentation Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203875.1578171274000.2277.1578246600077%40Atlassian.JIRA.
[JIRA] (JENKINS-60624) Repo not maintained anymore?
Title: Message Title Rik Turnbull commented on JENKINS-60624 Re: Repo not maintained anymore? Great! Thanks for testing Callum - I've released the changes now Cheers, Rik. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203857.1578001388000.2276.1578245700194%40Atlassian.JIRA.
[JIRA] (JENKINS-60640) Support rename job and sync it in pipeline module in ALM Octane
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-60640 Support rename job and sync it in pipeline module in ALM Octane Issue Type: Improvement Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2020-01-05 15:42 Priority: Minor Reporter: Radi Berkovich Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message
