[JIRA] (JENKINS-46592) Issue with Graph Plugin
Title: Message Title Bruno P. Kinoshita commented on JENKINS-46592 Re: Issue with Graph Plugin Available in the experimental update center, as 2.0-alpha-1. In order to release the plug-in, had to update the version of Jenkins it it built against. That resulted in new Findbugs issues. Fixing some of these errors, I realized I am not too sure about backward compatibility now. So bumped up the version to 2.0, and did a bit more of cleaning, like removing deprecated methods and fields. I will release the 2.0 version of the plugin by the next weekend if there are no issues reported for this alpha release. Thanks! Bruno Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184922.1504289511000.6898.1574757000487%40Atlassian.JIRA.
[JIRA] (JENKINS-59665) Rework sorting for Uninstall columns of Installed in Plugin Manager
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-59665 Rework sorting for Uninstall columns of Installed in Plugin Manager Change By: Oliver Gondža Released As: Jenkins 2. 105 205 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202357.1570213644000.6907.1574757121469%40Atlassian.JIRA.
[JIRA] (JENKINS-60267) Shorthand git step doesn't handle commit hashes
Title: Message Title Jeff MacLoue commented on JENKINS-60267 Re: Shorthand git step doesn't handle commit hashes Okay, valid point from Jesse Glick, but in this case the syntax is not "shorthand" but instead "broken and deprecated". Docs should say so right away - without adding more confusion about "limited functionality" or "different behaviour". Though it would definitely be nice to have it as advertised, a short syntax for 90% cases you face. Git is standard, and you rarely need to specify more than repo URL, credentials, and revision you want. PS Yes, full SHA commit hashes work the same - checkout() works with them and git() doesn't. As the logs I quoted show, git() uses different way to look revisions up, one that relies on them to be a HEAD of a branch or a tag in the remote repo (note "refs/remotes/origin/XXX" in rev-parse). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203255.1574683768000.6911.1574757900788%40Atlassian.JIRA.
[JIRA] (JENKINS-59793) Possible thread leak 'QueueSubTaskMetrics' in metrics - Allow finishing builds when SubTask badly fail
Title: Message Title Oliver Gondža commented on JENKINS-59793 Re: Possible thread leak 'QueueSubTaskMetrics' in metrics - Allow finishing builds when SubTask badly fail Ramon Leon, thanks for the prompt fix of the issue. I would appreciate if you can report back whether this fully mediated the problem in affected production deployment. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202523.1571157685000.6913.1574758380305%40Atlassian.JIRA.
[JIRA] (JENKINS-60145) Show full sidebar link name on hover
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-60145 Show full sidebar link name on hover Change By: Oliver Gondža Labels: UX lts 2.204.1 - candidate fixed UX ui Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203008.1573579369000.6922.1574758800303%40Atlassian.JIRA.
[JIRA] (JENKINS-59793) Possible thread leak 'QueueSubTaskMetrics' in metrics - Allow finishing builds when SubTask badly fail
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-59793 Possible thread leak 'QueueSubTaskMetrics' in metrics - Allow finishing builds when SubTask badly fail Change By: Oliver Gondža Labels: core lts 2.204.1 - candidate fixed core metrics Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202523.1571157685000.6926.1574759165303%40Atlassian.JIRA.
[JIRA] (TEST-184) Not relevant
Title: Message Title Radi Berkovich moved an issue test / TEST-184 Not relevant Change By: Radi Berkovich Project: Jenkins test Key: JENKINS TEST - 57044 184 Workflow: JNJira + In-Review Component/s: foo Component/s: hp-application-automation-tools-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkin
[JIRA] (TEST-185) Not relevant
Title: Message Title Radi Berkovich moved an issue test / TEST-185 Not relevant Change By: Radi Berkovich Project: Jenkins test Key: JENKINS TEST - 57036 185 Workflow: JNJira + In-Review Component/s: foo Component/s: hp-application-automation-tools-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkin
[JIRA] (TEST-184) Not relevant
Title: Message Title Radi Berkovich closed an issue as Fixed test / TEST-184 Not relevant Change By: Radi Berkovich Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198746.1555440611000.6937.1574759461759%40Atlassian.JIRA.
[JIRA] (TEST-186) Not relevant
Title: Message Title Radi Berkovich closed an issue as Fixed test / TEST-186 Not relevant Change By: Radi Berkovich Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198739.1555440421000.6936.1574759461469%40Atlassian.JIRA.
[JIRA] (TEST-186) Not relevant
Title: Message Title Radi Berkovich moved an issue test / TEST-186 Not relevant Change By: Radi Berkovich Project: Jenkins test Key: JENKINS TEST - 57037 186 Workflow: JNJira + In-Review Component/s: foo Component/s: hp-application-automation-tools-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkin
[JIRA] (TEST-185) Not relevant
Title: Message Title Radi Berkovich closed an issue as Fixed test / TEST-185 Not relevant Change By: Radi Berkovich Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198738.155544040.6938.1574759462155%40Atlassian.JIRA.
[JIRA] (TEST-187) Not relevant
Title: Message Title Radi Berkovich moved an issue test / TEST-187 Not relevant Change By: Radi Berkovich Project: Jenkins test Key: JENKINS TEST - 57039 187 Workflow: JNJira + In-Review Component/s: foo Component/s: hp-application-automation-tools-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkin
[JIRA] (TEST-187) Not relevant
Title: Message Title Radi Berkovich closed an issue as Fixed test / TEST-187 Not relevant Change By: Radi Berkovich Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198741.1555440452000.6940.1574759520579%40Atlassian.JIRA.
[JIRA] (TEST-190) Not relevant
Title: Message Title Radi Berkovich moved an issue test / TEST-190 Not relevant Change By: Radi Berkovich Project: Jenkins test Key: JENKINS TEST - 57040 190 Workflow: JNJira + In-Review Component/s: foo Component/s: hp-application-automation-tools-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkin
[JIRA] (JENKINS-60167) AtomicFileWriter performance issue on CephFS in case of Empty File creation
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-60167 AtomicFileWriter performance issue on CephFS in case of Empty File creation Change By: Oliver Gondža Labels: 2.204.1-rejected lts-candidate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203119.1573721452000.6943.1574759580501%40Atlassian.JIRA.
[JIRA] (TEST-188) Not relevant
Title: Message Title Radi Berkovich moved an issue test / TEST-188 Not relevant Change By: Radi Berkovich Project: Jenkins test Key: JENKINS TEST - 57038 188 Workflow: JNJira + In-Review Component/s: foo Component/s: hp-application-automation-tools-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkin
[JIRA] (TEST-189) Not relevant
Title: Message Title Radi Berkovich moved an issue test / TEST-189 Not relevant Change By: Radi Berkovich Project: Jenkins test Key: JENKINS TEST - 57041 189 Workflow: JNJira + In-Review Component/s: foo Component/s: hp-application-automation-tools-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkin
[JIRA] (TEST-189) Not relevant
Title: Message Title Radi Berkovich closed an issue as Fixed test / TEST-189 Not relevant Change By: Radi Berkovich Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198743.1555440555000.6947.1574759580580%40Atlassian.JIRA.
[JIRA] (TEST-188) Not relevant
Title: Message Title Radi Berkovich closed an issue as Fixed test / TEST-188 Not relevant Change By: Radi Berkovich Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198740.1555440445000.6945.1574759580524%40Atlassian.JIRA.
[JIRA] (TEST-191) Not relevant
Title: Message Title Radi Berkovich moved an issue test / TEST-191 Not relevant Change By: Radi Berkovich Project: Jenkins test Key: JENKINS TEST - 57043 191 Workflow: JNJira + In-Review Component/s: foo Component/s: hp-application-automation-tools-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkin
[JIRA] (TEST-190) Not relevant
Title: Message Title Radi Berkovich closed an issue as Fixed test / TEST-190 Not relevant Change By: Radi Berkovich Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198742.1555440467000.6949.1574759640318%40Atlassian.JIRA.
[JIRA] (TEST-192) Not relevant
Title: Message Title Radi Berkovich moved an issue test / TEST-192 Not relevant Change By: Radi Berkovich Project: Jenkins test Key: JENKINS TEST - 57042 192 Workflow: JNJira + In-Review Component/s: foo Component/s: hp-application-automation-tools-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkin
[JIRA] (TEST-191) Not relevant
Title: Message Title Radi Berkovich closed an issue as Fixed test / TEST-191 Not relevant Change By: Radi Berkovich Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198745.1555440574000.6951.1574759640483%40Atlassian.JIRA.
[JIRA] (TEST-194) Not relevant
Title: Message Title Radi Berkovich moved an issue test / TEST-194 Not relevant Change By: Radi Berkovich Project: Jenkins test Key: JENKINS TEST - 57046 194 Workflow: JNJira + In-Review Component/s: foo Component/s: hp-application-automation-tools-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkin
[JIRA] (TEST-193) Not relevant
Title: Message Title Radi Berkovich closed an issue as Fixed test / TEST-193 Not relevant Change By: Radi Berkovich Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198737.1555440393000.6955.1574759702032%40Atlassian.JIRA.
[JIRA] (TEST-193) Not relevant
Title: Message Title Radi Berkovich moved an issue test / TEST-193 Not relevant Change By: Radi Berkovich Project: Jenkins test Key: JENKINS TEST - 57035 193 Workflow: JNJira + In-Review Component/s: foo Component/s: hp-application-automation-tools-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkin
[JIRA] (TEST-192) Not relevant
Title: Message Title Radi Berkovich closed an issue as Fixed test / TEST-192 Not relevant Change By: Radi Berkovich Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198744.1555440561000.6953.1574759701494%40Atlassian.JIRA.
[JIRA] (TEST-194) Not relevant
Title: Message Title Radi Berkovich closed an issue as Fixed test / TEST-194 Not relevant Change By: Radi Berkovich Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198748.1555440615000.6957.1574759760127%40Atlassian.JIRA.
[JIRA] (JENKINS-59508) sidebar link names are not truncated causing funky rendering
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-59508 sidebar link names are not truncated causing funky rendering Change By: Oliver Gondža Labels: UX lts-candidate newbie-friendly ui Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202130.1569325102000.6971.1574759940759%40Atlassian.JIRA.
[JIRA] (JENKINS-59508) sidebar link names are not truncated causing funky rendering
Title: Message Title Oliver Gondža commented on JENKINS-59508 Re: sidebar link names are not truncated causing funky rendering JENKINS-60145 is beckported to 2.204.1 so there is no need for this to be a candidate (an the former part is included in baseline). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202130.1569325102000.6963.1574759940616%40Atlassian.JIRA.
[JIRA] (JENKINS-59508) sidebar link names are not truncated causing funky rendering
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-59508 sidebar link names are not truncated causing funky rendering Change By: Oliver Gondža Released As: Jenkins 2. 205 190 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202130.1569325102000.6969.1574759940731%40Atlassian.JIRA.
[JIRA] (JENKINS-59665) Rework sorting for Uninstall columns of Installed in Plugin Manager
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-59665 Rework sorting for Uninstall columns of Installed in Plugin Manager Change By: Oliver Gondža Labels: lts 2.204.1 - candidate fixed newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202357.1570213644000.6978.1574760240814%40Atlassian.JIRA.
[JIRA] (JENKINS-59793) Possible thread leak 'QueueSubTaskMetrics' in metrics - Allow finishing builds when SubTask badly fail
Title: Message Title Ramon Leon commented on JENKINS-59793 Re: Possible thread leak 'QueueSubTaskMetrics' in metrics - Allow finishing builds when SubTask badly fail It will take some time to land, I can give you some feedback by the end of December Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202523.1571157685000.6988.1574760300398%40Atlassian.JIRA.
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title
ovi craciun edited a comment on JENKINS-34610
Re: Windows AMI in endless loop
I am facing the same issue I have tried what [Alex Taylor|https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=ataylor] and [Brendan Stewart|https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=mumbles76] have suggested (all the settings for WinRM and everything else) but the master is still logging the same error:{code:java} EC2 (AWS ID account_id) - windows slave (sir-31i1js7h) booted at 1574726631000 Connecting to (17.30.6.34) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Waiting for WinRM to come up. Sleeping 10s.{code}However, I can telnet the slave on the 5985 port from master jenkins server and it connects. Does it mean it can't pass authentication or there's something else going won when the plugin is trying to connect via WinRM? The plugin doc is saying "By default, the plugin connects to the slave agent using an in-process Java SSH client.". What is the port is using the connect to this in-process ssh client? Any other ideas what should I try here? I've lost already two days to get this to work.Thank you
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170238.1462391043000.6991.1574760361297%40Atlassian.JIRA.
[JIRA] (JENKINS-59973) rtUpload / rtDownload fail with HTTP 401 / 403
Title: Message Title ethorsa commented on JENKINS-59973 Re: rtUpload / rtDownload fail with HTTP 401 / 403 I have manged to git bisect the causing commit: f2ca1492f64deb34b4cbb1ff286bd94411829bed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202777.157235158.7018.1574761026337%40Atlassian.JIRA.
[JIRA] (JENKINS-57512) Make About Jenkins always included in a bundle
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-57512 Make About Jenkins always included in a bundle Change By: Arnaud Héritier Component/s: cloudbees-jenkins-advisor-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199414.1558044714000.7028.1574762580364%40Atlassian.JIRA.
[JIRA] (JENKINS-57512) Make About Jenkins always included in a bundle
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-57512 Make About Jenkins always included in a bundle Change By: Arnaud Héritier Component/s: cloudbees-jenkins-advisor-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199414.1558044714000.7031.1574762700408%40Atlassian.JIRA.
[JIRA] (JENKINS-60281) Generating a support bundle with no about.md is useless
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-60281 Generating a support bundle with no about.md is useless Issue Type: Bug Assignee: Unassigned Components: cloudbees-jenkins-advisor-plugin Created: 2019-11-26 10:06 Priority: Major Reporter: Arnaud Héritier Related to JENKINS-57512, the problem comes from support-core as advisor is reusing/duplicating the same logic. A bundle with no about.md file is useless because our probes are using a lot of informations which are in this file (the product version ...) Maybe we could make the about component mandatory at least in Advisor if it is not in support-core Add Comment
[JIRA] (JENKINS-38669) SCM (Git) Will Not Notify Pipeline Before Execution
Title: Message Title
Angry Gami commented on JENKINS-38669
Re: SCM (Git) Will Not Notify Pipeline Before Execution
Ok, sorry for a delay. Now I have my fix working and it involves changes to 3 plugins: workflow-api
diff --git a/src/main/java/org/jenkinsci/plugins/workflow/flow/FlowDefinition.java b/src/main/java/org/jenkinsci/plugins/workflow/flow/FlowDefinition.java
index 55c29c7..ef71822 100644
--- a/src/main/java/org/jenkinsci/plugins/workflow/flow/FlowDefinition.java
+++ b/src/main/java/org/jenkinsci/plugins/workflow/flow/FlowDefinition.java
@@ -29,12 +29,15 @@ import hudson.Util;
import hudson.model.AbstractDescribableImpl;
import hudson.model.Action;
import hudson.model.TaskListener;
+import hudson.scm.SCM;
import hudson.util.LogTaskListener;
import javax.annotation.CheckForNull;
import javax.annotation.Nonnull;
import java.io.IOException;
import java.util.List;
+import java.util.Collection;
+import java.util.Collections;
import java.util.logging.Level;
import java.util.logging.Logger;
@@ -80,4 +83,7 @@ public abstract class FlowDefinition extends AbstractDescribableImplreturn (FlowDefinitionDescriptor) super.getDescriptor();
}
+public Collectionextends SCM> getSCMs() {
+return Collections.emptyList();
+}
}
Here I've added new method to FlowDefinition class that could be overridden by subclasses and by default it returns empty collection. This is meant to help subclasses of FlowDefinition to provide list of SCMs that it might be aware of.
workflow-cps
diff --git a/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition.java b/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition.java
index 6e665a8..6fcd729 100644
--- a/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition.java
+++ b/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition.java
@@ -46,6 +46,7 @@ import java.io.FileNotFoundException;
import java.io.IOException;
import java.io.InterruptedIOException;
import java.util.Collection;
+import java.util.Collections;
import java.util.List;
import jenkins.model.Jenkins;
import jenkins.scm.api.SCMFileSystem;
@@ -82,6 +83,11 @@ public class CpsScmFlowDefinition extends FlowDefinition {
return scm;
}
+@Override
+public Collectionextends SCM> getSCMs() {
+ return Collections.singletonList(scm);
+}
+
public String getScriptPath() {
return scriptPath;
}
Here I actually override getSCMs method from FlowDefinition for case when we are dealing with CpsScmFlowDefinition - i.e. definition of the flow that actually known to be based on SCM. For definitions that are based of inline script we can't tell if there are any SCM used until first build and this behavior is preserved. workflow-job
diff --git a/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowJob.java b/src/main/java/org/jenki
[JIRA] (JENKINS-38669) SCM (Git) Will Not Notify Pipeline Before Execution
Title: Message Title
Angry Gami edited a comment on JENKINS-38669
Re: SCM (Git) Will Not Notify Pipeline Before Execution
Ok, sorry for a delay. Now I have my fix working and it involves changes to 3 plugins:h4. workflow-api{code:java}diff --git a/src/main/java/org/jenkinsci/plugins/workflow/flow/FlowDefinition.java b/src/main/java/org/jenkinsci/plugins/workflow/flow/FlowDefinition.javaindex 55c29c7..ef71822 100644--- a/src/main/java/org/jenkinsci/plugins/workflow/flow/FlowDefinition.java+++ b/src/main/java/org/jenkinsci/plugins/workflow/flow/FlowDefinition.java@@ -29,12 +29,15 @@ import hudson.Util; import hudson.model.AbstractDescribableImpl; import hudson.model.Action; import hudson.model.TaskListener;+import hudson.scm.SCM; import hudson.util.LogTaskListener; import javax.annotation.CheckForNull; import javax.annotation.Nonnull; import java.io.IOException; import java.util.List;+import java.util.Collection;+import java.util.Collections; import java.util.logging.Level; import java.util.logging.Logger; @@ -80,4 +83,7 @@ public abstract class FlowDefinition extends AbstractDescribableImpl return (FlowDefinitionDescriptor) super.getDescriptor(); } +public Collection getSCMs() {+return Collections.emptyList();+} } {code} Here I've added new method to FlowDefinition class that could be overridden by subclasses and by default it returns empty collection. This is meant to help subclasses of FlowDefinition to provide list of SCMs that it might be aware of. {code} h4. workflow-cps{code:java}diff --git a/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition.java b/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition.javaindex 6e665a8..6fcd729 100644--- a/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition.java+++ b/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition.java@@ -46,6 +46,7 @@ import java.io.FileNotFoundException; import java.io.IOException; import java.io.InterruptedIOException; import java.util.Collection;+import java.util.Collections; import java.util.List; import jenkins.model.Jenkins; import jenkins.scm.api.SCMFileSystem;@@ -82,6 +83,11 @@ public class CpsScmFlowDefinition extends FlowDefinition { return scm; } +@Override+public Collection getSCMs() {+ return Collections.singletonList(scm);+}+ public String getScriptPath() { return scriptPath; }{code}Here I actually override getSCMs method from FlowDefinition for case when we are dealing with CpsScmFlowDefinition - i.e. definition of the flow that actually known to be based on SCM.For definitions that are based of inline script we can't tell if there are any SCM used until first build and this behavior is preserved.h4. workflow-job{code:java}diff --git a/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowJob.java b/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowJob.javaindex 57ea992..4c8b660 100644--- a/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowJob.java+++ b/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowJob.java@@ -531,7 +531,7 @@ public final class WorkflowJob extends Job implements L b = getLastCompletedBuild(); } if (b == null) {-return Collections.emptySet();+return definition != null ? definition.getSCMs() : Collections.emptySet(); } Map scms = new LinkedHashMap<>(); for (WorkflowRun.SCMCheckout co : b.checkouts(null)) {{code}And finally here I use getSCMs method from FlowDefinition to return known SCMs when there were no build happened yet.I can try to make pull requests from all of the above, though
[JIRA] (JENKINS-60270) Warnings-NG: recordIssue attribute 'name' probably ignored
Title: Message Title Ulli Hafner updated JENKINS-60270 Jenkins / JENKINS-60270 Warnings-NG: recordIssue attribute 'name' probably ignored Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed Released As: https://github.com/jenkinsci/warnings-ng-plugin/releases/tag/warnings-ng-7.2.2 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203260.157469810.7050.1574764741449%40Atlassian.JIRA.
[JIRA] (JENKINS-60270) Warnings-NG: recordIssue attribute 'name' probably ignored
Title: Message Title Ulli Hafner updated JENKINS-60270 Jenkins / JENKINS-60270 Warnings-NG: recordIssue attribute 'name' probably ignored Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203260.157469810.7052.1574764741917%40Atlassian.JIRA.
[JIRA] (JENKINS-60270) Warnings-NG: recordIssue attribute 'name' probably ignored
Title: Message Title Ulli Hafner reopened an issue Jenkins / JENKINS-60270 Warnings-NG: recordIssue attribute 'name' probably ignored Change By: Ulli Hafner Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203260.157469810.7056.1574764801889%40Atlassian.JIRA.
[JIRA] (JENKINS-60270) Warnings-NG: recordIssue attribute 'name' probably ignored
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-60270 Warnings-NG: recordIssue attribute 'name' probably ignored Change By: Ulli Hafner Released As: https://github.com/jenkinsci/warnings-ng-plugin/releases/tag/warnings-ng-7.2.2 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203260.157469810.7054.1574764801639%40Atlassian.JIRA.
[JIRA] (JENKINS-60270) Warnings-NG: recordIssue attribute 'name' probably ignored
Title: Message Title Ulli Hafner resolved as Duplicate Jenkins / JENKINS-60270 Warnings-NG: recordIssue attribute 'name' probably ignored Change By: Ulli Hafner Status: Reopened Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203260.157469810.7058.1574764802422%40Atlassian.JIRA.
[JIRA] (JENKINS-60263) Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not.
Title: Message Title Ulli Hafner updated JENKINS-60263 Jenkins / JENKINS-60263 Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not. Change By: Ulli Hafner Status: In Progress Fixed but Unreleased Resolution: Fixed Released As: [warnings-ng-7.2.2|https://github.com/jenkinsci/warnings-ng-plugin/releases/tag/warnings-ng-7.2.2] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203250.1574676933000.7060.1574764860348%40Atla
[JIRA] (JENKINS-60263) Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not.
Title: Message Title Ulli Hafner updated JENKINS-60263 Jenkins / JENKINS-60263 Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not. Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: [warnings-ng-7.2.2| https://github.com/jenkinsci/warnings-ng-plugin/releases/tag/warnings-ng-7.2.2 ] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203250.1574676933000.7062.1574764860383%40Atlassian.JIRA.
[JIRA] (JENKINS-38669) SCM (Git) Will Not Notify Pipeline Before Execution
Title: Message Title
Angry Gami commented on JENKINS-38669
Re: SCM (Git) Will Not Notify Pipeline Before Execution
I wrote a test for workflow-job project that shows the case and fix for it: pom.xml
diff --git a/pom.xml b/pom.xml
index b9b8e64..f255e37 100644
--- a/pom.xml
+++ b/pom.xml
@@ -93,13 +93,13 @@
org.jenkins-ci.plugins
script-security
-1.62
+1.63
test
org.jenkins-ci.plugins.workflow
workflow-cps
-2.74
+2.76
test
WorkflowJobTest.java
diff --git a/src/test/java/org/jenkinsci/plugins/workflow/job/WorkflowJobTest.java b/src/test/java/org/jenkinsci/plugins/workflow/job/WorkflowJobTest.java
index 53b27de..b32130f 100644
--- a/src/test/java/org/jenkinsci/plugins/workflow/job/WorkflowJobTest.java
+++ b/src/test/java/org/jenkinsci/plugins/workflow/job/WorkflowJobTest.java
@@ -69,6 +69,15 @@ public class WorkflowJobTest {
j.assertLogContains("second version", b2);
}
+@Issue("JENKINS-38669")
+@Test public void nonEmptySCMListForGitSCMJobBeforeBuild() throws Exception {
+WorkflowJob p = j.jenkins.createProject(WorkflowJob.class, "p");
+CpsScmFlowDefinition def = new CpsScmFlowDefinition(new GitSCM("I don't care"), "Jenkinsfile");
+assertEquals("Expecting one SCM for definition", 1, def.getSCMs().size());
+p.setDefinition(def);
+assertEquals("Expecting one SCM", 1, p.getSCMs().size());
+}
+
@Test
public void addAction() throws Exception {
WorkflowJob p = j.jenkins.createProject(WorkflowJob.class, "p");
Though I'm not sure this is good for master branch, I was working from repo tag 'workflow-job-2.36'.
Add Comment
[JIRA] (JENKINS-42369) agent docker parameters do not honor the current environment
Title: Message Title Philipp Jung commented on JENKINS-42369 Re: agent docker parameters do not honor the current environment Same issue here. Any chance to change the priority? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179270.1488278418000.7075.1574766120658%40Atlassian.JIRA.
[JIRA] (JENKINS-60251) multibranch streams don't allow lightweight checkout?
Title: Message Title Karl Wirth commented on JENKINS-60251 Re: multibranch streams don't allow lightweight checkout? HI Adam Smith - No need to aologise and great that you solved it. If there's anything else we can do to help, please let us know. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203241.1574477155000.7096.1574766780204%40Atlassian.JIRA.
[JIRA] (JENKINS-60213) P4 environment variables non-reentrant
Title: Message Title Karl Wirth commented on JENKINS-60213 Re: P4 environment variables non-reentrant James Bateman Thanks but no it didn't. That was 3 separate overlapping runs. Note that there is no '@' in the workspace name. Investigating if this is a problem with my test or the nightly build. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203186.1574180065000.7098.1574767260781%40Atlassian.JIRA.
[JIRA] (JENKINS-60213) P4 environment variables non-reentrant
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60213 P4 environment variables non-reentrant Change By: Karl Wirth Comment: [~jbateman]Thanks but no it didn't. That was 3 separate overlapping runs. Note that there is no '@' in the workspace name. Investigating if this is a problem with my test or the nightly build. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203186.1574180065000.7100.1574767500350%40Atlassian.JIRA.
[JIRA] (JENKINS-60213) P4 environment variables non-reentrant
Title: Message Title
Karl Wirth edited a comment on JENKINS-60213
Re: P4 environment variables non-reentrant
After discussing with the developers I tried the nightly with a different variable fix - but same behavior: - {code:java} See below for update. - #30 [JENKINS-60213-ConcurrentVariables] $ /bin/bash /tmp/jenkins6285754148517933441.sh == WORKSPACE:/var/lib/jenkins/workspace/JENKINS-60213-ConcurrentVariables P4_CLIENT:jenkins-master-JENKINS-60213-ConcurrentVariables-0 EXECUTOR NUMBER: 0 == #31 [JENKINS-60213-ConcurrentVariables] $ /bin/bash /tmp/jenkins6285754148517933441.sh == WORKSPACE:/var/lib/jenkins/workspace/JENKINS-60213-ConcurrentVariables P4_CLIENT:jenkins-master-JENKINS-60213-ConcurrentVariables-0 EXECUTOR NUMBER: 0 == #32 [JENKINS-60213-ConcurrentVariables] $ /bin/bash /tmp/jenkins6285754148517933441.sh == WORKSPACE:/var/lib/jenkins/workspace/JENKINS-60213-ConcurrentVariables P4_CLIENT:jenkins-master-JENKINS-60213-ConcurrentVariables-0 EXECUTOR NUMBER: 0 == {code} -
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this d
[JIRA] (JENKINS-60213) P4 environment variables non-reentrant
Title: Message Title Karl Wirth commented on JENKINS-60213 Re: P4 environment variables non-reentrant Hi James Bateman - Urgh. Sorry. You are correct. My fault for manually editing the URL. 30: [JENKINS-60213-ConcurrentVariables] $ /bin/bash /tmp/jenkins6285754148517933441.sh == WORKSPACE:/var/lib/jenkins/workspace/JENKINS-60213-ConcurrentVariables P4_CLIENT:jenkins-master-JENKINS-60213-ConcurrentVariables-0 EXECUTOR NUMBER: 0 ==31: [JENKINS-60213-ConcurrentVariables@2] $ /bin/bash /tmp/jenkins1481999870837323074.sh == WORKSPACE:/var/lib/jenkins/workspace/JENKINS-60213-ConcurrentVariables@2 P4_CLIENT:jenkins-master-JENKINS-60213-ConcurrentVariables-6 EXECUTOR NUMBER: 6 ==32: [JENKINS-60213-ConcurrentVariables@3] $ /bin/bash /tmp/jenkins3645232859628494475.sh == WORKSPACE:/var/lib/jenkins/workspace/JENKINS-60213-ConcurrentVariables@3 P4_CLIENT:jenkins-master-JENKINS-60213-ConcurrentVariables-3 EXECUTOR NUMBER: 3 == Are you able to test the nightly at the following location to prove that it fixes the bug? https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fp4-plugin/detail/PR-93/38/artifacts Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title ovi craciun commented on JENKINS-34610 Re: Windows AMI in endless loop I have managed to fix it, the culprit: port 445 need to be opened on the slave machines. More details here: https://stackoverflow.com/questions/38011683/how-to-run-windows-instance-on-ec2-from-jenkins Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170238.1462391043000.7107.1574768820423%40Atlassian.JIRA.
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title ovi craciun edited a comment on JENKINS-34610 Re: Windows AMI in endless loop I have managed to fix it, the culprit: port 445 need needs to be opened on the slave machines. More details here: https://stackoverflow.com/questions/38011683/how-to-run-windows-instance-on-ec2-from-jenkins Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170238.1462391043000.7118.1574768880376%40Atlassian.JIRA.
[JIRA] (JENKINS-60263) Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not.
Title: Message Title Uwe Brackenhoff closed an issue as Fixed Merci beaucoup. Jenkins / JENKINS-60263 Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not. Change By: Uwe Brackenhoff Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203250.1574676933000.7128.1574769601250%40Atlassian.JIRA.
[JIRA] (JENKINS-60282) Note environment variable
Title: Message Title Mike Safonov created an issue Jenkins / JENKINS-60282 Note environment variable Issue Type: Improvement Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-11-26 12:50 Priority: Minor Reporter: Mike Safonov Greetings! Could you add some environment variable for accessing note value when job triggered by MR comment? For example, how it is done in https://github.com/jenkinsci/gitlab-plugin (gitlabTriggerPhrase) Add Comment This message was sent
[JIRA] (JENKINS-31267) cannot push non-HEAD to remote repo
Title: Message Title Dmitry Baskakov commented on JENKINS-31267 Re: cannot push non-HEAD to remote repo Impacts us, too. We have a job which tags and merges the branch we have the release done from: first, it creates tag for the current branch, then it merges it into 'master', then it merges 'master' into 'develop'. We have a script which does tagging and merging by using native 'git' command, but it can't push without extra work. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.165995.1446137063000.7150.1574773380226%40Atlassian.JIRA.
[JIRA] (JENKINS-60283) jenkins has a dependencies on both log4j:logj4 and org.slf4j:log4j-over-slf4j
Title: Message Title James Nord created an issue Jenkins / JENKINS-60283 jenkins has a dependencies on both log4j:logj4 and org.slf4j:log4j-over-slf4j Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-11-26 13:02 Priority: Minor Reporter: James Nord log4j is a dependency coming from +- org.acegisecurity:acegi-security:jar:1.0.7:provided | +- org.springframework:spring-jdbc:jar:1.2.9:provided | | - org.springframework:spring-dao:jar:1.2.9:provided | +- oro:oro:jar:2.0.8:provided | - log4j:log4j:jar:1.2.17:provided slf4j is used directly by Jenkins. even though the scope is provided this causes duplicate entries on the compile classpath which causes issues when you are generating annimal sniffer annotations for example. [ERROR] Failed to execute goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.18:build (build) on project operations-center-jenkins-signature: A type incompatibility occurred while executing org.codehaus.mojo:animal-sniffer-maven-plugin:1.18:build: Cannot merger class org/apache/log4j/RollingFileAppender as it has changed superclass: the transitive dependency on log4j should be excluded
[JIRA] (JENKINS-60284) build_agent_name not working with Global Listener
Title: Message Title Andy Taylor created an issue Jenkins / JENKINS-60284 build_agent_name not working with Global Listener Issue Type: Bug Assignee: Aleksi Simell Components: influxdb-plugin Created: 2019-11-26 13:16 Environment: Jenkins 2.190.1 InfluxDB Plugin 2.0.2 Priority: Minor Reporter: Andy Taylor I just tried out the Global Listener feature and it seems to work great, except build_agent_name is always blank. This works fine for me if I disable Global Listener and use influxDbPublisher() in my Jenkinsfile so at least there is a workaround. I'm guessing this has something to do with the global listener not seeing the NODE_NAME environment variable. Add Comment
[JIRA] (JENKINS-45411) Unable to run UFT script on a locked remote host by Jenkins plugin HPE Test from File System
Title: Message Title Denis Abakumov commented on JENKINS-45411 Re: Unable to run UFT script on a locked remote host by Jenkins plugin HPE Test from File System I can confirm this for UFT 14.50 on Jenkins 2.190.3 with Micro Focus Application Automation Tools 5.9. No matter if the job is started by timer or manually, it will fail if an RDP session is disconnected. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183579.1499713653000.7155.1574775420484%40Atlassian.JIRA.
[JIRA] (JENKINS-45411) Unable to run UFT script on a locked remote host by Jenkins plugin HPE Test from File System
Title: Message Title
Denis Abakumov edited a comment on JENKINS-45411
Re: Unable to run UFT script on a locked remote host by Jenkins plugin HPE Test from File System
I can confirm this for UFT 14.50 on Jenkins 2.190.3 with Micro Focus Application Automation Tools 5.9.No matter if the job is started by timer or manually, it will fail if an RDP session is disconnected. The output will be:{noformat}Run build testsLauncher timeout is 10675199::02:48:05Controller Polling Interval: 30 secondsPerScenarioTimeout: 00::00:10:00 minutesFileSystemTestRunner timeout is 10675199.02:48:05.4775807UFT Mobile connection info is - UFT Mobile HostAddress: , Port: 8080, Username: , TenantId: , UseSSL: 0, UseProxy: 0, ProxyType: 0, ProxyAddress: , ProxyPort: 0, ProxyAuth: 0, ProxyUser: Results directory is: C:/Projects/UFT_Results1 tests found:C:\Program Files (x86)\Jenkins\workspace\UFT_Project\12.0226-11-2019 07:37:14 Running: C:\Program Files (x86)\Jenkins\workspace\UFT_Project\12.02Test result: Error26-11-2019 07:37:14 Test complete: C:\Program Files (x86)\Jenkins\workspace\UFT_Project\12.02---Run status: Job failed, total tests: 1, succeeded: 0, failures: 0, errors: 1, warnings: 0Error : C:\Program Files (x86)\Jenkins\workspace\UFT_Project\12.02Build step 'Execute Micro Focus tests from file system' changed build result to FAILURERecording test resultsReport archiving mode is set to: ALWAYS_ARCHIVE_TEST_REPORTartifactsDir: archive C:\Program Files (x86)\Jenkins\jobs\UFT_Project\builds\58\archiveFinished: FAILURE{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60285) Not able to use OAuth Credentials Plugin
Title: Message Title vikram kumar created an issue Jenkins / JENKINS-60285 Not able to use OAuth Credentials Plugin Issue Type: Bug Assignee: Unassigned Attachments: image-2019-11-26-19-40-27-318.png, image-2019-11-26-19-41-10-606.png Components: oauth-credentials-plugin Created: 2019-11-26 14:14 Priority: Blocker Reporter: vikram kumar When we are selecting OAuth Credentials, it is not giving us option for token When click on ok it goes to an error page. Add Comment
[JIRA] (JENKINS-60285) Not able to use OAuth Credentials Plugin
Title: Message Title vikram kumar commented on JENKINS-60285 Re: Not able to use OAuth Credentials Plugin Jenkins verison 2.190 & OAuth Plugin version 0.4 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203275.1574777643000.7177.157460985%40Atlassian.JIRA.
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-60286 durable-task v1.33 fails with agent Dockerfile Issue Type: Bug Assignee: Unassigned Components: durable-task-plugin Created: 2019-11-26 14:17 Environment: Jenkins version 2.190.3 Priority: Blocker Reporter: Marky Jackson Error I get process apparently never started in /home/ec2-user/workspace/ntend-pipeline_customer-settings@3@tmp/durable-f026a6cb (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer) Cannot contact EC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5): java.io.FileNotFoundException: File '/home/ec2-user/workspace/ntend-pipeline_customer-settings@3@tmp/durable-f026a6cb/output.txt' does not existHard kill! Add Comment
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Marky Jackson commented on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile I eventually have to hard kill the job. I tried all applicable workarounds including all noted in previous tickets as workaround to no avail. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203277.1574777832000.7181.1574778420775%40Atlassian.JIRA.
[JIRA] (JENKINS-60284) build_agent_name not working with Global Listener
Title: Message Title Andy Taylor commented on JENKINS-60284 Re: build_agent_name not working with Global Listener Quick update: I've noticed that build_agent_name is correctly set to 'master' when a job is running on the master, but if a job runs on any of the slaves it is null. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203274.1574774195000.7191.1574779080621%40Atlassian.JIRA.
[JIRA] (JENKINS-48038) "Could not find the history docker layer" when publishing build Info to artifactory
Title: Message Title
Alastair Houghton commented on JENKINS-48038
Re: "Could not find the history docker layer" when publishing build Info to artifactory
This problem still exists; we're using Artifactory 6.9.1, and I'm seeing similar behaviour. Interestingly it doesn't always fail in this particular manner; sometimes I'm told that Jenkins was unable to find the manifest.json file instead. I think the problem is actually a race condition between the Jenkins plugin and Artifactory itself; I think what's happening is that the Jenkins plugin uploads the Docker image to Artifactory, and then immediately tries to find the history layer in the image. If the Artifactory installation is fast enough, that's fine, but if the Jenkins plugin catches Artifactory just at the wrong moment (I assume while it's moving from _uploads to the final destination, or something of that nature), it can't find one or more of the files and so you get these error messages. Although this is listed as a "minor" problem, it's actually a pretty major bug in the Artifactory plug-in, because it makes doing
def server = Artifactory.server 'myServer'
def rtDocker = Artifactory.docker server:server
def buildInfo = rtDocker.push("myImage:some-tag", "docker/myImage")
server.publishBuildInfo buildInfo
fail, either on the push step, or alternatively (if it fails to find the manifest, as opposed to the history layer) it will succeed but the build will show a single empty module with no artifacts, even though you can see that the Docker image has been uploaded successfully.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-48038) "Could not find the history docker layer" when publishing build Info to artifactory
Title: Message Title Alastair Houghton updated an issue Jenkins / JENKINS-48038 "Could not find the history docker layer" when publishing build Info to artifactory Change By: Alastair Houghton Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186581.1510763397000.7207.1574779560692%40Atlassian.JIRA.
[JIRA] (JENKINS-50559) Authorization Folder property for Multibranch jobs
Title: Message Title Michel Zanini commented on JENKINS-50559 Re: Authorization Folder property for Multibranch jobs I have two folders that will be visible and accessible by different users. To avoid a pipeline step to trigger a job on the other folder I can't run jobs with the default SYSTEM user. I need to use Authorize Project plugin to change to run with a specific user. However, how can I configure a folder and sub-items to run with a specific user? I can only do that on Global Jenkins level, but I need to override the global definition on this 2 folders. The ticket here mentions support for multi-branch pipelines, I guess normal folders also apply. Possibly implementing for one will do for the other. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189628.1522813005000.7215.1574780041159%40Atlassian.JIRA.
[JIRA] (JENKINS-48038) "Could not find the history docker layer" when publishing build Info to artifactory
Title: Message Title
Alastair Houghton edited a comment on JENKINS-48038
Re: "Could not find the history docker layer" when publishing build Info to artifactory
This problem still exists; we're using Artifactory 6.9.1, and I'm seeing similar behaviour. Interestingly it doesn't _always_ fail in this particular manner; sometimes I'm told that Jenkins was unable to find the manifest.json file instead. I _think_ the problem is actually a race condition between the Jenkins plugin and Artifactory itself; I think what's happening is that the Jenkins plugin uploads the Docker image to Artifactory, and then immediately tries to find the history layer in the image. If the Artifactory installation is fast enough, that's fine, but if the Jenkins plugin catches Artifactory just at the wrong moment (I assume while it's moving from _uploads to the final destination, or something of that nature), it can't find one or more of the files and so you get these error messages.Although this is listed as a "minor" problem, it's actually a pretty major bug in the Artifactory plug-in, because it makes doing {code :groovy }def server = Artifactory.server 'myServer'def rtDocker = Artifactory.docker server:serverdef buildInfo = rtDocker.push("myImage:some-tag", "docker/myImage")server.publishBuildInfo buildInfo{code} fail, either on the {{push}} step, or alternatively (if it fails to find the manifest, as opposed to the history layer) it will succeed but the build will show a single empty module with no artifacts, even though you can see that the Docker image has been uploaded successfully. (It might be worth adding that the images I'm using here are very large. That might well increase the window during which this can happen.)
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60279) build symlink plugin creating incorrect links
Title: Message Title Jesse Glick resolved as Cannot Reproduce Just checked and it is working for me: the symlinks match the permalinks file. Check for log messages in the io.jenkins.plugins.build_symlink package, and see if you can reproduce in a fresh installation from scratch. Jenkins / JENKINS-60279 build symlink plugin creating incorrect links Change By: Jesse Glick Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To u
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Devin Nusbaum commented on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile Here are some questions to help understand what is happening: Was this working for you previously? If so, what plugin versions have been installed/upgraded since then? Does it happen consistently or intermittently? Can you turn on FINE logging for org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep and then post the full stack trace of the exception from the Jenkins system log (the message should contain "is evidently offline now")? Did you try adding -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true as indicated to your Jenkins Java startup settings to see if you get more detailed error information? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203277.1574777832000.7243.1574780940201%40Atlassian.JIRA.
[JIRA] (JENKINS-60287) Jenkins practice
Title: Message Title Geetha Parasuraman created an issue Jenkins / JENKINS-60287 Jenkins practice Issue Type: Epic Assignee: Victor Martinez Components: jenkinslint-plugin Created: 2019-11-26 15:16 Priority: Critical Reporter: Geetha Parasuraman Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Marky Jackson commented on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile Here is the stack trace from the logs: Nov 26, 2019 3:17:48 PM FINER org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepEC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5) seems to be online so using /home/ec2-user/workspace/ntend-pipeline_customer-settings@3 Nov 26, 2019 3:17:48 PM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepcould not check /home/ec2-user/workspace/ntend-pipeline_customer-settings@3 Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to EC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at hudson.FilePath.act(FilePath.java:1072) at hudson.FilePath.act(FilePath.java:1061) at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.getOutput(FileMonitoringTask.java:300) at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.getOutput(FileMonitoringTask.java:293) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.lambda$check$3(DurableTaskStep.java:604) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.handleExit(DurableTaskStep.java:651) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.check(DurableTaskStep.java:604) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.run(DurableTaskStep.java:548) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) java.io.FileNotFoundException: File '/home/ec2-user/workspace/ntend-pipeline_customer-settings@3@tmp/durable-a112d9e1/output.txt' does not exist at org.apache.commons.io.FileUtils.openInputStream(FileUtils.java:297) at org.apache.commons.io.FileUtils.readFileToByteArray(FileUtils.java:1851) at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController$1.invoke(FileMonitoringTask.java:302) at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController$1.invoke(FileMonitoringTask.java:300) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3052) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748)
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Marky Jackson commented on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile Was this working for you previously? If so, what plugin versions have been installed/upgraded since then? Yes it was on version 1.29 for durable task and core code Jenkins version 2.190.2 Does it happen consistently or intermittently? It happens consistently for jobs that have the agent set to use Dockerfiles but no other jobs types Did you try adding -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true as indicated to your Jenkins Java startup settings to see if you get more detailed error information? I will add that now Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received t
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Marky Jackson commented on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile JENKINS-34021: DurableTaskStep.Execution.listener present in CpsStepContext[16:sh]:Owner[monitor-frontend-pipeline/customer-settings/34:monitor-frontend-pipeline/customer-settings #34] Nov 26, 2019 3:32:04 PM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskSteplaunching task against hudson.remoting.Channel@13b6e486:EC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5) using RemoteLauncher[hudson.remoting.Channel@13b6e486:EC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5)] Nov 26, 2019 3:32:04 PM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskSteplaunched task Nov 26, 2019 3:32:04 PM FINER org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepEC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5) seems to be online so using /home/ec2-user/workspace/ntend-pipeline_customer-settings Nov 26, 2019 3:32:04 PM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepcreating filtered stream Nov 26, 2019 3:32:04 PM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepstill running in /home/ec2-user/workspace/ntend-pipeline_customer-settings on EC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5) Nov 26, 2019 3:32:04 PM FINER org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepEC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5) seems to be online so using /home/ec2-user/workspace/ntend-pipeline_customer-settings Nov 26, 2019 3:32:04 PM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepstill running in /home/ec2-user/workspace/ntend-pipeline_customer-settings on EC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5) Nov 26, 2019 3:32:05 PM FINER org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepEC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5) seems to be online so using /home/ec2-user/workspace/ntend-pipeline_customer-settings Nov 26, 2019 3:32:05 PM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepcalling close with nl=true Nov 26, 2019 3:32:06 PM FINEST org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepJENKINS-34021: DurableTaskStep.Execution.listener present in CpsStepContext[20:sh]:Owner[monitor-frontend-pipeline/customer-settings/34:monitor-frontend-pipeline/customer-settings #34] Nov 26, 2019 3:32:06 PM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskSteplaunching task against hudson.remoting.Channel@13b6e486:EC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5) using RemoteLauncher[hudson.remoting.Channel@13b6e486:EC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5)] Nov 26, 2019 3:32:06 PM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskSteplaunched task Nov 26, 2019 3:32:07 PM FINER org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepEC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5) seems to be online so using /home/ec2-user/workspace/ntend-pipeline_customer-settings Nov 26, 2019 3:32:07 PM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepcreating filtered stream Nov 26, 2019 3:32:07 PM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepcalling close with nl=true Nov 26, 2019 3:32:08 PM FINEST org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepJENKINS-34021: DurableTaskStep.Execution.listener present in CpsStepContext[25:sh]:Owne
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Marky Jackson commented on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile The 2nd above stack trace is with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true turned on and doesn't show anything new Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203277.1574777832000.7258.1574782800149%40Atlassian.JIRA.
[JIRA] (JENKINS-59752) Add support for ephemeral OS disk
Title: Message Title Bradley Wangia assigned an issue to Bradley Wangia Jenkins / JENKINS-59752 Add support for ephemeral OS disk Change By: Bradley Wangia Assignee: Jie Shen Bradley Wangia Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202475.1570808392000.7262.1574783160196%40Atlassian.JIRA.
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Devin Nusbaum commented on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile Marky Jackson LAUNCH_DIAGNOSTICS prints information to the build log, not the Jenkins system log. Can you post the build log from a failing build after you enabled that property? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203277.1574777832000.7270.1574783341722%40Atlassian.JIRA.
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-60286 durable-task v1.33 fails with agent Dockerfile Possibly a regression from the new native wrapper. I would not recommend using agent docker (or agent dockerfile). These ultimately rely on the withDockerContainer step and rather complex injection of docker exec into commands, which can easily break when there are issues with volume mounts and so on. Much safer and more transparent to use a plain label and run CLI docker commands (build, run) from sh. Change By: Jesse Glick Component/s: docker-workflow-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Devin Nusbaum commented on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile Possibly a regression from the new native wrapper. The new wrapper is disabled by default due to various problems, so if there is a regression, I suspect that something subtle was changed in the fallback code. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203277.1574777832000.7273.1574783460447%40Atlassian.JIRA.
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-60286
durable-task v1.33 fails with agent Dockerfile
Change By:
Devin Nusbaum
Error I getprocess apparently never started in /home/ec2-user/workspace/ntend-pipeline_customer-settings@3@tmp/durable-f026a6cb(running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer)Cannot contact EC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5): java.io.FileNotFoundException: File '/home/ec2-user/workspace/ntend-pipeline_customer-settings@3@tmp/durable-f026a6cb/output.txt' does not existHard kill! Stack trace:{noformat}Nov 26, 2019 3:17:48 PM FINER org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepEC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5) seems to be online so using /home/ec2-user/workspace/ntend-pipeline_customer-settings@3 Nov 26, 2019 3:17:48 PM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepcould not check /home/ec2-user/workspace/ntend-pipeline_customer-settings@3 Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to EC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5)at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743)at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)at hudson.remoting.Channel.call(Channel.java:957)at hudson.FilePath.act(FilePath.java:1072)at hudson.FilePath.act(FilePath.java:1061)at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.getOutput(FileMonitoringTask.java:300)at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.getOutput(FileMonitoringTask.java:293)at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.lambda$check$3(DurableTaskStep.java:604)at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.handleExit(DurableTaskStep.java:651)at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.check(DurableTaskStep.java:604)at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.run(DurableTaskStep.java:548)at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)at java.util.concurrent.FutureTask.run(FutureTask.java:266)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) java.io.FileNotFoundException: File '/home/ec2-user/workspace/ntend-pipeline_customer-settings@3@tmp/durable-a112d9e1/output.txt' does not existat org.apache.commons.io.FileUtils.openInputStream(FileUt
[JIRA] (JENKINS-45411) Unable to run UFT script on a locked remote host by Jenkins plugin HPE Test from File System
Title: Message Title Dinesh Krishnaswamy commented on JENKINS-45411 Re: Unable to run UFT script on a locked remote host by Jenkins plugin HPE Test from File System For all the followers, I dont think its gonna be fixed anytime sooner regardless of its criticality as it is lingering since 2017. If this is fixed you dont need micro focus CI solution I would suggest to move away from UFT is the only reliable solution. There are many great solutions are in place like Katalon Studio, Test Project which are awesome, supports the UI/API testing and also pretty much compatible with CI tools like Jenkins/Gitlab/github actions etc. Moreover all are completely free Please work on phased approach and it will be little tedious but you wont regret the effort that you put in to move away from UFT. Happy weekend pals!! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183579.1499713653000.7280.1574783760432%40Atlassian.JIRA.
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title
Marky Jackson commented on JENKINS-60286
Re: durable-task v1.33 fails with agent Dockerfile
Devin Nusbaum here is the build log from the console. I eventually have to hard kill the job because it just hangs at the missing file:
Started by user mark.jack...@sysdig.com 15:51:39 Connecting to https://api.github.com using xxx/** (z) Obtained Jenkinsfile from xxx Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] node Running on EC2 (ec2) - ${WORKER_NAME} (ec2ID) in /home/${USER}/workspace/ntend-pipeline_customer-settings [Pipeline] { [Pipeline] stage [Pipeline] { (Declarative: Checkout SCM) [Pipeline] checkout using credential ${TOKEN} Cloning the remote Git repository Cloning repository ${REPO} > git init /home/${USER}/workspace/ntend-pipeline_customer-settings # timeout=10 } Fetching upstream changes from ${REPO} > git --version # timeout=10 } using GIT_SSH to set credentials ${TOKEN} > git fetch --tags --progress -- ${REPO} +refs/heads/*:refs/remotes/origin/* # timeout=10 } Checking out Revision ${REVISION} (customer-settings) Commit message: "Reverting my changes" > git config remote.origin.url ${REPO} # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url ${REPO} # timeout=10 Fetching upstream changes from ${REPO} using GIT_SSH to set credentials ${TOKEN} > git fetch --tags --progress --${REPO} +refs/heads/customer-settings:refs/remotes/origin/customer-settings # timeout=10 > git config core.sparsecheckout # timeout=10 > git checkout -f ${REVISION} # timeout=10 > git rev-list --no-walk ${REVISION} # timeout=10 [Pipeline] } [Pipeline] // stage [Pipeline] withEnv [Pipeline] { [Pipeline] stage [Pipeline] { (Declarative: Agent Setup) [Pipeline] isUnix [Pipeline] readFile [Pipeline] sh + docker build -t c7c9f201c0dbb37091ac75c689812beae3bf54b4 -f Dockerfile . WARNING: Error loading config file: /home/${USER}/.docker/config.json: EOF Sending build context to Docker daemon 116.3MBStep 1/13 : FROM ubuntu:latest ---> 775349758637 Step 2/13 : ENV DEBIAN_FRONTEND=noninteractive ---> Using cache ---> 08bb415b8561 Step 3/13 : RUN apt-get update -y && apt-get install apt-transport-https ca-certificates curl gnupg git python-pip python2.7 python2.7-dev groff-base build-essential parallel jq grep awscli -y --no-install-recommends ---> Using cache ---> 2d2f267ee29f Step 4/13 : RUN groupadd ${USER} -g 500 ---> Using cache ---> c1508155cdc1 Step 5/13 : RUN useradd -m -d /home/${USER} -g ${USER} -u 500 ${USER} ---> Using cache ---> 12ad008b1a8a Step 6/13 : RUN curl -sSL https://dl.google.com/linux/linux_signing_key.pub | apt-key add - && echo "deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main" > /etc/apt/sources.list.d/google-chrome.list ---> Using cache ---> 1e4d342560b2 Step 7/13 : RUN curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add - ---> Using cache ---> 7ae11025dc8e Step 8/13 : RUN echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list ---> Using cache ---> 6f40d90e286a Step 9/13 : ENV YARN_VERSION=1.17.3-1 ---> Using cache ---> 818b40b458e3 Step 10/13 : RUN apt-get update && apt-get install -y yarn=$YARN_VERSION --no-install-recommends ---> Using cache ---> 88de9a37077f Step 11/13 : RUN apt-get update && apt-get install -y google-chrome-stable ---> Using cache ---> f57b038effc4 Step 12/13 : ENV NODE_VERSION=10.16.3 ---> Using cache
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Marky Jackson commented on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile ?? I would not recommend using agent docker (or agent dockerfile). These ultimately rely on the withDockerContainer step and rather complex injection of docker exec into commands, which can easily break when there are issues with volume mounts and so on. Much safer and more transparent to use a plain label and run CLI docker commands (build, run) from sh.?? Oh that is painful given our online documentation almost seems to promote the containerized approach (i.e. https://jenkins.io/doc/book/pipeline/docker/) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203277.1574777832000.7293.1574785560167%40Atlassian.JIRA.
[JIRA] (JENKINS-60288) Installator is broken on Alpine
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-60288
Installator is broken on Alpine
Change By:
Jakub Bochenski
The installer does not throw an error but the resulting installation is not usable. Sample output from trying to run this on a {{jenkinsci/slave: alpine}} with the docker-plugin{code}Running as SYSTEM[EnvInject] - Loading node environment variables.Installing AdoptOpenJDK to /home/jenkins/tools/hudson.model.JDK/jdkadoptERROR: Failed to download file:/var/lib/jenkins/caches/adoptopenjdk/LINUX/amd64/jdk-11.0.5+10.zip from agent; will retry from masterAlso: hudson.remoting.Channel$CallSiteStackTrace: Remote call to docker-006z72dcdzrtj at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at hudson.FilePath.act(FilePath.java:1070) at hudson.FilePath.act(FilePath.java:1059) at hudson.FilePath.installIfNecessaryFrom(FilePath.java:913) at hudson.FilePath.installIfNecessaryFrom(FilePath.java:846) at io.jenkins.plugins.adoptopenjdk.AdoptOpenJDKInstaller.performInstallation(AdoptOpenJDKInstaller.java:121) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:69) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:109) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:206) at hudson.model.JDK.forNode(JDK.java:147) at org.jenkinsci.plugins.envinject.util.RunHelper.getJDKVariables(RunHelper.java:111) at org.jenkinsci.plugins.envinject.util.RunHelper.getBuildVariables(RunHelper.java:134) at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironmentWithoutJobPropertyObject(EnvInjectListener.java:233) at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironment(EnvInjectListener.java:49) at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:542) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:462) at hudson.model.Run.execute(Run.java:1818) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)java.io.FileNotFoundException: /var/lib/jenkins/caches/adoptopenjdk/LINUX/amd64/jdk-11.0.5+10.zip (No such file or directory) at java.io.FileInputStream.open0(Native Method) at java.io.FileInputStream.open(FileInputStream.java:195) at java.io.FileInputStream.(FileInputStream.java:138) at java.io.FileInputStream.(FileInputStream.java:93) at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90) at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188) at java.net.URL.openStream(URL.java:1045) at hudson.FilePath$Unpack.invoke(FilePath.java:949) at hudson.FilePath$Unpack.invoke(FilePath.java:943) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3050) at hudson.remoting.UserRequest.perform(U
[JIRA] (JENKINS-60288) Installator is broken on Alpine
Title: Message Title Jakub Bochenski created an issue Jenkins / JENKINS-60288 Installator is broken on Alpine Issue Type: Bug Assignee: Mads Mohr Christensen Components: adoptopenjdk-plugin Created: 2019-11-26 16:26 Priority: Major Reporter: Jakub Bochenski The installer does not throw an error but the resulting installation is not usable. Sample output from trying to run this on a jenkinsci/slave: alpine with docker-plugin Running as SYSTEM [EnvInject] - Loading node environment variables. Installing AdoptOpenJDK to /home/jenkins/tools/hudson.model.JDK/jdkadopt ERROR: Failed to download file:/var/lib/jenkins/caches/adoptopenjdk/LINUX/amd64/jdk-11.0.5+10.zip from agent; will retry from master Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to docker-006z72dcdzrtj at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at hudson.FilePath.act(FilePath.java:1070) at hudson.FilePath.act(FilePath.java:1059) at hudson.FilePath.installIfNecessaryFrom(FilePath.java:913) at hudson.FilePath.installIfNecessaryFrom(FilePath.java:846) at io.jenkins.plugins.adoptopenjdk.AdoptOpenJDKInstaller.performInstallation(AdoptOpenJDKInstaller.java:121) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:69) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:109) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:206) at hudson.model.JDK.forNode(JDK.java:147) at org.jenkinsci.plugins.envinject.util.RunHelper.getJDKVariables(RunHelper.java:111) at org.jenkinsci.plugins.envinject.util.RunHelper.getBuildVariables(RunHelper.java:134) at org.jenkinsci.plugins.en
[JIRA] (JENKINS-60203) Git client plugin 3.0 fails to load trilead class
Title: Message Title Mark Waite commented on JENKINS-60203 Re: Git client plugin 3.0 fails to load trilead class Larry charbonneau have you been able to resolve this issue on your Windows server? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203174.157409897.7301.1574785680264%40Atlassian.JIRA.
[JIRA] (JENKINS-60288) Installator is broken on Alpine
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-60288
Installator is broken on Alpine
Change By:
Jakub Bochenski
The installer does not throw an error but the resulting installation is not usable. Sample output from trying to run this on a {{jenkinsci/slave:alpine}} with the docker-plugin{code}Running as SYSTEM[EnvInject] - Loading node environment variables.Installing AdoptOpenJDK to /home/jenkins/tools/hudson.model.JDK/jdkadoptERROR: Failed to download file:/var/lib/jenkins/caches/adoptopenjdk/LINUX/amd64/jdk-11.0.5+10.zip from agent; will retry from masterAlso: hudson.remoting.Channel$CallSiteStackTrace: Remote call to docker-006z72dcdzrtj at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at hudson.FilePath.act(FilePath.java:1070) at hudson.FilePath.act(FilePath.java:1059) at hudson.FilePath.installIfNecessaryFrom(FilePath.java:913) at hudson.FilePath.installIfNecessaryFrom(FilePath.java:846) at io.jenkins.plugins.adoptopenjdk.AdoptOpenJDKInstaller.performInstallation(AdoptOpenJDKInstaller.java:121) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:69) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:109) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:206) at hudson.model.JDK.forNode(JDK.java:147) at org.jenkinsci.plugins.envinject.util.RunHelper.getJDKVariables(RunHelper.java:111) at org.jenkinsci.plugins.envinject.util.RunHelper.getBuildVariables(RunHelper.java:134) at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironmentWithoutJobPropertyObject(EnvInjectListener.java:233) at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironment(EnvInjectListener.java:49) at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:542) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:462) at hudson.model.Run.execute(Run.java:1818) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)java.io.FileNotFoundException: /var/lib/jenkins/caches/adoptopenjdk/LINUX/amd64/jdk-11.0.5+10.zip (No such file or directory) at java.io.FileInputStream.open0(Native Method) at java.io.FileInputStream.open(FileInputStream.java:195) at java.io.FileInputStream.(FileInputStream.java:138) at java.io.FileInputStream.(FileInputStream.java:93) at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90) at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188) at java.net.URL.openStream(URL.java:1045) at hudson.FilePath$Unpack.invoke(FilePath.java:949) at hudson.FilePath$Unpack.invoke(FilePath.java:943) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3050) at hudson.remoting.UserRequest.perform(User
[JIRA] (JENKINS-60288) Installator is broken on Alpine
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-60288
Installator is broken on Alpine
Change By:
Jakub Bochenski
The installer does not throw an error but the resulting installation is not usable unusable . Sample output from trying to run this on a {{jenkinsci/slave:alpine}} with the docker-plugin{code}Running as SYSTEM[EnvInject] - Loading node environment variables.Installing AdoptOpenJDK to /home/jenkins/tools/hudson.model.JDK/jdkadoptERROR: Failed to download file:/var/lib/jenkins/caches/adoptopenjdk/LINUX/amd64/jdk-11.0.5+10.zip from agent; will retry from masterAlso: hudson.remoting.Channel$CallSiteStackTrace: Remote call to docker-006z72dcdzrtj at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at hudson.FilePath.act(FilePath.java:1070) at hudson.FilePath.act(FilePath.java:1059) at hudson.FilePath.installIfNecessaryFrom(FilePath.java:913) at hudson.FilePath.installIfNecessaryFrom(FilePath.java:846) at io.jenkins.plugins.adoptopenjdk.AdoptOpenJDKInstaller.performInstallation(AdoptOpenJDKInstaller.java:121) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:69) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:109) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:206) at hudson.model.JDK.forNode(JDK.java:147) at org.jenkinsci.plugins.envinject.util.RunHelper.getJDKVariables(RunHelper.java:111) at org.jenkinsci.plugins.envinject.util.RunHelper.getBuildVariables(RunHelper.java:134) at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironmentWithoutJobPropertyObject(EnvInjectListener.java:233) at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironment(EnvInjectListener.java:49) at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:542) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:462) at hudson.model.Run.execute(Run.java:1818) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)java.io.FileNotFoundException: /var/lib/jenkins/caches/adoptopenjdk/LINUX/amd64/jdk-11.0.5+10.zip (No such file or directory) at java.io.FileInputStream.open0(Native Method) at java.io.FileInputStream.open(FileInputStream.java:195) at java.io.FileInputStream.(FileInputStream.java:138) at java.io.FileInputStream.(FileInputStream.java:93) at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90) at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188) at java.net.URL.openStream(URL.java:1045) at hudson.FilePath$Unpack.invoke(FilePath.java:949) at hudson.FilePath$Unpack.invoke(FilePath.java:943) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3050) at hudson.remoting.UserRequest.
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Devin Nusbaum commented on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile Marky Jackson Can you please format your messages/stack traces so they aren't just one long line? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203277.1574777832000.7307.1574786280165%40Atlassian.JIRA.
[JIRA] (JENKINS-60289) Show agent name on "SSH Host Key Verifiers not configured" warning
Title: Message Title Ivan Fernandez Calvo created an issue Jenkins / JENKINS-60289 Show agent name on "SSH Host Key Verifiers not configured" warning Issue Type: Improvement Assignee: Ivan Fernandez Calvo Components: ssh-slaves-plugin Created: 2019-11-26 16:39 Priority: Minor Reporter: Ivan Fernandez Calvo Any hints to detect which agent is meant when the message "SSH Host Key Verifiers are not configured for all SSH agents on this Jenkins instance. This could leave these agents open to man-in-the-middle attacks. Update your agent configuration to resolve this." is shown? We have 50+ agents running, but neither logs, nor logging in to any of our machines gives me any hint who the culprit is? Would it be possible to make this message say WHICH agent is the culprit? Even server logs do not tell which agent it is. Add Comment
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Jesse Glick commented on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile Oh I definitely promote using containers to run builds—just not with this plugin that I wrote much of and now deeply regret. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203277.1574777832000.7312.1574786580193%40Atlassian.JIRA.
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Marky Jackson commented on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile Devin Nusbaum formatting is not working for some reason. Jesse Glick I totally know this feeling Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203277.1574777832000.7314.1574786700242%40Atlassian.JIRA.
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title
Devin Nusbaum commented on JENKINS-60286
Re: durable-task v1.33 fails with agent Dockerfile
Marky Jackson You mean formatting is not working in Jira? I think if you just use the non-WYSIWYG editor and surround whatever your text is in {noformat} it will work fine. It looks like your build log still contains:
[Pipeline] sh process apparently never started in /home/${USER}/workspace/ntend-pipeline_customer-settings@tmp/durable-d4083a8e (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer)
Which I think still means that the LAUNCH_DIAGNOSTICS is still false. Did you restart Jenkins after setting the property? If you don't want to restart Jenkins, I think you can run "org.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true" from the script console to enable it temporarily (not sure if Groovy will let you change the field though since it is private).
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.co
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Marky Jackson commented on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile I did a restart Devin Nusbaum. I did also just try running it in the script console Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203277.1574777832000.7325.1574787780698%40Atlassian.JIRA.
[JIRA] (JENKINS-60132) Add support for AWS parameter store as a backend for storing credentials
Title: Message Title Chris Kilding updated an issue Jenkins / JENKINS-60132 Add support for AWS parameter store as a backend for storing credentials Change By: Chris Kilding Particularly, storing *Feature*Allow Jenkins to look up credentials in AWS Parameter Store. (They will be stored as secure strings Secure String parameters can have a lower cost relative to secrets manager. [https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-paramstore-securestring.html] ). *Benefits* - Storing credentials in Parameter Store can be cheaper than storing them in Secrets Manager.*Pitfalls*- Secrets Manager may offer higher API rate limits or better QoS since it is a paid-for service. We would need to find out whether Parameter Store offers acceptable rate limits and performance for Jenkins to rely on.* Questions : * # - Does this belong in its own project/plugin or is there opportunity for code reuse as part of aws-secrets-manager-credentials-provider-plugin? # Is there opportunity to - Could we reuse the naming or storage conventions, such as tagging, that were defined when adding multiple credential support (JENKINS-58339)? # Any *Constraints*- Jenkins should be able to source credentials from both Secrets Manager and Parameter Store. (Using one should not rule out using the other comments? .)- If Jenkins encounters an error looking up secrets in one of the services, this should not impede lookups in the other. (An exception from a Secrets Manager API call should not break secret resolution in Parameter Store if PS is still functioning.)- Tag naming conventions should be shared in both PS and SM. (Eg a username tag should be called jenkins:credentials:username in PS, just like it is in SM today.) Add Comment
