[JIRA] (JENKINS-61727) publish artifacts fail
Title: Message Title huang zhiquan created an issue Jenkins / JENKINS-61727 publish artifacts fail Issue Type: Bug Assignee: Technical Support Attachments: image-2020-03-28-18-30-25-051.png, image-2020-03-28-18-31-07-966.png Components: absint-a3-plugin Created: 2020-03-28 10:32 Priority: Minor Reporter: huang zhiquan Add Comment
[JIRA] (JENKINS-61712) Improve tests for TestScore (in TestScoreTest)
Title: Message Title Lukas Kirner assigned an issue to Lukas Kirner Jenkins / JENKINS-61712 Improve tests for TestScore (in TestScoreTest) Change By: Lukas Kirner Assignee: Lukas Kirner Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205538.1585328871000.1809.1585396920437%40Atlassian.JIRA.
[JIRA] (JENKINS-61715) Improve tests for CoverageScore (in CoverageScoreTest)
Title: Message Title Patrick Rogg assigned an issue to Patrick Rogg Jenkins / JENKINS-61715 Improve tests for CoverageScore (in CoverageScoreTest) Change By: Patrick Rogg Assignee: Patrick Rogg Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205541.1585329793000.1813.1585397820125%40Atlassian.JIRA.
[JIRA] (JENKINS-61715) Improve tests for CoverageScore (in CoverageScoreTest)
Title: Message Title Patrick Rogg started work on JENKINS-61715 Change By: Patrick Rogg Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205541.1585329793000.1815.1585397880181%40Atlassian.JIRA.
[JIRA] (JENKINS-61712) Improve tests for TestScore (in TestScoreTest)
Title: Message Title Lukas Kirner started work on JENKINS-61712 Change By: Lukas Kirner Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205538.1585328871000.1817.1585398180184%40Atlassian.JIRA.
[JIRA] (JENKINS-45273) Pipeline Multibranch - Add the possibility to use a Jenkinsfile from other SCM
Title: Message Title Aytunc BEKEN commented on JENKINS-45273 Re: Pipeline Multibranch - Add the possibility to use a Jenkinsfile from other SCM Devin Nusbaum I agree with, I will try to change the plugin name. Thanks for the suggestion. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183409.1499103287000.1831.1585402260992%40Atlassian.JIRA.
[JIRA] (JENKINS-45273) Pipeline Multibranch - Add the possibility to use a Jenkinsfile from other SCM
Title: Message Title Aytunc BEKEN edited a comment on JENKINS-45273 Re: Pipeline Multibranch - Add the possibility to use a Jenkinsfile from other SCM [~dnusbaum] I agree with you , I will try to change the plugin name. Thanks for the suggestion. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183409.1499103287000.1833.1585402261026%40Atlassian.JIRA.
[JIRA] (JENKINS-61027) Add option to pass parameters/environment values from multibranch to triggered jobs
Title: Message Title Aytunc BEKEN commented on JENKINS-61027 Re: Add option to pass parameters/environment values from multibranch to triggered jobs I thought about this, However, the way that I implemented triggering jobs do not make it possible to parse Jenkins file of multibranch job. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204500.1581324478000.1849.1585402380189%40Atlassian.JIRA.
[JIRA] (JENKINS-61027) Add option to pass parameters/environment values from multibranch to triggered jobs
Title: Message Title Aytunc BEKEN closed an issue as Won't Do Jenkins / JENKINS-61027 Add option to pass parameters/environment values from multibranch to triggered jobs Change By: Aytunc BEKEN Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204500.1581324478000.1855.1585402500502%40Atlassian.JIRA.
[JIRA] (JENKINS-61027) Add option to pass parameters/environment values from multibranch to triggered jobs
Title: Message Title Aytunc BEKEN edited a comment on JENKINS-61027 Re: Add option to pass parameters/environment values from multibranch to triggered jobs I thought about this, However, the way that I implemented triggering jobs do not make it possible to parse Jenkins file of multibranch job. Sorry for the inconvenience. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204500.1581324478000.1852.1585402500423%40Atlassian.JIRA.
[JIRA] (JENKINS-61601) Unable to trigger job on deletion of branch when configured with job DSL.
Title: Message Title Aytunc BEKEN started work on JENKINS-61601 Change By: Aytunc BEKEN Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205299.1584706587000.1858.1585402560259%40Atlassian.JIRA.
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title Mark Waite commented on JENKINS-61693 Re: using git multi branch pipeline through proxy leads to fatal: unable to access Thomas Patzig I am also unable to duplicate the issue on Jenkins 2.222.1. The password is stored when I submit the form without validating the proxy. If I validate the proxy with 2.222.1, the validation fails with "ERROR" which can be expanded to show the null pointer exception. After the NPE during validation, the fields are still visible to the user, but there seem to be cases where pressing the Submit button does not write the password or username to the proxy.xml file. The bug in 2.222.1 that causes the null pointer exception seems to also cause unexpected interactions between the fields after the null pointer exception. I think that is understandable, since the null pointer exception is unexpected and interrupts the logic before it completes its tasks. I think that PR 4607 is the best solution for this, but that needs your confirmation that it addresses the case you had seen. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205518.1585229665000.1860.1585402920242%40Atlassian.JIRA.
[JIRA] (JENKINS-61601) Unable to trigger job on deletion of branch when configured with job DSL.
Title: Message Title Aytunc BEKEN updated JENKINS-61601 Jenkins / JENKINS-61601 Unable to trigger job on deletion of branch when configured with job DSL. Change By: Aytunc BEKEN Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205299.1584706587000.1867.1585407240391%40Atlassian.JIRA.
[JIRA] (JENKINS-61601) Unable to trigger job on deletion of branch when configured with job DSL.
Title: Message Title Aytunc BEKEN commented on JENKINS-61601 Re: Unable to trigger job on deletion of branch when configured with job DSL. Fixed with 1.8.1 release. Please let me know if it is solved on your side. Thanks Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205299.1584706587000.1864.1585407240350%40Atlassian.JIRA.
[JIRA] (JENKINS-61726) Nexus Platform plugin fail to connect to the Nexus 2 repository Server
Title: Message Title Tun Wei closed an issue as Not A Defect usage error Jenkins / JENKINS-61726 Nexus Platform plugin fail to connect to the Nexus 2 repository Server Change By: Tun Wei Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.co
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title Thomas Patzig commented on JENKINS-61693 Re: using git multi branch pipeline through proxy leads to fatal: unable to access ..have try jenkins.war from PR 4607 it works... Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205518.1585229665000.1872.1585416540160%40Atlassian.JIRA.
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title Thomas Patzig edited a comment on JENKINS-61693 Re: using git multi branch pipeline through proxy leads to fatal: unable to access ..have try jenkins.war from PR 4607 it works... have also found a mistake on my sideI automize the Jenkins installation and bootstrap config to check latest versions... for that I do some http posts like the user would do... for setup the proxy I have use "post descriptorByName/hudson.ProxyConfiguration/validateProxy" with body form url encoded content and the content password instead of secretPassword... I think "password" is no longer supported in that post. Am I right? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205518.1585229665000.1875.1585416840220%40Atlassian.JIRA.
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title Thomas Patzig edited a comment on JENKINS-61693 Re: using git multi branch pipeline through proxy leads to fatal: unable to access ..have try jenkins.war from PR 4607 it works... have also found a mistake on my sideI automize the Jenkins installation and bootstrap config to check latest versions... for that I do some http posts like the user would do... for setup the proxy I have use "post descriptorByName/hudson.ProxyConfiguration/validateProxy" with body form url encoded content and the content "password" instead of "secretPassword"...(same on http post pluginManager/proxyConfigure) I think "password" is no longer supported in that post. Am I right? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205518.1585229665000.1879.1585416960241%40Atlassian.JIRA.
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title Thomas Patzig edited a comment on JENKINS-61693 Re: using git multi branch pipeline through proxy leads to fatal: unable to access ..have try jenkins.war from PR 4607 it works... have also found a mistake on my sideI automize the Jenkins installation and bootstrap config to check latest versions... for that I do some http posts like the user would do... for setup the proxy I have use "post descriptorByName/hudson.ProxyConfiguration/validateProxy" with body form url encoded content and the content " password " instead of " secretPassword " ... (same on http post pluginManager/proxyConfigure) I think "password" is no longer supported in that post. Am I right? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205518.1585229665000.1878.1585416960222%40Atlassian.JIRA.
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title
Thomas Patzig edited a comment on JENKINS-61693
Re: using git multi branch pipeline through proxy leads to fatal: unable to access
..have try jenkins.war from PR 4607 it works... have also found a mistake on my sideI automize the Jenkins installation and bootstrap config to check latest versions... for that I do some http posts like the user would do... for setup the proxy I have use "post descriptorByName/hudson.ProxyConfiguration/validateProxy" with body form url encoded content and the content "password" instead of "secretPassword"...(same on http post pluginManager/proxyConfigure) I think "password" is no longer supported in that post. Am I right? with fix on my side ("secretPassword" instead of "password") it works fine.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205518.1585229665000.1885.1585417080334%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title
Thomas Patzig commented on JENKINS-61692
Re: "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
..have try jenkins.war from PR 4607 it works... have also found a mistake on my side I automize the Jenkins installation and bootstrap config to check latest versions... for that I do some http posts like the user would do... for setup the proxy I have use "post descriptorByName/hudson.ProxyConfiguration/validateProxy" with body form url encoded content and the content "password" instead of "secretPassword"... (same on http post pluginManager/proxyConfigure) I think "password" is no longer supported in that post. Am I right? (..and that were the Links before) with fix on my side ("secretPassword" instead of "password") it works fine.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205516.1585227401000.1884.1585417080320%40Atlassian.JIRA.
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title Mark Waite commented on JENKINS-61693 Re: using git multi branch pipeline through proxy leads to fatal: unable to access Thanks very much for verifying. That is great news. Yes, as far as I understand it, the field has changed from password to secretPassword in the form. Tim Jacomb can correct me if I've stated that incorrectly. The fix will be in the next weekly. Thanks for reporting it and for verifying that the fix works. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205518.1585229665000.1890.1585418460168%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title
Daniel Beck commented on JENKINS-61692
Re: "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
I think "password" is no longer supported in that post. Am I right? (..and that were the Links before)
with fix on my side ("secretPassword" instead of "password") it works fine.
That's correct; you're effectively saving the configuration without password when using the obsolete name.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205516.1585227401000.1894.1585419360221%40Atlassian.JIRA.
[JIRA] (JENKINS-61693) using git multi branch pipeline through proxy leads to fatal: unable to access
Title: Message Title Daniel Beck closed an issue as Not A Defect Caused by bad automation. Jenkins / JENKINS-61693 using git multi branch pipeline through proxy leads to fatal: unable to access Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web
[JIRA] (JENKINS-58753) Add proxy support for the zoom plugin
Title: Message Title Jorge Yanes updated an issue Jenkins / JENKINS-58753 Add proxy support for the zoom plugin Change By: Jorge Yanes Attachment: image-2020-03-28-19-17-24-692.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201056.1564651831000.1901.1585419480608%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title Daniel Beck updated JENKINS-61692 Jenkins / JENKINS-61692 "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException Change By: Daniel Beck Status: In Review Fixed but Unreleased Resolution: Fixed Released As: Jenkins 2.229 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205516.1585227401000.1908.1585419480708%40Atlassian.JIRA.
[JIRA] (JENKINS-58753) Add proxy support for the zoom plugin
Title: Message Title Jorge Yanes updated an issue Jenkins / JENKINS-58753 Add proxy support for the zoom plugin Change By: Jorge Yanes Attachment: image-2020-03-28-19-19-54-086.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201056.1564651831000.1920.1585419600954%40Atlassian.JIRA.
[JIRA] (JENKINS-61688) Global build discarders configuration isn't loaded from disk
Title: Message Title Daniel Beck updated JENKINS-61688 Jenkins / JENKINS-61688 Global build discarders configuration isn't loaded from disk Change By: Daniel Beck Status: In Review Fixed but Unreleased Resolution: Fixed Released As: Jenkins 2.229 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205511.1585182181000.1917.1585419600920%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-61692 "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException Change By: Daniel Beck Labels: lts-candidate regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205516.1585227401000.1911.1585419600819%40Atlassian.JIRA.
[JIRA] (JENKINS-58753) Add proxy support for the zoom plugin
Title: Message Title Jorge Yanes commented on JENKINS-58753 Re: Add proxy support for the zoom plugin Done! https://github.com/jenkinsci/zoom-plugin/pull/4 It is working for me, I hope they merge it Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201056.1564651831000.1926.1585419660215%40Atlassian.JIRA.
[JIRA] (JENKINS-58753) Add proxy support for the zoom plugin
Title: Message Title Jorge Yanes updated an issue Jenkins / JENKINS-58753 Add proxy support for the zoom plugin Change By: Jorge Yanes Attachment: image-2020-03-28-19-17-24-692.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201056.1564651831000.1932.1585419720280%40Atlassian.JIRA.
[JIRA] (JENKINS-61728) Broken search bar layout when using new UI components
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-61728 Broken search bar layout when using new UI components Issue Type: Bug Assignee: Ulli Hafner Attachments: Broken-Search.png Components: autograding-plugin, core, forensics-api-plugin, warnings-ng-plugin Created: 2020-03-28 19:04 Labels: UX ux-sig Priority: Minor Reporter: Ulli Hafner In Jenkins 2.222.1 a new header bar has been introduced. Seems that one of the libraries (or CSS files) that I am using in my plugins destroyed the search bar layout, see screenshot. Add Comment
[JIRA] (JENKINS-61728) Broken search bar layout when using new UI components
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-61728 Broken search bar layout when using new UI components Change By: Ulli Hafner In Jenkins 2.222.1 a new header bar has been introduced. Seems that one of the libraries (or CSS files) that I am using in my plugins destroyed the search bar layout, see screenshot. I still need to find out, which of the UI plugins cause these problems... Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205556.1585422294000.1937.1585422480066%40Atlassian.JIRA.
[JIRA] (JENKINS-58753) Add proxy support for the zoom plugin
Title: Message Title Jorge Yanes edited a comment on JENKINS-58753 Re: Add proxy support for the zoom plugin Done! [https://github.com/jenkinsci/zoom-plugin/pull/4]It is working for me, I hope they merge it ;) !image-2020-03-28-19-19-54-086.png! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201056.1564651831000.1940.1585423140238%40Atlassian.JIRA.
[JIRA] (JENKINS-61728) Broken search bar layout when using new UI components
Title: Message Title Daniel Beck commented on JENKINS-61728 Re: Broken search bar layout when using new UI components Could you clarify whether this is only in the UI refresh, or without? Screenshot shows the former, which is opt in via system property. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205556.1585422294000.1945.1585426680202%40Atlassian.JIRA.
[JIRA] (JENKINS-61696) Replace "top page"
Title: Message Title Daniel Beck commented on JENKINS-61696 Re: Replace "top page" The trivial fix is to call it "Dashboard" as everywhere else. The nontrivial fix would be to think of a new term and apply that consistently, IMO Dashboard View Plugin makes "Dashboard" for the regular index page ambiguous. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205521.1585235311000.1947.1585426740137%40Atlassian.JIRA.
[JIRA] (JENKINS-52939) Need to lint pipeline from UI, and also parse parameters
Title: Message Title Craig Rodrigues commented on JENKINS-52939 Re: Need to lint pipeline from UI, and also parse parameters When I originally filed this ticket, I thought Blue Ocean was the future direction of Jenkins. However, if you can expose a link on the classic UI, where I can just click it and it will run the linter on the pipeline in the current job, whether it is a Pipeline from SCM, or just a Pipeline, that would be a huge usability improvement. Liam Newman thanks! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192911.153375138.1949.1585430460336%40Atlassian.JIRA.
[JIRA] (JENKINS-52939) Need to lint pipeline from UI, and also parse parameters
Title: Message Title Craig Rodrigues edited a comment on JENKINS-52939 Re: Need to lint pipeline from UI, and also parse parameters When I originally filed this ticket, I thought Blue Ocean was the future direction of Jenkins.However, if you can expose a link on the classic UI, where I can just click it and it will run the linter on thepipeline in the current job, whether it is a Pipeline from SCM, or just a Pipeline,that would be a huge usability improvement. [~bitwiseman] thanks! The existing way of invoking the linter is convoluted and confusing!I can't be bothered to figure out how to do it, and neither can most users of Pipeline. Make it easier! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192911.153375138.1957.1585430520322%40Atlassian.JIRA.
[JIRA] (JENKINS-60342) Include support to BitBucket Pull Request
Title: Message Title Omer Kattan commented on JENKINS-60342 Re: Include support to BitBucket Pull Request +1 for this feature from me aswell. For my team, this plugin is not usable without it (and i really want us to use it). Our pipeline takes a lot of time to run, and we can't afford to run it for every push. The ability to run it only for pull requests (opened and updated at least) is critical. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203356.157528517.1965.1585432200382%40Atlassian.JIRA.
[JIRA] (JENKINS-61728) Broken search bar layout when using new UI components
Title: Message Title Ulli Hafner commented on JENKINS-61728 Re: Broken search bar layout when using new UI components Interesting, the problem is also visible with the old UI. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205556.1585422294000.1979.1585435080298%40Atlassian.JIRA.
[JIRA] (JENKINS-61728) Broken search bar layout when using new UI components
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-61728 Broken search bar layout when using new UI components Change By: Ulli Hafner Attachment: Broken-Search-Old.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205556.1585422294000.1981.1585435140158%40Atlassian.JIRA.
[JIRA] (JENKINS-61729) Reload Configuration from Disk does not work
Title: Message Title Christoph Vogtländer created an issue Jenkins / JENKINS-61729 Reload Configuration from Disk does not work Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-03-28 22:48 Environment: Jenkins 2.204.5 Priority: Major Reporter: Christoph Vogtländer Using "Manage" -> "Reload Configuration from Disk" does not reload the Repository URL configured for a Pipeline script from SCM when using Subversion. E.g., after changing "https://server/svn/JenkinsWorkflow/oldLib/trunk" to "https://server/svn/JenkinsWorkflow/newLib/trunk" in config.xml on disk and then using "Reload Configuration from Disk" the job configuration is still using "oldLib" (after Jenkins stated for a while that it is reloading the configuration). The old path is still shown at the configure page of the job and when running a build it tries to load the Jenkinsfile from the old path. The build will fail with (in my case the lib has been renamed, "oldLib" does not exist anymore) org.tmatesoft.svn.core.SVNException: svn: E160013: '/svn/JenkinsWorkflow/!svn/bc/1193/oldLib/trunk/JenkinsfileCI' path not found: 404 Not Found (https://server) Restarting Jenkins solves the problem. Changed parts in config.xml: "org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition" plugin="workflow-cps@2.74"> "hud
[JIRA] (JENKINS-61728) Broken search bar layout when using new UI components
Title: Message Title Ulli Hafner commented on JENKINS-61728 Re: Broken search bar layout when using new UI components Seems that we did upgrade our Jenkins as well. Here one can see the bug as well: https://ci.jenkins.io/job/Plugins/job/analysis-model/job/PR-324/3/spotbugs/ Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205556.1585422294000.1984.1585440360123%40Atlassian.JIRA.
[JIRA] (JENKINS-61728) Broken search bar layout when using new UI components
Title: Message Title Ulli Hafner edited a comment on JENKINS-61728 Re: Broken search bar layout when using new UI components Seems that we did upgrade our Jenkins as well. Here one can see the bug as well: https://ci.jenkins.io/job/Plugins/job/analysis-model/job/ PR-324 master / 3 java / spotbugs/ Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205556.1585422294000.1986.1585440720123%40Atlassian.JIRA.
[JIRA] (JENKINS-60342) Include support to BitBucket Pull Request
Title: Message Title Omer Kattan commented on JENKINS-60342 Re: Include support to BitBucket Pull Request Another thought, while i know this is better implemented on bitbucket's side, there is no webhook for when commits are added to an existing PR. A cool thing to check if there is an open PR when handling a push webhook request. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203356.157528517.1988.1585444380367%40Atlassian.JIRA.
