[JIRA] (JENKINS-61228) 有个问题咨询
Title: Message Title liu yuenwah created an issue Jenkins / JENKINS-61228 有个问题咨询 Issue Type: Task Assignee: Unassigned Attachments: image-2020-02-26-15-02-54-247.png, image-2020-02-26-15-03-22-871.png Components: pipeline Created: 2020-02-26 07:03 Priority: Minor Reporter: liu yuenwah 我想把参数化构建中的分支参数进行处理，由ref/remote/master处理为master以用于checkout，但不清楚声明式pipeline的语法该怎么处理，请协助，谢谢 Add Comment
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title Andrew Sumner commented on JENKINS-61167 Re: Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error It shouldn't be an issue with the .7z extension as this is packed into a universal package before being uploaded to proget, however I will do some testing to rule that out. 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.204701.1582203816000.6801.1582699920145%40Atlassian.JIRA.
[JIRA] (JENKINS-60240) XML parser crash
Title: Message Title Ronny Borchert commented on JENKINS-60240 Re: XML parser crash Today we had a stucking unit test. We have jobs with child jobs. The Xunit is in the child job. So I stopped the main job, but it look like the child job didn't. So I clicked on kill the child job too. Then it appears that jenkins was dead. Not sure if by killing main job or child job. No error in jenkins log file. In error log I see: Child process [3988 - H:\Jenkins\jre\bin\java -Dhttp.proxyHost=x.x.x.x -Dhttp.proxyPort=yyy -Xrs -Xmx512m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "H:\Jenkins\jenkins.war" --httpPort=8080] finished with -1073741510 The error code is in hex: 0xC13A So I guess 13A is 314 and from this page https://docs.microsoft.com/de-de/windows/win32/debug/system-error-codes--0-499- it is: ERROR_DISK_RESOURCES_EXHAUSTED 314 (0x13A) The physical resources of this disk have been exhausted. 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.203222.157433927.6799.1582699080191%40Atlassian.JIRA.
[JIRA] (JENKINS-43140) 404 error displayed on job configuration page
Title: Message Title Ajith Reddy reopened an issue I can still see the issue Jenkins / JENKINS-43140 404 error displayed on job configuration page Change By: Ajith Reddy Resolution: Fixed Status: Resolved Reopened 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/jenkinsc
[JIRA] (JENKINS-43140) 404 error displayed on job configuration page
Title: Message Title Ajith Reddy commented on JENKINS-43140 Re: 404 error displayed on job configuration page Issue still exists 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.180256.1490644133000.6791.1582692240250%40Atlassian.JIRA.
[JIRA] (JENKINS-60008) Build fails due to Distribution Group in AppCenter not having Correct Permissions
Title: Message Title Douglas Marques closed an issue as Fixed I am using the Jenkins Appcenter plugin to upload Android binaries but everytime I include the releaseNotes parameter I have errors on the Appcenter dashboard and I can't find the file that I've just upload but Jenkins console shows that the upload was successful Error on appcenter dashboard Jenkins / JENKINS-60008 Build fails due to Distribution Group in AppCenter not having Correct Permissions Change By: Douglas Marques Status: Resolved Closed Assignee: Mez Pahlan Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Bruno P. Kinoshita commented on JENKINS-61068 Re: Active Choices radio parameter has incorrect default value on parambuild URL Merged and added to the changelog for the next release. Thanks a lot Adam Gabryś! 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.204555.1581528008000.6785.1582689480092%40Atlassian.JIRA.
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-61068 Active Choices radio parameter has incorrect default value on parambuild URL Change By: Bruno P. Kinoshita Attachment: uno-choice.hpi 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.204555.1581528008000.6781.1582689420254%40Atlassian.JIRA.
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Bruno P. Kinoshita commented on JENKINS-61068 Re: Active Choices radio parameter has incorrect default value on parambuild URL Ioannis Moutsatsos, attached the plugin hpi file for testing: uno-choice.hpi 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.204555.1581528008000.6783.1582689420279%40Atlassian.JIRA.
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Bruno P. Kinoshita updated JENKINS-61068 Jenkins / JENKINS-61068 Active Choices radio parameter has incorrect default value on parambuild URL Change By: Bruno P. Kinoshita Status: Open Fixed but Unreleased 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.204555.1581528008000.6779.158260275%40Atlassian.JIRA.
[JIRA] (JENKINS-61193) When using proxy also export the no_proxy hosts.
Title: Message Title Gyanesha Prajjwal assigned an issue to Gyanesha Prajjwal Jenkins / JENKINS-61193 When using proxy also export the no_proxy hosts. Change By: Gyanesha Prajjwal Assignee: Gyanesha Prajjwal 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.204739.1582532685000.6777.1582688100238%40Atlassian.JIRA.
[JIRA] (JENKINS-60212) Unstash pipeline step hangs frequently
Title: Message Title Jie Shen commented on JENKINS-60212 Re: Unstash pipeline step hangs frequently Megan Smith sorry for the late response here. I am not working on this project anymore and I will assign this to the team. 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.203185.1574173604000.6772.1582686480216%40Atlassian.JIRA.
[JIRA] (JENKINS-60212) Unstash pipeline step hangs frequently
Title: Message Title Jie Shen assigned an issue to Azure DevOps Jenkins / JENKINS-60212 Unstash pipeline step hangs frequently Change By: Jie Shen Assignee: Jie Shen Azure DevOps 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.203185.1574173604000.6775.1582686480259%40Atlassian.JIRA.
[JIRA] (JENKINS-60998) Azure VM Agents is using incorrect subscription id
Title: Message Title Azure DevOps commented on JENKINS-60998 Re: Azure VM Agents is using incorrect subscription id Hi Chang Li, maybe you can take a took? 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.204466.1580995914000.6770.1582686060120%40Atlassian.JIRA.
[JIRA] (JENKINS-56457) Regression in timestamper 1.9: Start of maven plugins is logged with different format
Title: Message Title Basil Crow assigned an issue to Basil Crow Jenkins / JENKINS-56457 Regression in timestamper 1.9: Start of maven plugins is logged with different format Change By: Basil Crow Assignee: Steven G Brown Basil Crow 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.198055.1551959298000.6757.1582683840248%40Atlassian.JIRA.
[JIRA] (JENKINS-56457) Regression in timestamper 1.9: Start of maven plugins is logged with different format
Title: Message Title Basil Crow commented on JENKINS-56457 Re: Regression in timestamper 1.9: Start of maven plugins is logged with different format Likely a duplicate of JENKINS-59636, for which I have opened a PR with a fix. I will keep this bug open pending the release of the fix for JENKINS-59636 to verify that the issue is resolved. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198055.1551959298000.6750.1582683780245%40Atlassian.JIRA.
[JIRA] (JENKINS-59636) timestamper shows wrong time on [View as plain text] link
Title: Message Title Basil Crow commented on JENKINS-59636 Re: timestamper shows wrong time on [View as plain text] link This should be fixed in jenkinsci/timestamper-plugin#52. 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.202318.1570086045000.6732.1582683660813%40Atlassian.JIRA.
[JIRA] (JENKINS-59636) timestamper shows wrong time on [View as plain text] link
Title: Message Title Basil Crow assigned an issue to Basil Crow Jenkins / JENKINS-59636 timestamper shows wrong time on [View as plain text] link Change By: Basil Crow Assignee: Steven G Brown Basil Crow 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.202318.1570086045000.6737.1582683660906%40Atlassian.JIRA.
[JIRA] (JENKINS-59636) timestamper shows wrong time on [View as plain text] link
Title: Message Title Basil Crow updated JENKINS-59636 Jenkins / JENKINS-59636 timestamper shows wrong time on [View as plain text] link Change By: Basil Crow 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.202318.1570086045000.6745.1582683661025%40Atlassian.JIRA.
[JIRA] (JENKINS-59636) timestamper shows wrong time on [View as plain text] link
Title: Message Title Basil Crow started work on JENKINS-59636 Change By: Basil Crow Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202318.1570086045000.6743.1582683660991%40Atlassian.JIRA.
[JIRA] (JENKINS-54128) Deprecated calls to Run.getLogFile
Title: Message Title Basil Crow commented on JENKINS-54128 Re: Deprecated calls to Run.getLogFile I posted jenkinsci/timestamper-plugin#52, which eliminates the last call to the last call to Run#getLogFile in Timestamper and replaces it with a call to Run#getLogReader. 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.194755.1539777336000.6708.1582683480489%40Atlassian.JIRA.
[JIRA] (JENKINS-57180) folder "parent" in workspace not browseable
Title: Message Title
Mark Waite edited a comment on JENKINS-57180
Re: folder "parent" in workspace not browseable
I confirmed that the problem exists as described for pipeline jobs. Attempting to browse the workspace of a PIpeline job fails when attempting to navigate a directory named 'parent' at the root of the workspace.Same problem does not happen for Freestyle jobs. I've assigned the issue to a pipeline plugin.My test case job contained a pipeline definition like this:{noformat}node('!windows') {stage('create dirs') {deleteDir()sh ("mkdir -p parent/foo")sh ("mkdir -p bar/parent")sh ("mkdir parent-foo")echo "OK URL is ${env.BUILD_URL}/execution/node/3/ws/"echo "Odd URL is ${env.BUILD_URL}/execution/node/3/ws/parent/"echo "Broken URL is ${env.BUILD_URL}/execution/node/3/ws/parent/foo"}}{noformat}From the console output, clicking the "OK URL" works as expected. Clicking the "Odd URL" causes a surprising result. Clicking the "Broken URL" generates the 404 page not found. A test has also been added to [my docker-lfs repository|https://github.com/MarkEWaite/docker-lfs/blob/lts-with-plugins/ref/jobs/Bugs-Individual/jobs/JENKINS-57180-pipeline-folder-named-parent-cannot-be-browsed/config.xml].
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/jenkins
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title Amila Gunathilake commented on JENKINS-61167 Re: Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error hi Andrew Sumner my concern is when I'm uploading a 3 mb .txt file the plugin is working but when I'm uploading 58 mb .7z file its giving this bad gateway error. So if it's not a file size issue is it an issue with .7z file extension ? I'm sure it's not an network issue. In the mean time I will try to set up the UPack CLI tool. Amila 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.204701.1582203816000.6704.1582679400146%40Atlassian.JIRA.
[JIRA] (JENKINS-60409) Cloud Configuration Length Cap
Title: Message Title Olivier Lamy commented on JENKINS-60409 Re: Cloud Configuration Length Cap I guess we need to update the default value. maybe something around 50? I reckon it's a bit sensible to change that. but a default with no size limit is weird. 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.203466.1575915955000.6693.1582676641048%40Atlassian.JIRA.
[JIRA] (JENKINS-54128) Deprecated calls to Run.getLogFile
Title: Message Title Basil Crow commented on JENKINS-54128 Re: Deprecated calls to Run.getLogFile Tobias Gruetzmacher, I have a rough draft of a fix for Timestamper. I plan to post a PR soon and release the fix in the forthcoming Timestamper 1.11.1 release. To help me test this new functionality, would you mind posting the stack trace that you are seeing with the call to getLogFile? 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.194755.1539777336000.6691.1582676641022%40Atlassian.JIRA.
[JIRA] (JENKINS-57180) folder "parent" in workspace not browseable
Title: Message Title
Mark Waite edited a comment on JENKINS-57180
Re: folder "parent" in workspace not browseable
I confirmed that the problem exists as described for pipeline jobs. Attempting to browse the workspace of a PIpeline job fails when attempting to navigate a directory named 'parent' at the root of the workspace.Same problem does not happen for Freestyle jobs. I've assigned the issue to a pipeline plugin.My test case job contained a pipeline definition like this:{noformat}node('!windows') {stage('create dirs') {deleteDir()sh ("mkdir -p parent/foo && touch parent/foo/file-1 ")sh ("mkdir -p bar/parent && touch bar/parent/file-2 ")sh ("mkdir parent-foo && touch parent-foo/file-3 ")echo "OK URL is ${env.BUILD_URL}/execution/node/3/ws/"echo "Odd URL is ${env.BUILD_URL}/execution/node/3/ws/parent/"echo "Broken URL is ${env.BUILD_URL}/execution/node/3/ws/parent/foo"}}{noformat}From the console output, clicking the "OK URL" works as expected. Clicking the "Odd URL" causes a surprising result. Clicking the "Broken URL" generates the 404 page not found.
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.198931.1556177657000.6668.1582676220238%40Atlassian.JIRA.
[JIRA] (JENKINS-57180) folder "parent" in workspace not browseable
Title: Message Title
Mark Waite edited a comment on JENKINS-57180
Re: folder "parent" in workspace not browseable
I confirmed that the problem exists as described for pipeline jobs. Attempting to browse the workspace of a PIpeline job fails when attempting to navigate a directory named 'parent' at the root of the workspace.Same problem does not happen for Freestyle jobs. I've assigned the issue to a pipeline plugin. My test case job contained a pipeline definition like this:{noformat}node('!windows') {stage('create dirs') {deleteDir()sh ("mkdir -p parent/foo && touch parent/foo/file-1")sh ("mkdir -p bar/parent && touch bar/parent/file-2")sh ("mkdir parent-foo&& touch parent-foo/file-3")echo "OK URL is ${env.BUILD_URL}/execution/node/3/ws/"echo "Odd URL is ${env.BUILD_URL}/execution/node/3/ws/parent/"echo "Broken URL is ${env.BUILD_URL}/execution/node/3/ws/parent/foo"}}{noformat}From the console output, clicking the "OK URL" works as expected. Clicking the "Odd URL" causes a surprising result. Clicking the "Broken URL" generates the 404 page not found.
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.198931.1556177657000..1582676220177%40Atlassian.JIRA.
[JIRA] (JENKINS-57180) folder "parent" in workspace not browseable
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-57180 folder "parent" in workspace not browseable Change By: Mark Waite Component/s: pipeline Component/s: _unsorted 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.198931.1556177657000.6664.1582675680146%40Atlassian.JIRA.
[JIRA] (JENKINS-57180) folder "parent" in workspace not browseable
Title: Message Title Mark Waite commented on JENKINS-57180 Re: folder "parent" in workspace not browseable I confirmed that the problem exists as described for pipeline jobs. Attempting to browse the workspace of a PIpeline job fails when attempting to navigate a directory named 'parent' at the root of the workspace. Same problem does not happen for Freestyle jobs. I've assigned the issue to a pipeline 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.198931.1556177657000.6662.1582675620112%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Raihaan Shouhell commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart Plugin can't terminate all instances on shutdown / restart simply because that can cause shutdown to stall. Do you have any logs from the retention strategy. I see in your logs that the instances were stopped but I'm not certain why. 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.199745.1559315049000.6657.1582675320301%40Atlassian.JIRA.
[JIRA] (JENKINS-59807) SSH-Agent Broken User Interface
Title: Message Title Valeriy Fedorenko commented on JENKINS-59807 Re: SSH-Agent Broken User Interface From I've found, you need to ensure, that credential scope is set to "Global (Jenkins nodes, items etc)", not "System (Jenkins and nodes only)". This can be done by updating each particular credential. 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.202538.1571249068000.6642.1582671300123%40Atlassian.JIRA.
[JIRA] (JENKINS-60212) Unstash pipeline step hangs frequently
Title: Message Title Megan Smith commented on JENKINS-60212 Re: Unstash pipeline step hangs frequently Jie Shen - any update on this? 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.203185.1574173604000.6635.1582665360158%40Atlassian.JIRA.
[JIRA] (JENKINS-60392) Allow environment variables with Bitbucket Server Integration Pipeline
Title: Message Title
Bruce Coveny edited a comment on JENKINS-60392
Re: Allow environment variables with Bitbucket Server Integration Pipeline
[~mhenschke_atlassian]It appears using double quotes worked for the branch name but it does not appear to work for other variables like credentialsId and produces an error. Please note values have been changed from hard-coded values for data sensitivity reasons.Example call: {code:java}bbs_checkout branches: bbs_checkout branches: [[name: "${env.BRANCH}"]], credentialsId: "${env.CREDENTIALS_ID}", id: 'id', mirrorName: '', projectName: 'project', repositoryName: 'repo', serverId: 'serverid'{code}Log output: {noformat}[Pipeline] bbs_checkoutusing credential [proper-credential-id] > git.exe rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git.exe config remote.repo.url https://localhost:8443/scm/project/repo.git # timeout=10Fetching upstream changes from https://localhost:8443/scm/project/repo.git > git.exe --version # timeout=10using GIT_ASKPASS to set credentials Signon > git.exe fetch --tags --force --progress -- https://localhost:8443/scm/project/repo.git +refs/heads/*:refs/remotes/repo/* # timeout=10 > git.exe rev-parse "repo/*master^{commit}" # timeout=10 > git.exe rev-parse "develop^{commit}" # timeout=10[Pipeline] }Posting build status of FAILED to Bitbucket ServerERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished: FAILURE{noformat}Taking out the "${env.CREDENTIALS_ID}" and changing to something like 'hardcoded-credential-id' works.This would work better if the payload configured in the Jenkins job could be injected as per issue JENKINS-60340 and not having to duplicate these values in the Jenkins job and in the Jenkinsfile. We have different values for these based on different branches for access level information which is why we need to change the values around and not hard-code them in the Jenkinsfile.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60392) Allow environment variables with Bitbucket Server Integration Pipeline
Title: Message Title
Bruce Coveny commented on JENKINS-60392
Re: Allow environment variables with Bitbucket Server Integration Pipeline
Martin Henschke It appears using double quotes worked for the branch name but it does not appear to work for other variables like credentialsId and produces an error. Please note values have been changed from hard-coded values for data sensitivity reasons. Example call:
bbs_checkout branches: bbs_checkout branches: [[name: "${env.BRANCH}"]], credentialsId: "${env.CREDENTIALS_ID}", id: 'id', mirrorName: '', projectName: 'project', repositoryName: 'repo', serverId: 'serverid'
Log output:
[Pipeline] bbs_checkout
using credential [proper-credential-id]
> git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git.exe config remote.repo.url https://localhost:8443/scm/project/repo.git # timeout=10
Fetching upstream changes from https://localhost:8443/scm/project/repo.git
> git.exe --version # timeout=10
using GIT_ASKPASS to set credentials Signon
> git.exe fetch --tags --force --progress -- https://localhost:8443/scm/project/repo.git +refs/heads/*:refs/remotes/repo/* # timeout=10
> git.exe rev-parse "repo/*master^{commit}" # timeout=10
> git.exe rev-parse "develop^{commit}" # timeout=10
[Pipeline] }
Posting build status of FAILED to Bitbucket ServerERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
Finished: FAILURE
Taking out the "${env.CREDENTIALS_ID}" and changing to something like 'hardcoded-credential-id' works. This would work better if the payload configured in the Jenkins job could be injected as per issue JENKINS-60340 and not having to duplicate these values in the Jenkins job and in the Jenkinsfile. We have different values for these based on different branches for access level information which is why we need to change the values around and not hard-code them in the Jenkinsfile.
Add Comment
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title Andrew Sumner commented on JENKINS-61167 Re: Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error I don't think that is the problem - that is quite an old issue and I'm able to upload 200MB files to my ProGet instance. There is an issue with this plugin (rather than proget) around file size but I thought that was well in excess of 58 MB and throws an out of memory exceptions rather than Bad Gateway. I've been meaning to fix this for a while so will look for a solution. Seems to be an issue running under Jenkins as the code doesn't have this problem when run as a unit test. If you can't wait for this there is a [command line tool|https://docs.inedo.com/docs/upack/tools-and-libraries/upack-cli] for ProGet that you could use instead of this plugin. Obviously not as handy but would get your pipeline running while I work on the 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.204701.1582203816000.6627.1582664820280%40Atlassian.JIRA.
[JIRA] (JENKINS-61212) CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11
Title: Message Title Fred Vogt updated an issue Jenkins / JENKINS-61212 CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11 Change By: Fred Vogt Labels: java11-compatibility 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.204765.1582603216000.6625.1582664820253%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Jon Starbird commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 No worries. I'm not ready to move to 6.2.x of BM yet anyway. thanks for the update. Good luck with the move. 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.203842.1577724088000.6622.1582663980096%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Andrew Sumner commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 Just to let you know - I haven't forgotten about this. I am in the process of moving house so I haven't had much spare time lately. This change is ready to go. However... the BuildMaster 6.2.5 release has a bug in one of the APIs used by the "wait for build to complete" option. There where a couple of other minor changes to the API but those were easily fixed. As soon as I have a fix for this I will be getting a new version out. 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.203842.1577724088000.6620.1582663800115%40Atlassian.JIRA.
[JIRA] (JENKINS-61212) CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11
Title: Message Title Fred Vogt commented on JENKINS-61212 Re: CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11 Jesse Glick - hm... you are correct. jdk-11 with HTTP is working. TLS+websocket inbound cli/agent works with jdk-8, but NOT jdk-11. 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.204765.1582603216000.6617.1582663500156%40Atlassian.JIRA.
[JIRA] (JENKINS-61212) CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11
Title: Message Title Fred Vogt commented on JENKINS-61212 Re: CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11 Jesse Glick - I'll try to distill it down to the simplest reproducible jdk-11 setup (without TLS), and test it with your smoke test and websocat. 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.204765.1582603216000.6608.1582662300121%40Atlassian.JIRA.
[JIRA] (JENKINS-61212) CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11
Title: Message Title Fred Vogt edited a comment on JENKINS-61212 Re: CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11 [~jglick] - I retested with jdk8 and the web-socket inbound cli/agent are working.I'll update with more findings later today when I have more info - and you can decide if this is a bug or a jdk-11 compat issue to be addressed as described at [jenkins-on-java-11|https://jenkins . io/doc/administration/requirements/jenkins-on-java-11/]BTW - I was https with jdk-8 also. 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.204765.1582603216000.6605.1582662120138%40Atlassian.JIRA.
[JIRA] (JENKINS-61212) CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11
Title: Message Title Jesse Glick commented on JENKINS-61212 Re: CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11 Interesting. Is it the client or the server that matters? There are smoke tests of WebSocket modes in the Jenkins core tree which get run on JDK 11 in CI, but this is not using Jetty-terminated TLS or custom certificates. 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.204765.1582603216000.6602.1582662060634%40Atlassian.JIRA.
[JIRA] (JENKINS-61212) CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11
Title: Message Title Fred Vogt updated an issue Jenkins / JENKINS-61212 CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11 Change By: Fred Vogt Summary: CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11 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.204765.1582603216000.6585.1582661640259%40Atlassian.JIRA.
[JIRA] (JENKINS-61212) CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11
Title: Message Title Fred Vogt commented on JENKINS-61212 Re: CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11 Jesse Glick - I retested with jdk8 and the web-socket inbound cli/agent are working. I'll update later today when I have more info. 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.204765.1582603216000.6587.1582661640298%40Atlassian.JIRA.
[JIRA] (JENKINS-57749) Latest terraform version (0.12.0) not available for download via global tool installation from bintray
Title: Message Title David Pires updated JENKINS-57749 Can not reproduce. Jenkins / JENKINS-57749 Latest terraform version (0.12.0) not available for download via global tool installation from bintray Change By: David Pires Status: Open Fixed but Unreleased Resolution: Cannot Reproduce 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 t
[JIRA] (JENKINS-57749) Latest terraform version (0.12.0) not available for download via global tool installation from bintray
Title: Message Title David Pires updated JENKINS-57749 Jenkins / JENKINS-57749 Latest terraform version (0.12.0) not available for download via global tool installation from bintray Change By: David Pires Status: Fixed but Unreleased Closed Released As: https://github.com/jenkinsci/terraform-plugin/releases/tag/terraform-1.0.10 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.199694.155915236.6571.1582660680400%40Atlassian.JIRA.
[JIRA] (JENKINS-40125) Terraform plugin does not work with Jenkins v2.19
Title: Message Title David Pires closed an issue as Fixed Jenkins / JENKINS-40125 Terraform plugin does not work with Jenkins v2.19 Change By: David Pires 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.176770.1480521065000.6566.1582660560594%40Atlassian.JIRA.
[JIRA] (JENKINS-40125) Terraform plugin does not work with Jenkins v2.19
Title: Message Title David Pires resolved as Fixed Jenkins / JENKINS-40125 Terraform plugin does not work with Jenkins v2.19 Change By: David Pires Status: Open Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/terraform-plugin/releases/tag/terraform-1.0.10 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.176770.1480521065000.6564.1582660560555%40Atlassian.JIRA.
[JIRA] (JENKINS-40125) Terraform plugin does not work with Jenkins v2.19
Title: Message Title David Pires commented on JENKINS-40125 Re: Terraform plugin does not work with Jenkins v2.19 Plugin verified to work in at least 2.190.2. Release 1.0.10 includes annotation support for Terraform to be used in pipeline scripts. 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.176770.1480521065000.6560.1582660440247%40Atlassian.JIRA.
[JIRA] (JENKINS-60536) Jenkins job hangs in Jira call after git rev-list command
Title: Message Title Craig Rodrigues edited a comment on JENKINS-60536 Re: Jenkins job hangs in Jira call after git rev-list command Cool, let me know how it works for you.You can also post messages in the Gitter chat channel https:// github gitter . com im /jenkinsci/jira-plugin The more people who collaborate on this the better! 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.203639.1576745651000.6551.1582659840244%40Atlassian.JIRA.
[JIRA] (JENKINS-60536) Jenkins job hangs in Jira call after git rev-list command
Title: Message Title Craig Rodrigues commented on JENKINS-60536 Re: Jenkins job hangs in Jira call after git rev-list command Cool, let me know how it works for you. You can also post messages in https://github.com/jenkinsci/jira-plugin The more people who collaborate on this the better! 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.203639.1576745651000.6542.1582659720249%40Atlassian.JIRA.
[JIRA] (JENKINS-54365) Branch and commit fields are empty in BlueOcean UI Header-details element
Title: Message Title Marcel Wilson commented on JENKINS-54365 Re: Branch and commit fields are empty in BlueOcean UI Header-details element Agreed. I point it out in hopes that it helps identify the issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195116.1540981558000.6532.1582656420302%40Atlassian.JIRA.
[JIRA] (JENKINS-56833) Hundreds of REST calls to JOB_URL/runs/2/nodes/?limit=10000
Title: Message Title Ryan Fenton-Garcia commented on JENKINS-56833 Re: Hundreds of REST calls to JOB_URL/runs/2/nodes/?limit=1 That's actually extremely helpful to know! Do you know what kind of things the executor info plugin actually provides? I tried to look at the github page for the plugin, but I only see a link to a presentation that I'm not sure what is or isn't specifically related to the plugin. Also, do you know what other plugins that potentially degrade blue ocean's performance are optional? 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.198492.1554122782000.6529.1582656060169%40Atlassian.JIRA.
[JIRA] (JENKINS-60536) Jenkins job hangs in Jira call after git rev-list command
Title: Message Title Taylor Nelson edited a comment on JENKINS-60536 Re: Jenkins job hangs in Jira call after git rev-list command [~rodrigc] Yes I definitely saw your pull request. Thanks for all your work on that! I built the plugin with your PR #213 yesterday morning, but this issue here persists even with your changes. We use the plugin for anything from updating a fixVersion to adding comments on tasks, and for some reason these jobs started occasionally freezing and would require us to restart our Jenkins server to unclog the pipeline. (With the exact stack trace David has above – blocked thread cannot close HTTP connection and another thread waiting forever, etc)I was going to combine your changes in PR 213 with David's changes on PR 207, but 207 modifies that AsyncHttpClient class that you have deleted in your PR. So now I have to choose to build a plugin that doesn't work, but doesn't freeze *OR* a plugin that works but freezes and blocks all of our executors – connection freeze fix or GDPR fix, respectively. :)I realize I'm not contributing to the fix, I don't have any experience at all building Jenkins plugins. Just hoping my comments will give more context to the problem we are having. I'm sort of surprised this issue isn't affecting more people. Edit: I just saw you added some commits related to the apache dependencies being updated. Will try building again Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkins
[JIRA] (JENKINS-61227) S3 publisher plugin : Make dontSetBuildResultOnFailure an Optional Field
Title: Message Title Isaiah Mann created an issue Jenkins / JENKINS-61227 S3 publisher plugin : Make dontSetBuildResultOnFailure an Optional Field Issue Type: Improvement Assignee: Alexander A Components: s3-plugin Created: 2020-02-25 17:33 Priority: Minor Reporter: Isaiah Mann Hi, it appears on an upgrade of the "S3 publisher plugin" and there's a new required field that can break previous integrations: `dontSetBuildResultOnFailure` Would it be possible to make this field optional to avoid breaking those who upgrade in future? Add Comment
[JIRA] (JENKINS-44085) have a simple way to limit the number of parallel branches that run concurrently
Title: Message Title
Ronny Schuetz commented on JENKINS-44085
Re: have a simple way to limit the number of parallel branches that run concurrently
Just gave https://github.com/jenkinsci/concurrent-step-plugin a try (it doesn't seem to be available somewhere, so I had to build it from the sources and tweak it a bit to start a newer Jenkins version): It seems to work fine inside script {} blocks of declarative pipelines.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181710.1494001199000.6465.1582650661203%40Atlassian.JIRA.
[JIRA] (JENKINS-44115) Enable Remoting working directories by default in Swarm plugin
Title: Message Title Basil Crow updated JENKINS-44115 Fixed in jenkinsci/swarm-plugin#176. Jenkins / JENKINS-44115 Enable Remoting working directories by default in Swarm plugin Change By: Basil Crow Status: Open Fixed but Unreleased 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 http
[JIRA] (JENKINS-60536) Jenkins job hangs in Jira call after git rev-list command
Title: Message Title Taylor Nelson commented on JENKINS-60536 Re: Jenkins job hangs in Jira call after git rev-list command Craig Rodrigues Yes I definitely saw your pull request. Thanks for all your work on that! I built the plugin with your PR #213 yesterday morning, but this issue here persists even with your changes. We use the plugin for anything from updating a fixVersion to adding comments on tasks, and for some reason these jobs started occasionally freezing and would require us to restart our Jenkins server to unclog the pipeline. (With the exact stack trace David has above – blocked thread cannot close HTTP connection and another thread waiting forever, etc) I was going to combine your changes in PR 213 with David's changes on PR 207, but 207 modifies that AsyncHttpClient class that you have deleted in your PR. So now I have to choose to build a plugin that doesn't work, but doesn't freeze OR a plugin that works but freezes and blocks all of our executors – connection freeze fix or GDPR fix, respectively. I realize I'm not contributing to the fix, I don't have any experience at all building Jenkins plugins. Just hoping my comments will give more context to the problem we are having. I'm sort of surprised this issue isn't affecting more people. 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/jenkins
[JIRA] (JENKINS-54365) Branch and commit fields are empty in BlueOcean UI Header-details element
Title: Message Title Dmitry Mihailov commented on JENKINS-54365 Re: Branch and commit fields are empty in BlueOcean UI Header-details element Me too. I just don't believe it should be that way... 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.195116.1540981558000.6445.158265512%40Atlassian.JIRA.
[JIRA] (JENKINS-44115) Enable Remoting working directories by default in Swarm plugin
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-44115 Enable Remoting working directories by default in Swarm plugin Change By: Basil Crow Summary: Enable Remoting work dir working directories by default in Swarm Plugin 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.181741.1494227581000.6433.1582649820289%40Atlassian.JIRA.
[JIRA] (JENKINS-60995) Triggered builds section not displaying intermittently since upgrading to blue ocean 1.17
Title: Message Title Luis Roalter commented on JENKINS-60995 Re: Triggered builds section not displaying intermittently since upgrading to blue ocean 1.17 Looks the same here. But not for all builds. Old builds (before upgrading) still show the triggered build sections. 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.204463.158098930.6424.1582649400219%40Atlassian.JIRA.
[JIRA] (JENKINS-54365) Branch and commit fields are empty in BlueOcean UI Header-details element
Title: Message Title Marcel Wilson commented on JENKINS-54365 Re: Branch and commit fields are empty in BlueOcean UI Header-details element I've noticed this when I use a single pipeline. Using a multi-pipeline appears to work ok. 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.195116.1540981558000.6416.1582646520319%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart I tried this a few more times. So far it's reproducible 100% (which is in a way good) 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.199745.1559315049000.6410.1582646100205%40Atlassian.JIRA.
[JIRA] (JENKINS-60409) Cloud Configuration Length Cap
Title: Message Title Oleg Nenashev commented on JENKINS-60409 Re: Cloud Configuration Length Cap We just received a bunch of new reports, linked them to this ticket. Olivier Lamy any hints on the Jetty side? "+ 3856 Different behaviour with maxFormContentSize=0 if Content-Length header is present/missing" mentioned by Daniel Beck makes me think we need to alter the defaults in Winstone to restore the original behavior 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.203466.1575915955000.6402.1582645380310%40Atlassian.JIRA.
[JIRA] (JENKINS-60968) role-strategy-Submit fails with version 2.209. Not able to save new user.
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60968 role-strategy-Submit fails with version 2.209. Not able to save new user. Change By: Oleg Nenashev Component/s: core Component/s: winstone-jetty 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.204431.1580889821000.6386.1582645260821%40Atlassian.JIRA.
[JIRA] (JENKINS-60968) role-strategy-Submit fails with version 2.209. Not able to save new user.
Title: Message Title Oleg Nenashev commented on JENKINS-60968 Re: role-strategy-Submit fails with version 2.209. Not able to save new user. It might be related to the recent Jetty behavior changes. JENKINS-60409 contains a potential workaround. There is nothing I can do on the plugin side 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.204431.1580889821000.6382.1582645260720%40Atlassian.JIRA.
[JIRA] (JENKINS-60409) Cloud Configuration Length Cap
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60409 Cloud Configuration Length Cap Change By: Oleg Nenashev Component/s: winstone-jetty 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.203466.1575915955000.6388.1582645260846%40Atlassian.JIRA.
[JIRA] (JENKINS-60984) Editable Email Notification not working for Trigger Failure.
Title: Message Title Oleg Nenashev commented on JENKINS-60984 Re: Editable Email Notification not working for Trigger Failure. It may be related to Jetty behavior changes. JENKINS-60409 and so on 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.204452.1580946416000.6378.1582645200318%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title
Jakub Bochenski edited a comment on JENKINS-57795
Re: Orphaned EC2 instances after Jenkins restart
Actually I've noticed another problematic thing. After I manually terminate the instance the plugin will spawn 4 new instances that will get terminated immediatelly before finally getting the fifth one up. I thought it's was a fluke at first but it seems to be reproducible consistently.Log: https://gist.github.com/jakub-bochenski/c24b1f8e24e7be77aa2522df2c8caaed It seems the plugin just terminates the instance for no reason:{code}Feb 25, 2020 3:18:30 PM INFO hudson.plugins.ec2.EC2Cloud logLaunching remoting agent (via Trilead SSH2 Connection): java -jar /tmp/remoting.jar -workDir /opt/jenkinsFeb 25, 2020 3:18:32 PM INFO hudson.plugins.ec2.EC2OndemandSlave terminateTerminated EC2 instance (terminated): i-046afc69c32c1acddFeb 25, 2020 3:18:32 PM INFO hudson.plugins.ec2.EC2OndemandSlave terminateRemoved EC2 instance from jenkins master: i-046afc69c32c1acdd{code}Also notice this, despite instance cap=1{code}Feb 25, 2020 3:18:21 PM INFO hudson.slaves.NodeProvisioner lambda$update$6EC2 (ec2) - ec2 (ami-028d96c69234f9d1a) provisioning successfully completed. We have now 2 computer(s){code}
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.199745.1559315049000.6373.1582645140403
[JIRA] (JENKINS-61226) Unable to save or apply changes "Form is larger than max length 200000"
Title: Message Title Oleg Nenashev commented on JENKINS-61226 Re: Unable to save or apply changes "Form is larger than max length 20" It likely duplicates JENKINS-60409. When did it start happening? 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.204780.1582643892000.6375.1582645140467%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart Actually I've noticed another problematic thing. After I manually terminate the instance the plugin will spawn 4 new instances that will get terminated immediatelly before finally getting the fifth one up. I thought it's was a fluke at first but it seems to be reproducible consistently. Log: https://gist.github.com/jakub-bochenski/c24b1f8e24e7be77aa2522df2c8caaed 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.199745.1559315049000.6363.1582644900210%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title
Jakub Bochenski edited a comment on JENKINS-57795
Re: Orphaned EC2 instances after Jenkins restart
We have only 1 cloud active, you can find the groovy script to configure it above (I have disabled to ECS cloud to test this).I'm on version 1.49.1 of plugin and Jenkins ver. 2.204.2.I was able to reproduce this with just: - start Jenkins master instance - trigger job that will ask for the EC2-powered agent - wait for job to finish and stop Jenkins - start Jenkins again - trigger job that will ask for the EC2-powered agent, now it won't be able to hook the running instance againThe log output looks like this: {code}Feb 25, 2020 2:55:21 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 unitsFeb 25, 2020 2:55:21 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfigConfiguring Proxy. Proxy Host: ew1-internal-proxy.services-ci-infra-services.fsapi.com Proxy Port: 8080Feb 25, 2020 2:55:22 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0Feb 25, 2020 2:55:22 PM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}Feb 25, 2020 2:55:22 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 unitsFeb 25, 2020 2:55:22 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0Feb 25, 2020 2:55:22 PM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}Feb 25, 2020 2:55:31 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 unitsFeb 25, 2020 2:55:31 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0Feb 25, 2020 2:55:31 PM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}{code}After I terminate the instance manually in EC2 Console the log is {code}Feb 25, 2020 3:18:01 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 unitsFeb 25, 2020 3:18:01 PM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfoSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Considering launchingFeb 25, 2020 3:18:01 PM INFO hudson.plugins.ec2.SlaveTemplate setupRootDeviceAMI had xvdaFeb 25, 2020 3:18:01 PM INFO hudson.plugins.ec2.SlaveTemplate setupRootDevice{DeleteOnTermination: true,SnapshotId: snap-040ff84a8c849bc15,VolumeSize: 8,VolumeType: gp2,Encrypted: false}Feb 25, 2020 3:18:01 PM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfoSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Setting Instance Initiated Shutdown Behavior : ShutdownBehavior.TerminateFeb 25, 2020 3:18:02 PM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfoSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title
Jakub Bochenski edited a comment on JENKINS-57795
Re: Orphaned EC2 instances after Jenkins restart
We have only 1 cloud active, you can find the groovy script to configure it above (I have disabled to ECS cloud to test this).I'm on version 1.49.1 of plugin and Jenkins ver. 2.204.2.I was able to reproduce this with just: - start Jenkins master instance - trigger job that will ask for the EC2-powered agent - wait for job to finish and stop Jenkins - start Jenkins again - trigger job that will ask for the EC2-powered agent, now it won't be able to hook the running instance againThe log output looks like this: {code}Feb 25, 2020 2:55:21 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 unitsFeb 25, 2020 2:55:21 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfigConfiguring Proxy. Proxy Host: ew1-internal-proxy.services-ci-infra-services.fsapi.com Proxy Port: 8080Feb 25, 2020 2:55:22 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0Feb 25, 2020 2:55:22 PM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}Feb 25, 2020 2:55:22 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 unitsFeb 25, 2020 2:55:22 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0Feb 25, 2020 2:55:22 PM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}Feb 25, 2020 2:55:31 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 unitsFeb 25, 2020 2:55:31 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0Feb 25, 2020 2:55:31 PM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}{code} After I terminate the instance manually in EC2 Console the log is {code}Feb 25, 2020 3:18:01 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 unitsFeb 25, 2020 3:18:01 PM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfoSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Considering launchingFeb 25, 2020 3:18:01 PM INFO hudson.plugins.ec2.SlaveTemplate setupRootDeviceAMI had xvdaFeb 25, 2020 3:18:01 PM INFO hudson.plugins.ec2.SlaveTemplate setupRootDevice{DeleteOnTermination: true,SnapshotId: snap-040ff84a8c849bc15,VolumeSize: 8,VolumeType: gp2,Encrypted: false}Feb 25, 2020 3:18:01 PM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfoSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Setting Instance Initiated Shutdown Behavior : ShutdownBehavior.TerminateFeb 25, 2020 3:18:02 PM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfoSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docke
[JIRA] (JENKINS-61226) Unable to save or apply changes "Form is larger than max length 200000"
Title: Message Title deirdre rodgers created an issue Jenkins / JENKINS-61226 Unable to save or apply changes "Form is larger than max length 20" Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-02-25 15:18 Environment: version 2.220 Priority: Critical Reporter: deirdre rodgers Hi There, I am unable to add new users or make any changes under "Configure Global Security" as I get the below error java.lang.IllegalStateException: Form is larger than max length 20 at org.eclipse.jetty.server.Request.extractFormParameters(Request.java:562) at org.eclipse.jetty.server.Request.extractContentParameters(Request.java:519) at org.eclipse.jetty.server.Request.getParameters(Request.java:430) Caused: org.eclipse.jetty.http.BadMessageException: 400: Unable to parse form content at org.eclipse.jetty.server.Request.getParameters(Request.java:434) at org.eclipse.jetty.server.Request.getParameter(Request.java:1059) at javax.servlet.ServletRequestWrapper.getParameter(ServletRequestWrapper.java:194) at org.kohsuke.stapler.RequestImpl.getParameter(RequestImpl.java:174) at org.kohsuke.stapler.RequestImpl.getSubmittedForm(RequestImpl.java:1002) at hudson.security.GlobalSecurityConfiguration.doConfigure(GlobalSecurityConfiguration.java:100) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.SelectionInterceptedFunction$Adapter.invoke(SelectionInterceptedFunction.java:36) at org.kohsuke.stapler.verb.HttpVerbInterceptor.invoke(HttpVerbInterceptor.java:48) at org.kohsuke.stapler.SelectionInterceptedFunction.bin
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski edited a comment on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart BTW I didn't think about it earlier, but shouldn't the plugin actually terminate the EC2 instance on Jenkins shutdown? Otherwise it could stay there indefinatly indefinitely 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.199745.1559315049000.6344.1582643820566%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart BTW I didn't think about it earlier, but shouldn't the plugin actually terminate the EC2 instance on shutdown? Otherwise it could stay there indefinatly 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.199745.1559315049000.6342.1582643820476%40Atlassian.JIRA.
[JIRA] (JENKINS-61225) build-metrics plugin - Unknown buildStatId parameter
Title: Message Title Len Isac updated an issue Jenkins / JENKINS-61225 build-metrics plugin - Unknown buildStatId parameter Change By: Len Isac After upgrading to Jenkins LTS version 2.204.2, build-metrics version 1.3 no longer works. Stack tracejava.lang.IllegalArgumentException: Unknown buildStatId parameter !at hudson.plugins.global_build_stats.GlobalBuildStatsPlugin.doShowChart(GlobalBuildStatsPlugin.java:294)at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408)at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212)at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145)at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)Caused: javax.servlet.ServletExceptionat org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:797)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878)at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676)at org.kohsuke.stapler.Stapler.service(Stapler.java:238)at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873)at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154)at jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter.java:76)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151)at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:125)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151)at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151)at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157)at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610)at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:105)at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610)at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:118)at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)at org.acegisecurity.p
[JIRA] (JENKINS-60968) role-strategy-Submit fails with version 2.209. Not able to save new user.
Title: Message Title deirdre rodgers commented on JENKINS-60968 Re: role-strategy-Submit fails with version 2.209. Not able to save new user. Hello, I am having the same issue. How did you resolve it? Oleg Nenashev 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.204431.1580889821000.6328.1582643580418%40Atlassian.JIRA.
[JIRA] (JENKINS-61225) build-metrics plugin - Unknown buildStatId parameter
Title: Message Title Len Isac created an issue Jenkins / JENKINS-61225 build-metrics plugin - Unknown buildStatId parameter Issue Type: Bug Assignee: Yoann Dubreuil Components: build-metrics-plugin Created: 2020-02-25 15:12 Priority: Critical Reporter: Len Isac After upgrading to LTS version 2.204.2, build-metrics 1.3 no longer works. Stack trace java.lang.IllegalArgumentException: Unknown buildStatId parameter ! at hudson.plugins.global_build_stats.GlobalBuildStatsPlugin.doShowChart(GlobalBuildStatsPlugin.java:294) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:797) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter
[JIRA] (JENKINS-60968) role-strategy-Submit fails with version 2.209. Not able to save new user.
Title: Message Title brian odriscoll commented on JENKINS-60968 Re: role-strategy-Submit fails with version 2.209. Not able to save new user. We also have the same issue after upgrading to 2.220-exact same error-did you ever find a workaround for this issue Kiran? Thanks Brian 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.204431.1580889821000.6333.1582643580544%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title
Jakub Bochenski edited a comment on JENKINS-57795
Re: Orphaned EC2 instances after Jenkins restart
We have only 1 cloud active, you can find the groovy script to configure it above (I have disabled to ECS cloud to test this).I'm on version 1.49.1 of plugin and Jenkins ver. 2.204.2.I was able to reproduce this with just: - start Jenkins master instance - trigger job that will ask for the EC2-powered agent - wait for job to finish and stop Jenkins - start Jenkins again - trigger job that will ask for the EC2-powered agent, now it won't be able to hook the running instance againThe log output looks like this: {code} Feb 25, 2020 2:55:21 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 unitsFeb 25, 2020 2:55:21 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfigConfiguring Proxy. Proxy Host: ew1-internal-proxy.services-ci-infra-services.fsapi.com Proxy Port: 8080Feb 25, 2020 2:55:22 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0Feb 25, 2020 2:55:22 PM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}Feb 25, 2020 2:55:22 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 unitsFeb 25, 2020 2:55:22 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0Feb 25, 2020 2:55:22 PM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}Feb 25, 2020 2:55:31 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 unitsFeb 25, 2020 2:55:31 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0Feb 25, 2020 2:55:31 PM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}{code}
Add Comment
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title
Jakub Bochenski commented on JENKINS-57795
Re: Orphaned EC2 instances after Jenkins restart
We have only 1 cloud active, you can find the groovy script to configure it above (I have disabled to ECS cloud to test this). I'm on version 1.49.1 of plugin and Jenkins ver. 2.204.2. I was able to reproduce this with just:
start Jenkins master instance
trigger job that will ask for the EC2-powered agent
wait for job to finish and stop Jenkins
start Jenkins again
trigger job that will ask for the EC2-powered agent, now it won't be able to hook the running instance again
The log output looks like this:
Feb 25, 2020 2:55:21 PM INFO hudson.plugins.ec2.EC2Cloud provision
SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 units
Feb 25, 2020 2:55:21 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfig
Configuring Proxy. Proxy Host: ew1-internal-proxy.services-ci-infra-services.fsapi.com Proxy Port: 8080
Feb 25, 2020 2:55:22 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlave
SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0
Feb 25, 2020 2:55:22 PM WARNING hudson.plugins.ec2.EC2Cloud provision
Can't raise nodes for SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}
Feb 25, 2020 2:55:22 PM INFO hudson.plugins.ec2.EC2Cloud provision
SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 units
Feb 25, 2020 2:55:22 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlave
SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0
Feb 25, 2020 2:55:22 PM WARNING hudson.plugins.ec2.EC2Cloud provision
Can't raise nodes for SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}
Feb 25, 2020 2:55:31 PM INFO hudson.plugins.ec2.EC2Cloud provision
SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 units
Feb 25, 2020 2:55:31 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlave
SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0
Feb 25, 2020 2:55:31 PM WARNING hudson.plugins.ec2.EC2Cloud provision
Can't raise nodes for SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}
[JIRA] (JENKINS-61224) "Monitors" terminology should not be used in GUI
Title: Message Title Jesse Glick assigned an issue to Félix Queiruga Balado Jenkins / JENKINS-61224 "Monitors" terminology should not be used in GUI Change By: Jesse Glick Assignee: Félix Queiruga Balado 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.204778.158264254.6313.1582642620126%40Atlassian.JIRA.
[JIRA] (JENKINS-61224) "Monitors" terminology should not be used in GUI
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-61224 "Monitors" terminology should not be used in GUI Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-02-25 14:55 Priority: Trivial Reporter: Jesse Glick After JENKINS-60920 (I guess?), the header bar shows monitors 2 and the tooltip shows bq . There are 2 active administrative monitors. We should not be using the bare term "monitor" in the GUI. This word in English has various meanings (video displays, bureaucratic police, ...) but none of them would be intuitive in this context. In some spots in the GUI like /configure we do use the phrase "administrative monitor" which is more tolerable, though something like "alert" or "notification" would be more conventional. (I think the Java API introduced AdministrativeMonitor to describe how the implementations are written—by monitoring some condition and conditionally displaying the result to administrators—but this does not well capture the user's perspective.) I would suggest just deleting the word from the toolbar. The bell icon suffices for people to understand that there are some alerts they can see by clicking on it. Add Comment
[JIRA] (JENKINS-44085) have a simple way to limit the number of parallel branches that run concurrently
Title: Message Title jerry wiltse commented on JENKINS-44085 Re: have a simple way to limit the number of parallel branches that run concurrently No, it looks really good, unfortunately it says "can only be used in pipeline script" which seems to indicate declarative pipeline cannot use it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181710.1494001199000.6264.1582642320948%40Atlassian.JIRA.
[JIRA] (JENKINS-61212) CLI, Agent -websockets DeploymentException: Handshake response not received
Title: Message Title Jesse Glick commented on JENKINS-61212 Re: CLI, Agent -websockets DeploymentException: Handshake response not received Definitely I never tried to test against Winstone’s built-in --httpsPort, only against TLS termination done by reverse proxies (specifically Kubernetes ingress). In principle it ought to work to the extent that Jetty supports TLS + WebSocket. Offhand I suspect that the system properties you are passing to the client are not sufficient for the Tyrus library to recognize the custom certificate. Do you get the same error if you simply omit those properties? If so, this may just be a matter of inadequate error logging. 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.204765.1582603216000.6261.1582641600145%40Atlassian.JIRA.
[JIRA] (JENKINS-61197) Running a job with a custom workspace set to eg. 'F:\' causes NullPointerException
Title: Message Title Jesse Glick commented on JENKINS-61197 Re: Running a job with a custom workspace set to eg. 'F:\' causes NullPointerException I filed a variant patch, plus a plugin one. 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.204745.1582545957000.6256.1582640940267%40Atlassian.JIRA.
[JIRA] (JENKINS-61197) Running a job with a custom workspace set to eg. 'F:\' causes NullPointerException
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-61197 Running a job with a custom workspace set to eg. 'F:\' causes NullPointerException Change By: Jesse Glick Labels: lts-candidate regression windows 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.204745.1582545957000.6259.1582640940316%40Atlassian.JIRA.
[JIRA] (JENKINS-57129) java.io.IOException: Unexpected cgroup syntax (docker+jenkins+systemd)
Title: Message Title
Ivan Abramov edited a comment on JENKINS-57129
Re: java.io.IOException: Unexpected cgroup syntax (docker+jenkins+systemd)
[https://github.com/jenkinsci/docker-workflow-plugin/pull/206] This is the workaround. docker-workflow-plugin/src/main/java/org/jenkinsci/plugins/docker/workflow/client/ControlGroup.java{code:java}package org.jenkinsci.plugins.docker.workflow.client;import com.google.common.base.Optional;import hudson.FilePath;import java.io.BufferedReader;import java.io.IOException;import java.io.InputStreamReader;import java.io.Reader;import java.nio.charset.StandardCharsets;import java.util.ArrayList;import java.util.List;import java.util.regex.Matcher;import java.util.regex.Pattern;/** * @author Nicolas De Loof */public class ControlGroup {/** hierarchy ID number */public final int id;/** set of subsystems bound to the hierarchy */public final String subsystems;/** control group in the hierarchy to which the process belongs */public final String group;private ControlGroup(String line) throws NumberFormatException, IndexOutOfBoundsException {String[] fields = line.split(":");id = Integer.parseInt(fields[0]);subsystems = fields[1];group = fields[2];}public static Optional getContainerId(FilePath procfile) throws IOException, InterruptedException {return getContainerId(new InputStreamReader(procfile.read(), StandardCharsets.UTF_8));}static Optional getContainerId(Reader reader) throws IOException {try (BufferedReader r = new BufferedReader(reader)) {String line;while ((line = r.readLine()) != null) {final ControlGroup cgroup = new ControlGroup(line);final String containerId = cgroup.getContainerId();if (containerId != null) return Optional.of(containerId);}}return Optional.absent();}public String getContainerId() throws IOException { Pattern regex // 4:cpuset:/system.slice/docker-3dd988081e7149463c043b5d9c57d7309e079c5e9290f91feba1cc45a04d6a5b.scope// 2:cpu:/docker/3dd988081e7149463c043b5d9c57d7309e079c5e9290f91feba1cc45a04d6a5b// 2:cpu:/docker-ce/docker/7cacbc548047c130ae50653548f037285806d49c0c4c1543925cffb8873ed213// 10:cpu,cpuacct:/docker/a9f3c3932cd81c4a74cc7e0a18c3300255159512f1d000545c42895adaf68932/docker/3dd988081e7149463c043b5d9c57d7309e079c5e9290f91feba1cc45a04d6a5b// 3:cpu:/docker/4193df6bcf5fce75f3fc77f303b2ac06fb664adeb269b959b7ae17b3f8dcf329/3dd988081e7149463c043b5d9c57d7309e079c5e9290f91feba1cc45a04d6a5b// 7:cpu:/ecs/0410eff2-7e59-4111-823e-1e0d98ef7f30/3dd988081e7149463c043b5d9c57d7309e079c5e9290f91feba1cc45a04d6a5b// 8:cpuset:/kubepods.slice/kubepods-pod9c26dfb6_b9c9_11e7_bfb9_02c6c1fc4861.slice/docker-3dd988081e7149463c043b5d9c57d7309e079c5e9290f91feba1cc45a04d6a5b.scope// 12:freezer:/actions_job/ddecc467e1fb3295425e663efb6531282c1c936f25a3eeb7bb64e7b0fc61a216// /kubepods/burstable/pod1fe52ba4-5709-11ea-9ee3-00505682780f/d65c8853fa45d139ce95d5c2b68a6e4aa8da83894d8eb0396cd6edd1c134c97c/user.sliceMatcher matcher = Pattern.compile("([a-z0-9]{64})") ;Matcher matcher = regex .matcher(group);String containerId = null; while (matcher.find()) { containerId = matcher.group();}if ( containerId != null == containerId && Pattern.compile("^(\\/docker\\/|\\/ecs\\/|\\/docker-|\\/kubepods\\/|\\/actions_job\\/ ) .*").matcher(group).matches() ) { return containerId;} else { throw new IOException("Unexpected cgroup
[JIRA] (JENKINS-44085) have a simple way to limit the number of parallel branches that run concurrently
Title: Message Title Ronny Schuetz commented on JENKINS-44085 Re: have a simple way to limit the number of parallel branches that run concurrently Has anybody tried https://github.com/jenkinsci/concurrent-step-plugin already? 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.181710.1494001199000.6237.1582640162500%40Atlassian.JIRA.
[JIRA] (JENKINS-61212) CLI, Agent -websockets DeploymentException: Handshake response not received
Title: Message Title
Fred Vogt commented on JENKINS-61212
Re: CLI, Agent -websockets DeploymentException: Handshake response not received
Jesse Glick - thanks for the prompt response. You are probably right. I'll do testing with different combinations of jdk-8 and without HTTPS today. It will take me a bit of time to come up with the smallest reproducible setup and test with jdk-8. server-*.pem is a self-signed cert with :
localhost
127.0.0.1
jenkins-server
google chrome likes it when imported (Mac/Linux) The client / agent are connecting using a different container over a bridge network. server:
# winstone args
--httpsPort=${HTTPS_PORT-8443} \
--httpsPrivateKey=/var/jenkins_home/tls/server-rsa.pem \
--httpsCertificate=/var/jenkins_home/tls/server-cert.pem} \
--extraLibFolder=/var/jenkins_home/extraLibs \
--accessLoggerClassName=winstone.accesslog.SimpleAccessLogger \
--simpleAccessLogger.format=combined \
--simpleAccessLogger.file=/var/jenkins_home/logs/access.log \
client:
java \
-Djavax.net.ssl.trustStore=/var/lib/jenkins/truststore.jks \
-Djavax.net.ssl.trustStorePassword=jenkins \
-Djava.util.logging.config.file=/var/lib/jenkins/debug-logging.properties \
-jar "../jenkins-cli.jar" \
-s "https://jenkins-server:8443" \
-webSocket \
-logger FINE \
-auth "$AGENT_AUTH" \
Add Comment
[JIRA] (JENKINS-61220) plugin version 2.1.0 can not parse output.xml any more
Title: Message Title Dirk Richter commented on JENKINS-61220 Re: plugin version 2.1.0 can not parse output.xml any more see also https://github.com/jenkinsci/robot-plugin/pull/26#issuecomment-590851197 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.204774.1582633578000.6184.1582639560122%40Atlassian.JIRA.
[JIRA] (JENKINS-61212) CLI, Agent -websockets DeploymentException: Handshake response not received
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-61212 CLI, Agent -websockets DeploymentException: Handshake response not received Change By: Oleg Nenashev Comment: [https://github.com/jenkinsci/jenkins/pull/4526] - my draft. It is a bit different from what Jesse suggested 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.204765.1582603216000.6173.1582638480549%40Atlassian.JIRA.
[JIRA] (JENKINS-61212) CLI, Agent -websockets DeploymentException: Handshake response not received
Title: Message Title Oleg Nenashev commented on JENKINS-61212 Re: CLI, Agent -websockets DeploymentException: Handshake response not received UPD: deleted comment, wrong 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.204765.1582603216000.6176.1582638480649%40Atlassian.JIRA.
[JIRA] (JENKINS-61197) Running a job with a custom workspace set to eg. 'F:\' causes NullPointerException
Title: Message Title Oleg Nenashev updated JENKINS-61197 Jenkins / JENKINS-61197 Running a job with a custom workspace set to eg. 'F:\' causes NullPointerException Change By: Oleg Nenashev 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.204745.1582545957000.6181.1582638480803%40Atlassian.JIRA.
[JIRA] (JENKINS-61197) Running a job with a custom workspace set to eg. 'F:\' causes NullPointerException
Title: Message Title Oleg Nenashev commented on JENKINS-61197 Re: Running a job with a custom workspace set to eg. 'F:\' causes NullPointerException https://github.com/jenkinsci/jenkins/pull/4526 - my draft. It is a bit different from what Jesse suggested 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.204745.1582545957000.6179.1582638480769%40Atlassian.JIRA.
[JIRA] (JENKINS-61212) CLI, Agent -websockets DeploymentException: Handshake response not received
Title: Message Title Oleg Nenashev commented on JENKINS-61212 Re: CLI, Agent -websockets DeploymentException: Handshake response not received https://github.com/jenkinsci/jenkins/pull/4526 - my draft. It is a bit different from what Jesse suggested 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.204765.1582603216000.6170.1582638420153%40Atlassian.JIRA.
[JIRA] (JENKINS-61212) CLI, Agent -websockets DeploymentException: Handshake response not received
Title: Message Title Jesse Glick commented on JENKINS-61212 Re: CLI, Agent -websockets DeploymentException: Handshake response not received Probably something specific to your environment. First try using JDK 8 on both client and server (11 is in general poorly tested in Jenkins). Then check your service setup. You are using the built-in Winstone/Jetty servlet container? How is HTTPS being terminated—by Jetty’s built-in options (never before tested with WebSocket AFAIK), or using some sort of reverse proxy (which)? 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.204765.1582603216000.6166.1582638300249%40Atlassian.JIRA.
[JIRA] (JENKINS-57977) Investigate Use of File Locks for Plugin Manager Tool
Title: Message Title Ganghui Hu stopped work on JENKINS-57977 Change By: Ganghui Hu Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199961.1560287923000.6163.1582638180230%40Atlassian.JIRA.
[JIRA] (JENKINS-57977) Investigate Use of File Locks for Plugin Manager Tool
Title: Message Title Ganghui Hu started work on JENKINS-57977 Change By: Ganghui Hu Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199961.1560287923000.6160.1582638060258%40Atlassian.JIRA.
