[JIRA] (JENKINS-55232) regarding Authentication response is not success message
Title: Message Title Dhilip Kanna commented on JENKINS-55232 Re: regarding Authentication response is not success message Hey Hokwang Lee ! Have you fixed this issue. Can you please let me know. I have been struck in the same stage. Thanks 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.196314.154510253.11831.1575445680245%40Atlassian.JIRA.
[JIRA] (JENKINS-55649) X-Bitbucket-Type header / server_url request parameter not found
Title: Message Title Christoph Forster edited a comment on JENKINS-55649 Re: X-Bitbucket-Type header / server_url request parameter not found For me the " Workaround " also works.[~rhierlmeier]: The log shows that the server_url Parameter is found and is working as expected so your problem must be within the job configuration 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.196826.1547727059000.11828.1575444360752%40Atlassian.JIRA.
[JIRA] (JENKINS-55649) X-Bitbucket-Type header / server_url request parameter not found
Title: Message Title Christoph Forster closed an issue as Won't Fix Jenkins / JENKINS-55649 X-Bitbucket-Type header / server_url request parameter not found Change By: Christoph Forster Status: Open Closed Resolution: Won't Fix 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.196826.1547727059000.11809.1575444302055%40Atlassian.JIRA.
[JIRA] (JENKINS-22494) Multiconfiguration project does not respect label restrictions
Title: Message Title Shai Shapira commented on JENKINS-22494 Re: Multiconfiguration project does not respect label restrictions Any plans to fix this? If binding using Node axis, is there any workaround that does not require running all configurations on all nodes with label? 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.154296.1396565762000.11808.1575444302045%40Atlassian.JIRA.
[JIRA] (JENKINS-55649) X-Bitbucket-Type header / server_url request parameter not found
Title: Message Title Christoph Forster commented on JENKINS-55649 Re: X-Bitbucket-Type header / server_url request parameter not found For me the Workaround also works. rhierlmeier: The log shows that the server_url Parameter is found and is working as expected so your problem must be within the job configuration 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.196826.1547727059000.11774.1575444240948%40Atlassian.JIRA.
[JIRA] (JENKINS-60359) Use standard bread crumbs
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-60359 Use standard bread crumbs Change By: Ulli Hafner Attachment: Bildschirmfoto 2019-12-04 um 07.38.20.png 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.203380.1575442072000.11762.1575442260993%40Atlassian.JIRA.
[JIRA] (JENKINS-60359) Use standard bread crumbs
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-60359 Use standard bread crumbs Change By: Ulli Hafner Attachment: Bildschirmfoto 2019-12-04 um 07.38.20.png 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.203380.1575442072000.11764.1575442261176%40Atlassian.JIRA.
[JIRA] (JENKINS-60359) Use standard bread crumbs
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-60359 Use standard bread crumbs Change By: Ulli Hafner The coverage reports create an additional bread crumb in the middle of the screen. They should use the default bread crumb in the header (for instance look at the warnings plugin). !Bildschirmfoto 2019-12-04 um 07.38.20.png! 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.203380.1575442072000.11760.1575442200148%40Atlassian.JIRA.
[JIRA] (JENKINS-60359) Use standard bread crumbs
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-60359 Use standard bread crumbs Issue Type: Improvement Assignee: Shenyu Zheng Attachments: Bildschirmfoto 2019-12-04 um 07.38.20.png Components: code-coverage-api-plugin Created: 2019-12-04 06:47 Priority: Minor Reporter: Ulli Hafner The coverage reports create an additional bread crumb in the middle of the screen. They should use the default bread crumb in the header (for instance look at the warnings plugin). Add Comment
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title Ulli Hafner edited a comment on JENKINS-59308 Re: Cobertura Code coverage all reports are showing in similar [~amila_devops] - You can create a feature request in Jira for the code - coverage -api- plugin. Maybe they can reuse the same concepts as the warnings plugin: using an *id* and *name* property. -See JENKINS-51367. 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.201856.1568169015000.11755.1575441960222%40Atlassian.JIRA.
[JIRA] (JENKINS-51148) GSoC: Community Bonding tasks for Code Coverage API plugin
Title: Message Title Ulli Hafner edited a comment on JENKINS-51148 Re: GSoC: Community Bonding tasks for Code Coverage API plugin I wonder if it makes sense to iterate over all issues if in the coverage plugin and leave only those open that still make sense (and move them as top level and not part of an Epics). 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.190443.1525524437000.11751.1575441840381%40Atlassian.JIRA.
[JIRA] (JENKINS-51148) GSoC: Community Bonding tasks for Code Coverage API plugin
Title: Message Title Ulli Hafner commented on JENKINS-51148 Re: GSoC: Community Bonding tasks for Code Coverage API plugin I wonder if it makes sense to iterate over all issues if the coverage plugin and leave only those open that still make sense (and move them as top level and not part of an Epics). 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.190443.1525524437000.11748.1575441840339%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title Ulli Hafner edited a comment on JENKINS-59308 Re: Cobertura Code coverage all reports are showing in similar [~amila_devops] You can create a feature request in Jira for the code-coverage-api-plugin. Maybe they can reuse the same concepts as the warnings plugin: using a an *id* and *name* 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.201856.1568169015000.11743.1575440640210%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title Ulli Hafner commented on JENKINS-59308 Re: Cobertura Code coverage all reports are showing in similar Amila Gunathilake You can create a feature request in Jira for the code-coverage-api-plugin. Maybe they can reuse the same concepts as the warnings plugin: using a id and name 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.201856.1568169015000.11739.1575440580316%40Atlassian.JIRA.
[JIRA] (JENKINS-59571) Removing non-serializable member from CucumberTestResultsAction
Title: Message Title Radi Berkovich updated JENKINS-59571 Jenkins / JENKINS-59571 Removing non-serializable member from CucumberTestResultsAction Change By: Radi Berkovich Status: Fixed but Unreleased 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.202207.1569674659000.11736.1575440460099%40Atlassian.JIRA.
[JIRA] (JENKINS-60350) Recover Deleted Dashboard view in jenkins main page
Title: Message Title Senthilkumar Palanisamy commented on JENKINS-60350 Re: Recover Deleted Dashboard view in jenkins main page Hi Tobias Gruetzmacher Many Thanks for your 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.203367.1575372289000.11733.1575437520159%40Atlassian.JIRA.
[JIRA] (JENKINS-60358) Root=null value in Template is overridden, failing sync
Title: Message Title Shai Shapira created an issue Jenkins / JENKINS-60358 Root=null value in Template is overridden, failing sync Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2019-12-04 05:29 Environment: Windows Priority: Minor Reporter: Shai Shapira P4 Windows use Root:null to support mapping sync to different drives. this value is always overwritten when using p4 plugin, thus failing the sync. p4 sync should use .../@ instead, and the workspace Root should not change. Add Comment
[JIRA] (JENKINS-60338) After jenkins restarts, the webhook event occasionally cannot be monitored
Title: Message Title Rick assigned an issue to Rick Jenkins / JENKINS-60338 After jenkins restarts, the webhook event occasionally cannot be monitored Change By: Rick Assignee: Parichay Barpanda Rick 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.203350.157526527.11708.1575437220687%40Atlassian.JIRA.
[JIRA] (JENKINS-60338) After jenkins restarts, the webhook event occasionally cannot be monitored
Title: Message Title Rick updated JENKINS-60338 Jenkins / JENKINS-60338 After jenkins restarts, the webhook event occasionally cannot be monitored Change By: Rick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203350.157526527.11714.1575437220824%40Atlassian.JIRA.
[JIRA] (JENKINS-60338) After jenkins restarts, the webhook event occasionally cannot be monitored
Title: Message Title Rick started work on JENKINS-60338 Change By: Rick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203350.157526527.11712.1575437220742%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title Federico Pellegrin commented on JENKINS-59308 Re: Cobertura Code coverage all reports are showing in similar As of now there is no possibility to customize that name label, it will just pick the filename (with some minor filtering of characters), sorry! 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.201856.1568169015000.11704.1575435240241%40Atlassian.JIRA.
[JIRA] (JENKINS-60040) Forward slash in branch name causes archived artifacts to not be copied to a new build when restarting a pipeline from a stage
Title: Message Title Jesse Glick updated JENKINS-60040 Jenkins / JENKINS-60040 Forward slash in branch name causes archived artifacts to not be copied to a new build when restarting a pipeline from a stage Change By: Jesse Glick 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.202868.1572884243000.11701.1575427740223%40Atlassian.JIRA.
[JIRA] (JENKINS-43348) Option to use author instead of commiter in declarative pipeline
Title: Message Title Brian J Murrell commented on JENKINS-43348 Re: Option to use author instead of commiter in declarative pipeline I have to agree completely that substituting the commiter for what should really be the patch author is really not very useful at all. It doesn't make sense to e-mail the commiter when there is a problem with the patch. It doesn't make sense for Blue Ocean to list the commiter as the person responsible for the change. Is this issue anywhere near completion? 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.180496.1491327788000.11696.1575426300255%40Atlassian.JIRA.
[JIRA] (JENKINS-60040) Forward slash in branch name causes archived artifacts to not be copied to a new build when restarting a pipeline from a stage
Title: Message Title Jesse Glick updated JENKINS-60040 Jenkins / JENKINS-60040 Forward slash in branch name causes archived artifacts to not be copied to a new build when restarting a pipeline from a stage Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 1.7 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.202868.1572884243000.11693.1575424560299%40Atlassian.JIRA.
[JIRA] (JENKINS-59633) EC2 Plugin: Windows EC2 instances are not launching
Title: Message Title Raihaan Shouhell updated an issue Jenkins / JENKINS-59633 EC2 Plugin: Windows EC2 instances are not launching Change By: Raihaan Shouhell Summary: EC2 Plguin Plugin : Windows EC2 instances are not launching 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.202315.157004916.11688.1575423840382%40Atlassian.JIRA.
[JIRA] (JENKINS-59633) EC2 Plguin: Windows EC2 instances are not launching
Title: Message Title Raihaan Shouhell updated JENKINS-59633 Jenkins / JENKINS-59633 EC2 Plguin: Windows EC2 instances are not launching Change By: Raihaan Shouhell Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202315.157004916.11681.1575423780518%40Atlassian.JIRA.
[JIRA] (JENKINS-59633) EC2 Plguin: Windows EC2 instances are not launching
Title: Message Title Raihaan Shouhell commented on JENKINS-59633 Re: EC2 Plguin: Windows EC2 instances are not launching Thanks for the fix. 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.202315.157004916.11686.1575423780613%40Atlassian.JIRA.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Nathan Neulinger commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted FYI in case it helps any – I just had to go through a big diag effort on my site with a bunch of windows JNLP agents that stopped working sometime in past few days with the same above failures/errors. After a long set of rabbit trails - what I found in my case – the problem wound up being reverse DNS resolution stopped working (unrelated local problem – "It's always DNS", right?) - but that inability to reverse resolve the connecting client (windows box) was causing the JNLP server side to drop the connection. Just wanted to add this here in case it helps anyone else with future similar issues if it happens to be related. 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.164090.1437742638000.11637.1575420780965%40Atlassian.JIRA.
[JIRA] (JENKINS-57143) JNLP4 error: "Connection closed before acknowledgement sent"
Title: Message Title Nathan Neulinger commented on JENKINS-57143 Re: JNLP4 error: "Connection closed before acknowledgement sent" I realize this has already been closed - but just had to go through a big diag effort on my site with a bunch of windows JNLP agents that stopped working sometime in past few days. After a long set of rabbit trails - what I found in my case – the problem wound up being reverse DNS resolution stopped working (unrelated local problem – "It's always DNS", right?) - but that inability to reverse resolve the connecting client (windows box) was causing the JNLP server side to drop the connection. Just wanted to add this here in case it helps anyone else with future similar issues if it happens to be related. 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.198893.1555967243000.11633.1575420420188%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title
Amila Gunathilake edited a comment on JENKINS-59308
Re: Cobertura Code coverage all reports are showing in similar
[~fedepell] Hi mate how are you?I have tested this your second solution, by using [code-coverage-api-plugin|https://github.com/jenkinsci/code-coverage-api-plugin] I able to generate 04 different reports. So I renamed my Cobertura.xml file by 04 different names in each stage's Post build section in my Jenkins file. Like below, {code:java}publishCoverage adapters: [coberturaAdapter(path: '**/build/Tests/NunitFast/NUnitTestsSlow_Test_Report.xml')]{code} * Below is the my output: !image-2019-12-04-06-12-09-697.png!!image-2019-12-04-06-13-35-714.png! Its It's really better output than my previous reports. Thank you for that. So do you know how to rename the Title of the reports ? Because it showing my .xml file name as the report heading. eg:!image-2019-12-04-06-15-47-865.png!
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.201856.1568169015000.11628.1575420360228%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title
Amila Gunathilake edited a comment on JENKINS-59308
Re: Cobertura Code coverage all reports are showing in similar
[~fedepell] Hi mate how are you?I have tested this your second solution, by using [code-coverage-api-plugin|https://github.com/jenkinsci/code-coverage-api-plugin] I able to generate 04 different reports. So I renamed my Cobertura.xml file by 04 different names in each stage's Post build section in my Jenkins file. Like below , {code:java}publishCoverage adapters: [coberturaAdapter(path: '**/build/Tests/NunitFast/NUnitTestsSlow_Test_Report.xml')]{code} * Below is the my output: !image-2019-12-04-06-12-09-697.png! !image-2019-12-04-06- 11 13 - 58 35 - 349 714 .png! Its
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.201856.1568169015000.11624.1575420240183%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title
Amila Gunathilake edited a comment on JENKINS-59308
Re: Cobertura Code coverage all reports are showing in similar
[~fedepell] Hi mate how are you?I have tested this your second solution, by using [code-coverage-api-plugin|https://github.com/jenkinsci/code-coverage-api-plugin] I able to generate 04 different reports. So I renamed my Cobertura.xml file by 04 different names in each stage's Post build section in my Jenkins file. Like below {code:java}publishCoverage adapters: [coberturaAdapter(path: '**/build/Tests/NunitFast/NUnitTestsSlow_Test_Report.xml')]{code} * Below is the my output: !image-2019-12-04-06-12-09-697.png!!image-2019-12-04-06-11-58-349.png!
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.201856.1568169015000.11620.1575420120169%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title Amila Gunathilake commented on JENKINS-59308 Re: Cobertura Code coverage all reports are showing in similar Federico Pellegrin Hi mate how are you? I have tested this your second solution, by using code-coverage-api-plugin I able to generate 04 different reports. So I renamed my Cobertura.xml file by 04 different names in each stage's Post build section in my Jenkins file. publishCoverage adapters: [coberturaAdapter(path: '**/build/Tests/NunitFast/NUnitTestsSlow_Test_Report.xml')] * Below is the my output: 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.201856.1568169015000.11616.1575419820313%40Atlassian.JIRA.
[JIRA] (JENKINS-60105) Kubernetes plugin fails with EKS
Title: Message Title Caleb Mayeux commented on JENKINS-60105 Re: Kubernetes plugin fails with EKS Jochen Niebuhr I think this is covered in the plugin readme under the EKS section (https://plugins.jenkins.io/kubernetes) Copy/pasting from that readme for convenience: Running with a remote Kubernetes Cloud in AWS EKS EKS enforces authentication to the cluster through aws-iam-authenticator. The token expires after 15 minutes so the kubernetes client cache needs to be set to something below this by setting a java argument, like so: JAVA_ARGS="-Dorg.csanchez.jenkins.plugins.kubernetes.clients.cacheExpiration=60" 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.202951.1573213399000.11608.1575418440269%40Atlassian.JIRA.
[JIRA] (JENKINS-59169) JNLP4 Connect Error - Connection closed before acknowledgement sent
Title: Message Title Nathan Neulinger commented on JENKINS-59169 Re: JNLP4 Connect Error - Connection closed before acknowledgement sent I realize this has already been closed - but just had to go through a big diag effort on my site with a bunch of windows JNLP agents that stopped working sometime in past few days. After a long set of rabbit trails - what I found in my case – the problem wound up being reverse DNS resolution stopped working (unrelated local problem – "It's always DNS", right?) - but that inability to reverse resolve the connecting client (windows box) was causing the JNLP server side to drop the connection. Just wanted to add this here in case it helps anyone else with future similar issues if it happens to be related. 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.201606.1567306209000.11610.1575418440300%40Atlassian.JIRA.
[JIRA] (JENKINS-52593) Support EKS authentication, or specifying a kubeconfig directly
Title: Message Title Caleb Mayeux commented on JENKINS-52593 Re: Support EKS authentication, or specifying a kubeconfig directly Justin Patrin and junaid mukhtar jI'm in the same boat as y'all. I also haven't gotten it to work, but based on spending entirely too much time googling and looking through code changes, I think the general idea is to do something like this (this example is if you're using the public jenkins docker image): FROM jenkins/jenkins:2.176.4 USER root RUN apt-get update && apt-get install -y python3-pip vim RUN pip3 install awscli USER jenkins Then inside the container you exec in and run the command "aws configure" and put in the access and secret key from IAM. Then you create a file ~/.kube/config and fill it out as per https://docs.aws.amazon.com/eks/latest/userguide/create-kubeconfig.html Test out that the command as per that config file works, i.e. run "aws eks get-token --cluster-name whateverYouNamedYourCluster" and make sure it spits out a json that has a token in it. That's what I've cobbled together based on looking at this change https://github.com/fabric8io/kubernetes-client/pull/1224/commits/ef2c87472d87e144da09190e1896a9dcbf6208c4 and looking at the readme for the kubernetes client here: https://github.com/fabric8io/kubernetes-client Like I said, this hasn't worked for me yet, but I feel like I'm close. If this helps you solve it, please post how to do it here for me and anyone else who runs into this issue. We should probably open an issue to update the plugin readme on this as well. If we can figure out how to get it to work we could even make that PR. Also if suryatej yaramada or Carlos Sanchez wanted to weigh in on how to configure using this I'd be much obliged. Thanks! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-41764) Perforce triggered build should not trigger polling on jobs unless there are changes related to that view
Title: Message Title Alena Volarevic commented on JENKINS-41764 Re: Perforce triggered build should not trigger polling on jobs unless there are changes related to that view Also the jobs that are being triggered by preforce should be build no matter if they are using Source Code Management or not. Like I have a job that is using the files from the perforce, but I am syncing the workspace files in the build process instead of source code managements portion. and I realized if I don't have source code management set to use perforce. the jobs wont be picked up when the P4 trigger is emitted... 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.178605.1486395343000.11586.1575414600187%40Atlassian.JIRA.
[JIRA] (JENKINS-59973) rtUpload / rtDownload fail with HTTP 401 / 403
Title: Message Title Jesper Reenberg commented on JENKINS-59973 Re: rtUpload / rtDownload fail with HTTP 401 / 403 ethorsa, could you perhaps elaborate a bit about the credentials used on the repository you are trying to upload to? I'm the author of that patch, and I have tried to reproduce it, without any luck. However offa seems to be able to reproduce it, so there might be something missing in the example I used to try and reproduce it. See the link you provided for more information about what I have tried so far. In short, I have tried the maven-example from the jfrog/jenkins-examples repo, against a brand new installation of Artifactory-oss (version 6.16.0 rev 61600900), running in a container. I have configured a repository named 'libs-snapshot-local' (as this is what the example upload spec uses), where anonymous have manage permissions for both repo action and build action. 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.11583.1575413940207%40Atlassian.JIRA.
[JIRA] (JENKINS-60040) Forward slash in branch name causes archived artifacts to not be copied to a new build when restarting a pipeline from a stage
Title: Message Title Jesse Glick commented on JENKINS-60040 Re: Forward slash in branch name causes archived artifacts to not be copied to a new build when restarting a pipeline from a stage Reproduced in a functional test which passes when picking up a jclouds update with the fix of JCLOUDS-1447. 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.202868.1572884243000.11578.1575413340252%40Atlassian.JIRA.
[JIRA] (JENKINS-60040) Forward slash in branch name causes archived artifacts to not be copied to a new build when restarting a pipeline from a stage
Title: Message Title Jesse Glick updated JENKINS-60040 Jenkins / JENKINS-60040 Forward slash in branch name causes archived artifacts to not be copied to a new build when restarting a pipeline from a stage Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202868.1572884243000.11580.1575413340285%40Atlassian.JIRA.
[JIRA] (JENKINS-41764) Perforce triggered build should not trigger polling on jobs unless there are changes related to that view
Title: Message Title Alena Volarevic commented on JENKINS-41764 Re: Perforce triggered build should not trigger polling on jobs unless there are changes related to that view Is there any progress on this? Also not sure if it's related or not.. but I have a pipeline script job, that is set to "Perforce triggered build" and it never gets picked up when I send manual P4 Trigger. 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.178605.1486395343000.11574.1575412920176%40Atlassian.JIRA.
[JIRA] (JENKINS-60040) Forward slash in branch name causes archived artifacts to not be copied to a new build when restarting a pipeline from a stage
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-60040 Forward slash in branch name causes archived artifacts to not be copied to a new build when restarting a pipeline from a stage Change By: Jesse Glick Assignee: Jesse Glick 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.202868.1572884243000.11570.1575411900275%40Atlassian.JIRA.
[JIRA] (JENKINS-60040) Forward slash in branch name causes archived artifacts to not be copied to a new build when restarting a pipeline from a stage
Title: Message Title Jesse Glick started work on JENKINS-60040 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202868.1572884243000.11572.1575411900333%40Atlassian.JIRA.
[JIRA] (JENKINS-60088) Change pod label - build label from unique key to value.
Title: Message Title Jesse Glick started work on JENKINS-60088 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202932.1573141389000.11564.1575408540605%40Atlassian.JIRA.
[JIRA] (JENKINS-60088) Change pod label - build label from unique key to value.
Title: Message Title Jesse Glick assigned an issue to Matthew Ludlum Jenkins / JENKINS-60088 Change pod label - build label from unique key to value. Change By: Jesse Glick Assignee: Matthew Ludlum 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.202932.1573141389000.11562.1575408540554%40Atlassian.JIRA.
[JIRA] (JENKINS-60088) Change pod label - build label from unique key to value.
Title: Message Title Jesse Glick updated JENKINS-60088 Jenkins / JENKINS-60088 Change pod label - build label from unique key to value. Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202932.1573141389000.11566.1575408540640%40Atlassian.JIRA.
[JIRA] (JENKINS-60111) Pipeline extremely slow when triggered by a user in comparison with the time triggered pipeline
Title: Message Title Sean Dugan commented on JENKINS-60111 Re: Pipeline extremely slow when triggered by a user in comparison with the time triggered pipeline Thank you Jon Denly. This has saved us a lot of headaches!! 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.202957.1573231443000.11556.1575405962178%40Atlassian.JIRA.
[JIRA] (JENKINS-59953) Job's Promotion Status generating invalid links
Title: Message Title Craig Lutgen resolved as Fixed Jenkins / JENKINS-59953 Job's Promotion Status generating invalid links Change By: Craig Lutgen Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202757.1572189054000.11560.1575406020447%40Atlassian.JIRA.
[JIRA] (JENKINS-59953) Job's Promotion Status generating invalid links
Title: Message Title Craig Lutgen commented on JENKINS-59953 Re: Job's Promotion Status generating invalid links Looks good. I will close this issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202757.1572189054000.11558.1575405962310%40Atlassian.JIRA.
[JIRA] (JENKINS-48828) Bitbucket Team/Folder project: View Configuration pages shows Access Denied, Jenkins throws hudson.security.AccessDeniedException2
Title: Message Title Timothy Tabing commented on JENKINS-48828 Re: Bitbucket Team/Folder project: View Configuration pages shows Access Denied, Jenkins throws hudson.security.AccessDeniedException2 Same issue here. Any update? I am running Jenkins: 2.181 Bitbucket Branch Source: 2.4.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.187612.1515180451000.11523.1575402600660%40Atlassian.JIRA.
[JIRA] (JENKINS-60357) Test may fail due to a different order of items in XML
Title: Message Title Context Shuffling updated an issue Jenkins / JENKINS-60357 Test may fail due to a different order of items in XML Change By: Context Shuffling Test in [CopyOnWriteListTest | https://github.com/jenkinsci/jenkins/blob/ead55ac41d7a06cca09fcc59cbbf1bfc8c0f81f7/core/src/test/java/hudson/util/CopyOnWriteListTest.java] depends on XStream to serialize and deserilize XML. The test assertions use hard-coded strings. However, the test may fail due to a different order of serialization results. So tests may fail or pass without any modifications to source 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.203374.1575398244000.11521.15753983
[JIRA] (JENKINS-60357) Test may fail due to a different order of items in XML
Title: Message Title Context Shuffling created an issue Jenkins / JENKINS-60357 Test may fail due to a different order of items in XML Issue Type: Bug Assignee: Oliver Gondža Components: jenkins-test-harness Created: 2019-12-03 18:37 Priority: Minor Reporter: Context Shuffling Test in CopyOnWriteListTest depends on XStream to serialize and deserilize XML. The test assertions use hard-coded strings. However, the test may fail due to a different order of serialization results. Add Comment This
[JIRA] (JENKINS-60350) Recover Deleted Dashboard view in jenkins main page
Title: Message Title Tobias Gruetzmacher closed an issue as Not A Defect Jenkins / JENKINS-60350 Recover Deleted Dashboard view in jenkins main page Change By: Tobias Gruetzmacher Status: Open Closed Resolution: Not A Defect 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.203367.1575372289000.11517.1575398040724%40Atlassian.JIRA.
[JIRA] (JENKINS-60350) Recover Deleted Dashboard view in jenkins main page
Title: Message Title Tobias Gruetzmacher commented on JENKINS-60350 Re: Recover Deleted Dashboard view in jenkins main page No, there is not. There are ways if you are prepared: You could use the https://plugins.jenkins.io/jobConfigHistory plugin You could restore from backup (You do have backups, right?) You could power off your system and try disaster recovery from the file system Anyways, since is not problem with the plugin itself, I'll close this issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203367.1575372289000.11515.1575398040671%40Atlassian.JIRA.
[JIRA] (JENKINS-60356) Provide a link to the jacoco XML report
Title: Message Title
Glauco Aquino updated an issue
Jenkins / JENKINS-60356
Provide a link to the jacoco XML report
Change By:
Glauco Aquino
Portfolio metrics and other project quality-related automated tools could should consume JaCoCo results directly from CI to collect coverage data even if they don't have access to the codebase or build environment.The JaCoCo XML report is the most suitable representation of the coverage data to be processed by an automated tool.Currently, jacoco-plugin provides a link for to the aggregated {{jacoco.exec}} file, however, it cannot be processed without having a working local build.The goal here is to provide an additional link in the coverage results page to download the aggregated {{jacoco.xml}} file.
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 jenkin
[JIRA] (JENKINS-60356) Provide a link to the jacoco XML report
Title: Message Title Glauco Aquino updated JENKINS-60356 Jenkins / JENKINS-60356 Provide a link to the jacoco XML report Change By: Glauco Aquino Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203373.1575395724000.11512.1575397920169%40Atlassian.JIRA.
[JIRA] (JENKINS-60144) Cant delete Jenkins job if the perforce template client has been deleted
Title: Message Title Karl Wirth assigned an issue to Unassigned Jenkins / JENKINS-60144 Cant delete Jenkins job if the perforce template client has been deleted Change By: Karl Wirth Assignee: Karl Wirth 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.203005.1573570536000.11510.1575396180177%40Atlassian.JIRA.
[JIRA] (JENKINS-60144) Cant delete Jenkins job if the perforce template client has been deleted
Title: Message Title
Karl Wirth edited a comment on JENKINS-60144
Re: Cant delete Jenkins job if the perforce template client has been deleted
Confirmed. The job is disabled but not deleted. An alternative workaround is to change the source control in the job to 'None' if this is a Freestyle job.Passing to developers. Error seen when using *Above Reproduction Steps*:{code:java}A problem occurred while processing the request.Please check our bug tracker to see if a similar problem has already been reported.If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem.If you think this is a new issue, please file a new issue.When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins.The users list might be also useful in understanding what has happened.Stack traceAlso: hudson.remoting.Channel$CallSiteStackTrace: Remote call to KarlsDesktop 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 org.jenkinsci.plugins.p4.PerforceScm.processWorkspaceBeforeDeletion(PerforceScm.java:830) at hudson.scm.SCM.processWorkspaceBeforeDeletion(SCM.java:245) at hudson.model.AbstractProject.performDelete(AbstractProject.java:358) at hudson.model.AbstractItem.delete(AbstractItem.java:775) at hudson.model.Job.delete(Job.java:675) at hudson.model.AbstractItem.doDoDelete(AbstractItem.java:645) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:243) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFi
[JIRA] (JENKINS-60144) Cant delete Jenkins job if the perforce template client has been deleted
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60144 Cant delete Jenkins job if the perforce template client has been deleted Change By: Karl Wirth Labels: P4_SUPPORT P4_A P4_VERIFY 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.203005.1573570536000.11507.1575396120474%40Atlassian.JIRA.
[JIRA] (JENKINS-60144) Cant delete Jenkins job if the perforce template client has been deleted
Title: Message Title
Karl Wirth edited a comment on JENKINS-60144
Re: Cant delete Jenkins job if the perforce template client has been deleted
Confirmed. The job is disabled but not deleted. An alternative workaround is to change the source control in the job to 'None' if this is a Freestyle job. Error seen when using *Above Reproduction Steps*:{code:java}A problem occurred while processing the request.Please check our bug tracker to see if a similar problem has already been reported.If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem.If you think this is a new issue, please file a new issue.When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins.The users list might be also useful in understanding what has happened.Stack traceAlso: hudson.remoting.Channel$CallSiteStackTrace: Remote call to KarlsDesktop 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 org.jenkinsci.plugins.p4.PerforceScm.processWorkspaceBeforeDeletion(PerforceScm.java:830) at hudson.scm.SCM.processWorkspaceBeforeDeletion(SCM.java:245) at hudson.model.AbstractProject.performDelete(AbstractProject.java:358) at hudson.model.AbstractItem.delete(AbstractItem.java:775) at hudson.model.Job.delete(Job.java:675) at hudson.model.AbstractItem.doDoDelete(AbstractItem.java:645) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:243) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.ja
[JIRA] (JENKINS-60144) Cant delete Jenkins job if the perforce template client has been deleted
Title: Message Title Karl Wirth commented on JENKINS-60144 Re: Cant delete Jenkins job if the perforce template client has been deleted Confirmed. The job is disabled but not deleted. An alternative workaround is to change the source control in the job to 'None' if this is a Freestyle job. 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.203005.1573570536000.11499.1575396060435%40Atlassian.JIRA.
[JIRA] (JENKINS-60356) Provide a link to the jacoco XML report
Title: Message Title Glauco Aquino started work on JENKINS-60356 Change By: Glauco Aquino Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203373.1575395724000.11496.1575395820230%40Atlassian.JIRA.
[JIRA] (JENKINS-60356) Provide a link to the jacoco XML report
Title: Message Title Glauco Aquino created an issue Jenkins / JENKINS-60356 Provide a link to the jacoco XML report Issue Type: Improvement Assignee: Glauco Aquino Attachments: jacoco-xml-link.png Components: jacoco-plugin Created: 2019-12-03 17:55 Priority: Major Reporter: Glauco Aquino Portfolio metrics and other project quality-related automated tools could consume JaCoCo results directly from CI to collect coverage data even if they don't have access to the codebase or build environment. The JaCoCo XML report is the most suitable representation of the coverage data to be processed by an automated tool. Currently, jacoco-plugin provides a link for the aggregated jacoco.exec file, however, it cannot be processed without having a working local build. The goal here is to provide an additional link in the coverage results page to download the aggregated jacoco.xml file. Add Comment
[JIRA] (JENKINS-60142) ConnectionHelper.java constructors call connectionRetry()
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60142 ConnectionHelper.java constructors call connectionRetry() Change By: Karl Wirth Labels: P4_A P4_VERIFY 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.203003.1573562093000.11493.1575395460464%40Atlassian.JIRA.
[JIRA] (JENKINS-60142) ConnectionHelper.java constructors call connectionRetry()
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60142 ConnectionHelper.java constructors call connectionRetry() Change By: Karl Wirth Labels: P4_SUPPORT P4_A 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.203003.1573562093000.11488.1575395460355%40Atlassian.JIRA.
[JIRA] (JENKINS-60142) ConnectionHelper.java constructors call connectionRetry()
Title: Message Title Karl Wirth assigned an issue to Unassigned Jenkins / JENKINS-60142 ConnectionHelper.java constructors call connectionRetry() Change By: Karl Wirth Assignee: Karl Wirth 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.203003.1573562093000.11491.1575395460398%40Atlassian.JIRA.
[JIRA] (JENKINS-60142) ConnectionHelper.java constructors call connectionRetry()
Title: Message Title
Karl Wirth updated an issue
Jenkins / JENKINS-60142
ConnectionHelper.java constructors call connectionRetry()
Change By:
Karl Wirth
Comment:
Confirmed. One invocation of the above script against a freestyle job that had 8 successful executions caused 24 P4 commands to be run:{code:java} 2019/12/03 17:32:31 pid 1868 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1869 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1870 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1871 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1872 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1873 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1874 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1875 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1876 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1877 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1878 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1879 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1880 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1881 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1882 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1883 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1884 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1885 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1886 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:32 pid 1887 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1888 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1889 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:32 pid 1890 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1891 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s'$ grep user- tmpa.txt | wc -l24{code}For a job with 4 successful runs I saw 11 commands kicked off:{code:java} 2019/12/03 17:40:17 pid 2509 super@_CLIENT_UNSET_ 127.0.0.1 [je
[JIRA] (JENKINS-60142) ConnectionHelper.java constructors call connectionRetry()
Title: Message Title
Karl Wirth edited a comment on JENKINS-60142
Re: ConnectionHelper.java constructors call connectionRetry()
Confirmed. One invocation of the above script against a freestyle job that had 8 successful executions caused 24 P4 commands to be run:{code:java} 2019/12/03 17:32:31 pid 1868 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1869 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1870 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1871 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1872 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1873 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1874 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1875 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1876 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1877 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1878 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1879 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1880 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1881 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1882 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1883 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1884 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1885 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1886 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:32 pid 1887 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1888 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1889 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:32 pid 1890 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1891 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s'$ grep user- tmpa.txt | wc -l24{code}For a job with 4 successful runs I saw 11 commands kicked off:{code:java} 2019/12/03 17:40:17 pid 2509 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:40:17 pid 2510 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:40:48 pid 2512 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:40:48 pid 2513 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:40:48 pid 2514 super@_CLIENT_UNSET
[JIRA] (JENKINS-60142) ConnectionHelper.java constructors call connectionRetry()
Title: Message Title Karl Wirth commented on JENKINS-60142 Re: ConnectionHelper.java constructors call connectionRetry() Confirmed. One invocation of the above script against a freestyle job that had 8 successful executions caused 24 P4 commands to be run: 2019/12/03 17:32:31 pid 1868 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1869 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1870 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1871 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1872 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1873 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1874 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1875 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1876 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1877 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1878 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1879 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1880 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1881 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1882 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1883 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1884 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1885 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1886 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:32 pid 1887 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1888 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1889 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:32 pid 1890 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1891 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' $ grep user- tmpa.txt | wc -l 24 For a job with 4 successful runs I saw 11 commands kicked off: 2019/12/03 17:40:17 pid 2509 super@__
[JIRA] (JENKINS-60142) ConnectionHelper.java constructors call connectionRetry()
Title: Message Title Karl Wirth commented on JENKINS-60142 Re: ConnectionHelper.java constructors call connectionRetry() Confirmed. One invocation of the above script against a freestyle job that had 8 successful executions caused 24 P4 commands to be run: 2019/12/03 17:32:31 pid 1868 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1869 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1870 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1871 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1872 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1873 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1874 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1875 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1876 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1877 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1878 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1879 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1880 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1881 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1882 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1883 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1884 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1885 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1886 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:32 pid 1887 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1888 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1889 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:32 pid 1890 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1891 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' $ grep user- tmpa.txt | wc -l 24 For a job with 4 successful runs I saw 11 commands kicked off: 2019/12/03 17:40:17 pid 2509 super@__
[JIRA] (JENKINS-60213) P4CLIENT environment variable non-reentrant
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60213 P4CLIENT environment variable non-reentrant Change By: Karl Wirth Summary: P4 P4CLIENT environment variables variable non-reentrant 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.11473.1575393540572%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
Verified still sporadically broken in 1.10.7. P4_CLIENT is wrong. The full expansion for me is correct and matches the rest of the job:
P4: saving built changes.
Found last change 2240 on syncID jenkins-NODE_NAME-JENKINS-60213-ConcurrentVariables-EXECUTOR_NUMBER
... p4 login -s
... p4 client -o jenkins-master-JENKINS-60213-ConcurrentVariables-3
... p4 info
... p4 info
... p4 client -o jenkins-master-JENKINS-60213-ConcurrentVariables-3
... p4 login -s
... p4 client -o jenkins-master-JENKINS-60213-ConcurrentVariables-3
... p4 info
... p4 info
... p4 client -o jenkins-master-JENKINS-60213-ConcurrentVariables-3
... done
[JENKINS-60213-ConcurrentVariables@2] $ /bin/bash /tmp/jenkins6561639748343680378.sh
==
WORKSPACE:/var/lib/jenkins/workspace/JENKINS-60213-ConcurrentVariables@2
P4_CLIENT:jenkins-master-JENKINS-60213-ConcurrentVariables-4
EXECUTOR NUMBER: 3
CLIENT_FROM_VARS: jenkins-master-JENKINS-60213-ConcurrentVariables-3
==
Finished: SUCCESS
Note for dev: In the above ${P4_CLIENT} is wrong but expansion is correct.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this m
[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 Labels: P4_A P4_VERIFY 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.11469.1575392820137%40Atlassian.JIRA.
[JIRA] (JENKINS-60354) Updated pipeline build step does not work with retry
Title: Message Title
Jonathan B updated an issue
Jenkins / JENKINS-60354
Updated pipeline build step does not work with retry
Change By:
Jonathan B
We just upgraded pipeline-build-step from 2.9 to 2.10. The following no longer retries:{code}pipeline {agent anystages {stage('bug') {steps {retry(3) {echo 'in the retry loop'//throw new Exception('failing in retry loop') // This runs (when uncommented) several times before the pipeline exits with failure.build(job: 'some/job/that/fails', propagate: true) // This only runs once before the pipeline exits with failure.}}}}}{code}When the sub-build fails, the retry loop exits immediately and does not retry. This didn't used to happen. When raising an error in another way (e.g. the `throw new Exception`, commented out, in the code above), `retry` works as expected. A workaround is to try/catch the `build()` call and, in catch, `throw new Exception(...)`. If the caught exception is directly re-thrown, we see the same behavior where `retry` does not loop.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60355) Updating openshift-sync-configuration from jenkins-cli does not result in watching newly assigned namespaces
Title: Message Title Daniel Horn updated an issue Jenkins / JENKINS-60355 Updating openshift-sync-configuration from jenkins-cli does not result in watching newly assigned namespaces Change By: Daniel Horn Summary: Updating openshift- synch sync -configuration from jenkins-cli does not result in watching newly assigned namespaces 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.203372.1575392303000.11466.1575392340355%40Atlassian.JIRA.
[JIRA] (JENKINS-60355) Updating openshift-synch-configuration from jenkins-cli does not result in watching newly assigned namespaces
Title: Message Title Daniel Horn created an issue Jenkins / JENKINS-60355 Updating openshift-synch-configuration from jenkins-cli does not result in watching newly assigned namespaces Issue Type: Improvement Assignee: Gabe Montero Attachments: image-2019-12-03-17-30-29-372.png, image-2019-12-03-17-36-07-360.png Components: cli, openshift-sync-plugin Created: 2019-12-03 16:58 Priority: Minor Reporter: Daniel Horn Hi Support Team, we are currently trying to set up a containerized Jenkins-Soulution in our company based n OpenShift. For this, we want to onboard new OpenShuft-Projects via self-service and needed a solution to update the monitored namespaces without human intervention. On our research we found, that it is possible to update the OpenShift-Synch values by jenkins-cli and developed a solution. The update does result in the values being visible by the Configuration-Screen, but created BuildConfigurations do not appear in the Project-Dashboard. Configuration on a freshly deployed Jenkins in namespace dhorn-jenkins-test Content of newConfig.yaml - after reading the whole configuration, we have seen, that the menitored namespaces are listed under unclassified -> globalPluginConfiguration -> namespace --- unclassified: globalPluginConfiguration: namespace: dhorn-jenkins-test dhorn-automated
[JIRA] (JENKINS-60354) Updated pipeline build step does not work with retry
Title: Message Title
Jonathan B created an issue
Jenkins / JENKINS-60354
Updated pipeline build step does not work with retry
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline-build-step-plugin, workflow-basic-steps-plugin
Created:
2019-12-03 16:54
Priority:
Minor
Reporter:
Jonathan B
We just upgraded pipeline-build-step from 2.9 to 2.10. The following no longer retries:
pipeline {
agent any
stages {
stage('bug') {
steps {
retry(3) {
echo 'in the retry loop'
//throw new Exception('failing in retry loop') // This runs (when uncommented) several times before the pipeline exits with failure.
build(job: 'some/job/that/fails', propagate: true) // This only runs once before the pipeline exits with failure.
}
}
}
}
}
When the sub-build fails, the retry loop exits immediately and does not retry. This didn't used to happen. When raising an error in another way (e.g. the `throw new Exception`, commented out, in the code above), `retry` works as expected.
[JIRA] (JENKINS-59633) EC2 Plguin: Windows EC2 instances are not launching
Title: Message Title tapvir virk commented on JENKINS-59633 Re: EC2 Plguin: Windows EC2 instances are not launching Raphael Pionke Fix is working for me. Thanks 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.202315.157004916.11458.1575391800185%40Atlassian.JIRA.
[JIRA] (JENKINS-38316) Entering, then cancelling, quiet mode causes builds to hang
Title: Message Title Jesse Glick reopened an issue (incorrect resolution) Jenkins / JENKINS-38316 Entering, then cancelling, quiet mode causes builds to hang Change By: Jesse Glick Resolution: Fixed Status: Closed 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/
[JIRA] (JENKINS-38316) Entering, then cancelling, quiet mode causes builds to hang
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-38316 Entering, then cancelling, quiet mode causes builds to hang Change By: Jesse Glick 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.174488.147422949.11456.1575390969080%40Atlassian.JIRA.
[JIRA] (JENKINS-39287) Ability to select from existing credentials list at runtime
Title: Message Title Drew Waranis commented on JENKINS-39287 Re: Ability to select from existing credentials list at runtime Unfortunately, therein lies the rub: We already have the Jenkins Perforce Credentials created and can pick between them at DSL job generation time, but now we have a set of jobs that can use either of two Jenkins P4 Credentials at job runtime based on the location of the build node running them. So we need either: The likely simpler way is to have an option for the P4 Plugin use the P4PORT, P4SERVER, and P4TRUST variables set in the job runner's Jenkins Node Properties. Or, a more complicated option is the ability to map Jenkins Node Labels to Jenkins P4 Credentials and then be able to pass that mapping to the P4 Plugin instead of a Jenkins P4 Credential. 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.175718.1477521864000.11428.1575390968439%40Atlassian.JIRA.
[JIRA] (JENKINS-60199) jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login
Title: Message Title Pierre-Yves Bigourdan commented on JENKINS-60199 Re: jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login Adding ProxyPreserveHost On to our httpd configuration did solve the problem for us as well. Thanks for the tip! 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.203169.1574080196000.11396.1575390900845%40Atlassian.JIRA.
[JIRA] (JENKINS-60311) contentReplace does not appear in the Snippet Generator
Title: Message Title Florian Patzl commented on JENKINS-60311 Re: contentReplace does not appear in the Snippet Generator I experienced the same issues today and had to downgrade to 1.0.10. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203307.1574923665000.11399.1575390901005%40Atlassian.JIRA.
[JIRA] (JENKINS-59633) EC2 Plguin: Windows EC2 instances are not launching
Title: Message Title Raphael Pionke commented on JENKINS-59633 Re: EC2 Plguin: Windows EC2 instances are not launching tapvir virk you can find the hpi file here: https://ci.jenkins.io/job/Plugins/job/ec2-plugin/job/PR-418/1/artifact/org/jenkins-ci/plugins/ec2/1.47-rc1073.62885629c57c/ec2-1.47-rc1073.62885629c57c.hpi Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202315.157004916.11378.1575390720967%40Atlassian.JIRA.
[JIRA] (JENKINS-59633) EC2 Plguin: Windows EC2 instances are not launching
Title: Message Title Raphael Pionke started work on JENKINS-59633 Change By: Raphael Pionke Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202315.157004916.11383.1575390721255%40Atlassian.JIRA.
[JIRA] (JENKINS-60334) The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:3.6 is missing
Title: Message Title Ted commented on JENKINS-60334 Re: The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:3.6 is missing If you are not a developer and you just want to try it out, please use the update center to download https://jenkins.io/doc/book/managing/plugins/ The simplest and most common way of installing plugins is through the Manage Jenkins > Manage Plugins view, available to administrators of a Jenkins environment. 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.203346.1575115143000.11375.1575390420238%40Atlassian.JIRA.
[JIRA] (JENKINS-59633) EC2 Plguin: Windows EC2 instances are not launching
Title: Message Title tapvir virk commented on JENKINS-59633 Re: EC2 Plguin: Windows EC2 instances are not launching Raphael Pionke - Can you give me the hpi file to test on my jenkins instance? 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.202315.157004916.11373.1575390180717%40Atlassian.JIRA.
[JIRA] (JENKINS-59633) EC2 Plguin: Windows EC2 instances are not launching
Title: Message Title Raphael Pionke commented on JENKINS-59633 Re: EC2 Plguin: Windows EC2 instances are not launching i submitted a pull request, which fixes the problem: https://github.com/jenkinsci/ec2-plugin/pull/418 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.202315.157004916.11366.1575389520295%40Atlassian.JIRA.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Brian J Murrell commented on JENKINS-58085 Re: BlueOcean UI stuck in "Waiting for run to start" Can we please have this re-opened. I can confirm it's still happening here on 1.19.0 also. This together with stage-view being pretty crippled means finding logs of currently-running pipelines (i.e. in Pipeline Steps) is pretty cumbersome even for a Jenkins pro. Pretty much unusable for casual users with it's lack of collapsibility, etc. 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.200110.1560887329000.11336.1575387421086%40Atlassian.JIRA.
[JIRA] (JENKINS-60353) Non-mergable Pull-request Contents Get into GH Cache with False-Positive 404
Title: Message Title Vladimir Kuklin updated an issue Jenkins / JENKINS-60353 Non-mergable Pull-request Contents Get into GH Cache with False-Positive 404 Change By: Vladimir Kuklin How to reproduce:Use multibranch-pipeline workflow with merge PR strategy # Create a branch, develop it and make it nonmergable into the target branch # Push the branch and open the Pull Request in GH # Find out that the branch is not-mergeable # Fix the code, push the newer revision Expected Result:The pipeline is triggered.Actual Result: # On step #2 Jenkins gets the 404 in the request to ...refs/pull//merge/contents # The 404 is cached # On the step 4 it does not query GH but rather returns a cryptic error of 'Jenkins File not found' although it does not check for it at allProposed solution: do not check for the contents of the "refs.//merge" URL if the PR is not mergable.Versions:Jenkins 2.190.1GitHub Branch Source Plugin 2.5.8+ (some irrelevant local patches) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60353) Non-mergable Pull-request Contents Get into GH Cache with False-Positive 404
Title: Message Title Vladimir Kuklin created an issue Jenkins / JENKINS-60353 Non-mergable Pull-request Contents Get into GH Cache with False-Positive 404 Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2019-12-03 15:25 Priority: Minor Reporter: Vladimir Kuklin How to reproduce: Use multibranch-pipeline workflow Create a branch, develop it and make it nonmergable into the target branch Push the branch and open the Pull Request in GH Find out that the branch is not-mergeable Fix the code, push the newer revision # Add Comment
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Alessio Moscatello commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Liam Newman your comment you are saing to set a JVM argument. I've added it to my Jenkins instance, and from the Jenkins script console I see that JAVA_OPTS variable is being populated like this: JAVA_OPTS=-Dorg.jenkinsci.plugins.pipeline.modeldefinition.parser.RuntimeASTTransformer.SCRIPT_SPLITTING_TRANSFORMATION=true This is sufficient to verify that the script splitting is enabled? Because I haven't seen any differences (my declarative pipeline is still failing). Another question you are talking about version 1.4 of which plugin? BR, Alessio 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.174127.1473169024000.11260.1575385863755%40Atlassian.JIRA.
[JIRA] (JENKINS-60176) Groups are not working | SAML | Authorization Matrix
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-60176 Re: Groups are not working | SAML | Authorization Matrix This Jira is not a support site if you have questions please use the google groups, see https://wiki.jenkins.io/display/JENKINS/How+to+report+an+issue Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203136.157375217.11258.1575385320117%40Atlassian.JIRA.
[JIRA] (JENKINS-60352) Ansible Tower Plugin does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title Viv Cheolu created an issue Jenkins / JENKINS-60352 Ansible Tower Plugin does not pass credentials from job to Ansible tower 3.6.1 Issue Type: Bug Assignee: John Westcott Components: ansible-tower-plugin Created: 2019-12-03 14:50 Environment: CloudBees Jenkins : 1.11.22 Managed Master Version: 2.176.4 Priority: Critical Reporter: Viv Cheolu Jenkins job is not passing credentials to job template in Tower for Ansible tower version 3.6.1. This used to work with Tower version 2.9 Add Comment
[JIRA] (JENKINS-60351) can not disable the retries of Util.delete
Title: Message Title James Nord started work on JENKINS-60351 Change By: James Nord Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203368.1575383029000.11254.1575384060310%40Atlassian.JIRA.
[JIRA] (JENKINS-60351) can not disable the retries of Util.delete
Title: Message Title James Nord assigned an issue to James Nord Jenkins / JENKINS-60351 can not disable the retries of Util.delete Change By: James Nord Assignee: James Nord 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.203368.1575383029000.11253.1575384060208%40Atlassian.JIRA.
[JIRA] (JENKINS-60351) can not disable the retries of Util.delete
Title: Message Title
James Nord updated an issue
Jenkins / JENKINS-60351
can not disable the retries of Util.delete
Change By:
James Nord
[https://github.com/jenkinsci/jenkins/blob/c8efc7c78e26f3aefad24ef4c8a161cb9a269ea3/core/src/main/java/hudson/Util.java#L1581-L1596] is confused. The properties is for "retries" which you should be able to disable with a count of zero. but you can not. but the comment implies it is just for the number of tries (not retries).However the code calls [{{PathRemover.newFilteredRobustRemover(pathChecker, DELETION_MAX - 1, GC_AFTER_FAILED_DELETE, WAIT_BETWEEN_DELETION_RETRIES);}}|#L1635]] which ends up in [https://github.com/jenkinsci/jenkins/blob/c8efc7c78e26f3aefad24ef4c8a161cb9a269ea3/core/src/main/java/jenkins/util/io/PathRemover.java#L63-L65] which is using a max retries.However if you run a test with the system property set to one. then you do get one retry not one try.-DargLine=-Dhudson.Util.maxFileDeletionRetries=1 {noformat} Unable to delete 'C:\Users\IEUser\Desktop\oc-server\target\tmp\j h6725733765603761727'. Tried 2 time (of a maximum of 2) waiting 0.1 sec between attempts. {noformat}so the property does seem to be acting as a retry despite the code comment but you can not set it to zero one because...{noformat}static int DELETION_MAX = Math.max(1, SystemProperties.getInteger(Util.class.getName() + ".maxFileDeletionRetries", 3)); {noformat} and the [PathRemover| [https://github.com/jenkinsci/jenkins/blob/c8efc7c78e26f3aefad24ef4c8a161cb9a269ea3/core/src/main/java/jenkins/util/io/PathRemover.java #L64]].. {noformat}return new PathRemover(new PausingGCRetryStrategy(Math.max(maxRetries, 1), gcAfterFailedRemove, waitBetweenRetries), pathChecker);{noformat} which means it will always retry once, which is a PITA when trying to some timing bugs.
Add Comment
[JIRA] (JENKINS-57304) Multiple "idle" entries on Build Executor Status for non-existant executors
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-57304 Multiple "idle" entries on Build Executor Status for non-existant executors Change By: Baptiste Mathus Released As: (towards) 2.208 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.199072.1556795988000.11238.1575383288962%40Atlassian.JIRA.
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title Ihor Tymoshenko commented on JENKINS-59503 Re: Plugin does not save settings It is still producing for the `Notify Build Start` option. 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.202124.1569316263000.11235.1575383288155%40Atlassian.JIRA.
[JIRA] (JENKINS-60351) can not disable the retries of Util.delete
Title: Message Title
James Nord updated an issue
Jenkins / JENKINS-60351
can not disable the retries of Util.delete
Change By:
James Nord
[https://github.com/jenkinsci/jenkins/blob/c8efc7c78e26f3aefad24ef4c8a161cb9a269ea3/core/src/main/java/hudson/Util.java#L1581-L1596] is confused. The properties is for "retries" which you should be able to disable with a count of zero. but you can not. but the comment implies it is just for the number of tries (not retries).However the code calls [{{PathRemover.newFilteredRobustRemover(pathChecker, DELETION_MAX - 1, GC_AFTER_FAILED_DELETE, WAIT_BETWEEN_DELETION_RETRIES);}}| [https://github.com/jenkinsci/jenkins/blob/c8efc7c78e26f3aefad24ef4c8a161cb9a269ea3/core/src/main/java/hudson/Util.java #L1635]]which ends up in [https://github.com/jenkinsci/jenkins/blob/c8efc7c78e26f3aefad24ef4c8a161cb9a269ea3/core/src/main/java/jenkins/util/io/PathRemover.java#L63-L65] which is using a max retries. However if you run a test with the system property set to one. then you do get one retry not one try. -DargLine=-Dhudson.Util.maxFileDeletionRetries=1 {noformat} Unable to delete 'C:\Users\IEUser\Desktop\oc-server\target\tmp\j h6725733765603761727'. Tried 2 time (of a maximum of 2) waiting 0.1 sec between attempts. {noformat} so the property does seem to be acting as a retry despite the code comment but you can not set it to zero one because... {noformat}static int DELETION_MAX = Math.max(1, SystemProperties.getInteger(Util.class.getName() + ".maxFileDeletionRetries", 3)); {noformat} and the [PathRemover|[https://github.com/jenkinsci/jenkins/blob/c8efc7c78e26f3aefad24ef4c8a161cb9a269ea3/core/src/main/java/jenkins/util/io/PathRemover.java#L64]]..{noformat}return new PathRemover(new PausingGCRetryStrategy(Math.max(maxRetries, 1), gcAfterFailedRemove, waitBetweenRetries), pathChecker);{noformat}
Add Comment
