[JIRA] (JENKINS-58539) Tool always exits with value of 1
Title: Message Title Natasha Stopa created an issue Jenkins / JENKINS-58539 Tool always exits with value of 1 Issue Type: Task Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-07-18 05:32 Labels: gsoc-2019 plugin-manager Priority: Minor Reporter: Natasha Stopa The tool checks the if there are failed plugins, but instead of conditionally exiting with a value of 1, it always exits with a value of 1. It should exit with a value of zero if there are no failed plugins. Add Comment
[JIRA] (JENKINS-58539) Tool always exits with value of 1
Title: Message Title Natasha Stopa started work on JENKINS-58539 Change By: Natasha Stopa Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200688.1563427958000.14998.1563427980584%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57251) pipeline shell expect : No such property... for class: groovy.lang.Binding
Title: Message Title g5nius x commented on JENKINS-57251 Re: pipeline shell expect : No such property... for class: groovy.lang.Binding hi are you resolve it? i alse have this problem。 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199015.155662710.14996.1563426120139%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58531) New GitLab Group w/ SSH key can't check out repos
Title: Message Title Parichay Barpanda updated JENKINS-58531 Jenkins / JENKINS-58531 New GitLab Group w/ SSH key can't check out repos Change By: Parichay Barpanda Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200680.1563375308000.14994.1563426060320%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58157) "delete build" button is to long
Title: Message Title Aakash Kanvinde assigned an issue to Aakash Kanvinde Jenkins / JENKINS-58157 "delete build" button is to long Change By: Aakash Kanvinde Assignee: Aakash Kanvinde Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200205.1561341295000.14991.1563423960140%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58355) Fix GitLab Avatar Cache
Title: Message Title Parichay Barpanda commented on JENKINS-58355 Re: Fix GitLab Avatar Cache Removed avatar cache for now. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200470.1562321144000.14987.1563423900194%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58355) Fix GitLab Avatar Cache
Title: Message Title Parichay Barpanda started work on JENKINS-58355 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200470.1562321144000.14988.1563423900253%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58355) Fix GitLab Avatar Cache
Title: Message Title Parichay Barpanda resolved as Fixed Jenkins / JENKINS-58355 Fix GitLab Avatar Cache Change By: Parichay Barpanda Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200470.1562321144000.14989.1563423900262%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58477) No automatic builds for tags
Title: Message Title Parichay Barpanda edited a comment on JENKINS-58477 Re: No automatic builds for tags Tags are not built by default. See Stephen's comment in the related issue . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200613.1562949475000.14986.1563423840100%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58477) No automatic builds for tags
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-58477 No automatic builds for tags Change By: Parichay Barpanda Priority: Blocker Minor Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200613.1562949475000.14985.1563423780174%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58477) No automatic builds for tags
Title: Message Title Parichay Barpanda commented on JENKINS-58477 Re: No automatic builds for tags We can implement a build strategy to automatically built tags. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200613.1562949475000.14984.1563423780145%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58477) No automatic builds for tags
Title: Message Title Parichay Barpanda commented on JENKINS-58477 Re: No automatic builds for tags Tags are not built by default. See Stephen's comment. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200613.1562949475000.14983.1563423720045%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58506) Redirect to root url determined from request
Title: Message Title Vincent Latombe edited a comment on JENKINS-58506 Re: Redirect to root url determined from request Hi [~michaelrush], your reverse proxy must be properly configured. See [Running Jenkins behind Apache| [ https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+Apache] ] . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200649.1563261173000.14981.1563422880269%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58506) Redirect to root url determined from request
Title: Message Title Vincent Latombe commented on JENKINS-58506 Re: Redirect to root url determined from request Hi Michael Rush, your reverse proxy must be properly configured. See [Running Jenkins behind Apache|https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+Apache]. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200649.1563261173000.14979.1563422880203%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58506) Redirect to root url determined from request
Title: Message Title Vincent Latombe updated JENKINS-58506 Jenkins / JENKINS-58506 Redirect to root url determined from request Change By: Vincent Latombe Status: Fixed but Unreleased Resolved Released As: 1.5 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200649.1563261173000.14975.1563422760273%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58336) ERROR: Exception reading response javax.mail.MessagingException: Exception reading response
Title: Message Title yang zz closed an issue as Not A Defect caused by my network security firewall Jenkins / JENKINS-58336 ERROR: Exception reading response javax.mail.MessagingException: Exception reading response Change By: yang zz Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200448.1562224624000.14973.1563421860217%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58336) ERROR: Exception reading response javax.mail.MessagingException: Exception reading response
Title: Message Title yang zz commented on JENKINS-58336 Re: ERROR: Exception reading response javax.mail.MessagingException: Exception reading response the problem is solved ,Which is caused by the network security firewall。tks Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200448.1562224624000.14971.1563421740170%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58536) Remove dependency on jquery-ui
Title: Message Title Michael Düsterhus commented on JENKINS-58536 Re: Remove dependency on jquery-ui Yes the transitive dependencies, especially the implied ones are really annoying when trying to cleanup the list of needed plugins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200685.1563397489000.14969.1563416700146%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47461) Null pointer exception in h.p.emailext.plugins.ContentBuilder
Title: Message Title Owen Mehegan closed an issue as Cannot Reproduce I no longer work at the company where I saw this issue. Jenkins / JENKINS-47461 Null pointer exception in h.p.emailext.plugins.ContentBuilder Change By: Owen Mehegan Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185909.1508194573000.14950.1563412980431%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58538) Support for relative paths in folder view
Title: Message Title Andrew Barnish updated an issue Jenkins / JENKINS-58538 Support for relative paths in folder view Change By: Andrew Barnish In the legacy version of the warnings plugin the directories were displayed with path relative to the SCM workspace root when the "folders" tab was selected. This made a lot more sense than the current warnings-ng behavior which displays the full absolute path to the folder directory .Please change the back to the old behavior or add a new option to enable to old behavior.!https://wiki.jenkins.io/download/attachments/25591835/image2019-2-12_11-51-24.png?version=1&modificationDate=1549968686000&api=v2! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200687.1563409751000.14941.1563409860144%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58538) Support for relative paths in folder view
Title: Message Title Andrew Barnish created an issue Jenkins / JENKINS-58538 Support for relative paths in folder view Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-07-18 00:29 Priority: Minor Reporter: Andrew Barnish In the legacy version of the warnings plugin the directories were displayed with path relative to the SCM workspace root when the "folders" tab was selected. This made a lot more sense than the current warnings-ng behavior which displays the full absolute path to the folder. Please change the back to the old behavior or add a new option to enable to old behavior. Add Comment
[JIRA] (JENKINS-56508) Service account secret not visible when using folders plugin
Title: Message Title Lu Shen commented on JENKINS-56508 Re: Service account secret not visible when using folders plugin No even if I log in as a Jenkins admin, I don't see the credential in the drop down. It is simply not available. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198115.1552334901000.14937.1563409200144%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58537) Plugin Version Must Be Exact
Title: Message Title Natasha Stopa created an issue Jenkins / JENKINS-58537 Plugin Version Must Be Exact Issue Type: Task Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-07-17 23:32 Labels: gsoc-2019 plugin-manager Priority: Minor Reporter: Natasha Stopa I noticed when I was doing some testing that if you specify the blue ocean plugin, version 1.8, the library won't be able to find the url since it is 1.8.0. https://updates.jenkins.io/download/plugins/blueocean/ Add Comment
[JIRA] (JENKINS-58535) Fix redundant api calls and other fixes
Title: Message Title Joseph Petersen updated an issue Jenkins / JENKINS-58535 Fix redundant api calls and other fixes Change By: Joseph Petersen Based on discussion in gitter chat. https://gitter.im/jenkinsci/gitlab-branch-source-plugin?at=5d2f7bbeacfb784293604ba2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200684.1563394593000.14933.1563402240220%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58373) Restore "all" gates to version 5
Title: Message Title Steve Springett assigned an issue to Steve Springett Jenkins / JENKINS-58373 Restore "all" gates to version 5 Change By: Steve Springett Assignee: Steve Springett Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200494.1562587793000.14931.1563402000126%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title Matthew Mallard commented on JENKINS-28447 Re: CpsScmFlowDefinition does not resolve variables Has this "separate feature" been added yet to the "lightweight checkout" functionality? In my case, I have a pipeline job that is parameterized. One of the parameters is the branch name which I intend to use later on in the job when selecting the definition "Pipeline script from SCM". When selecting that you have the option to select your Git repository and Branches to build, but it doesn't recognize the parameter when "Lightweight checkout" is selected. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162884.1431919551000.14866.1563400981215%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56117) SCP Style Git URI on Pipeline Library breaks Plugin
Title: Message Title Dicom J commented on JENKINS-56117 Re: SCP Style Git URI on Pipeline Library breaks Plugin This happens because git scp-like syntax for "URL" (which technically and according to specification it not an URL, Torvalds simply confused stuff, as man packages for scp never even mention URL word) is not compatible with URI syntax, so it's not safe to just blindly wrap that string into java.net.URI, as again it could be either git scp-like "URL" (scp path) or true URL, which are incompatible cases and java.net.URI strictly follows just URI spec and so it fails for "git scp-like "URLs" (scp pathes)" Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197552.1550038396000.14863.1563400920196%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58340) docker-plugin-1.1.6 docker cloud does not work with >=ssh-slaves-plugin-1.30.0
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-58340 Re: docker-plugin-1.1.6 docker cloud does not work with >=ssh-slaves-plugin-1.30.0 I've changed the implementation of checkconfig to work with SSHLauncher classes that do not have the correct type of descriptor. I'll release a new version this weekend. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200453.1562229896000.14855.1563400800191%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58391) Allow customisation of distribution group by name
Title: Message Title Mez Pahlan updated JENKINS-58391 Jenkins / JENKINS-58391 Allow customisation of distribution group by name Change By: Mez Pahlan Status: Fixed but Unreleased Closed Released As: 0.2.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200515.1562609321000.14852.1563399900131%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58521) Refactor application structure
Title: Message Title Mez Pahlan updated JENKINS-58521 Jenkins / JENKINS-58521 Refactor application structure Change By: Mez Pahlan Status: Fixed but Unreleased Closed Released As: 0.2.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200665.1563299845000.14853.1563399900176%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58340) docker-plugin-1.1.6 docker cloud does not work with >=ssh-slaves-plugin-1.30.0
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-58340 Re: docker-plugin-1.1.6 docker cloud does not work with >=ssh-slaves-plugin-1.30.0 I've changed the implementation of checkconfig to work with SSHLauncher classes that do not have the correct type of descriptor. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200453.1562229896000.14847.1563399840372%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58521) Refactor application structure
Title: Message Title Mez Pahlan updated JENKINS-58521 Jenkins / JENKINS-58521 Refactor application structure Change By: Mez Pahlan Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200665.1563299845000.14845.1563399840218%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58521) Refactor application structure
Title: Message Title Mez Pahlan updated JENKINS-58521 Jenkins / JENKINS-58521 Refactor application structure Change By: Mez Pahlan Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200665.1563299845000.14844.1563399780082%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58340) docker-plugin-1.1.6 docker cloud does not work with >=ssh-slaves-plugin-1.30.0
Title: Message Title Ivan Fernandez Calvo updated JENKINS-58340 Jenkins / JENKINS-58340 docker-plugin-1.1.6 docker cloud does not work with >=ssh-slaves-plugin-1.30.0 Change By: Ivan Fernandez Calvo Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200453.1562229896000.14839.1563399721357%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58340) docker-plugin-1.1.6 docker cloud does not work with >=ssh-slaves-plugin-1.30.0
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-58340 docker-plugin-1.1.6 docker cloud does not work with >=ssh-slaves-plugin-1.30.0 Change By: Ivan Fernandez Calvo Assignee: Nicolas De Loof Ivan Fernandez Calvo Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200453.1562229896000.14827.1563399721093%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58340) docker-plugin-1.1.6 docker cloud does not work with >=ssh-slaves-plugin-1.30.0
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-58340 Change By: Ivan Fernandez Calvo Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200453.1562229896000.14837.1563399721331%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58079) Update README add link to issue tracker
Title: Message Title Mez Pahlan closed an issue as Fixed Jenkins / JENKINS-58079 Update README add link to issue tracker Change By: Mez Pahlan Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200104.1560877907000.14824.1563399600161%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58080) Update README add link to AppCenter
Title: Message Title Mez Pahlan closed an issue as Fixed Jenkins / JENKINS-58080 Update README add link to AppCenter Change By: Mez Pahlan Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200105.156087914.14823.1563399600131%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58080) Update README add link to AppCenter
Title: Message Title Mez Pahlan updated JENKINS-58080 Jenkins / JENKINS-58080 Update README add link to AppCenter Change By: Mez Pahlan Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200105.156087914.14821.1563399540149%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58079) Update README add link to issue tracker
Title: Message Title Mez Pahlan updated JENKINS-58079 Jenkins / JENKINS-58079 Update README add link to issue tracker Change By: Mez Pahlan Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200104.1560877907000.14822.1563399540205%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58536) Remove dependency on jquery-ui
Title: Message Title Reed Palmer updated an issue Jenkins / JENKINS-58536 Remove dependency on jquery-ui Change By: Reed Palmer Role strategy plugin has a dependency on the jquery-ui plugin which has been deprecated in favor of the jquery plugin (which role-strategy already has a dependency on). jquery-ui plugin hasn't been pushed in 8 years and brings in many implied and un-needed dependencies, some of which have security vulnerabilities.All existing dependencies on the jquery-ui plugin should be reimplemented using the jquery plugin and the dependency on jquery-ui plugin should be removed.[ [ https://plugins.jenkins.io/jquery| | https://plugins.jenkins.io/jquery-ui] [https://plugins.jenkins.io/jquery|https://plugins.jenkins.io/jquery-ui] []|https://plugins.jenkins.io/jquery-ui] [ [ https://plugins.jenkins.io/jquery ||https://plugins.jenkins.io/jquery -ui] [https://plugins.jenkins.io/jquery|https://plugins.jenkins.io/jquery-ui] []|https://plugins.jenkins.io/jquery-ui] [ [ https://plugins.jenkins.io/role-strategy ||https://plugins.jenkins.io/jquery-ui ] [https://plugins.jenkins.io/|https://plugins.jenkins.io/jquery-ui] [role-strategy|https://plugins.jenkins.io/jquery-ui] [|https://plugins.jenkins.io/jquery-ui] []|https://plugins.jenkins.io/jquery-ui] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you
[JIRA] (JENKINS-58391) Allow customisation of distribution group by name
Title: Message Title Mez Pahlan commented on JENKINS-58391 Re: Allow customisation of distribution group by name https://github.com/jenkinsci/appcenter-plugin/pull/10 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200515.1562609321000.14811.1563397620168%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58536) Remove dependency on jquery-ui
Title: Message Title Reed Palmer updated an issue Jenkins / JENKINS-58536 Remove dependency on jquery-ui Change By: Reed Palmer Role strategy plugin has a dependency on the jquery-ui plugin which has been deprecated in favor of the jquery plugin (which role-strategy already has a dependency on). jquery-ui plugin hasn't been pushed in 8 years and brings in many implied and un-needed dependencies, some of which have security vulnerabilities.All existing dependencies on the jquery-ui plugin should be reimplemented using the jquery plugin and the dependency on jquery-ui plugin should be removed.[ [ https://plugins.jenkins.io/jquery| | https://plugins.jenkins.io/jquery-ui] [https://plugins.jenkins.io/jquery |https://plugins.jenkins.io/jquery -ui ] [] |https://plugins.jenkins.io/jquery-ui ] [[ https://plugins.jenkins.io/jquery | | https://plugins.jenkins.io/ jquery-ui] [https://plugins.jenkins.io/jquery|https://plugins.jenkins.io/jquery-ui] []|https://plugins.jenkins.io/jquery-ui][[https://plugins.jenkins.io/ role-strategy ||https://plugins.jenkins.io/jquery-ui ] [https://plugins.jenkins.io/ |https://plugins.jenkins.io/ jquery-ui] [ role-strategy |https://plugins.jenkins.io/jquery-ui ] [|https://plugins.jenkins.io/jquery-ui] []|https://plugins.jenkins.io/jquery-ui] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message
[JIRA] (JENKINS-58536) Remove dependency on jquery-ui
Title: Message Title Reed Palmer updated an issue Jenkins / JENKINS-58536 Remove dependency on jquery-ui Change By: Reed Palmer Role strategy plugin has a dependency on the jquery-ui plugin which has been deprecated in favor of the jquery plugin (which role-strategy already has a dependency on). jquery-ui plugin hasn't been pushed in 8 years and brings in many implied and un-needed dependencies, some of which have security vulnerabilities.All existing dependencies on the jquery-ui plugin should be reimplemented using the jquery plugin and the dependency on jquery-ui plugin should be removed.[https://plugins.jenkins.io/jquery|https://plugins.jenkins.io/jquery-ui][https://plugins.jenkins.io/jquery-ui |https://plugins.jenkins.io/jquery-ui [[| https://plugins.jenkins.io/role-strategy ] |https://plugins.jenkins.io/ jquery role - ui strategy ] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200685.1563397489000.14808.1563397560142%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58536) Remove dependency on jquery-ui
Title: Message Title Reed Palmer created an issue Jenkins / JENKINS-58536 Remove dependency on jquery-ui Issue Type: Improvement Assignee: Oleg Nenashev Components: role-strategy-plugin Created: 2019-07-17 21:04 Environment: jenkins:2.176.2 (lts) role-strategy:2.13 (latest) Priority: Trivial Reporter: Reed Palmer Role strategy plugin has a dependency on the jquery-ui plugin which has been deprecated in favor of the jquery plugin (which role-strategy already has a dependency on). jquery-ui plugin hasn't been pushed in 8 years and brings in many implied and un-needed dependencies, some of which have security vulnerabilities. All existing dependencies on the jquery-ui plugin should be reimplemented using the jquery plugin and the dependency on jquery-ui plugin should be removed. https://plugins.jenkins.io/jquery [https://plugins.jenkins.io/jquery-ui https://plugins.jenkins.io/role-strategy|https://plugins.jenkins.io/jquery-ui] Add Comment
[JIRA] (JENKINS-58522) Support multiple distribution groups
Title: Message Title Mez Pahlan closed an issue as Won't Do "Accidentally" completed under JENKINS-58521 Jenkins / JENKINS-58522 Support multiple distribution groups Change By: Mez Pahlan Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200666.1563299962000.14804.1563397020229%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56255) occasionally builds the branch for a PR also
Title: Message Title Brian J Murrell commented on JENKINS-56255 Re: occasionally builds the branch for a PR also But having to do branch filtering does not embrace the principle of least surprise. I am sure most people will find it surprising that the branch/PR race design is not more robust and that they have to employ branch filtering to augment it. On the other hand, I think a configuration item, right next to (or below) the selector for whether you want to build branches that are not PRs – for how long to delay a first-time branch build to decide if it's going to become a PR is really straightforward. I think most people would understand that delay is how Jenkins decides if branches are going to become PRs. Not having anything at all leaves people to not even consider the design problem and assuming that Jenkins will then just figure it out. And then it doesn't. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197825.1550941413000.14803.1563396720179%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46441) After moving the job to a folder, the editor link is not available anymore
Title: Message Title Jim Yanko commented on JENKINS-46441 Re: After moving the job to a folder, the editor link is not available anymore I have run into this same issue today. Observations... When job catbox is at the root of jobs, the edit option is available. If I move the job within a folder, to SRE/catbox , then the edit option disappears If I move the catbox job back to the root list of jobs, the edit option re-appears My Env... A multibranch pipeline, catbox, ** pointing to a git repo at github auth via ssh key CloudBees Jenkins 2.176.1.4 BlueOcean 1.10.2 Screenshots... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184711.1503631317000.14799.1563396120160%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56255) occasionally builds the branch for a PR also
Title: Message Title Liam Newman commented on JENKINS-56255 Re: occasionally builds the branch for a PR also Brian J Murrell Hey, thanks for testing that alternative. And yes, I totally agree branch-in-organization is a totally a valid workflow, in which case the branch filtering work-around is the way to go. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197825.1550941413000.14793.1563395940332%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46441) After moving the job to a folder, the editor link is not available anymore
Title: Message Title Jim Yanko updated an issue Jenkins / JENKINS-46441 After moving the job to a folder, the editor link is not available anymore Change By: Jim Yanko Attachment: image-2019-07-17-13-38-43-045.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184711.1503631317000.14797.1563395940559%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46441) After moving the job to a folder, the editor link is not available anymore
Title: Message Title Jim Yanko updated an issue Jenkins / JENKINS-46441 After moving the job to a folder, the editor link is not available anymore Change By: Jim Yanko Attachment: image-2019-07-17-13-37-33-475.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184711.1503631317000.14791.1563395880703%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56255) occasionally builds the branch for a PR also
Title: Message Title Liam Newman edited a comment on JENKINS-56255 Re: occasionally builds the branch for a PR also [~brianjmurrell]It sounds like you're getting frustrated with my responses. I want to be clear that I am not trying to block you, I am trying to help.I want to make sure you (and anyone else encountering this issue) have a reasonable work-around. It sound like we've achieved that using branch filtering - either by script added to the pipeline or by branch filter setting added to the job configuration. The more involved work-around is to move to the more mainstream pattern of doing PRs from forks (and using "Ignore change requests flagged as originating from an untrusted source" if you need to prevent building of PRs from any rando forks).I'm not blocking anyone from implementing a fix for this. I'd like that fix to make sense and be useful, so I'm asking questions about what it should look like. I apologize if that came off as too skeptical or pessimistic. Let me try again.The fix you proposed in seems like a reasonable improvement, which also has some limitations. I'd like to make sure that when someone goes to implement this they understand those limitations as part of the proposed behavior. I'm one of several regular contributors to this plugin but to my knowledge most us are already at full capacity currently. Perhaps you or someone from your organization could implement this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197825.1550941413000.14787.1563395640133%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52742) jira-trigger-plugin not supported using jenkinsfile
Title: Message Title Wisen Tanasa commented on JENKINS-52742 Re: jira-trigger-plugin not supported using jenkinsfile Hi shagun jian, thanks for raising this issue. Unfortunately this is not supported at the moment. The project is open sourced, your contribution is welcomed to the plug-in to support this feature. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192635.153252705.14785.1563394800087%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58531) New GitLab Group w/ SSH key can't check out repos
Title: Message Title Parichay Barpanda started work on JENKINS-58531 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200680.1563375308000.14782.1563394740230%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58446) Fix log in GitLabSCMNavigator
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-58446 Fix log in GitLabSCMNavigator Change By: Parichay Barpanda Summary: Implement visit source and fix Fix log in GitLabSCMNavigator Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200578.1562856443000.14783.1563394740280%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58531) New GitLab Group w/ SSH key can't check out repos
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-58531 New GitLab Group w/ SSH key can't check out repos Change By: Parichay Barpanda Sprint: GSoC 2019. Coding Phase 2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200680.1563375308000.14780.1563394680281%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58531) New GitLab Group w/ SSH key can't check out repos
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-58531 New GitLab Group w/ SSH key can't check out repos Change By: Parichay Barpanda Labels: gsoc-2019 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200680.1563375308000.14778.1563394680249%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58535) Fix redundant api calls and other fixes
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-58535 Fix redundant api calls and other fixes Issue Type: Bug Assignee: Joseph Petersen Components: gitlab-branch-source-plugin Created: 2019-07-17 20:16 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda Based on discussion in gitter chat. Add Comment
[JIRA] (JENKINS-56508) Service account secret not visible when using folders plugin
Title: Message Title Christopher Orr commented on JENKINS-56508 Re: Service account secret not visible when using folders plugin Are you able to see the credentials if you're an admin user? From a very quick look at the code, it seems like we're just delegating to the Google OAuth Plugin, calling getCredentialsListBox: https://github.com/jenkinsci/google-play-android-publisher-plugin/blob/google-play-android-publisher-1.8/src/main/java/org/jenkinsci/plugins/googleplayandroidpublisher/GooglePlayBuildStepDescriptor.java#L37-L40 That plugin just appears to be fetching all available credentials in the system, rather than anything scoped by folder: https://github.com/jenkinsci/google-oauth-plugin/blob/google-oauth-plugin-0.8/src/main/java/com/google/jenkins/plugins/credentials/oauth/GoogleRobotCredentials.java#L133-L155 So I'm not sure where the problem lies, at the moment… Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198115.1552334901000.14774.1563393300144%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58497) Jenkins picks a random agent if agent is 'null'
Title: Message Title
hemil patel commented on JENKINS-58497
Re: Jenkins picks a random agent if agent is 'null'
Hmm, If this is as designed, I can see this being potentially destructive. For eg.
pipeline {
agent none
stages {
stage ('This stage should not run anywhere.') {
agent {
label env.NODE_THAT_DOES_NOT_EXIST
}
steps {
echo "Agent is : " + env.NODE_THAT_DOES_NOT_EXIST
echo 'Do a destructive action'
killServer()
}
}
}
}
def killServer() {
//kill server code here
}
For such a small mistake, user should not have to suffer potentially catastrophic damage.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200636.1563204753000.14771.1563393180226%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58415) Google Play Android Publisher Plugin - folder level credential setup not working
Title: Message Title Christopher Orr closed an issue as Duplicate Jenkins / JENKINS-58415 Google Play Android Publisher Plugin - folder level credential setup not working Change By: Christopher Orr Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200542.1562706593000.14768.1563392760312%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49789) NPE when attempting to parse exception
Title: Message Title Christopher Orr closed an issue as Done Jenkins / JENKINS-49789 NPE when attempting to parse exception Change By: Christopher Orr Status: Reopened Closed Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188739.1519809631000.14762.1563392700377%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56855) MessagingException message: IOException while sending message
Title: Message Title Garrett Nickerson updated JENKINS-56855 Jenkins / JENKINS-56855 MessagingException message: IOException while sending message Change By: Garrett Nickerson Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198515.1554219263000.14756.1563390780775%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56855) MessagingException message: IOException while sending message
Title: Message Title Garrett Nickerson commented on JENKINS-56855 Re: MessagingException message: IOException while sending message Thanks for your response. We actually stopped seeing the issue after upgrading all of our components. I did not see any relevant information in the release notes for the upgraded version. Our working system has these components (among others) Jenkins Version: 2.164.2 email-ext-plugin version: 2.66 java.version: 1.8.0_144 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198515.1554219263000.14752.1563390780701%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56855) MessagingException message: IOException while sending message
Title: Message Title Garrett Nickerson updated JENKINS-56855 Jenkins / JENKINS-56855 MessagingException message: IOException while sending message Change By: Garrett Nickerson Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198515.1554219263000.14758.1563390780807%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58506) Redirect to root url determined from request
Title: Message Title Michael Rush commented on JENKINS-58506 Re: Redirect to root url determined from request This doesn't work in a proxied setup, where a web server such as Apache is only accepting https requests that a proxied to Jenkins. Jenkins is sending Google a http redirect URL which isn't registered in the OAuth client. Adding the http URL to the Google OAuth client doesn't work either since http isn't not accepted on the originating server. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200649.1563261173000.14748.1563389520350%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52359) Cannot use custom CA Cert with vault plugin
Title: Message Title suryatej yaramada commented on JENKINS-52359 Re: Cannot use custom CA Cert with vault plugin Any update on this issue as we are also facing a similar problem Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192149.1530653617000.14734.1563388920306%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47773) email-ext cannot expand ${FAVORITE_USERS_EMAIL} macro in pipeline
Title: Message Title
Alex Earl commented on JENKINS-47773
Re: email-ext cannot expand ${FAVORITE_USERS_EMAIL} macro in pipeline
See https://github.com/jenkinsci/email-ext-plugin/blob/master/src/main/java/hudson/plugins/emailext/plugins/content/FailedTestsContent.java#L46-L96 for an example of how to allow the token to work in pipeline jobs.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186268.1509557824000.14725.1563388260270%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47773) email-ext cannot expand ${FAVORITE_USERS_EMAIL} macro in pipeline
Title: Message Title
Alex Earl assigned an issue to James Dumay
Jenkins / JENKINS-47773
email-ext cannot expand ${FAVORITE_USERS_EMAIL} macro in pipeline
Change By:
Alex Earl
Assignee:
Alex Earl James Dumay
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186268.1509557824000.14716.1563388141319%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47773) email-ext cannot expand ${FAVORITE_USERS_EMAIL} macro in pipeline
Title: Message Title
Alex Earl updated an issue
Jenkins / JENKINS-47773
email-ext cannot expand ${FAVORITE_USERS_EMAIL} macro in pipeline
Change By:
Alex Earl
Component/s:
email-ext-plugin
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186268.1509557824000.14713.1563388141287%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47773) email-ext cannot expand ${FAVORITE_USERS_EMAIL} macro in pipeline
Title: Message Title
Alex Earl commented on JENKINS-47773
Re: email-ext cannot expand ${FAVORITE_USERS_EMAIL} macro in pipeline
That token won't work in a pipeline job, it has not been updated to support pipeline.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186268.1509557824000.14704.1563388141090%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47773) email-ext cannot expand ${FAVORITE_USERS_EMAIL} macro in pipeline
Title: Message Title
rao rao commented on JENKINS-47773
Re: email-ext cannot expand ${FAVORITE_USERS_EMAIL} macro in pipeline
FAVORITE_USERS_EMAIL is a Token Macro as part of [Favorite |https://plugins.jenkins.io/favorite] plugin.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186268.1509557824000.14689.1563387840278%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47773) email-ext cannot expand ${FAVORITE_USERS_EMAIL} macro in pipeline
Title: Message Title
Alex Earl commented on JENKINS-47773
Re: email-ext cannot expand ${FAVORITE_USERS_EMAIL} macro in pipeline
Where is FAVORITE_USERS_EMAIL defined? Is it a job parameter, or an environment variable? I don't think it is a token (from token-macro). If it's a parameter or environment variable, you should be able to access it as:
emailext body: 'Hello World - fifth', recipientProviders: [recipients()], subject: 'Hi', to: FAVORITE_USERS_EMAIL
or
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186268.1509557824000.14679.1563387240444%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47773) email-ext cannot expand ${FAVORITE_USERS_EMAIL} macro in pipeline
Title: Message Title
rao rao commented on JENKINS-47773
Re: email-ext cannot expand ${FAVORITE_USERS_EMAIL} macro in pipeline
The Favorites plugin generates that file for each job that has been Favorited.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186268.1509557824000.14671.1563387120256%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47773) email-ext cannot expand ${FAVORITE_USERS_EMAIL} macro in pipeline
Title: Message Title
Kyle Leinen commented on JENKINS-47773
Re: email-ext cannot expand ${FAVORITE_USERS_EMAIL} macro in pipeline
How did that text file get generated?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186268.1509557824000.14662.1563387060335%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58402) On Windows slaves, any call of dependency check tool results in "The input line is too long" error
Title: Message Title Kelly Hickel commented on JENKINS-58402 Re: On Windows slaves, any call of dependency check tool results in "The input line is too long" error I did a bit of digging, and the problem is the set CLASSPATH in dependency-check.bat, which seems to be the cause of this problem reported against Dependency-Check [https://github.com/jeremylong/DependencyCheck/issues/2062]. In my windows jenkins agent, the path to the tool BASEDIR is 135 characters, so the fully expanded CLASSPATH value would be 10841 characters, the longest command line for modern windows is 8191. I'll add this info to that ticket as well, not sure the best way to solve it, although for Java 9, that may be to use a manifest jar file. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200527.1562668975000.14658.1563386880313%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47773) email-ext cannot expand ${FAVORITE_USERS_EMAIL} macro in pipeline
Title: Message Title
rao rao commented on JENKINS-47773
Re: email-ext cannot expand ${FAVORITE_USERS_EMAIL} macro in pipeline
The workaround that i did is below.
def email_list = []
if(fileExists ('favorites.txt')) {
def file_contents = readFile 'favorites.txt'
email_list = file_contents.tokenize('\n')
echo "FILE CONTENTS OF FAVORITES ARE -- ${email_list}"
} else {
echo "FAVORITES FILE DOESNT EXIST"
}
emailext body: "${email_job_url}${currentBuild.description}", recipientProviders: [[$class: 'RequesterRecipientProvider']], mimeType: 'text/html', subject: "Pipeline '${env.JOB_NAME}' was ${currentBuild.result}", to: "${email_list.join(',')}"
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186268.1509557824000.14649.1563386760411%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57980) Incorrect links in /manage
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-57980 Incorrect links in /manage Change By: Daniel Beck Labels: core jenkins management newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199965.1560329204000.14643.1563386520142%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41377) Polling has not run yet, although received push event
Title: Message Title yuval shalgi commented on JENKINS-41377 Re: Polling has not run yet, although received push event try to copy to a new job, see if it happens in the new one. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178159.148527334.14627.1563384540335%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57314) P4 Sync to label after sync to head without deleting non labeled files
Title: Message Title Karl Wirth commented on JENKINS-57314 Re: P4 Sync to label after sync to head without deleting non labeled files Hi Chris Carr, Jose Valverde, I just wanted to check in again to see if either of you are available for a webex during UK working hours? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199083.1556813511000.14623.1563382500167%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51090) Emails no longer sent to developers on build failure
Title: Message Title Alex Earl commented on JENKINS-51090 Re: Emails no longer sent to developers on build failure Please enable debug mode in the global config and post the build log (redacted). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190377.1525289455000.14612.1563381840320%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58448) History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline
Title: Message Title Ankush Pandit edited a comment on JENKINS-58448 Re: History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline Added the result when displaying the build number on the graph. FYI, This problem occurs with build dates as well. I do not know how to check the jenkins logs, can you please provide instructions on how to tail them ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200581.1562870523000.14621.1563382020100%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58448) History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline
Title: Message Title Ankush Pandit commented on JENKINS-58448 Re: History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline Added the result when displaying the build number on the graph. FYI, This problem occurs with build dates as well. I do not know how to check the jenkins logs, can you please provide instructions? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200581.1562870523000.14619.1563381960173%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58448) History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline
Title: Message Title Ankush Pandit updated an issue Jenkins / JENKINS-58448 History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline Change By: Ankush Pandit Attachment: buildtxt.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200581.1562870523000.14617.1563381900192%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58336) ERROR: Exception reading response javax.mail.MessagingException: Exception reading response
Title: Message Title Alex Earl assigned an issue to Alex Earl Jenkins / JENKINS-58336 ERROR: Exception reading response javax.mail.MessagingException: Exception reading response Change By: Alex Earl Assignee: David van Laatum Alex Earl Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200448.1562224624000.14609.1563381660197%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58489) Convert .jtl output to binary image
Title: Message Title Alex Earl commented on JENKINS-58489 Re: Convert .jtl output to binary image I misread you initial description I think. Really the issue here is that you need to fetch the contents of the URL and then base64 encode. I didn't understand that at first. Being able to access any URL would be a huge security issue that I am not willing to undertake . You could possibly use a groovy template to do it though. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200627.1563182842000.14606.1563381600211%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57732) 安装插件报错
Title: Message Title
Andrew Mroczkowski commented on JENKINS-57732
Re: 安装插件报错
Update: I tried a few things, and now it's working. I'm not sure what exactly did it:
First I removed the{{ false }}from{{ config.xml}}
I also manually removed the{{ htmlpublisher-plugin }}from the{{ $JENKINS_HOME/plugins }}as the original ticket mentioned it
Then I started getting "out of heap space" errors in Jenkins. Next
I increased this heap size to 1G, which didn't work
Then I increased to 2G. Jenkins loaded!
Finally, I got errors saying that the html-publisher plugin was missing (which makes sense, I forcibly removed it
I re-installed the html-publisher plugin and everything appears to be working.
If I had to guess, the real fix was probably the heap size increase. The auth-related stack trace was a red-herring. HTH
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199675.1559117775000.14604.1563381600185%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50057) email-ext: Unable to unset triggers
Title: Message Title Alex Earl commented on JENKINS-50057 Re: email-ext: Unable to unset triggers I verified that if you uncheck ALL default triggers, then update will occur. Basically this is to avoid people shooting themselves in the foot and complaining that no email triggers are setup by default. Generally, the behavior is that if there are no default triggers defined then at least the "Failure - Any" trigger is added by default. This was the historical behavior of the plugin. Would this be acceptable? Basically, if you uncheck everything, it will set "Failure - Any" as selected? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189023.1520527395000.14600.1563381480151%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58534) Impossible to access promotion's console output (navigation is broken from links and breadcrumbs)
Title: Message Title slav dok created an issue Jenkins / JENKINS-58534 Impossible to access promotion's console output (navigation is broken from links and breadcrumbs) Issue Type: Bug Assignee: Oleg Nenashev Components: promoted-builds-plugin Created: 2019-07-17 16:34 Environment: Jenkins LTS version: 2.176.1 Promoted Builds version: 3.3 openjdk version: 1.8.0_161 CentOS version: 7.2.1511 Labels: plugin promoted-builds breadcrumb navigation consoleoutput Priority: Major Reporter: slav dok This works fine in Promoted Builds version 3.2, but breaks once you upgrade to 3.3 Usually, you can access the promotion's console output by: Selecting Build job (for example "Build_Job") Selecting Build Number (for example "#5") Clicking Promotion Status link Picking a promotion from the list (for example "Promo1 > #2") This will provide navigation breadcrumbs like: Jenkins > Build_Job > #5 > Promotion Status > #2 At the same time, the URL would be like: server_url:port/job/Build_Job/5/promotion/Promo1/promotionBuild/2/console After upgrading to 3.3 The URL remains same, but the UI loops back to the cons
[JIRA] (JENKINS-58452) Determining Dependencies from Update Center json
Title: Message Title Natasha Stopa commented on JENKINS-58452 Re: Determining Dependencies from Update Center json The last PR resulted in an error when the user requested an experimental or incrementals version. Because the experimental and incremental versions might require dependencies not yet released in the latest update center, resolving the dependencies based on the latest json or plugin-versions json might not be accurate. Another PR was created that should resolve these issues and although initially there was relunctance about getting json from multiple locations, it seemed that this was the only way to accurately resolve the dependencies. https://github.com/jenkinsci/plugin-installation-manager-tool/pull/35 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200585.1562885556000.14589.1563380700054%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57870) Request too large for server memory since 10.1.0
Title: Message Title Karl Wirth resolved as Fixed Test patch released. Jenkins / JENKINS-57870 Request too large for server memory since 10.1.0 Change By: Karl Wirth Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199833.1559782353000.14585.1563380460566%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57870) Request too large for server memory since 10.1.0
Title: Message Title Karl Wirth commented on JENKINS-57870 Re: Request too large for server memory since 10.1.0 Have released a test patch version to fix the "Request too large for memory" problem. Instead of running 'p4 changes -m1' it now runs for the last N changes: p4 changes m1 -ssubmitted //jenkins-masterJENKINS-57870-changes-m1-0/...@27+23784,273+3784 N is a configurable variable that can be set under: Jenkins > Manage Jenkins > Configure System > Head change query limit The test patch can be downloaded from: https://ci.jenkins.io/job/Plugins/job/p4-plugin/job/master/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199833.1559782353000.14583.1563380460544%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58533) Stapler request dispatch: Automatically allow public getters with StaplerRequest argument
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-58533 Stapler request dispatch: Automatically allow public getters with StaplerRequest argument Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-07-17 16:17 Priority: Minor Reporter: Daniel Beck The SECURITY-595 fix does not currently allow dispatch to getters with StaplerRequest argument. This is a documented behavior of Stapler and should be allowed without requiring the return type to be considered dispatchable. Add Comment
[JIRA] (JENKINS-56255) occasionally builds the branch for a PR also
Title: Message Title
Brian J Murrell edited a comment on JENKINS-56255
Re: occasionally builds the branch for a PR also
{quote}What about "Ignore change requests flagged as originating from an untrusted source"? It is in your image above.{quote}-My understanding of that option is that it doesn't actually prevent Jenkins from building from the untrusted source but rather just instructs Jenkins to ignore the {{Jenkinsfile}} such a change-request and use the {{Jenkinsfile}} from the project's master.- This The above was my confusing the new feature you are suggesting using with some previous functionality around PRs from untrusted sources.{quote}I agree, but my point was I think the problem is inherent in the feature. How would you redesign this to make it not flawed? Adding a delay would be mean that all branches wait a certain amount of time before they are built, which is generally not desirable.{quote}How frequent is creating new branches that are not backed by a PR in the real world? Because this delay should only really be required by new branches given that subsequent pushes to the branch already have the PR in place to tell Jenkins not to build the branch. And if it were configurable from 0 to whatever delay a Jenkins admin desires, then it's backward compatible with existing (flawed) behaviour of anyone wants to retain that. But it does allow fixing this behaviour for anyone who desires that.{quote}Let's get those gripers together and discuss how to address the problem. {quote}-The gripers are griping about a completely different issue to this issue so it's really quite orthogonal. They are griping about an issue that occurs when trying to employ your suggested "work-around". And the explanation of why your work-around cannot work in some situations is only use-case why that work-around doesn't work.- It could just plainly be that an organisation doesn't want PRs from forks for other organisational reasons.Ultimately any workarounds are just pussy-footing around the real issue of the branch/PR race that is inherent in any design which doesn't allow for a (configurable if you wish) delay to give the PR time to be submitted. So please, let's not get off into the weeds about why any particular work-around is not suitable and just fix the root issue?
Add Comment
[JIRA] (JENKINS-57732) 安装插件报错
Title: Message Title Andrew Mroczkowski commented on JENKINS-57732 Re: 安装插件报错 I'm getting the same stack trace on my Jenkins instance. I get an "Oops" page for any URL. I don't have any more insight yet. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199675.1559117775000.14574.1563379920740%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56255) occasionally builds the branch for a PR also
Title: Message Title
Brian J Murrell edited a comment on JENKINS-56255
Re: occasionally builds the branch for a PR also
{quote} What about "Ignore change requests flagged as originating from an untrusted source"? It is in your image above.{quote} - My understanding of that option is that it doesn't actually prevent Jenkins from building from the untrusted source but rather just instructs Jenkins to ignore the {{Jenkinsfile}} such a change-request and use the {{Jenkinsfile}} from the project's master. -This was confusing the new feature you are suggesting using with some previous functionality around PRs from untrusted sources. {quote} I agree, but my point was I think the problem is inherent in the feature. How would you redesign this to make it not flawed? Adding a delay would be mean that all branches wait a certain amount of time before they are built, which is generally not desirable.{quote} How frequent is creating new branches that are not backed by a PR in the real world? Because this delay should only really be required by new branches given that subsequent pushes to the branch already have the PR in place to tell Jenkins not to build the branch. And if it were configurable from 0 to whatever delay a Jenkins admin desires, then it's backward compatible with existing (flawed) behaviour of anyone wants to retain that. But it does allow fixing this behaviour for anyone who desires that. {quote} Let's get those gripers together and discuss how to address the problem. {quote} - The gripers are griping about a completely different issue to this issue so it's really quite orthogonal. They are griping about an issue that occurs when trying to employ your suggested "work-around". And the explanation of why your work-around cannot work in some situations is only use-case why that work-around doesn't work. - It could just plainly be that an organisation doesn't want PRs from forks for other organisational reasons.Ultimately any workarounds are just pussy-footing around the real issue of the branch/PR race that is inherent in any design which doesn't allow for a (configurable if you wish) delay to give the PR time to be submitted. So please, let's not get off into the weeds about why any particular work-around is not suitable and just fix the root issue?
Add Comment
[JIRA] (JENKINS-56255) occasionally builds the branch for a PR also
Title: Message Title Brian J Murrell commented on JENKINS-56255 Re: occasionally builds the branch for a PR also Liam Newman I tested your work-around, and have verified that the Ignore change requests flagged as originating from an untrusted source option (recently added I think) feature does as it seems and as such could be a valid work-around. But that doesn't make our current workflow any less valid[1] and it might be that I cannot convince all of my users to switch to submitting from forks now that they have gotten used to the branch-in-organisation workflow. [1] One redeeming feature of the workflow of using branches inside the main repo is that everyone can easily be aware of all of all WIP simply by inspecting the branches of repo. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197825.1550941413000.14562.1563379740123%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58532) Credentials don't seem to refresh or can't switch protocol for a server?
Title: Message Title Parichay Barpanda commented on JENKINS-58532 Re: Credentials don't seem to refresh or can't switch protocol for a server? But the checkout with SSH credential is not working. That I acknowledge. Will fix it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200681.1563377051000.14560.1563379260115%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56855) MessagingException message: IOException while sending message
Title: Message Title Alex Earl commented on JENKINS-56855 Re: MessagingException message: IOException while sending message Are you willing to try a debug build that will give more information as to the cause of this issue? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198515.1554219263000.14556.1563378900157%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56855) MessagingException message: IOException while sending message
Title: Message Title Alex Earl assigned an issue to Alex Earl Jenkins / JENKINS-56855 MessagingException message: IOException while sending message Change By: Alex Earl Assignee: David van Laatum Alex Earl Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198515.1554219263000.14552.1563378840306%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
