[JIRA] (JENKINS-57776) Support kv2 version for vault secrets in Jenkins Pipeline
Title: Message Title sivanarayana baisani created an issue Jenkins / JENKINS-57776 Support kv2 version for vault secrets in Jenkins Pipeline Issue Type: New Feature Assignee: Phil Madden Components: hashicorp-vault-pipeline-plugin Created: 2019-05-31 05:53 Labels: plugin pipeline jenkins plugins vault Priority: Major Reporter: sivanarayana baisani The present Hashicorp Vault Pipeline Plugin depend on Hashicorp Vault Plugin. The Hashicorp Vault Plugin was modified to support KV2 secrets from vault but don't have a release that include the feature. And we also need the support for this feature in the Hashicorp Vault Pipeline plugin as well to be able to use the feature in a Jenkinsfile. Add Comment
[JIRA] (JENKINS-50711) plugin doesn't work with ssh link to git repo
Title: Message Title Praveen Kumar commented on JENKINS-50711 Re: plugin doesn't work with ssh link to git repo Hello, I'm facing the same issue with Linux Jenkins Master and Windows Slave. Is there a workaround for this issue ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189802.1523350889000.17142.1559281680150%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57775) NullPointerException when scan bitbucket mulit-branch
Title: Message Title Rick created an issue Jenkins / JENKINS-57775 NullPointerException when scan bitbucket mulit-branch Issue Type: Bug Assignee: Rick Attachments: image-2019-05-31-12-33-54-393.png Components: bitbucket-branch-source-plugin Created: 2019-05-31 04:34 Priority: Major Reporter: Rick This will happen when there are some PRs that don't have any commits. Add Comment
[JIRA] (JENKINS-57774) JenkinsRule: Jetty leaves stray threads running after server.stop()
Title: Message Title
Abhyudaya Sharma created an issue
Jenkins / JENKINS-57774
JenkinsRule: Jetty leaves stray threads running after server.stop()
Issue Type:
Bug
Assignee:
Oliver Gondža
Attachments:
threads_report.txt
Components:
jenkins-test-harness
Created:
2019-05-31 03:49
Priority:
Minor
Reporter:
Abhyudaya Sharma
I was debugging through JenkinsRule from Jenkins Test Harness. After the Jetty server and Jenkins have both been terminated in JenkinsRule#after() (line 488 and line 502, respectively) stray threads keep running. Attached is the dump of the running threads. Is it possible to terminate these threads to allow the JVM to exit gracefully? This issue may already have been reported before in this Stack Overflow question: https://stackoverflow.com/questions/13769007/jetty-server-leaves-behind-threads-after-stop A minimal example would be following test code and setting a breakpoint at the System.gc() call on line 517: import org.junit.Rule; import org.junit.Test; import org.jvnet.hudson.test.JenkinsRule; public class RandomTest { @Rule public JenkinsRule jenkinsRule = new JenkinsRule(); {{ @Test public void randomTest() { System.out.println("Hello world"); } }}} I was able to confirm the behaviour with the latest Jetty on both Windows 10 and Linux. This issues was discussed on the developer mailing list: https://groups.google.com/forum/#!topic/jenkinsci-dev/7yL0MKjxQwA
[JIRA] (JENKINS-56176) GIT_REVISION no longer set in git plugin 4.0.0-rc
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-56176 GIT_REVISION no longer set in git plugin 4.0.0-rc Change By: Mark Waite Summary: GIT_COMMIT GIT_REVISION no longer set in git plugin 4.0.0-rc Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197715.155047453.17134.1559274120149%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57771) email ext plugin doesn't send emails
Title: Message Title David van Laatum closed an issue as Not A Defect If it says sent then it has sent the email to your mail server. Have you checked the mail server logs to see where they went? Jenkins / JENKINS-57771 email ext plugin doesn't send emails Change By: David van Laatum Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199718.1559257316000.17132.1559273700307%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57539) Prepare design document for a top level architecture
Title: Message Title Marky Jackson commented on JENKINS-57539 Re: Prepare design document for a top level architecture Per team agreeable, this document is meeting acceptance. Parichay Barpanda says he would like to add a few more items to this body of work. I will leave open until then but it is agreed that this can be closed once that is done. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199447.1558177073000.17129.1559273580120%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57660) Git plugin stack trace saving job with invalid refspec
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-57660 Git plugin stack trace saving job with invalid refspec Change By: Mark Waite Summary: Git plugin crash on stack trace saving the project on Amazon EC while using git for Amazon Code Commit job with invalid refspec Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199593.1558700538000.17127.1559272080115%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57772) Build strategy for tags is not working, if you specify ignore tags lesser than 7days
Title: Message Title Mark Waite commented on JENKINS-57772 Re: Build strategy for tags is not working, if you specify ignore tags lesser than 7days I'm not sure I understand your statement. I added a new tag called 'temp-tag-a' and then clicked the link to scan the repository. The new tag was detected by the scan and a new build was scheduled. I removed the new tag called 'temp-tag-a' and then clicked the link to scan the repository. The deletion of the tag was detected and the job for temp-tag-a was deleted. Please provide numbered steps to recreate the problem you are seeing. Others cannot help you if they cannot duplicate the problem you're seeing. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199719.1559261241000.17125.1559271060162%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57772) Build strategy for tags is not working, if you specify ignore tags lesser than 7days
Title: Message Title
Mark Waite edited a comment on JENKINS-57772
Re: Build strategy for tags is not working, if you specify ignore tags lesser than 7days
I am unable to duplicate the problem that you are describing. Please provide instructions to create the job which is showing the failure. # Steps I took attempting to show the failure: # # Create a multibranch Pipeline job using the GitHub branch source# Disable all default behaviors (no branch discovery, no pull request discovery)# Add the "Discover tags" behavior# Add the build strategy "Tags" with an empty value for {{Ignore tags newer than}}# Change the "Tags" build strategy {{Ignore tags older than}} from its default 7 to 1# Run the job, confirm that it selected no tags to be built and no branches to be built (because there have been no tags created on that repository in the last 1 day)The job definition I used is uploaded as [^config.xml]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199719.1559261241000.17123.1559271000261%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57772) Build strategy for tags is not working, if you specify ignore tags lesser than 7days
Title: Message Title
Mark Waite edited a comment on JENKINS-57772
Re: Build strategy for tags is not working, if you specify ignore tags lesser than 7days
I am unable to duplicate the problem that you are describing. Please provide instructions to create the job which is showing the failure. # Steps I took attempting to show the failure: * # # Create a multibranch Pipeline job using the GitHub branch source * # Disable all default behaviors (no branch discovery, no pull request discovery) * # Add the "Discover tags" behavior * # Add the build strategy "Tags" with an empty value for {{Ignore tags newer than}} * # Change the "Tags" build strategy {{Ignore tags older than}} from its default 7 to 1 * # Run the job, confirm that it selected no tags to be built and no branches to be built (because there have been no tags created on that repository in the last 1 day)The job definition I used is uploaded as [^config.xml]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199719.1559261241000.17121.1559271000240%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57772) Build strategy for tags is not working, if you specify ignore tags lesser than 7days
Title: Message Title vinoth SS commented on JENKINS-57772 Re: Build strategy for tags is not working, if you specify ignore tags lesser than 7days when you scan it is not detected tags less than 1 day, but can u create a new tag , It is detected but not triggered automated build. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199719.1559261241000.17119.1559270160123%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57772) Build strategy for tags is not working, if you specify ignore tags lesser than 7days
Title: Message Title
Mark Waite edited a comment on JENKINS-57772
Re: Build strategy for tags is not working, if you specify ignore tags lesser than 7days
I am unable to duplicate the problem that you are describing. Please provide instructions to create the job which is showing the failure.Steps I took attempting to show the failure:* Create a multibranch Pipeline job using the GitHub branch source* Disable all default behaviors (no branch discovery, no pull request discovery)* Add the "Discover tags" behavior* Add the build strategy "Tags" with an empty value for {{Ignore tags newer than}}* Change the "Tags" build strategy {{Ignore tags older than}} from its default 7 to 1* Run the job, confirm that it selected no tags to be built and no branches to be built (because there have been no tags created on that repository in the last 1 day) The job definition I used is uploaded as [^config.xml]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199719.1559261241000.17117.1559270040264%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57772) Build strategy for tags is not working, if you specify ignore tags lesser than 7days
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-57772 Build strategy for tags is not working, if you specify ignore tags lesser than 7days Change By: Mark Waite Attachment: config.xml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199719.1559261241000.17115.1559270040149%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57772) Build strategy for tags is not working, if you specify ignore tags lesser than 7days
Title: Message Title Mark Waite commented on JENKINS-57772 Re: Build strategy for tags is not working, if you specify ignore tags lesser than 7days I am unable to duplicate the problem that you are describing. Please provide instructions to create the job which is showing the failure. Steps I took attempting to show the failure: Create a multibranch Pipeline job using the GitHub branch source Disable all default behaviors (no branch discovery, no pull request discovery) Add the "Discover tags" behavior Add the build strategy "Tags" with an empty value for Ignore tags newer than Change the "Tags" build strategy Ignore tags older than from its default 7 to 1 Run the job, confirm that it selected no tags to be built and no branches to be built (because there have been no tags created on that repository in the last 1 day) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199719.1559261241000.17113.1559269920111%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57609) Finalize coding tasks for M1
Title: Message Title Jack Shen resolved as Fixed Jenkins / JENKINS-57609 Finalize coding tasks for M1 Change By: Jack Shen Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199536.1558535132000.17110.1559269380292%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57772) Build strategy for tags is not working, if you specify ignore tags lesser than 7days
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-57772 Build strategy for tags is not working, if you specify ignore tags lesser than 7days Change By: Mark Waite Component/s: basic-branch-build-strategies-plugin Component/s: branch-api-plugin Component/s: git-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199719.1559261241000.17106.1559266800280%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57772) Build strategy for tags is not working, if you specify ignore tags lesser than 7days
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-57772 Build strategy for tags is not working, if you specify ignore tags lesser than 7days Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199719.1559261241000.17108.1559266800304%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57773) nonexisting_workspace should be nonexistent_workspace
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-57773 nonexisting_workspace should be nonexistent_workspace Issue Type: Task Assignee: Unassigned Components: core Created: 2019-05-31 01:21 Priority: Minor Reporter: Josh Soref https://github.com/jenkinsci/jenkins/search?q=nonexisting_workspace_q=nonexisting_workspace Scheduling a new build to get a workspace. (nonexisting_workspace) Add Comment
[JIRA] (JENKINS-57665) Hubotapprove does not exclude build_user from approve/abort
Title: Message Title Naresh Rayapati closed an issue as Won't Fix Jenkins / JENKINS-57665 Hubotapprove does not exclude build_user from approve/abort Change By: Naresh Rayapati Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199598.1558710022000.17103.1559263140421%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57665) Hubotapprove does not exclude build_user from approve/abort
Title: Message Title Naresh Rayapati updated an issue Jenkins / JENKINS-57665 Hubotapprove does not exclude build_user from approve/abort Change By: Naresh Rayapati Issue Type: Bug Task Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199598.1558710022000.17097.1559262360353%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57665) Hubotapprove does not exclude build_user from approve/abort
Title: Message Title Naresh Rayapati updated an issue Jenkins / JENKINS-57665 Hubotapprove does not exclude build_user from approve/abort Change By: Naresh Rayapati Priority: Critical Minor Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199598.1558710022000.17100.1559262360402%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57665) Hubotapprove does not exclude build_user from approve/abort
Title: Message Title Naresh Rayapati commented on JENKINS-57665 Re: Hubotapprove does not exclude build_user from approve/abort Rashmi Nair hubotApprove is a just wrapper on top of input step, so it should have the same behavior as that step. My guess, make sure you aren't an admin on this Jenkins, admins can approve though they were not on the submitter list. if not probably some issue input step, I would log a follow up JIRA for that plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199598.1558710022000.17094.1559262300138%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47496) No automatic builds for tags
Title: Message Title vinoth SS commented on JENKINS-47496 Re: No automatic builds for tags Sure, thanks i have opened up the ticket : https://issues.jenkins-ci.org/browse/JENKINS-57772 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185952.1508325472000.17091.1559261700428%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57772) Build strategy for tags is not working, if you specify ignore tags lesser than 7days
Title: Message Title vinoth SS updated an issue Jenkins / JENKINS-57772 Build strategy for tags is not working, if you specify ignore tags lesser than 7days Change By: vinoth SS Build strategy for tags is not working, if you specify ignore tags lesser than 7daysMultibranch pipeline configuration on Automated build tags, Used Build strategy pluginAdded Tags–> Ignore tags older than as 1 (Events : No Automated automatic build is scheduled to trigger triggered for 1.*.* )it works only if you specify as 7 days older. (Anything less than 7 is ignoring automated build trigger for tag) Is this the expected one? shall we have a tags to restrict to build automatically only if that is less than one day too? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199719.1559261241000.17080.1559261580213%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57772) Build strategy for tags is not working, if you specify ignore tags lesser than 7days
Title: Message Title vinoth SS updated an issue Jenkins / JENKINS-57772 Build strategy for tags is not working, if you specify ignore tags lesser than 7days Change By: vinoth SS Attachment: Screen Shot 2019-05-31 at 9.09.23.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199719.1559261241000.17078.1559261460122%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57772) Build strategy for tags is not working, if you specify ignore tags lesser than 7days
Title: Message Title vinoth SS updated an issue Jenkins / JENKINS-57772 Build strategy for tags is not working, if you specify ignore tags lesser than 7days Change By: vinoth SS Attachment: Screen Shot 2019-05-31 at 9.00.22.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199719.1559261241000.17076.1559261341283%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57772) Build strategy for tags is not working, if you specify ignore tags lesser than 7days
Title: Message Title vinoth SS created an issue Jenkins / JENKINS-57772 Build strategy for tags is not working, if you specify ignore tags lesser than 7days Issue Type: Bug Assignee: Mark Waite Components: branch-api-plugin, git-plugin Created: 2019-05-31 00:07 Priority: Major Reporter: vinoth SS Build strategy for tags is not working, if you specify ignore tags lesser than 7days Multibranch pipeline configuration on Automated build tags, Used Build strategy plugin Added Tags–> Ignore tags older than as 1 (Events : No Automated build is scheduled to trigger) it works only if you specify as 7 days older. Is this the expected one? shall we have a tags to restrict to build automatically only if that is less than one day too? Add Comment
[JIRA] (JENKINS-57182) When configuring a Jira steps site in casc yaml file. If the Jenkins service is restarted, the site is duplicated in Jenkins config
Title: Message Title Naresh Rayapati commented on JENKINS-57182 Re: When configuring a Jira steps site in casc yaml file. If the Jenkins service is restarted, the site is duplicated in Jenkins config Not very sure on how jcasc plugin works I will look into it soon. I would encourage pull request if anyone interested in. Thank you. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198934.1556196877000.17071.1559261220121%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57191) Certificate Problem only with jira-step.plugin
Title: Message Title Naresh Rayapati commented on JENKINS-57191 Re: Certificate Problem only with jira-step.plugin Sounds good Lars Biermanski I am trying to get to this but unfortunately I didn't much time these days. Probably within next couple of weeks but not promising, but if you have some time pull request is welcome. Thank you for understanding. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198945.155625872.17068.1559261100334%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57765) No output returned from sshCommand
Title: Message Title Naresh Rayapati commented on JENKINS-57765 Re: No output returned from sshCommand Evan Hamrick Even I am trying to understand more about this behavior, but so far my understanding was that for these kind of quick commands like less than mill seconds there is always a chance that file streams would get close before the entire output being sent to it. so kind of hack but thats the option that we are using, as it is just a couple of seconds for the job that we are running for hours Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199712.155923150.17065.1559260980150%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57771) email ext plugin doesn't send emails
Title: Message Title Adil Ashraf created an issue Jenkins / JENKINS-57771 email ext plugin doesn't send emails Issue Type: Bug Assignee: David van Laatum Attachments: email_ext.jpg Components: email-ext-plugin Created: 2019-05-30 23:01 Priority: Critical Reporter: Adil Ashraf Not receiving email from email-ext plugin. All the configuration in jenkins looks fine, have attached screenshot for your reference. I am using Jenkins pipeline and even as per the logs it says the email is sent. However i am not receiving any email to outbox. Analyzing: exam...@foo.com Analyzing: exam...@foo.com Looking for: exam...@foo.com starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: exam...@foo.com => found type: 0 Adding recipients from trigger recipient list Successfully created MimeMessage Sending email to: exam...@foo.com using version 2.66 Add Comment
[JIRA] (JENKINS-49374) 'Could not find dependency command-launcher of [package]' for every installed plugin when trying to run the jenkins check for updates
Title: Message Title Michael Rush commented on JENKINS-49374 Re: 'Could not find dependency command-launcher of [package]' for every installed plugin when trying to run the jenkins check for updates This was happening for me too. Nathan Hodson's comment above helped resolve the issue. In the Advanced tab of Plugin Manager, my Update Site was previously configured to http://updates.jenkins-ci.org/update-center.json changing to https://updates.jenkins.io/current/update-center.json got updates working again. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188246.151784264.17041.1559256660167%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57173) Issue with Darcs SCM plugin saving build records
Title: Message Title Ilya Perminov commented on JENKINS-57173 Re: Issue with Darcs SCM plugin saving build records I compiled your new version without any issues and tested it with the latest Jenkins LTS. It works correctly. Thank you very much! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198924.1556132083000.17035.1559255220106%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57768) Throughput graph showing wrong data
Title: Message Title JJ K updated an issue Jenkins / JENKINS-57768 Throughput graph showing wrong data Change By: JJ K I am currently using Performance-plugin 3.16 to create throughput and response time graphs based on my web service test result. Response time aligns with the actual numbers (thread counts , elapsed time, and etc) I am seeing in my log but throughput is way off.For instance, when my Samples (total count ) increases, Response Time in my graph decreases (which as it should. The problem is correct) and Throughput also decreases. I believe Isn't Throughput is supposed to increase when Response Time becomes shorter and Samples count increases . ? Isn't Throughput supposed to be equal to Samples/duration of test in seconds?Ticket JENKINS-44410 states that a wrong throughput data issue in performance report was fixed in version 3.3. I don't know if the same issue is recurring or I am configuring something wrong. Another weird thing I noticed is that the first run of all my projects always has a high throughput rate. The throughput rate always declines after the first run. Am I supposed to clean out workspace/ or job/ directories after each run? I don't know if this helps troubleshooting this issue. I just wanted to share this as well. I would appreciate any help or clarification on this. JENKINSdfdsfsdf Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57770) For the life of me cannot get this to work
Title: Message Title Marky Jackson closed an issue as Incomplete I think I found my error Jenkins / JENKINS-57770 For the life of me cannot get this to work Change By: Marky Jackson Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199717.1559251055000.17030.1559254201720%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57769) Jenkins crashes with SIGSEGV SEGV_MAPERR in native code
Title: Message Title Mike Estes updated an issue Jenkins / JENKINS-57769 Jenkins crashes with SIGSEGV SEGV_MAPERR in native code Change By: Mike Estes Attachment: hs_err_pid689704.log.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199716.1559249411000.17027.1559253060052%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53162) Blueocean support for visualizing stages in parallel block in scripted pipeline
Title: Message Title Jake Hilborn updated an issue Jenkins / JENKINS-53162 Blueocean support for visualizing stages in parallel block in scripted pipeline Change By: Jake Hilborn Attachment: Screen Shot 2019-05-30 at 2.49.21 PM.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193173.1534855202000.16964.1559253003723%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53162) Blueocean support for visualizing stages in parallel block in scripted pipeline
Title: Message Title
Jake Hilborn commented on JENKINS-53162
Re: Blueocean support for visualizing stages in parallel block in scripted pipeline
leromarinvit Wow that actually works for scripted pipelines. The key is to have a stage inside the parallel block that has the same name as the parallel stage. Here's a working example.
parallel (
"one": {
stage("one") {
stage("one-child1") {
println "one-child1"
}
stage("one-child2") {
println "one-child2"
}
}
},
"two": {
stage("two") {
stage("two-child1") {
println "two-child1"
}
stage("two-child2") {
println "two-child2"
}
}
},
"three": {
stage("three") {
stage("three-child1") {
println "three-child1"
}
stage("three-child2") {
println "three-child2"
}
}
}
)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193173.1534855202000.16966.1559253003741%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29964) EC2 plugin floods AWS with API calls if it references a deleted AMI
Title: Message Title Luis Pollo edited a comment on JENKINS-29964 Re: EC2 plugin floods AWS with API calls if it references a deleted AMI If it helps anyone that lands here, I wanted to report that I ran across a very similar issue with the plugin, however upon further investigation determined that, in my case, all AMIs referenced in cloud profiles were still valid, but the plugin seems to be recurrently and indefinitely checking for EC2 instances that had either been stopped or deleted, and that had previously been configured as nodes in Jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164542.1439603071000.16902.1559252760112%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29964) EC2 plugin floods AWS with API calls if it references a deleted AMI
Title: Message Title Luis Pollo commented on JENKINS-29964 Re: EC2 plugin floods AWS with API calls if it references a deleted AMI I wanted to report that I ran across a very similar issue with the plugin, however upon further investigation determined that, in my case, all AMIs referenced in cloud profiles were still valid, but the plugin seems to be recurrently and indefinitely checking for EC2 instances that had either been stopped or deleted, and that had previously been configured as nodes in Jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164542.1439603071000.16899.1559252700201%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57770) For the life of me cannot get this to work
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-57770 For the life of me cannot get this to work Issue Type: Bug Assignee: Carlos Sanchez Attachments: log.rtfd.zip Components: kubernetes-plugin Created: 2019-05-30 21:17 Labels: kuberenetes-plugin Priority: Minor Reporter: Marky Jackson I have a very vanilla setup using kops on AWS. I also have a super simple job that just executes a shell and sleeps for 5 No matter what I try the agent always fails. I have searched old tickets, google and asked around to no avail. Any help is greatly appreciated This is what the pods look like and the logs are attached: NAME READY STATUS RESTARTS AGE jenkins-7c94bc6dc8-dlx5q 1/1 Running 0 17h worker-2qpq5 0/2 Pending 0 0s worker-2qpq5 0/2 Pending 0 0s worker-2qpq5 0/2 ContainerCreating 0 0s worker-2qpq5 1/2 Error 0 2s worker-cpnww 0/2 Pending 0 0s worker-cpnww 0/2 Pending 0 0s worker-cpnww 0/2 ContainerCreating 0 0s worker-cpnww 2/2 Running 0 2s worker-cpnww 1/2 Error 0 3s worker-hkgbx 0/2 Pending 0 0s worker-hkgbx 0/2 Pending 0 0s worker-hkgbx 0/2 ContainerCreating 0 0s worker-hkgbx
[JIRA] (JENKINS-55013) support for App Center
Title: Message Title Mez Pahlan updated JENKINS-55013 Jenkins / JENKINS-55013 support for App Center Change By: Mez Pahlan Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196049.1543936697000.16881.1559250901313%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55013) support for App Center
Title: Message Title Mez Pahlan updated JENKINS-55013 Jenkins / JENKINS-55013 support for App Center Change By: Mez Pahlan Status: In Review Resolved Resolution: Fixed Released As: 0.1.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196049.1543936697000.16883.1559250901332%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57630) Support Multi User Picker custom field parameter mapping for email address
Title: Message Title Wisen Tanasa updated an issue Jenkins / JENKINS-57630 Support Multi User Picker custom field parameter mapping for email address Change By: Wisen Tanasa Summary: Support Multi User Picker custom field parameter mapping for email address Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199560.1558603816000.16869.1559250901169%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55013) support for App Center
Title: Message Title Mez Pahlan started work on JENKINS-55013 Change By: Mez Pahlan Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196049.1543936697000.16865.1559250841183%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55013) support for App Center
Title: Message Title Mez Pahlan commented on JENKINS-55013 Re: support for App Center Hello again. I've published an alpha version that should be available in the repos in a few hours. If you have the time I would very much appreciate any feedback. https://wiki.jenkins.io/display/JENKINS/App+Center+Plugin Next on my list of things to do is to add support for change notes / release notes. But any further early feedback is welcomed. Sorry that took so long. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196049.1543936697000.16853.1559250841046%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57630) Support Multi User Picker custom field parameter mapping
Title: Message Title Wisen Tanasa commented on JENKINS-57630 Re: Support Multi User Picker custom field parameter mapping Thanks for sharing them here Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199560.1558603816000.16867.1559250841206%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57769) Jenkins crashes with SIGSEGV SEGV_MAPERR in native code
Title: Message Title
Mike Estes updated an issue
Jenkins / JENKINS-57769
Jenkins crashes with SIGSEGV SEGV_MAPERR in native code
Change By:
Mike Estes
We've not been able to narrow down the exact repro.We've had 2 different instances servers with the jenkins master running on them crash in a similar way, it always appears to be random memory addresses for the SIGSEGV SEGV_MAPERR crash.All I could narrow it down to is that it happens during the day when devs are likely to be either in the UI, using plugins, pushing changes that might trigger a job, etc. Outside of those hours I haven't noticed any of these crashes. Though even some days the crashes wouldn't happen, other days it happened many times throughout the day. No particular patterns that I could find.We also appear to be able to run fine when we downgrade to 2.168, no crashes yet there on either of the instances servers .I can provide more of the log files it generates if it helps. And can add other log files but they're all very similar.I'm new to debugging Java issues and tried to search for ways of narrowing it down but it seems that it happening in native code has made it difficult for me to provide more useful information. I even tried upping the verbosity of the logging but that didn't seem to change much if it's in the same jenkins.log files.If you have any other information or tools I might use to better narrow down the issue please let me know as I'd like to get this figured out so that we can update to a version of Jenkins that doesn't regularly crash. {noformat}## A fatal error has been detected by the Java Runtime Environment:## SIGSEGV (0xb) at pc=0x7fff342d05d0, pid=689704, tid=0x7fff9cbfd700## JRE version: OpenJDK Runtime Environment (8.0_212-b03) (build 1.8.0_212-8u212-b03-0ubuntu1.16.04.1-b03)# Java VM: OpenJDK 64-Bit Server VM (25.212-b03 mixed mode linux-amd64 compressed oops)# Problematic frame:# C 0x7fff342d05d0## Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again## If you would like to submit a bug report, please visit:# http://bugreport.java.com/bugreport/crash.jsp#--- T H R E A D ---Current thread is native threadsiginfo: si_signo: 11 (SIGSEGV), si_code: 1 (SEGV_MAPERR), si_addr: 0x7fff342d05d0Registers:RAX=0x0001, RBX=0x7fff9cbfda68, RCX=0x7fff9cbfd700, RDX=0x7fff342d05d0RSP=0x7fff9cbfcf18, RBP=0x7fffee018318, RSI=0x, RDI=0x7ffcd8049740R8 =0x7ffcd803c460, R9 =0x0001, R10=0x10e0, R11=0x7fffee2002d8R12=0x, R13=0x7fffee0182c8, R14=0x0004, R15=0x7fff9cbfdc18RIP=0x7fff342d05d0, EFLAGS=0x00010206, CSGSFS=0x004b0053, ERR=0x0014 TRAPNO=0x000eTop of Stack: (sp=0x7fff9cbfcf18)0x7fff9cbfcf18: 7fffede06439 7fffa6bfd10f0x7fff9cbfcf28: 0x7fff9cbfcf38:
[JIRA] (JENKINS-57769) Jenkins crashes with SIGSEGV SEGV_MAPERR in native code
Title: Message Title Mike Estes created an issue Jenkins / JENKINS-57769 Jenkins crashes with SIGSEGV SEGV_MAPERR in native code Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-05-30 20:50 Environment: Jenkins ver. 2.178 Ubuntu 16.04 Priority: Critical Reporter: Mike Estes We've not been able to narrow down the exact repro. We've had 2 different instances crash in a similar way, it always appears to be random memory addresses for the SIGSEGV SEGV_MAPERR crash. All I could narrow it down to is that it happens during the day when devs are likely to be either in the UI, using plugins, pushing changes that might trigger a job, etc. Outside of those hours I haven't noticed any of these crashes. Though even some days the crashes wouldn't happen, other days it happened many times throughout the day. No particular patterns that I could find. We also appear to be able to run fine when we downgrade to 2.168, no crashes yet there on either of the instances. I can provide more of the log files it generates if it helps. And can add other log files but they're all very similar. I'm new to debugging Java issues and tried to search for ways of narrowing it down but it seems that it happening in native code has made it difficult for me to provide more useful information. I even tried upping the verbosity of the logging but that didn't seem to change much if it's in the same jenkins.log files. If you have any other information or tools I might use to better narrow down the issue please let me know as I'd like to get this figured out so that we can update to a version of Jenkins that doesn't regularly crash.
[JIRA] (JENKINS-57672) Determine Dependencies between PluginManager.java on Jenkins Core
Title: Message Title Natasha Stopa commented on JENKINS-57672 Re: Determine Dependencies between PluginManager.java on Jenkins Core I created a diagram showing some of the dependencies between the Plugin Manager and Jenkins Core. Black arrows represent a superclass/subclass or interface relationship; green arrows represent some other kind of relationship/dependency, and next to the methods in red are dependencies on Jenkins Core. Because of the intricacy of the dependencies on Jenkins core, on the mentor call today we talked about instead either trying to only pull out the part of Plugin Manager that does plugin installations or having the library be completely separate, but input from mentors to confirm this decision would be appreciated. https://www.lucidchart.com/invitations/accept/f35d3b14-0d41-4dd8-a787-e765f4582de8 Kristin Whetstone, Arnab Banerjee Baptiste Mathus, Oleg Nenashev, Jon Brohauge Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199605.1558721108000.16834.1559248800256%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57672) Determine Dependencies between PluginManager.java on Jenkins Core
Title: Message Title Natasha Stopa updated JENKINS-57672 Jenkins / JENKINS-57672 Determine Dependencies between PluginManager.java on Jenkins Core Change By: Natasha Stopa Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199605.1558721108000.16836.1559248800409%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57768) Throughput graph showing wrong data
Title: Message Title JJ K updated an issue Jenkins / JENKINS-57768 Throughput graph showing wrong data Change By: JJ K Summary: Throughput graph show showing wrong data Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199715.1559245185000.16832.1559245260112%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57768) Throughput graph show wrong data
Title: Message Title JJ K created an issue Jenkins / JENKINS-57768 Throughput graph show wrong data Issue Type: Bug Assignee: Andrey Pokhilko Components: performance-plugin Created: 2019-05-30 19:39 Labels: performance plugin Priority: Critical Reporter: JJ K I am currently using Performance-plugin 3.16 to create throughput and response time graphs based on my web service test result. Response time aligns with the actual counts I am seeing in my log but throughput is way off. For instance, when my Samples count increases, Response Time in my graph decreases (which is correct) and Throughput also decreases. I believe Throughput is supposed to increase when Response Time becomes shorter and Samples count increases. Isn't Throughput supposed to be equal to Samples/duration of test in seconds? Ticket JENKINS-44410 states that a wrong throughput data issue in performance report was fixed in version 3.3. I don't know if the same issue is recurring or I am configuring something wrong. I would appreciate any help or clarification on this. JENKINSdfdsfsdf
[JIRA] (JENKINS-56007) Can't copy source files from slave to master if security is enabled
Title: Message Title Roman Pickl commented on JENKINS-56007 Re: Can't copy source files from slave to master if security is enabled Ok thanks. No it did not. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197425.1549494089000.16823.1559244480259%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57766) Configuring Global Pipeline Libraries in GUI doesn't save retrieval method
Title: Message Title Kelvin Acosta updated an issue Jenkins / JENKINS-57766 Configuring Global Pipeline Libraries in GUI doesn't save retrieval method Change By: Kelvin Acosta Environment: Jenkins 1 2 .164.3Pipeline: Shared Groovy Libraries 2.13 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199713.1559241707000.16820.1559244060057%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56007) Can't copy source files from slave to master if security is enabled
Title: Message Title Ulli Hafner commented on JENKINS-56007 Re: Can't copy source files from slave to master if security is enabled No, it is not required anymore. (I thought, whitelisting did not work as advertised?) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197425.1549494089000.16819.1559242380309%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57767) Remote call failed
Title: Message Title
John Zila updated an issue
Jenkins / JENKINS-57767
Remote call failed
Change By:
John Zila
Builds are randomly failing when assigned to some linux agents. Those agents are part of a fleet that behaves identically to whose other instances that work. Usually disconnecting then reconnecting to the instance fixes the problem. The builds that experience this issue fail pretty much right away.{noformat}java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:177) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:286)Caused: hudson.remoting.RemotingSystemException at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:299) at com.sun.proxy.$Proxy5.fetch(Unknown Source) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:315) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:763) at java.lang.ClassLoader.defineClass(ClassLoader.java:642) at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:383) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:307) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) at java.lang.Class.getDeclaredMethod(Class.java:2128) at java.io.ObjectStreamClass.getPrivateMethod(ObjectStreamClass.java:1629) at java.io.ObjectStreamClass.access$1700(ObjectStreamClass.java:79) at java.io.ObjectStreamClass$3.run(ObjectStreamClass.java:520) at java.io.ObjectStreamClass$3.run(ObjectStreamClass.java:494) at java.security.AccessController.doPrivileged(Native Method) at java.io.ObjectStreamClass.(ObjectStreamClass.java:494) at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:391) at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:681) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1885) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1751) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2042) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1573) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2287) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2211) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2069) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1573) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2287) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2211) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2069) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1573) at
[JIRA] (JENKINS-57767) Remote call failed
Title: Message Title John Zila created an issue Jenkins / JENKINS-57767 Remote call failed Issue Type: Bug Assignee: Jeff Thompson Components: remoting Created: 2019-05-30 18:44 Priority: Critical Reporter: John Zila Builds are randomly failing when assigned to some linux agents. Those agents are part of a fleet that behaves identically to other instances that work. Usually disconnecting then reconnecting to the instance fixes the problem. The builds that experience this issue fail pretty much right away. java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:177) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:286) Caused: hudson.remoting.RemotingSystemException at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:299) at com.sun.proxy.$Proxy5.fetch(Unknown Source) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:315) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:763) at java.lang.ClassLoader.defineClass(ClassLoader.java:642) at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:383) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:307) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) at java.lang.Class.getDeclaredMethod(Class.java:2128) at java.io.ObjectStreamClass.getPrivateMethod(ObjectStreamClass.java:1629) at
[JIRA] (JENKINS-57766) Configuring Global Pipeline Libraries in GUI doesn't save retrieval method
Title: Message Title Kelvin Acosta created an issue Jenkins / JENKINS-57766 Configuring Global Pipeline Libraries in GUI doesn't save retrieval method Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2019-05-30 at 2.28.45 PM.png Components: workflow-cps-global-lib-plugin Created: 2019-05-30 18:41 Environment: Jenkins 1.164.3 Pipeline: Shared Groovy Libraries 2.13 Priority: Major Reporter: Kelvin Acosta We recently updated our Pipeline: Shared Groovy Libraries plugin from 2.8 to 2.13. As a side effect of upgrading, our retrieval method was wiped. We added the retrieval method again and set it to use GitHub and saved the configuration. Now every time we go back to the jenkins configuration screen, without modifying the Global Pipeline Libraries, the retrieval method is gone. So if someone were to change a different setting entirely, It would get rid of the retrieval method that was set causing issues to our jobs that depend on these shared libraries. I attached a screenshot of what the retrieval method looks like every time on the configuration screen no matter if the retrieval method has been set and saved before.
[JIRA] (JENKINS-56007) Can't copy source files from slave to master if security is enabled
Title: Message Title Roman Pickl commented on JENKINS-56007 Re: Can't copy source files from slave to master if security is enabled Great! Thanks for the update. Is whitelisting still needed after this change? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197425.1549494089000.16801.1559240880248%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55726) GitHub commit status context not unique enough or configurable - jobs always overwrite each other
Title: Message Title Jon-Paul Sullivan commented on JENKINS-55726 Re: GitHub commit status context not unique enough or configurable - jobs always overwrite each other Liam Newman, I did not change it, but I do think that the default behaviour of the plugin should not be one that allows information loss. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196920.154815684.16792.1559236560266%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51291) 'new view' wrong url - not relative
Title: Message Title Michael Keyser commented on JENKINS-51291 Re: 'new view' wrong url - not relative Can confirm this is still an issue and my environment is configured similar to original reporter. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190625.1526291411000.16787.1559235780218%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57765) No output returned from sshCommand
Title: Message Title Evan Hamrick edited a comment on JENKINS-57765 Re: No output returned from sshCommand Hey [~nrayapati], adding a sleep seems to work but I have to admit I don't understand why–it's like the sshCommand runs successfully but Jenkins closes the job before the result comes back? Edit- Doing some editing searching for log truncation specifically I found this, seems pretty similar to what I"m seeing: https://issues.jenkins-ci.org/browse/JENKINS-29198 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199712.155923150.16782.1559235070175%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57765) No output returned from sshCommand
Title: Message Title Evan Hamrick edited a comment on JENKINS-57765 Re: No output returned from sshCommand Hey [~nrayapati], adding a sleep seems to work but I have to admit I don't understand why–it's like the sshCommand runs successfully but Jenkins closes the job before the result comes back? Edit- Doing some editing searching for log truncation specifically I found this, seems pretty similar to what I"m seeing: https://issues.jenkins-ci.org/browse/JENKINS-29198 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199712.155923150.16784.1559235120031%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57765) No output returned from sshCommand
Title: Message Title Evan Hamrick edited a comment on JENKINS-57765 Re: No output returned from sshCommand Hey [~nrayapati], adding a sleep seems to work but I have to admit I don't understand why–it's like the sshCommand runs successfully but Jenkins closes the job before the result comes back? Edit- Doing some editing for log truncation specifically I found this, seems pretty similar to what I"m seeing: https://issues.jenkins-ci.org/browse/JENKINS-29198 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199712.155923150.16780.1559234820845%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28942) Allow plugins to declare that they do not use certain implied dependencies
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-28942 Allow plugins to declare that they do not use certain implied dependencies Change By: Jesse Glick Assignee: Baptiste Mathus Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.163400.1434531203000.16778.1559234820827%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48578) Create BOM for components included into the Core
Title: Message Title Jesse Glick commented on JENKINS-48578 Re: Create BOM for components included into the Core A possible subtask: move symbol-annotation out of the structs-plugin repository, as it rarely changes and does not need the same lifecycle. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187218.151334614.16765.1559234820649%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28942) Allow plugins to declare that they do not use certain implied dependencies
Title: Message Title Jesse Glick stopped work on JENKINS-28942 Change By: Jesse Glick Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.163400.1434531203000.16773.1559234820769%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56927) Request: EC2 plugin should use SSH keys via credentials plugin
Title: Message Title Kinnaird McQuade commented on JENKINS-56927 Re: Request: EC2 plugin should use SSH keys via credentials plugin I don't have the expertise to make this kind of modifications, unfortunately. Also don't have the time to do it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198606.1554663571000.16768.1559234820692%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56927) Request: EC2 plugin should use SSH keys via credentials plugin
Title: Message Title Kinnaird McQuade edited a comment on JENKINS-56927 Re: Request: EC2 plugin should use SSH keys via credentials plugin [~thoulen] - any updates on this? This is a pretty serious security issue.[~jbochenski] - we do check in our JCasC to Git, but the SSH key isn't rendered when it's in Git. We followed this approach: * Terraform generates the SSH key * JCasC is in a templates/jcasc.yml file * Terraform uses the `template_file` data source to inject parameters into the template file * Private key is loaded into the build file properly using `jsonencode` and `chomp` Terraform functions * aws_s3_object is used to take the rendered template and load it to a locked down S3 bucket. * We used [my-bloody-jenkins]([https://github.com/odavid/my-bloody-jenkins]) and passed in the S3 object key location into the container via environment variables. This container runs on AWS ECS with a Task role that is permitted to access the S3 bucket. This way, it can grab it at launch. ** Additionally, all secrets are set via AWS Parameter store, so they are accessible as environment variables on the container, which JCasC then reads.It's a sound approach workaround , but still, the private key is still embedded in the JCasC at some point. At least in this case, the private key is not checked into Git, but it's still stored as part of the JCasC file in S3. They need to fix this ASAP. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198606.1554663571000.16758.1559234760110%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56927) Request: EC2 plugin should use SSH keys via credentials plugin
Title: Message Title Kinnaird McQuade commented on JENKINS-56927 Re: Request: EC2 plugin should use SSH keys via credentials plugin FABRIZIO MANFREDI - any updates on this? This is a pretty serious security issue. Jakub Bochenski - we do check in our JCasC to Git, but the SSH key isn't rendered when it's in Git. We followed this approach: Terraform generates the SSH key JCasC is in a templates/jcasc.yml file Terraform uses the `template_file` data source to inject parameters into the template file Private key is loaded into the build file properly using `jsonencode` and `chomp` Terraform functions aws_s3_object is used to take the rendered template and load it to a locked down S3 bucket. We used [my-bloody-jenkins](https://github.com/odavid/my-bloody-jenkins) and passed in the S3 object key location into the container via environment variables. This container runs on AWS ECS with a Task role that is permitted to access the S3 bucket. This way, it can grab it at launch. Additionally, all secrets are set via AWS Parameter store, so they are accessible as environment variables on the container, which JCasC then reads. It's a sound approach, but still, the private key is still embedded in the JCasC at some point. At least in this case, the private key is not checked into Git, but it's still stored as part of the JCasC file in S3. They need to fix this ASAP. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57765) No output returned from sshCommand
Title: Message Title Evan Hamrick commented on JENKINS-57765 Re: No output returned from sshCommand Hey Naresh Rayapati, adding a sleep seems to work but I have to admit I don't understand why–it's like the sshCommand runs successfully but Jenkins closes the job before the result comes back? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199712.155923150.16753.1559233500085%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57765) No output returned from sshCommand
Title: Message Title
Naresh Rayapati commented on JENKINS-57765
Re: No output returned from sshCommand
def remote = [:]
remote.name = 'Test run'
remote.host = 'host'
remote.filetransfer = 'SCP'
remote.allowAnyHosts = true
remote.appendName = true
remote.logLevel = 'FINEST'
remote.pty = true
node
{
withCredentials([usernamePassword(credentialsId: 'user', passwordVariable: 'p', usernameVariable: 'u')])
{
remote.user = u
remote.password = p
stage('Remote SSH')
{
sshCommand remote: remote, command: "cd / && ls"
}
}
sleep 5
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199712.155923150.16751.1559232840392%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57765) No output returned from sshCommand
Title: Message Title Naresh Rayapati commented on JENKINS-57765 Re: No output returned from sshCommand Evan Hamrick By chance are you running on k8s agents? or some kind of dynamic agents? if so I would sleep at the end for about couple of seconds to catch up the logs Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199712.155923150.16748.1559232720238%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56768) Unable to switch to a sudo user using ssh pipeline
Title: Message Title Naresh Rayapati closed an issue as Won't Fix Jenkins / JENKINS-56768 Unable to switch to a sudo user using ssh pipeline Change By: Naresh Rayapati Status: In Progress Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198411.1553644739000.16745.1559232300363%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56768) Unable to switch to a sudo user using ssh pipeline
Title: Message Title Naresh Rayapati commented on JENKINS-56768 Re: Unable to switch to a sudo user using ssh pipeline Anurag GADDAMANUGU Closing this request as it is been a while we don't have any updates. Please log a new ticket of reopen this one if you need more details. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198411.1553644739000.16742.1559232300319%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57269) Declarative pipeline with ssh-steps-plugin
Title: Message Title Naresh Rayapati edited a comment on JENKINS-57269 Re: Declarative pipeline with ssh-steps-plugin As mentioned before please use script block to execute these steps within declarative pipelines. And in the above code, it isn't setting the credentials to the remote: please follow the documentation on the readme for more information. https://github.com/jenkinsci/ssh-steps-plugin#configurationusername identityFile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199035.1556696089000.16739.1559232180138%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57269) Declarative pipeline with ssh-steps-plugin
Title: Message Title Naresh Rayapati commented on JENKINS-57269 Re: Declarative pipeline with ssh-steps-plugin As mentioned before please use script block to execute these steps within declarative pipelines. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199035.1556696089000.16736.1559232000229%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57765) No output returned from sshCommand
Title: Message Title
Evan Hamrick created an issue
Jenkins / JENKINS-57765
No output returned from sshCommand
Issue Type:
Bug
Assignee:
Naresh Rayapati
Components:
ssh-steps-plugin
Created:
2019-05-30 15:51
Environment:
Jenkins 2.164.1 ssh-steps 1.2.1
Priority:
Minor
Reporter:
Evan Hamrick
Setting up a test case to verify a few things at once--ssh-steps, service account creation, and so forth, by running a simple command on a remote server and getting the output. I'm seeing that the ssh connection seems to work and the command is executed, but output doesn't reliably come back. Looking through the console output I can't help but notice that
logging = none
is in the command parameters, but I can't find that documented anywhere. Could that be part of the problem? Here is my script:
def remote = [:]
remote.name = 'Test run'
remote.host = 'host'
remote.filetransfer = 'SCP'
remote.allowAnyHosts = true
remote.appendName = true
remote.logLevel = 'FINEST'
remote.pty = true
node
{
withCredentials([usernamePassword(credentialsId: 'user', passwordVariable: 'p', usernameVariable: 'u')])
{
remote.user = u
remote.password = p
stage('Remote SSH')
{
sshCommand remote: remote, command: "cd / && ls"
}
}
}
[JIRA] (JENKINS-48631) Automatically remove the cache created on disk when lightweight checkout is used
Title: Message Title Liam Newman commented on JENKINS-48631 Re: Automatically remove the cache created on disk when lightweight checkout is used Lorenzo Solano Martinez Lightweight checkout is not part of git-plugin, so that plugin has no way of controlling that. Having a way to clean them up makes sense, but determining when to do so automatically would be difficult. Which plugin is alternating between lightweight checkout and not? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187285.151369896.16723.1559230200199%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47867) Make "Committers To Ignore" configurable via traits
Title: Message Title Liam Newman started work on JENKINS-47867 Change By: Liam Newman Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186379.1510079108000.16718.1559229660255%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47496) No automatic builds for tags
Title: Message Title Liam Newman commented on JENKINS-47496 Re: No automatic builds for tags vinoth SS Please open a new JIRA for that. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185952.1508325472000.16708.1559229540392%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55726) GitHub commit status context not unique enough or configurable - jobs always overwrite each other
Title: Message Title Liam Newman commented on JENKINS-55726 Re: GitHub commit status context not unique enough or configurable - jobs always overwrite each other Jon-Paul Sullivan I see you changed this to in-progress. What else needs to be done here? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196920.154815684.16703.1559229480205%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48361) ‘Jenkinsfile’ not found when PR triggers a build with Bitbucket
Title: Message Title Stacy Bowler commented on JENKINS-48361 Re: ‘Jenkinsfile’ not found when PR triggers a build with Bitbucket I dont' think I've seen an issue like this in some time. Currently our Jenkins server is firewalled off from the Bitbucket server so we can only pull and are not even using webhooks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186956.1512391291000.16691.1559229300276%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57661) The incrementals-publisher does not provide a reason for some 400 Bad Request errors
Title: Message Title Chris Kilding closed an issue as Duplicate Jenkins / JENKINS-57661 The incrementals-publisher does not provide a reason for some 400 Bad Request errors Change By: Chris Kilding Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199594.1558701241000.16680.1559226900457%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33596) Disable DNSMultiCast & UDPBroadcastThread by default
Title: Message Title Jesse Glick stopped work on JENKINS-33596 Change By: Jesse Glick Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.169040.1458146484000.16674.1559224020622%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57740) M1-Extract the plugin from system configure to a standalone page
Title: Message Title Jeff Pearce updated an issue Jenkins / JENKINS-57740 M1-Extract the plugin from system configure to a standalone page Change By: Jeff Pearce * Settings are accessed via a management link instead of global config * Settings are persisted (maybe via Saveable implementation) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199685.1559142249000.1.1559223480099%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57764) Document developer workflow for changing React component in a README in the repo
Title: Message Title Jeff Pearce created an issue Jenkins / JENKINS-57764 Document developer workflow for changing React component in a README in the repo Issue Type: New Feature Assignee: Jack Shen Components: working-hours-plugin Created: 2019-05-30 13:34 Labels: gsoc-2019 Priority: Minor Reporter: Jeff Pearce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-57740) M1-Extract the plugin from system configure to a standalone page
Title: Message Title Jeff Pearce started work on JENKINS-57740 Change By: Jeff Pearce Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199685.1559142249000.16662.1559223240221%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57636) Show job link and charts even if latest build does not contain results
Title: Message Title Jakub Pawlinski commented on JENKINS-57636 Re: Show job link and charts even if latest build does not contain results possibility of empty build action would do just right Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199566.1558606318000.16660.1559222940120%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title akostadinov commented on JENKINS-44930 Re: Allow sh to return exit status, stdout and stderr all at once Suraj Sharma, and if you have a multiline string that function works in a surprising way. It needs to be done on the lower level by the plugin to be reliable. I actually wonder if we can have a console wrapper that will capture whatever output produced inside. Like AnsiColor Plugin. It will not be able to differentiate stdin from stderr though. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183003.149756330.16582.1559221921649%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56927) Request: EC2 plugin should use SSH keys via credentials plugin
Title: Message Title Jakub Bochenski commented on JENKINS-56927 Re: Request: EC2 plugin should use SSH keys via credentials plugin Also if you want to use JCasC it will force you to enter the ssh key in plaintext in JCasC yaml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198606.1554663571000.16580.1559220780116%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55491) AWS Private key stored as plain text - when using Config as Code plugin
Title: Message Title Jakub Bochenski closed an issue as Duplicate Jenkins / JENKINS-55491 AWS Private key stored as plain text - when using Config as Code plugin Change By: Jakub Bochenski Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196622.1547051812000.16577.1559220720316%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57760) Add support for webhooks management
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57760 Add support for webhooks management Change By: Parichay Barpanda Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199706.1559207961000.16572.1559216280340%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57749) Latest terraform version (0.12.0) not available for download via global tool installation from bintray
Title: Message Title David Goate edited a comment on JENKINS-57749 Re: Latest terraform version (0.12.0) not available for download via global tool installation from bintray Thanks [~dpires]. Any clues on how to "invalidate" the cache , or who might be better placed to know ? Things i have already tried: * restart jenkins * reload config from disk * uninstall and reinstall the plugin from scratch * manually edit the file /var/lib/jenkins/org.jenkinsci.plugins.terraform.TerraformBuildWrapper.xml to change the version string and reload jenkins config from disk * restart the serverin all cases above I have not been able to get the plugin to show the desired 0.12.0 build as an option, even when hardcoding that into the org.jenkinsci.plugins.terraform.TerraformBuildWrapper.xml file. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199694.155915236.16574.1559216280364%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57749) Latest terraform version (0.12.0) not available for download via global tool installation from bintray
Title: Message Title David Goate commented on JENKINS-57749 Re: Latest terraform version (0.12.0) not available for download via global tool installation from bintray Thanks David Pires. Any clues on how to "invalidate" the cache? Things i have already tried: restart jenkins reload config from disk uninstall and reinstall the plugin from scratch manually edit the file /var/lib/jenkins/org.jenkinsci.plugins.terraform.TerraformBuildWrapper.xml to change the version string and reload jenkins config from disk restart the server in all cases above I have not been able to get the plugin to show the desired 0.12.0 build as an option, even when hardcoding that into the org.jenkinsci.plugins.terraform.TerraformBuildWrapper.xml file. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199694.155915236.16571.1559216280319%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57747) Add form validation for gitlab gold and ultimate server urls
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57747 Add form validation for gitlab gold and ultimate server urls Change By: Parichay Barpanda Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199692.1559151818000.16569.1559216220176%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57763) trigger-parameterized-builds doesn't propagate results upstream
Title: Message Title Alexander Todorov created an issue Jenkins / JENKINS-57763 trigger-parameterized-builds doesn't propagate results upstream Issue Type: Bug Assignee: Unassigned Components: parameterized-trigger-plugin Created: 2019-05-30 11:35 Priority: Critical Reporter: Alexander Todorov Jenkins ver. 2.121.3 Parameterized Trigger Plugin v2.35.2 My config is as follows (using Jenkins Job Builder): ``` publishers: trigger-parameterized-builds: project: runtest block: true current-parameters: true node-label: '$SLAVE_VM_NAME' condition: 'SUCCESS' fail-on-missing: true ``` I can see the "runtest" job triggered and executing. It also looks like it is successfully blocking the current job although I couldn't find the `block` parameter documented. However my "runtest" job failed but the status of the upstream job was still SUCCESS! This breaks the entire pipeline I am trying to build. FTR using builders.trigger-builds with block=true does propagate the results properly but I am unable to use it due to other constraints (other downstream jobs require artifacts from the current job which we need to upload BEFORE the runtest job is started).
[JIRA] (JENKINS-57698) Results are not saving in the mentioned directory after the execution in Execute Microfocus Test from Filesystem
Title: Message Title tanmoy roy commented on JENKINS-57698 Re: Results are not saving in the mentioned directory after the execution in Execute Microfocus Test from Filesystem Thanks Rolando-Mihai Vlad, when can we expect a new release for this plugin. The feature will be available after next release most likely. >> And is it confirmed that the feature will be in the next release? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199636.155895364.16566.1559215980103%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
