[JIRA] (JENKINS-58231) Job build failed when one of domain in Active Directory unreachable
Title: Message Title shan shan assigned an issue to Félix Belzunce Arcos Jenkins / JENKINS-58231 Job build failed when one of domain in Active Directory unreachable Change By: shan shan Assignee: shan shan Félix Belzunce Arcos 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.200292.1561609045000.10280.1561613280246%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58231) Job build failed when one of domain in Active Directory unreachable
Title: Message Title shan shan assigned an issue to shan shan Jenkins / JENKINS-58231 Job build failed when one of domain in Active Directory unreachable Change By: shan shan Assignee: Félix Belzunce Arcos shan shan 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.200292.1561609045000.10277.1561613220235%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58224) Jenkins Job Build, Changes does not show COMMITS from Bitbucket.
Title: Message Title Mark Waite edited a comment on JENKINS-58224 Re: Jenkins Job Build, Changes does not show COMMITS from Bitbucket. That output likely means that you are running a version of command line git which is not supported by the Jenkins git plugin. The git plugin supports command git versions 1.7.10 and later, and full support for all features requires command line git 1.9 or later. Since command line git 1.7 release released 9 years ago and 1.9 released 5 years ago, I think it is reasonable to upgrade to a newer version of command line git. Command line git has improved significantly in those many intervening years. You'll benefit significantly by using a newer version. Look at 1.22.0 for the latest features. If you're running CentOS 6 or Red Hat 6, then you will need to install a newer version of command line git in order to see those changes. If you're running CentOS 7 or Red Hat 7, you may also need to install a newer version of command line git. A bug fix for line truncation behavior made the conscious choice to use command line git options which require one of the supported versions of command line git. 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.200284.1561581863000.10272.1561609320148%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58224) Jenkins Job Build, Changes does not show COMMITS from Bitbucket.
Title: Message Title Mark Waite edited a comment on JENKINS-58224 Re: Jenkins Job Build, Changes does not show COMMITS from Bitbucket. That output likely means that you are running a version of command line git which is not supported by the Jenkins git plugin. The git plugin supports command git versions 1.7.10 and later, and full support for all features requires command line git 1.9 or later. Since command line git 1.7 released 9 years ago and 1.9 released 5 years ago, I think it is reasonable to upgrade to a newer version of command line git. Command line git has improved significantly in those many intervening years. You'll benefit significantly by using a newer version. Look at 1 2 .22.0 for the latest features.If you're running CentOS 6 or Red Hat 6, then you will need to install a newer version of command line git in order to see those changes. If you're running CentOS 7 or Red Hat 7, you may also need to install a newer version of command line git. A bug fix for line truncation behavior made the conscious choice to use command line git options which require one of the supported versions of command line git. 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.200284.1561581863000.10274.1561609320181%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58224) Jenkins Job Build, Changes does not show COMMITS from Bitbucket.
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-58224 Jenkins Job Build, Changes does not show COMMITS from Bitbucket. Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200284.1561581863000.10270.1561609260403%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58224) Jenkins Job Build, Changes does not show COMMITS from Bitbucket.
Title: Message Title Mark Waite updated JENKINS-58224 Jenkins / JENKINS-58224 Jenkins Job Build, Changes does not show COMMITS from Bitbucket. Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200284.1561581863000.10268.1561609260357%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58224) Jenkins Job Build, Changes does not show COMMITS from Bitbucket.
Title: Message Title Mark Waite commented on JENKINS-58224 Re: Jenkins Job Build, Changes does not show COMMITS from Bitbucket. That output likely means that you are running a version of command line git which is not supported by the Jenkins git plugin. The git plugin supports command git versions 1.7.10 and later, and full support for all features requires command line git 1.9 or later. Since command line git 1.7 release 9 years ago and 1.9 released 5 years ago, I think it is reasonable to upgrade to a newer version of command line git. Command line git has improved significantly in those many intervening years. You'll benefit significantly by using a newer version. If you're running CentOS 6 or Red Hat 6, then you will need to install a newer version of command line git in order to see those changes. If you're running CentOS 7 or Red Hat 7, you may also need to install a newer version of command line git. A bug fix for line truncation behavior made the conscious choice to use command line git options which require one of the supported versions of command line git. 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.200284.1561581863000.10266.1561609260327%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58231) Job build failed when one of domain in Active Directory unreachable
Title: Message Title Dennis Tran created an issue Jenkins / JENKINS-58231 Job build failed when one of domain in Active Directory unreachable Issue Type: Story Assignee: Félix Belzunce Arcos Components: active-directory-plugin Created: 2019-06-27 04:17 Environment: AD plugin 2.13 Jenkins 2.164.2 Priority: Minor Reporter: Dennis Tran In Action Directory section on Configure global security, I added 3 domain, let said domain A, B, and C. Today, domain B has been down, so users could not login with LDAP account in domain B, that is definitely. But, I have no idea why some build jobs have been failed with error below. FATAL: org.acegisecurity.AuthenticationServiceException: Failed to bind to LDAP server with the bind name/password; nested exception is javax.naming.CommunicationException: 192.168.1.3:3268 [Root exception is java.net.SocketTimeoutException: connect timed out] java.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:589) at sun.reflect.GeneratedMethodAccessor10329.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at
[JIRA] (JENKINS-58230) how to disable automatic build by default?
Title: Message Title rock luo created an issue Jenkins / JENKINS-58230 how to disable automatic build by default? Issue Type: Improvement Assignee: Unassigned Components: gitea-plugin Created: 2019-06-27 03:39 Priority: Minor Reporter: rock luo I use gitea plugin and import an organization ，the plugin always trigger a build automatically after any push,but I don't want this. Where can I disable this featuer? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58222) xunit 2.3.4 fails to read xunit 1.102 configs
Title: Message Title Nikolas Falco updated JENKINS-58222 Jenkins / JENKINS-58222 xunit 2.3.4 fails to read xunit 1.102 configs Change By: Nikolas Falco Status: In Progress 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.200282.1561578395000.10226.1561601880375%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58222) xunit 2.3.4 fails to read xunit 1.102 configs
Title: Message Title Nikolas Falco started work on JENKINS-58222 Change By: Nikolas Falco 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.200282.1561578395000.10224.1561601880346%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58089) Can't configure report pattern in job configuration UI
Title: Message Title Nikolas Falco commented on JENKINS-58089 Re: Can't configure report pattern in job configuration UI Fix released in DTKit API plugin 2.1.1-1. Jelly file for tools are moved there. Tested in our production environment. 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.200130.1560932882000.10218.1561601460152%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58089) Can't configure report pattern in job configuration UI
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-58089 Can't configure report pattern in job configuration UI Change By: Nikolas Falco Component/s: dtkit-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.200130.1560932882000.10213.1561601410417%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58089) Can't configure report pattern in job configuration UI
Title: Message Title Nikolas Falco closed an issue as Fixed Jenkins / JENKINS-58089 Can't configure report pattern in job configuration UI Change By: Nikolas Falco Status: In Progress Closed Resolution: Fixed Released As: 2.1.1-1 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.200130.1560932882000.10208.1561601340481%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58089) Can't configure report pattern in job configuration UI
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-58089 Can't configure report pattern in job configuration UI Change By: Nikolas Falco Summary: Can't configure report pattern in job configuration ui UI 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.200130.1560932882000.10201.1561600860519%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58089) Can't configure report pattern in job configuration UI
Title: Message Title Nikolas Falco started work on JENKINS-58089 Change By: Nikolas Falco 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.200130.1560932882000.10203.1561600860557%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52764) Improve crumb compatibility with Azure Application Gateway
Title: Message Title mike margala commented on JENKINS-52764 Re: Improve crumb compatibility with Azure Application Gateway I attempted to enable the 'proxy compatibility' but that didn't seem to work when behind an Azure Application Gateway. Has this been resolved? Does anyone have any other suggestions? 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.192660.1532663237000.10195.1561600320154%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55271) Jenkinsfile Active Choice Parameter
Title: Message Title
J P commented on JENKINS-55271
Re: Jenkinsfile Active Choice Parameter
I am getting the same issue with the parameter separator plugin. Not sure it is localized to this. What is the correct way to do this in the job's DSL?
String sectionHeaderStyleCss = ' color: white; background: green; font-family: Roboto, sans-serif !important; padding: 5px; text-align: center; '
String separatorStyleCss = ' border: 0; border-bottom: 1px dashed #ccc; background: #999; '
pipelineJob("Foo-job") { description("FOO with separators")
parameters {
parameterSeparatorDefinition { name('FOO_1') separatorStyle(separatorStyleCss) sectionHeader('FOO_1') sectionHeaderStyle(sectionHeaderStyleCss)
}
{{}}
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.196358.1545287457000.10191.1561599180195%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58204) Closing out coding phase 1
Title: Message Title Marky Jackson updated JENKINS-58204 This officially closes out coding phase 1 Jenkins / JENKINS-58204 Closing out coding phase 1 Change By: Marky Jackson Status: In Review Resolved 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.200262.1561534963000.10189.1561596360300%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57508) NodeJSInstallation marks "home" parameter as required
Title: Message Title Nikolas Falco started work on JENKINS-57508 Change By: Nikolas Falco 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.199410.1558021019000.10184.1561595640446%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57508) NodeJSInstallation marks "home" parameter as required
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-57508 NodeJSInstallation marks "home" parameter as required Change By: Nikolas Falco Assignee: Ewelina Wilkosz Nikolas Falco 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.199410.1558021019000.10182.1561595640316%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57508) NodeJSInstallation marks "home" parameter as required
Title: Message Title Nikolas Falco updated JENKINS-57508 Jenkins / JENKINS-57508 NodeJSInstallation marks "home" parameter as required Change By: Nikolas Falco Status: In Progress 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.199410.1558021019000.10186.1561595640921%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57508) NodeJSInstallation marks "home" parameter as required
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-57508 NodeJSInstallation marks "home" parameter as required Change By: Nikolas Falco Summary: NodeJSInstallation marks "home" parameter as required but not documented 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.199410.1558021019000.10179.1561595460447%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58229) Optionally skip plugins listed in plugins.txt on latest version
Title: Message Title Zbynek Konecny commented on JENKINS-58229 Re: Optionally skip plugins listed in plugins.txt on latest version you can use https://updates.jenkins.io/current/update-center.actual.json instead of update-center.json to obtain the list as actual JSON and simplify https://github.com/jenkinsci/plugin-installation-manager-tool/blob/master/plugin-management-library/src/main/java/io/jenkins/tools/pluginmanager/impl/PluginManager.java#L217 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.200289.1561592204000.10176.1561595160226%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58197) Enable the Release Drafter for the repository
Title: Message Title Natasha Stopa commented on JENKINS-58197 Re: Enable the Release Drafter for the repository Requested access from Infra team: https://issues.jenkins-ci.org/browse/INFRA-2162 Created PR for configuration: https://github.com/jenkinsci/plugin-installation-manager-tool/pull/22 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.200253.1561502069000.10174.1561594380110%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58197) Enable the Release Drafter for the repository
Title: Message Title Natasha Stopa started work on JENKINS-58197 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.200253.1561502069000.10170.1561594320366%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58197) Enable the Release Drafter for the repository
Title: Message Title Natasha Stopa updated JENKINS-58197 Jenkins / JENKINS-58197 Enable the Release Drafter for the repository Change By: Natasha Stopa Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200253.1561502069000.10172.1561594320396%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58229) Optionally skip plugins listed in plugins.txt on latest version
Title: Message Title Natasha Stopa created an issue Jenkins / JENKINS-58229 Optionally skip plugins listed in plugins.txt on latest version Issue Type: Task Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-06-26 23:36 Labels: gsoc-2019 plugin-manager Priority: Minor Reporter: Natasha Stopa Use case: updating all currently installed plugins to their latest version. It’s hard to know if plugins are the latest version until checking the update center because to find out what version an installed plugin is, we parse the manifest, which doesn’t give any info about if that version is the latest. In general, information about plugins needs to be retrieved from the update center sooner - this will also help with displaying security warnings only relevant to the plugins in which the user is interested. Related to: https://issues.jenkins-ci.org/browse/JENKINS-58191 Add Comment
[JIRA] (JENKINS-58199) Alpha Release of Plugin Installation Manager Tool
Title: Message Title Natasha Stopa updated JENKINS-58199 Initial alpha version was released: https://github.com/jenkinsci/plugin-installation-manager-tool/releases Jenkins / JENKINS-58199 Alpha Release of Plugin Installation Manager Tool Change By: Natasha Stopa Status: In Review 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.200255.1561505179000.10165.1561591980093%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58199) Alpha Release of Plugin Installation Manager Tool
Title: Message Title Natasha Stopa updated JENKINS-58199 Jenkins / JENKINS-58199 Alpha Release of Plugin Installation Manager Tool Change By: Natasha Stopa Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200255.1561505179000.10164.1561591860160%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58199) Alpha Release of Plugin Installation Manager Tool
Title: Message Title Natasha Stopa started work on JENKINS-58199 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.200255.1561505179000.10163.1561591860132%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58228) CLI usage doesn't work if typo in args
Title: Message Title Natasha Stopa created an issue Jenkins / JENKINS-58228 CLI usage doesn't work if typo in args Issue Type: Task Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-06-26 23:27 Labels: plugin-manager cli gsoc Priority: Minor Reporter: Natasha Stopa Args4J just throws a NPE. Plugins might need to default to [] rather than null to workaround this. Add Comment
[JIRA] (JENKINS-58176) Create Phase 1 Blog Post
Title: Message Title Natasha Stopa updated JENKINS-58176 Jenkins / JENKINS-58176 Create Phase 1 Blog Post Change By: Natasha Stopa Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200227.1561440641000.10162.1561591680167%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57508) NodeJSInstallation "home" parameter required but not documented
Title: Message Title Nikolas Falco edited a comment on JENKINS-57508 Re: NodeJSInstallation "home" parameter required but not documented For what I know nodeJS plugin has never been tested with configuration as plugin and do not support it till now. I can see that NodeJSInstallation has the same constructor of hudson.tasks.Maven.MavenInstallation and hudson.model.JDK that takes the path already installed home directory (empty by default if install automatically is checked) 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.199410.1558021019000.10160.1561590780161%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57508) NodeJSInstallation "home" parameter required but not documented
Title: Message Title Nikolas Falco edited a comment on JENKINS-57508 Re: NodeJSInstallation "home" parameter required but not documented For what I know nodeJS plugin has never been tested with configuration as plugin and do not support it till 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.199410.1558021019000.10157.1561590540549%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57508) NodeJSInstallation "home" parameter required but not documented
Title: Message Title Nikolas Falco commented on JENKINS-57508 Re: NodeJSInstallation "home" parameter required but not documented For what I know nodeJS plugin has never been tested with configuration as 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.199410.1558021019000.10154.1561590480123%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53767) Offer plugin management tooling
Title: Message Title Natasha Stopa updated an issue Jenkins / JENKINS-53767 Offer plugin management tooling Change By: Natasha Stopa Jenkins does offer a web UI to manage plugin installation from a live master instance, but in many deployments administrator would like to control installed plugins by version and by tooling, before jenkins master starts. * docker official image provides an install-plugins.sh script which evolved far beyond its initial "help script" scope. * configuration-as-code implemented plugin installation hack based on PluginSite.Plugin#deploy. (Removed as of v1.8 of JCasC plugin) * open-source update center does expose plugins-version.json on casc request so one can manage versions for all hosted plugins, not just latest * custom war packager does support plugin installation on his own * jenkins evergreen does manage plugin installation based on updates from metadata server, using his own logic implemented by nodejs evergreen client. * jenkinsfile-runner does manage plugin installation implemented in Go * coreOS provides a [groovy script|https://github.com/coreos/jenkins-os/blob/master/init.groovy] to handle required plugins * cloudbees DEV@Cloud uses a set of Chef Ruby recipes for the same purpose * etc Everybody is re-inventing the wheel, partially implementing the "details" of plugin management (signed metadata, artifacts checksums, plugins detached from core, ...). It becomes obvious Jenkins should provide adequate tooling for plugin installation _outside_ jenkins a live Jenkins instance. Add Comment
[JIRA] (JENKINS-47874) Support multiple repositories in multi-branch pipeline
Title: Message Title
Jon Kelley commented on JENKINS-47874
Re: Support multiple repositories in multi-branch pipeline
Mark Waite Here is a use-case for you. See the multi-lined comment areas below. Is there any ideas to achieve something similar?? We need to run an external pipeline script which lives in a scripts repository, because we don't want to put our shared pipeline scripts in 900+ chef module repositories or use submodules. We've hit a brick wall for our use case since updating Job DSL 1.70 to 1.74 since pipelineJob is dead for supporting SCM. multibranchPipelineJob is lacking multi git functionality.
// Generate PR push pipeline jobs for all of the repos passed in via REPO_LISTdef repoList = "${REPO_LIST}".trim().replaceAll('"', '').split(",")
println "Generating PR push jobs for the following repos:: $repoList"
repoList.each {
def cookbook = it
multibranchPipelineJob("chef-${cookbook}-PR-push") {
description("Chef push pipeline job")
branchSources {
github {
buildOriginPRHead() // Build fork PRs (unmerged head).
// buildOriginPRMerge() // Build fork PRs (merged with base branch).
buildOriginBranchWithPR() // Build origin branches also filed as PRs.
checkoutCredentialsId('f-f-f-f')
// scanCredentialsId('github-ci')
repoOwner('myOwner')
repository("${cookbook}")
}
}
configure {
// my Jenkinsfile doesn't exist in the chef coookbooks for 900 repositories...
// how can we set a seperate git repo for shared scripts?
// https://stackoverflow.com/questions/48284589/jenkins-jobdsl-multibranchpipelinejob-change-script-path
it / factory(class: 'org.jenkinsci.plugins.workflow.multibranch.WorkflowBranchProjectFactory') {
owner(class: 'org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject', reference: '../..')
scriptPath("jenkins/[where ever you want]/Jenkinsfile")
}
}
}
}
pipelineJob worked excellent for our needs, the old broken syntax is below:
repoList.each {
def cookbook = it
pipelineJob("chef-${cookbook}-PR-push") {
definition {
cpsScm {
lightweight(true)
scriptPath('jenkins/[where ever you want]/Jenkinsfile')
scm {
git {
branch('master')
remote {
github("organization/scripts", 'ssh')
credentials('-fff-fff-ff)
}
}
}
}
}
}
}
[JIRA] (JENKINS-58226) Include repositories in mvn
Title: Message Title Natasha Stopa updated JENKINS-58226 Jenkins / JENKINS-58226 Include repositories in mvn Change By: Natasha Stopa Status: In Review 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.200286.1561584707000.10128.1561588080088%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58226) Include repositories in mvn
Title: Message Title Natasha Stopa started work on JENKINS-58226 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.200286.1561584707000.10125.1561588020151%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58226) Include repositories in mvn
Title: Message Title Natasha Stopa commented on JENKINS-58226 Re: Include repositories in mvn Fix merged in https://github.com/jenkinsci/plugin-installation-manager-tool/pull/21. 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.200286.1561584707000.10126.1561588020234%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58226) Include repositories in mvn
Title: Message Title Natasha Stopa updated JENKINS-58226 Jenkins / JENKINS-58226 Include repositories in mvn Change By: Natasha Stopa Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200286.1561584707000.10127.1561588020245%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58227) Role Strategy: JCasC expoer fails for dangerous permissions
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-58227 Role Strategy: JCasC expoer fails for dangerous permissions Issue Type: Bug Assignee: Oleg Nenashev Components: role-strategy-plugin Created: 2019-06-26 22:25 Labels: jcasc-compatibility Priority: Minor Reporter: Oleg Nenashev authorizationStrategy: "FAILED TO EXPORT hudson.model.Hudson#authorizationStrategy:\ \ java.lang.SecurityException: Rejected dangerous permission: hudson.model.Hudson.UploadPlugins\ \ at org.jenkinsci.plugins.rolestrategy.permissions.PermissionHelper.fromStrings(PermissionHelper.java:86)\ \ at com.michelin.cio.hudson.plugins.rolestrategy.Role.(Role.java:98) \ \ at org.jenkinsci.plugins.rolestrategy.casc.RoleDefinition.getRole(RoleDefinition.java:55)\ \ at org.jenkinsci.plugins.rolestrategy.casc.RoleDefinition.(RoleDefinition.java:41)\ \ at org.jenkinsci.plugins.rolestrategy.casc.RoleBasedAuthorizationStrategyConfigurator.lambda$getRoleDefinition$2(RoleBasedAuthorizationStrategyConfigurator.java:84)\ \ at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)\ \ at java.util.Collections$UnmodifiableMap$UnmodifiableEntrySet.lambda$entryConsumer$0(Collections.java:1575)\ \ at java.util.concurrent.ConcurrentSkipListMap$EntrySpliterator.forEachRemaining(ConcurrentSkipListMap.java:3535)\ \ at java.util.Collections$UnmodifiableMap$UnmodifiableEntrySet$UnmodifiableEntrySetSpliterator.forEachRemaining(Collections.java:1600)\ \ at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) at\ \
[JIRA] (JENKINS-47867) Make "Committers To Ignore" configurable via traits
Title: Message Title John Gaunt resolved as Fixed Fix is present in v2.4.5 of the bitbucket-branch-source plugin. Jenkins / JENKINS-47867 Make "Committers To Ignore" configurable via traits Change By: John Gaunt 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.186379.1510079108000.10119.1561586880587%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58226) Include repositories in mvn
Title: Message Title Natasha Stopa created an issue Jenkins / JENKINS-58226 Include repositories in mvn Issue Type: Task Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-06-26 21:31 Labels: gsoc-2019 plugin-manager Priority: Minor Reporter: Natasha Stopa It is a common practice to include repositories and pluginRepositories into POM and would help fix compiling the plugin installer locally. Add Comment
[JIRA] (JENKINS-58131) Jenkins master propagates environment variables to agents running a pipeline
Title: Message Title Ilguiz Latypov edited a comment on JENKINS-58131 Re: Jenkins master propagates environment variables to agents running a pipeline Thanks to my colleague I saw the Jenkins machine's configuration UI page (which was not available to me) and noticed the "Tool locations" thing which selected some Java version option probably defined in the Jenkins system configuration. I am guessing this was the root cause of the bug. The "tool locations" drop-down in computer configuration should account for major OS differences such as directory notation in JAVA_HOME for Windows and MacOS. The system configuration should recognize this chance and offer at least two versions of each environment variable to be specified. Selecting the respective option in the computer configuration will automatically choose one of the two depending on the computer's OS. 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.200176.1561073587000.10116.1561583760101%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58131) Jenkins master propagates environment variables to agents running a pipeline
Title: Message Title Ilguiz Latypov commented on JENKINS-58131 Re: Jenkins master propagates environment variables to agents running a pipeline Thanks to my colleague I saw the Jenkins machine's configuration UI page (which was not available to me) and noticed the "Tool locations" thing which selected some Java version option probably defined in the Jenkins system configuration. I am guessing this was the root cause of the bug. The "tool locations" drop-down in computer configuration should account for major OS differences such as directory notation in JAVA_HOME for Windows and MacOS. 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.200176.1561073587000.10114.1561583640220%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58222) xunit 2.3.4 fails to read xunit 1.102 configs
Title: Message Title Nikolas Falco commented on JENKINS-58222 Re: xunit 2.3.4 fails to read xunit 1.102 configs Yes, version 2.x is not compatible with 1.x. I had mark in the pom.xml 2.0.3 but maybe after refactoring I delete setting in 2.3.5 version for mistake. I will re add in 2.3.6. 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.200282.1561578395000.10112.1561582980442%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58225) Command line flag for debug output
Title: Message Title Tim Jacomb closed an issue as Fixed Jenkins / JENKINS-58225 Command line flag for debug output Change By: Tim Jacomb Status: Open Closed 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.200285.1561582169000.10110.1561582680294%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58225) Command line flag for debug output
Title: Message Title Tim Jacomb commented on JENKINS-58225 Re: Command line flag for debug output I see this is already there, -verbose 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.200285.1561582169000.10108.1561582620220%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58192) No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types
Title: Message Title
Jon Kelley edited a comment on JENKINS-58192
Re: No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types
{code:java}// This won't work either.agent {label 'slave'} {code} How is *pipelineJob* suppose to be executed on an agent these days? Does it only support master now?This issue appeared upgrading from Jenkins job DSL from 1.70 to 1.74. We create hundreds of jobs using pipelineJob so it is a lot of manual effort to edit the produced jobs to an agent in the U.I.
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.200247.1561483009000.10106.1561582380125%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58192) No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types
Title: Message Title
Jon Kelley edited a comment on JENKINS-58192
Re: No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types
{code:java} // This won't work either. agent {label 'slave'} {code} How is *pipelineJob* suppose to be executed on an agent these days? Does it only support master now?This issue appeared upgrading from Jenkins job DSL from 1.70 to 1.74.
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.200247.1561483009000.10103.1561582320191%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58225) Command line flag for debug output
Title: Message Title Tim Jacomb created an issue Jenkins / JENKINS-58225 Command line flag for debug output Issue Type: Improvement Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-06-26 20:49 Priority: Minor Reporter: Tim Jacomb As fine level logging is being added there needs to be a way to easily enable debug logging. Some potential examples: -v -vv --verbose --debug --log-level debug Add Comment
[JIRA] (JENKINS-58192) No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types
Title: Message Title
Jon Kelley edited a comment on JENKINS-58192
Re: No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types
{code:java}agent {label 'slave'} {code} How is * pipelineJob * suppose to be executed on an agent these days? Does it only support master now? This issue appeared upgrading from Jenkins job DSL from 1.70 to 1.74.
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.200247.1561483009000.10098.1561582020147%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58192) No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types
Title: Message Title
Jon Kelley commented on JENKINS-58192
Re: No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types
agent {label 'slave'}
How is pipelineJob suppose to be executed on an agent these days? This issue appeared upgrading from 1.70 to 1.74.
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.200247.1561483009000.10095.1561581960142%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58192) No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types
Title: Message Title
Jon Kelley updated an issue
Jenkins / JENKINS-58192
No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types
Change By:
Jon Kelley
Job error:*No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types* I have defined a job pipeline DSL from SCM according to documentation:{code:java}node('master'){withEnv(['JENKINS_CREDENTIAL_ID_GITHUB= 540d97fc-bcfe-419b-a6a4-dcc1b2b0be0f ','GIT_BRANCH=development','GIT_REPO=g...@github.com:x/x.git','GROOVY_SCRIPT_DIR=jenkinsfiles','GROOVY_SCRIPT_FILENAME=dslCreatePipeline.groovy']){stage('Clean Workspace') {cleanWs()}stage('Clone sources') {git branch: "${env.GIT_BRANCH}", credentialsId: "${env.JENKINS_CREDENTIAL_ID_GITHUB}", url: "${env.GIT_REPO}"}stage("ExecuteDslScripts: ${GROOVY_SCRIPT_FILENAME}") {def repos = "a,b,c,d"dir("${env.GROOVY_SCRIPT_DIR}") {sh "echo CWD is `pwd`"// https://github.com/jenkinsci/job-dsl-plugin/wiki/User-Power-Moves#use-job-dsl-in-pipeline-scriptsstep([$class: 'ExecuteDslScripts',targets: "${env.GROOVY_SCRIPT_FILENAME}",removedJobAction: 'IGNORE',removedViewAction: 'IGNORE',removedViewAction: 'IGNORE',lookupStrategy: 'SEED_JOB',additionalParameters: [REPO_LIST: "${repos}"] // repos PARAM was created manually])}}}} {code} This executes my groovy script, which fails when building with the error: ERROR: (dslCreatePushPipeline.groovy, line 9) No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.label() is applicable for argument types: (java.lang.String) values: [swarm] Here is "dslCreatePipeline.groovy" for reference. If there is proper way to set worker labels, let me know. This works fine when pasting the script into ""Process job DSL"" box inline so I am assuming there's a bug here.{code:java}def repoList = "${REPO_LIST}".trim().replaceAll('"', '').split(",")println "Generating PR push jobs for the following repos:: $repoList"repoList.each { def cookbook = it pipelineJob("${cookbook}-PR-push") {label('swarm') // this is throwing an error // why does this work without SCM?description("Chef push pipeline job")properties { githubProjectUrl("https://github.com/git_org/${cookbook}/")}scm { git {remote { github("git_org/${cookbook}", 'ssh') refspec('+refs/pull/*:refs/remotes/origin/pr/*') credentials('d6f6e9f1-43cb-4ea1-83da-e5581d3f9472')}branch('${ghprbActualCommit}')extensions { relativeTargetDirectory("${cookbook}")}configure { gitScm -> gitScm / 'extensions' << 'hudson.plugins.git.extensions.impl.UserExclusion'
[JIRA] (JENKINS-58224) Jenkins Job Build, Changes does not show COMMITS from Bitbucket.
Title: Message Title Omar Velazquez created an issue Jenkins / JENKINS-58224 Jenkins Job Build, Changes does not show COMMITS from Bitbucket. Issue Type: Improvement Assignee: Mark Waite Attachments: Current.JPG, Original.JPG Components: git-plugin Created: 2019-06-26 20:44 Labels: jenkins change Priority: Minor Reporter: Omar Velazquez Our users reports that their jobs are not displaying the commit information into Build page (please see screenshots), they consider that was a really useful behavior in previous Jenkins versions. Current Jenkins Version: 2.164.2 We really appreciate your help. Add Comment
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Jonathan B commented on JENKINS-58085 Re: BlueOcean UI stuck in "Waiting for run to start" Marco Pracucci thank you. I revisited this and downgrading to Blue Ocean 1.16 did resolve the issue here as well. When I tried initially, I had downgraded only the metapackage `blueocean`, but all of the subpackages were still on `1.17`. 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.200110.1560887329000.10081.1561581540371%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Jonathan B edited a comment on JENKINS-58085 Re: BlueOcean UI stuck in "Waiting for run to start" [~pracucci] thank you. I revisited this and downgrading to Blue Ocean 1.16 did resolve the issue here as well. When I tried initially, I had downgraded only the metapackage `blueocean`, but all of the subpackages were still on ` 1.17 ` . 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.200110.1560887329000.10083.1561581540404%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58145) Blue Ocean pipeline shows no progress
Title: Message Title Jonathan B closed an issue as Duplicate Jenkins / JENKINS-58145 Blue Ocean pipeline shows no progress Change By: Jonathan B 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.200190.156113573.10075.1561581480667%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56891) EC2 Plugin using Spot Instances fails
Title: Message Title Serban Nicusor commented on JENKINS-56891 Re: EC2 Plugin using Spot Instances fails I had Jenkins on an old mac machine. Switched to new machine of Ubuntu 18.04 with a fresh install of Jenkins LTS, everything is working smooth 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.198562.1554422015000.10073.1561579740113%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58213) Jenkins Slave Can't reach Gitlab, but Server can
Title: Message Title Matt Sicker commented on JENKINS-58213 Re: Jenkins Slave Can't reach Gitlab, but Server can What type of SSH key are you using? And did this behavior start in a specific version of the 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.200273.1561559419000.10071.1561579560205%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58223) No config UI for KubernetesDeclarativeAgent
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-58223 No config UI for KubernetesDeclarativeAgent Issue Type: Bug Assignee: Carlos Sanchez Attachments: Screenshot_2019-06-26_16-01-57.png Components: kubernetes-plugin Created: 2019-06-26 20:04 Labels: ux Priority: Major Reporter: Jesse Glick Other Declarative agent directives have short descriptions and configuration forms. The kubernetes one does not. Seems that it is missing getDisplayName config.jelly Add Comment
[JIRA] (JENKINS-58222) xunit 2.3.4 fails to read xunit 1.102 configs
Title: Message Title Darrel Vuncannon created an issue Jenkins / JENKINS-58222 xunit 2.3.4 fails to read xunit 1.102 configs Issue Type: Bug Assignee: Nikolas Falco Components: xunit-plugin Created: 2019-06-26 19:46 Priority: Major Reporter: Darrel Vuncannon Somewhere between versions 1.102 and 2.3.4 xunit introduced a not-backward-compatible change to reading its config. Steps to reproduce: Install xunit 1.102. Add xunit to a job config, including a tool (such a GoogleTest). Upgrade to xunit 2.3.4. Run the job. Expected Result Job succeeds. Actual Result Job fails with: ERROR: Build step failed with exception java.lang.IllegalArgumentException: The tools section is required. at org.jenkinsci.plugins.xunit.XUnitProcessor.(XUnitProcessor.java:141) at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:170) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1835) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Matt Sicker commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) If there's contention in the SecureRandom instance, that could be causing issues. Let me see if I can reproduce any slowdowns with a benchmark test. Thanks for verifying that this isn't AD-specific at least. I might be able to help figure this out. 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.197810.1550821517000.10028.1561578240817%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58196) UTF8 BOM override issue in 1.10.0
Title: Message Title Peter Hopkins commented on JENKINS-58196 Re: UTF8 BOM override issue in 1.10.0 Thanks for the quick response Karl. (utf8) versions - P4D/LINUX26X86_64/2017.1/1622573 (2018/02/20) CentOS release 6.7 Linux 2.6.32-573.12.1.el6.x86_64 #1 SMP Tue Dec 15 21:19:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux server is not Unicode Using the vSphere slave plugin for jenkins, optional Java startup parameter Slave java = SE RE 1.8.0_152 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.200252.1561501047000.10023.1561577940167%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58221) Swarm cannot connect to Jenkins Master provided port:50000 is not reachable
Title: Message Title
Joey Khashab updated an issue
Jenkins / JENKINS-58221
Swarm cannot connect to Jenkins Master provided port:5 is not reachable
Change By:
Joey Khashab
Hello,I am currently running Jenkins 2.138.3 with plugin version 3.12, I am attempting to upgrade to Jenkins 2.182 and plugin 3.17. Looks like I am getting an error that it can't connect to port 5 (the fixed agent port). I attached the verbose logs. When I do a curl from the slave to the master I see 5 is available.{code:java}[ec2-user@ip-10-0-6-121 ~]$ curl 10.0.7.19:5Jenkins-Agent-Protocols: JNLP4-connect, PingJenkins-Version: 2.182Jenkins-Session: 02bf8ba3Client: 10.0.6.121Server: 10.0.7.19 Remoting-Minimum-Version: 3.4 {code}Any ideas would be appreciated, I am currently just downgrading Jenkins to previous versions to see if that will help.
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.200281.1561577565000.10020.1561577760059%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57967) vSphere Cloud: java.lang.NoSuchMethodError in SSHLauncher
Title: Message Title Nick Jones commented on JENKINS-57967 Re: vSphere Cloud: java.lang.NoSuchMethodError in SSHLauncher I opened https://github.com/jenkinsci/vsphere-cloud-plugin/pull/104 to attempt to address 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.199950.1560271877000.10019.1561577640591%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58221) Swarm cannot connect to Jenkins Master provided port:50000 is not reachable
Title: Message Title Joey Khashab created an issue Jenkins / JENKINS-58221 Swarm cannot connect to Jenkins Master provided port:5 is not reachable Issue Type: Bug Assignee: Unassigned Attachments: jenkins_swarm_verbose_logs.txt Components: swarm-plugin Created: 2019-06-26 19:32 Environment: jenkins version: 2.182 swarm plugin version: 3.17 Java Version on slave and master is open JDK 1.8.0_201 Priority: Major Reporter: Joey Khashab Hello, I am currently running Jenkins 2.138.3 with plugin version 3.12, I am attempting to upgrade to Jenkins 2.182 and plugin 3.17. Looks like I am getting an error that it can't connect to port 5 (the fixed agent port). I attached the verbose logs. When I do a curl from the slave to the master I see 5 is available. [ec2-user@ip-10-0-6-121 ~]$ curl 10.0.7.19:5 Jenkins-Agent-Protocols: JNLP4-connect, Ping Jenkins-Version: 2.182 Jenkins-Session: 02bf8ba3 Client: 10.0.6.121 Server: 10.0.7.19 Any ideas would be appreciated, I am currently just downgrading Jenkins to previous versions to see if that will help.
[JIRA] (JENKINS-58219) Active Choices Reactive Parameter Groovy script returning String instead of List
Title: Message Title Brett Hand updated an issue Jenkins / JENKINS-58219 Active Choices Reactive Parameter Groovy script returning String instead of List Change By: Brett Hand I have an Active Choices parameter defined: It is an Active Choices Reactive parameter, where I am simply returning a list of character strings via the Groovy script (i.e: return ['example1','example2']) that will be used to create some check boxes. I notice from the documentation that the way I have formatted this should return an a List. I have also verified that this does return an a List in a Groovy web console.Now, the problem occurs when I attempt to index the List later on in my Jenkinsfile. If my List contained ["example1","example2"], then list[0] would return "e" instead of "example1". It looked like my List was actually a String instead. I debugged the parameter and found that it actually was a String type.I am wondering why my parameter is being returned as a String instead of a List, as it appears that the way I have set it up should return a List, which I should then be able to index. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-58220) eks slave provided port:5000 is not reachable
Title: Message Title
bob james updated an issue
Jenkins / JENKINS-58220
eks slave provided port:5000 is not reachable
Change By:
bob james
Jenkins Master: 2.164.1kubernetes-plugin: 1.16.1Jenkins master is running *outside* of Kubernetes and i'm trying to get my Jenkins slaves to run on my EKS worker nodes Jenkins slave pod error message:{code:java}INFO: Locating server among [https://my-jenkins-url.com] Jun 26, 2019 6:37:59 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping] Jun 26, 2019 6:38:04 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver isPortVisible WARNING: connect timed out Jun 26, 2019 6:38:04 PM hudson.remoting.jnlp.Main$CuiListener error SEVERE: https://my-jenkins-url.com provided port:5000 is not reachable java.io.IOException: https://my-jenkins-url.com provided port:5000 is not reachable at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:287) at hudson.remoting.Engine.innerRun(Engine.java:523) at hudson.remoting.Engine.run(Engine.java:474) {code}How can I override this "port:5000" default setting? !image-2019-06-26-21-13-59-228.png!!image-2019-06-26-21-13-51-122.png!
Add Comment
This message was sent by Atlassian Jira
[JIRA] (JENKINS-58219) Active Choices Reactive Parameter Groovy script returning String instead of List
Title: Message Title Brett Hand updated an issue Jenkins / JENKINS-58219 Active Choices Reactive Parameter Groovy script returning String instead of List Change By: Brett Hand I have an Active Choices parameter defined: It is an Active Choices Reactive parameter, where I am simply returning a list of character strings via the Groovy script (i.e: return ['example1','example2']) that will be used to create some check boxes. I notice from the documentation that the way I have formatted this should return an List. I have also verified that this does return an List in a Groovy web console.Now, the problem occurs when I attempt to index the list List later on in my Jenkinsfile. If my list List contained ["example1","example2"], then list[0] would return "e" instead of "example1". It looked like my list List was actually a String instead. I debugged the parameter and found that it actually was a String type.I am wondering why my parameter is being returned as a String instead of a list List , as it appears that the way I have set it up should return a list List , which I should then be able to index. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-58219) Active Choices Reactive Parameter Groovy script returning String instead of List
Title: Message Title Brett Hand updated an issue Jenkins / JENKINS-58219 Active Choices Reactive Parameter Groovy script returning String instead of List Change By: Brett Hand I have an Active Choices parameter defined: It is an Active Choices Reactive parameter, where I am simply returning a list of character strings via the Groovy script (i.e: return ['example1','example2']) that will be used to create some check boxes. I notice from the documentation that the way I have formatted this should return an ArrayList List . I have also verified that this does return an ArrayList List in a Groovy web console.Now, the problem occurs when I attempt to index the list later on in my Jenkinsfile. If my list contained ["example1","example2"], then list[0] would return "e" instead of "example1". It looked like my list was actually a String instead. I debugged the parameter and found that it actually was a String type.I am wondering why my parameter is being returned as a String instead of a list, as it appears that the way I have set it up should return a list, which I should then be able to index. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-58219) Active Choices Reactive Parameter Groovy script returning String instead of List
Title: Message Title Brett Hand commented on JENKINS-58219 Re: Active Choices Reactive Parameter Groovy script returning String instead of List I also suspected the parameter was actually a String because I was able to use the tokenize() method on it. I would not be able to do this if the returned parameter were a List. 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.200279.1561574404000.10002.1561575000200%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58219) Active Choices Reactive Parameter Groovy script returning String instead of List
Title: Message Title Brett Hand updated an issue Jenkins / JENKINS-58219 Active Choices Reactive Parameter Groovy script returning String instead of List Change By: Brett Hand I have an Active Choices parameters parameter defined: It is an Active Choices Reactive parameter, where I am simply returning a list of character strings via the Groovy script (i.e: return ['example1','example2']) that will be used to create some check boxes. I notice from the documentation that the way I have formatted this should return an ArrayList. I have also verified that this does return an ArrayList in a Groovy web console.Now, the problem occurs when I attempt to index the list later on in my Jenkinsfile. If my list contained ["example1","example2"], then list[0] would return "e" instead of "example1". It looked like my list was actually a String instead. I debugged the parameter and found that it actually was a String type. I am wondering why my parameter is being returned as a String instead of a list, as it appears that the way I have set it up should return a list, which I should then be able to index. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-58219) Active Choices Reactive Parameter Groovy script returning String instead of List
Title: Message Title Brett Hand created an issue Jenkins / JENKINS-58219 Active Choices Reactive Parameter Groovy script returning String instead of List Issue Type: Bug Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 2019-06-26 18:40 Environment: Active Choices plugin version 2.1 Jenkins version 2.164.1 Labels: jenkins pipeline plugins Priority: Minor Reporter: Brett Hand I have an Active Choices parameters defined: It is an Active Choices Reactive parameter, where I am simply returning a list of character strings via the Groovy script (i.e: return ['example1','example2']) that will be used to create some check boxes. I notice from the documentation that the way I have formatted this should return an ArrayList. I have also verified that this does return an ArrayList in a Groovy web console. Now, the problem occurs when I attempt to index the list later on in my Jenkinsfile. If my list contained ["example1","example2"], then list[0] would return "e" instead of "example1". It looked like my list was actually a String instead. I debugged the parameter and found that it actually was a String type. I am wondering why my parameter is being returned as a String instead of a list, as it appears that the way I have set it up should return a list, which I should then be able to index.
[JIRA] (JENKINS-57967) vSphere Cloud: java.lang.NoSuchMethodError in SSHLauncher
Title: Message Title Nick Jones commented on JENKINS-57967 Re: vSphere Cloud: java.lang.NoSuchMethodError in SSHLauncher Ah, I see the issue. The SSHLauncher constructor used by vSphereCloudSlaveTemplate.java is what was removed in https://github.com/jenkinsci/ssh-slaves-plugin/pull/114/commits/471fcbea57429022e457c723923a40a5519a2f1e#diff-80fc627a638d10d5056a52e20a13d8cb. That means we'll need a new build of the vSphere Cloud plugin that uses the remaining constructor (adding a SshHostKeyVerificationStrategy argument). 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.199950.1560271877000.9996.1561573862155%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58218) Support JCasC
Title: Message Title Long Nguyen created an issue Jenkins / JENKINS-58218 Support JCasC Issue Type: New Feature Assignee: Pham Vu Tuan Components: remoting-kafka-plugin Created: 2019-06-26 18:07 Labels: gsoc-2019 Priority: Minor Reporter: Long Nguyen 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
[JIRA] (JENKINS-58216) Issues with Failed Download Output File in Docker
Title: Message Title Tim Jacomb commented on JENKINS-58216 Re: Issues with Failed Download Output File in Docker I would just collect all failed plugins, print them at the end and do System.exit(1) so it exits as a failure 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.200276.156156802.9988.1561571940150%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58206) Default directory for failed plugins
Title: Message Title Tim Jacomb commented on JENKINS-58206 Re: Default directory for failed plugins Why not just output it to stdout / stderr? and then exit with a non 0 code When another output mode (such as json) is added you could add a field in that for failed 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.200265.1561539742000.9986.1561571700110%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58075) Create demo for end of Phase 1 coding period
Title: Message Title Natasha Stopa updated JENKINS-58075 Presentation recorded here: https://www.youtube.com/watch?v=MDs0Vr7gnnA Jenkins / JENKINS-58075 Create demo for end of Phase 1 coding period Change By: Natasha Stopa Status: In Review 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.200099.1560871996000.9984.1561570320205%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27413) Handle file parameters
Title: Message Title
Chris Frolik edited a comment on JENKINS-27413
Re: Handle file parameters
{quote} "I am not particularly inclined to fix this per se" {quote} That is very disappointing, and a stumbling block for those trying to convert their freestyle jobs to declarative pipeline jobs. I really hope you change your mind on this.At the very least, the documentation should mention that it isn't supported.
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.161212.1426248363000.9887.1561569545251%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58217) Support Maven repository as an installation source
Title: Message Title Natasha Stopa created an issue Jenkins / JENKINS-58217 Support Maven repository as an installation source Issue Type: Task Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-06-26 17:18 Labels: plugin-manager gsoc Priority: Minor Reporter: Natasha Stopa Supporting Maven repository as an installation source was feedback given in the Phase 1 presentation. Related to: https://issues.jenkins-ci.org/browse/JENKINS-58147 Add Comment
[JIRA] (JENKINS-27413) Handle file parameters
Title: Message Title Chris Frolik commented on JENKINS-27413 Re: Handle file parameters "I am not particularly inclined to fix this per se" That is very disappointing, and a stumbling block for those trying to convert their freestyle jobs to declarative pipeline jobs. I really hope you change your mind on this. At the very least, the documentation should mention that it isn't supported. 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.161212.1426248363000.9790.1561569543293%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58215) Coloring breaks timestamp output in Declarative Pipeline (NOT Blueocean)
Title: Message Title Jesse Glick commented on JENKINS-58215 Re: Coloring breaks timestamp output in Declarative Pipeline (NOT Blueocean) Probably. Maybe due to multiline (unterminated) ANSI sequences? Would be helpful to have a script to reproduce from scratch, e.g. using echo with format. 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.200275.1561560107000.9787.1561568520093%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58215) Coloring breaks timestamp output in Declarative Pipeline (NOT Blueocean)
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-58215 Coloring breaks timestamp output in Declarative Pipeline (NOT Blueocean) Change By: Jesse Glick Assignee: Andrew Bayer 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.200275.1561560107000.9785.1561568460170%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58216) Issues with Failed Download Output File in Docker
Title: Message Title Natasha Stopa updated an issue Jenkins / JENKINS-58216 Issues with Failed Download Output File in Docker Change By: Natasha Stopa When running the plugin management jar in Docker, the following error is thrown:java.io.FileNotFoundException: failedplugins.txt (Permission denied)I tried copying an empty failedplugins file into the image using a COPY command in the Dockerfile, but I'm not sure if I'm copying the file to the wrong location or if there's some other issue with permissions . 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.200276.156156802.9782.1561568400193%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58216) Issues with Failed Download Output File in Docker
Title: Message Title Natasha Stopa updated an issue Jenkins / JENKINS-58216 Issues with Failed Download Output File in Docker Change By: Natasha Stopa When running the plugin management jar in Docker, the following error is thrown: java. lang io . reflect.InaccessibleObjectException FileNotFoundException : Unable to make boolean jdk failedplugins . nio.zipfs.ZipFileSystem.isDirectory txt ( byte[] Permission denied ) throws java.io.IOException accessible: module jdk.zipfs does not "opens jdk.nio.zipfs" I tried copying an empty faildplugins file into the image using a COPY command in the Dockerfile, but I'm not sure if I'm copying the file to the wrong location or if there's some other 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.200276.156156802.9780.1561568340095%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58216) Issues with Failed Download Output File in Docker
Title: Message Title Natasha Stopa updated an issue Jenkins / JENKINS-58216 Issues with Failed Download Output File in Docker Change By: Natasha Stopa When running the plugin management jar in Docker, the following error is thrown:java.io.FileNotFoundException: failedplugins.txt (Permission denied) I tried copying an empty faildplugins failedplugins file into the image using a COPY command in the Dockerfile, but I'm not sure if I'm copying the file to the wrong location or if there's some other 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.200276.156156802.9781.1561568340133%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58216) Issues with Failed Download Output File in Docker
Title: Message Title Natasha Stopa created an issue Jenkins / JENKINS-58216 Issues with Failed Download Output File in Docker Issue Type: Task Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-06-26 16:53 Labels: gsoc-2019 plugin-manager docker Priority: Minor Reporter: Natasha Stopa When running the plugin management jar in Docker, the following error is thrown: java.lang.reflect.InaccessibleObjectException: Unable to make boolean jdk.nio.zipfs.ZipFileSystem.isDirectory(byte[]) throws java.io.IOException accessible: module jdk.zipfs does not "opens jdk.nio.zipfs" I tried copying an empty faildplugins file into the image using a COPY command in the Dockerfile, but I'm not sure if I'm copying the file to the wrong location or if there's some other issue. Add Comment
[JIRA] (JENKINS-58061) Can't configure SonarQube User Token (text field replaced with credentials drop-down).
Title: Message Title alexis villegas edited a comment on JENKINS-58061 Re: Can't configure SonarQube User Token (text field replaced with credentials drop-down). Same Issue...I was looking to add a new credential for sonarqube like I did for SSH but there is no option for that. EDIT: I follow the configuration for this url [https://groups.google.com/forum/#!topic/jenkinsci-users/ONnVPSIExH4] basically on the credentials page you have to add the token as secret text and give it an ID. after that the ID will show up on the dropdown for sonarqube token option. 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.200082.1560824562000.9778.1561567800086%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58061) Can't configure SonarQube User Token (text field replaced with credentials drop-down).
Title: Message Title alexis villegas commented on JENKINS-58061 Re: Can't configure SonarQube User Token (text field replaced with credentials drop-down). Same Issue...I was looking to add a new credential for sonarqube like I did for SSH but there is no option for that. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200082.1560824562000.9776.1561567500121%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58205) GenerateTestHpl task should be reusable and declare its inputs and dependencies
Title: Message Title Steve Hill commented on JENKINS-58205 Re: GenerateTestHpl task should be reusable and declare its inputs and dependencies Marc Philipp sounds good to me! Feel free to send in a PR. 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.200264.1561537667000.9770.1561565580112%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48812) Developer guide for gradle-jpi-plugin
Title: Message Title Steve Hill closed an issue as Won't Do Trying to move this plugin in a direction of leveraging standard gradle features and encouraging gradle's official docs over creating a developer guide that is likely to get out of date very quickly for this plugin. Jenkins / JENKINS-48812 Developer guide for gradle-jpi-plugin Change By: Steve Hill Status: In Progress 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.187592.1515140273000.9768.1561565520382%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35107) ec2 plugin documentation states that Windows is unsupported, is it?
Title: Message Title Raihaan Shouhell resolved as Fixed Windows is supported and the docs was updated at somepoint Jenkins / JENKINS-35107 ec2 plugin documentation states that Windows is unsupported, is it? Change By: Raihaan Shouhell 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.170791.1464120337000.9765.1561565280471%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32469) Allow falling back to on demand when spot prices are higher then limit.
Title: Message Title Raihaan Shouhell commented on JENKINS-32469 Re: Allow falling back to on demand when spot prices are higher then limit. This should be resolved in the latest version could people test that Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.167599.1452832858000.9757.1561565040410%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25832) Launch multiple slaves in parallel for jobs with same node label
Title: Message Title Raihaan Shouhell resolved as Fixed This has already been fixed in 1.40 Jenkins / JENKINS-25832 Launch multiple slaves in parallel for jobs with same node label Change By: Raihaan Shouhell Status: Reopened 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.159407.1417258326000.9729.1561564802313%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58215) Coloring breaks timestamp output in Declarative Pipeline (NOT Blueocean)
Title: Message Title Jakub Bochenski updated an issue Jenkins / JENKINS-58215 Coloring breaks timestamp output in Declarative Pipeline (NOT Blueocean) Change By: Jakub Bochenski Environment: Jenkins ver. 2.176.1Timestamper 1.9AnsiColor 0.6.2Pipeline: Declarative 1.3.9 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.200275.1561560107000.9726.1561564500875%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54723) EC2 Plugin: Include tags in created EBS volumes
Title: Message Title Raihaan Shouhell resolved as Fixed Fixed in 1.44 Jenkins / JENKINS-54723 EC2 Plugin: Include tags in created EBS volumes Change By: Raihaan Shouhell Status: Reopened Resolved Resolution: Fixed Released As: 1.44 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.195525.1542713511000.9724.1561564500815%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58024) Upgrading the EC2 Plugin to v1.43 causes all agents to be terminated due to maxTotalUses
Title: Message Title Raihaan Shouhell updated JENKINS-58024 Fixed in 1.44.1 Jenkins / JENKINS-58024 Upgrading the EC2 Plugin to v1.43 causes all agents to be terminated due to maxTotalUses Change By: Raihaan Shouhell Status: In Review Resolved Resolution: Fixed Released As: 1.44.1 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.200044.156053795.9718.1561564440212%40Atlassian.JIRA. For more options,
