[JIRA] (JENKINS-53356) Scriptlet 'ViewScript' link and Required Parameters not displayed in configuration
Title: Message Title Bruno P. Kinoshita updated JENKINS-53356 Jenkins / JENKINS-53356 Scriptlet 'ViewScript' link and Required Parameters not displayed in configuration Change By: Bruno P. Kinoshita Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53356) Scriptlet 'ViewScript' link and Required Parameters not displayed in configuration
Title: Message Title Bruno P. Kinoshita commented on JENKINS-53356 Re: Scriptlet 'ViewScript' link and Required Parameters not displayed in configuration Fixed! Think so at least 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53356) Scriptlet 'ViewScript' link and Required Parameters not displayed in configuration
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-53356 Scriptlet 'ViewScript' link and Required Parameters not displayed in configuration Change By: Bruno P. Kinoshita Attachment: Screenshot from 2019-03-02 20-03-03.png Attachment: Screenshot from 2019-03-02 20-36-24.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54406) [JEP-200] Failed to serialize class
Title: Message Title Juncheol Cho commented on JENKINS-54406 Re: [JEP-200] Failed to serialize class same 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55497) BlueOcean Pipeline View for the Latest Run shows No Changes
Title: Message Title Stuart Rowe commented on JENKINS-55497 Re: BlueOcean Pipeline View for the Latest Run shows No Changes In progress: https://github.com/jenkinsci/blueocean-plugin/pull/1919 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55497) BlueOcean Pipeline View for the Latest Run shows No Changes
Title: Message Title Stuart Rowe assigned an issue to Stuart Rowe Jenkins / JENKINS-55497 BlueOcean Pipeline View for the Latest Run shows No Changes Change By: Stuart Rowe Assignee: Stuart Rowe 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55497) BlueOcean Pipeline View for the Latest Run shows No Changes
Title: Message Title Stuart Rowe started work on JENKINS-55497 Change By: Stuart Rowe 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55697) NegotiateSSO Plugin is not compatible with SECURITY-901 FIX (Upgrading to 2.160/2.150.2)
Title: Message Title Bryson Gibbons commented on JENKINS-55697 Re: NegotiateSSO Plugin is not compatible with SECURITY-901 FIX (Upgrading to 2.160/2.150.2) So, if some of you want to also test the changes, you should be able to download a snapshot build from https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fnegotiatesso-plugin/detail/PR-2/1/artifacts (I don't know when the artifacts will expire) 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55697) NegotiateSSO Plugin is not compatible with SECURITY-901 FIX (Upgrading to 2.160/2.150.2)
Title: Message Title Bryson Gibbons started work on JENKINS-55697 Change By: Bryson Gibbons 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54170) Kubernetes agent does not connect on first several attempts
Title: Message Title
John Jeffers updated an issue
Jenkins / JENKINS-54170
Kubernetes agent does not connect on first several attempts
Change By:
John Jeffers
Comment:
I could never find a network issue, but I have noticed that behavior has changed with the latest version of the plugin (specifically, version 1.14.6). Now, instead of a constant stream of failed connection messages, it instead keep spinning up pods until one of them finally accepts the job. In one recent run, it created 9 of the same pod, finally ran the job on one, then eventually terminated all of the pods it didn't need.{code:java}Mar 02, 2019 4:13:04 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Excess workload after pending Kubernetes agents: 1Mar 02, 2019 4:13:04 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Template for label jfrog-cli-go: Kubernetes Pod TemplateMar 02, 2019 4:13:04 AM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path?Mar 02, 2019 4:13:04 AM hudson.slaves.NodeProvisioner$StandardStrategyImpl applyINFO: Started provisioning Kubernetes Pod Template from common-operations with 1 executors. Remaining excess workload: 0Mar 02, 2019 4:13:14 AM hudson.slaves.NodeProvisioner$2 runINFO: Kubernetes Pod Template provisioning successfully completed. We have now 2 computer(s)Mar 02, 2019 4:13:14 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Created Pod: jfrog-cli-go-rb88g-p7n9q in namespace jenkinsMar 02, 2019 4:13:14 AM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path?Mar 02, 2019 4:13:24 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Excess workload after pending Kubernetes agents: 1Mar 02, 2019 4:13:24 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Template for label jfrog-cli-go: Kubernetes Pod TemplateMar 02, 2019 4:13:24 AM hudson.slaves.NodeProvisioner$StandardStrategyImpl applyINFO: Started provisioning Kubernetes Pod Template from common-operations with 1 executors. Remaining excess workload: 0Mar 02, 2019 4:13:34 AM hudson.slaves.NodeProvisioner$2 runINFO: Kubernetes Pod Template provisioning successfully completed. We have now 3 computer(s)Mar 02, 2019 4:13:34 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Created Pod: jfrog-cli-go-rb88g-96jd0 in namespace jenkinsMar 02, 2019 4:13:34 AM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path?Mar 02, 2019 4:13:44 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Excess workload after pending Kubernetes agents: 1Mar 02, 2019 4:13:44 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Template for label jfrog-cli-go: Kubernetes Pod TemplateMar 02, 2019 4:13:44 AM hudson.slaves.NodeProvisioner$StandardStrategyImpl applyINFO: Started provisioning Kubernetes Pod Template from common-operations with 1 executors. Remaining excess workload: 0Mar 02, 2019 4:13:54 AM hudson.slaves.NodeProvisioner$2 runINFO: Kubernetes Pod Template provisioning successfully completed. We hav
[JIRA] (JENKINS-54170) Kubernetes agent does not connect on first several attempts
Title: Message Title
John Jeffers edited a comment on JENKINS-54170
Re: Kubernetes agent does not connect on first several attempts
I could never find a network issue, but I have noticed that behavior has changed with the latest version (s) of the plugin (specifically, version 1 . 14.6). Now, instead of a constant stream of failed connection messages, it instead keep spinning up pods until one of them finally accepts the job. In one recent run, it created 9 of the same pod, finally ran the job on one, then eventually terminated all of the pods it didn't need.{code:java}Mar 02, 2019 4:13:04 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Excess workload after pending Kubernetes agents: 1Mar 02, 2019 4:13:04 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Template for label jfrog-cli-go: Kubernetes Pod TemplateMar 02, 2019 4:13:04 AM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path?Mar 02, 2019 4:13:04 AM hudson.slaves.NodeProvisioner$StandardStrategyImpl applyINFO: Started provisioning Kubernetes Pod Template from common-operations with 1 executors. Remaining excess workload: 0Mar 02, 2019 4:13:14 AM hudson.slaves.NodeProvisioner$2 runINFO: Kubernetes Pod Template provisioning successfully completed. We have now 2 computer(s)Mar 02, 2019 4:13:14 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Created Pod: jfrog-cli-go-rb88g-p7n9q in namespace jenkinsMar 02, 2019 4:13:14 AM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path?Mar 02, 2019 4:13:24 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Excess workload after pending Kubernetes agents: 1Mar 02, 2019 4:13:24 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Template for label jfrog-cli-go: Kubernetes Pod TemplateMar 02, 2019 4:13:24 AM hudson.slaves.NodeProvisioner$StandardStrategyImpl applyINFO: Started provisioning Kubernetes Pod Template from common-operations with 1 executors. Remaining excess workload: 0Mar 02, 2019 4:13:34 AM hudson.slaves.NodeProvisioner$2 runINFO: Kubernetes Pod Template provisioning successfully completed. We have now 3 computer(s)Mar 02, 2019 4:13:34 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Created Pod: jfrog-cli-go-rb88g-96jd0 in namespace jenkinsMar 02, 2019 4:13:34 AM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path?Mar 02, 2019 4:13:44 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Excess workload after pending Kubernetes agents: 1Mar 02, 2019 4:13:44 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Template for label jfrog-cli-go: Kubernetes Pod TemplateMar 02, 2019 4:13:44 AM hudson.slaves.NodeProvisioner$StandardStrategyImpl applyINFO: Started provisioning Kubernetes Pod Template from common-operations with 1 executors. Remaining excess workload: 0Mar 02, 2019 4:13:54 AM hudson.slaves.NodeProvisioner$2 runINFO: Kubernetes Pod Template provisioning successfully completed. We have now 4 computer(s)Mar 02, 2019 4:13:54 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Created Pod: jfrog-cli-go-rb88g-j7qmx in namespace jenkinsMar 02, 2019 4:13:54 AM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path?Mar 02, 2019 4:14:00 AM com.squareup.okhttp.internal.Platform$JdkWithJettyBootPlatform getSelectedProtocolINFO: ALPN callbac
[JIRA] (JENKINS-54170) Kubernetes agent does not connect on first several attempts
Title: Message Title
John Jeffers edited a comment on JENKINS-54170
Re: Kubernetes agent does not connect on first several attempts
I could never find a network issue, but I have noticed that behavior has changed with the latest version(s) of the plugin. Now, instead of a constant stream of failed connection messages, it instead keep spinning up pods until one of them finally accepts the job. In one recent run, it created 9 of the same pod, finally ran the job on one, then eventually terminated all of the pods it didn't need. { {``` code:java} Mar 02, 2019 4:13:04 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision }} {{ INFO: Excess workload after pending Kubernetes agents: 1 }} {{ Mar 02, 2019 4:13:04 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision }} {{ INFO: Template for label jfrog-cli-go: Kubernetes Pod Template }} {{ Mar 02, 2019 4:13:04 AM okhttp3.internal.platform.Platform log }} {{ INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path? }} {{ Mar 02, 2019 4:13:04 AM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply }} {{ INFO: Started provisioning Kubernetes Pod Template from common-operations with 1 executors. Remaining excess workload: 0 }} {{ Mar 02, 2019 4:13:14 AM hudson.slaves.NodeProvisioner$2 run }} {{ INFO: Kubernetes Pod Template provisioning successfully completed. We have now 2 computer(s) }} {{ Mar 02, 2019 4:13:14 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch }} {{ INFO: Created Pod: jfrog-cli-go-rb88g-p7n9q in namespace jenkins }} {{ Mar 02, 2019 4:13:14 AM okhttp3.internal.platform.Platform log }} {{ INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path? }} {{ Mar 02, 2019 4:13:24 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision }} {{ INFO: Excess workload after pending Kubernetes agents: 1 }} {{ Mar 02, 2019 4:13:24 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision }} {{ INFO: Template for label jfrog-cli-go: Kubernetes Pod Template }} {{ Mar 02, 2019 4:13:24 AM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply }} {{ INFO: Started provisioning Kubernetes Pod Template from common-operations with 1 executors. Remaining excess workload: 0 }} {{ Mar 02, 2019 4:13:34 AM hudson.slaves.NodeProvisioner$2 run }} {{ INFO: Kubernetes Pod Template provisioning successfully completed. We have now 3 computer(s) }} {{ Mar 02, 2019 4:13:34 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch }} {{ INFO: Created Pod: jfrog-cli-go-rb88g-96jd0 in namespace jenkins }} {{ Mar 02, 2019 4:13:34 AM okhttp3.internal.platform.Platform log }} {{ INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path? }} {{ Mar 02, 2019 4:13:44 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision }} {{ INFO: Excess workload after pending Kubernetes agents: 1 }} {{ Mar 02, 2019 4:13:44 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision }} {{ INFO: Template for label jfrog-cli-go: Kubernetes Pod Template }} {{ Mar 02, 2019 4:13:44 AM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply }} {{ INFO: Started provisioning Kubernetes Pod Template from common-operations with 1 executors. Remaining excess workload: 0 }} {{ Mar 02, 2019 4:13:54 AM hudson.slaves.NodeProvisioner$2 run }} {{ INFO: Kubernetes Pod Template provisioning successfully completed. We have now 4 computer(s) }} {{ Mar 02, 2019 4:13:54 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch }} {{ INFO: Created Pod: jfrog-cli-go-rb88g-j7qmx in namespace jenkins }} {{ Mar 02, 201
[JIRA] (JENKINS-54170) Kubernetes agent does not connect on first several attempts
Title: Message Title John Jeffers commented on JENKINS-54170 Re: Kubernetes agent does not connect on first several attempts I could never find a network issue, but I have noticed that behavior has changed with the latest version(s) of the plugin. Now, instead of a constant stream of failed connection messages, it instead keep spinning up pods until one of them finally accepts the job. In one recent run, it created 9 of the same pod, finally ran the job on one, then eventually terminated all of the pods it didn't need. ```Mar 02, 2019 4:13:04 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Excess workload after pending Kubernetes agents: 1 Mar 02, 2019 4:13:04 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Template for label jfrog-cli-go: Kubernetes Pod Template Mar 02, 2019 4:13:04 AM okhttp3.internal.platform.Platform log INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path? Mar 02, 2019 4:13:04 AM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply INFO: Started provisioning Kubernetes Pod Template from common-operations with 1 executors. Remaining excess workload: 0 Mar 02, 2019 4:13:14 AM hudson.slaves.NodeProvisioner$2 run INFO: Kubernetes Pod Template provisioning successfully completed. We have now 2 computer(s) Mar 02, 2019 4:13:14 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Created Pod: jfrog-cli-go-rb88g-p7n9q in namespace jenkins Mar 02, 2019 4:13:14 AM okhttp3.internal.platform.Platform log INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path? Mar 02, 2019 4:13:24 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Excess workload after pending Kubernetes agents: 1 Mar 02, 2019 4:13:24 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Template for label jfrog-cli-go: Kubernetes Pod Template Mar 02, 2019 4:13:24 AM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply INFO: Started provisioning Kubernetes Pod Template from common-operations with 1 executors. Remaining excess workload: 0 Mar 02, 2019 4:13:34 AM hudson.slaves.NodeProvisioner$2 run INFO: Kubernetes Pod Template provisioning successfully completed. We have now 3 computer(s) Mar 02, 2019 4:13:34 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Created Pod: jfrog-cli-go-rb88g-96jd0 in namespace jenkins Mar 02, 2019 4:13:34 AM okhttp3.internal.platform.Platform log INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path? Mar 02, 2019 4:13:44 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Excess workload after pending Kubernetes agents: 1 Mar 02, 2019 4:13:44 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Template for label jfrog-cli-go: Kubernetes Pod Template Mar 02, 2019 4:13:44 AM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply INFO: Started provisioning Kubernetes Pod Template from common-operations with 1 executors. Remaining excess workload: 0 Mar 02, 2019 4:13:54 AM hudson.slaves.NodeProvisioner$2 run INFO: Kubernetes Pod Template provisioning successfully completed. We have now 4 computer(s) Mar 02, 2019 4:13:54 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Created Pod: jfrog-cli-go-rb88g-j7qmx in namespace jenkins Mar 02, 2019 4:13:54 AM okhttp3.internal.platform.Platform log INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path? Mar 02, 2019 4:14:00 AM com.squareup.okhttp.internal.Platform$JdkWithJettyBootPlatform getSelectedProtocol INFO: ALPN callback dropped: S
[JIRA] (JENKINS-46606) Stash-pullrequest-builder-plugin describes the job with verbatim HTML markup
Title: Message Title Pavel Roskin commented on JENKINS-46606 Re: Stash-pullrequest-builder-plugin describes the job with verbatim HTML markup I don't see any issues with the text posted to the Stash PR pages. The job descriptions in Jenkins GUI are indeed not rendered by default. To make them show correctly, install "OWASP Markup Formatter Plugin" and enable HTML markup in Manage Jenkins -> Configure Global Security. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55853) Customized Post Build Comment ignored for multi-configuration projects
Title: Message Title Pavel Roskin updated an issue Jenkins / JENKINS-55853 Customized Post Build Comment ignored for multi-configuration projects Change By: Pavel Roskin URL: https://github.com/jenkinsci/stash-pullrequest-builder-plugin/pull/43 Labels: configuration matrix stash 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56071) Workflow job support
Title: Message Title Pavel Roskin commented on JENKINS-56071 Re: Workflow job support JENKINS-56349 should take care of the crash issue. The rest of the PR #21 should be updated for the current code. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56349) Stash Pull Request Builder can throw in StashBuildTrigger#run
Title: Message Title Pavel Roskin updated an issue Jenkins / JENKINS-56349 Stash Pull Request Builder can throw in StashBuildTrigger#run Change By: Pavel Roskin Labels: NPE stash trigger 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56337) Stash Pull Request Builder ignores quiet time
Title: Message Title Pavel Roskin updated an issue Jenkins / JENKINS-56337 Stash Pull Request Builder ignores quiet time Change By: Pavel Roskin Issue Type: New Feature Bug URL: https://github.com/jenkinsci/stash-pullrequest-builder-plugin/pull/46 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56349) Stash Pull Request Builder can throw in StashBuildTrigger#run
Title: Message Title Pavel Roskin updated an issue Jenkins / JENKINS-56349 Stash Pull Request Builder can throw in StashBuildTrigger#run Change By: Pavel Roskin URL: https://github.com/jenkinsci/stash-pullrequest-builder-plugin/pull/48 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56349) Stash Pull Request Builder can throw in StashBuildTrigger#run
Title: Message Title Pavel Roskin updated JENKINS-56349 Jenkins / JENKINS-56349 Stash Pull Request Builder can throw in StashBuildTrigger#run Change By: Pavel Roskin 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56349) Stash Pull Request Builder can throw in StashBuildTrigger#run
Title: Message Title Pavel Roskin updated an issue Jenkins / JENKINS-56349 Stash Pull Request Builder can throw in StashBuildTrigger#run Change By: Pavel Roskin Issue Type: New Feature Bug 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56349) Stash Pull Request Builder can throw in StashBuildTrigger#run
Title: Message Title Pavel Roskin started work on JENKINS-56349 Change By: Pavel Roskin 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56149) Copy artifact fails on first pipeline run with buildParameter selector
Title: Message Title
Ryan Desmond edited a comment on JENKINS-56149
Re: Copy artifact fails on first pipeline run with buildParameter selector
Thank you for looking into this and noting that!I did find this to be a weird gotcha, since the documentation suggests that the other way would work (and outside of the first run – it does). Might you consider noting this gotcha in the help and/or readme? The documentation suggests that it these items are interchangeable, and with the recent development on pipelines, I would think more people would will hit this.For instance, in the help: {noformat}A "build selector" parameter's name or value. A special parameter type existswhich presents the user with selector options.If using the name, it must match the parameter name in the properties.In a pipeline and with the workflow-plugin you can use the parameter value itself.This is necessary in pipelines with dynamically created parameters, in whichthe defaults are not available during the first run when using the parameter's name.{noformat}And then in the wiki at [https://wiki.jenkins.io/display/JENKINS/Copy+Artifact+Plugin#CopyArtifactPlugin-Pipelinesyntax]|buildParameter|Specified by a build parameter value (such as params.VALUE)||lastCompleted|completed build (ignoring build status)||lastSuccessful|Latest successful build||latestSavedBuild|Latest saved build (marked "keep forever")||permalink|Specified by permalink||specific|Specific build||upstream|Upstream build that triggered this job|
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56149) Copy artifact fails on first pipeline run with buildParameter selector
Title: Message Title
Ryan Desmond edited a comment on JENKINS-56149
Re: Copy artifact fails on first pipeline run with buildParameter selector
Thank you for looking into this and noting that!I did find this to be a weird gotcha, since the documentation suggests that the other way would work (and outside of the first run – it does). Might you consider noting this gotcha in the help and/or readme? The documentation suggests that it these items are interchangeable, and with the recent development on pipelines, I would think more people would hit this.For instance, in the help: {noformat}A "build selector" parameter's name or value. A special parameter type existswhich presents the user with selector options.If using the name, it must match the parameter name in the properties.In a pipeline and with the workflow-plugin you can use the parameter value itself.This is necessary in pipelines with dynamically created parameters, in whichthe defaults are not available during the first run when using the parameter's name.{noformat}And then in the wiki at [https://wiki.jenkins.io/display/JENKINS/Copy+Artifact+Plugin#CopyArtifactPlugin-Pipelinesyntax]|buildParameter|Specified by a build parameter value (such as params.VALUE)||lastCompleted|completed build (ignoring build status)||lastSuccessful|Latest successful build||latestSavedBuild|Latest saved build (marked "keep forever")||permalink|Specified by permalink||specific|Specific build||upstream|Upstream build that triggered this job|
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56149) Copy artifact fails on first pipeline run with buildParameter selector
Title: Message Title Ryan Desmond commented on JENKINS-56149 Re: Copy artifact fails on first pipeline run with buildParameter selector Thank you for looking into this and noting that! I did find this to be a weird gotcha, since the documentation suggests that the other way would work (and outside of the first run – it does). Might you consider noting this gotcha in the help and/or readme? The documentation suggests that it these items are interchangeable, and with the recent development on pipelines, I would think more people would hit this. For instance, in the help: A "build selector" parameter's name or value. A special parameter type exists which presents the user with selector options. If using the name, it must match the parameter name in the properties. In a pipeline and with the workflow-plugin you can use the parameter value itself. This is necessary in pipelines with dynamically created parameters, in which the defaults are not available during the first run when using the parameter's name. And then in the wiki at https://wiki.jenkins.io/display/JENKINS/Copy+Artifact+Plugin#CopyArtifactPlugin-Pipelinesyntax buildParameter Specified by a build parameter value (such as params.VALUE) lastCompleted completed build (ignoring build status) lastSuccessful Latest successful build latestSavedBuild Latest saved build (marked "keep forever") permalink Specified by permalink specific Specific build
[JIRA] (JENKINS-55150) [jenkins-dev] jenkins-dev:run no longer has hot reload after 2.152
Title: Message Title Daniel Beck commented on JENKINS-55150 Re: [jenkins-dev] jenkins-dev:run no longer has hot reload after 2.152 Workaround seems to be running: mvn org.jenkins-ci.tools:maven-jenkins-dev-plugin:9.4.5.v20170502-jenkins-1:run 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56149) Copy artifact fails on first pipeline run with buildParameter selector
Title: Message Title ikedam updated JENKINS-56149 Pass the parameter value, not the parameter name, like: selector: buildParameter(params.UPSTREAM) Please also see the help of parameterName: https://github.com/jenkinsci/copyartifact-plugin/blob/master/src/main/resources/hudson/plugins/copyartifact/ParameterizedBuildSelector/help-parameterName.html Jenkins / JENKINS-56149 Copy artifact fails on first pipeline run with buildParameter selector Change By: ikedam Status: Open Fixed but Unreleased Assignee: Ryan Desmond Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-s
[JIRA] (JENKINS-35417) Support "last exist" condition.
Title: Message Title ikedam updated JENKINS-35417 feng yu (cc: Chad Gilman) Released copyartifact-1.42. It will be available in the update center in a day. Jenkins / JENKINS-35417 Support "last exist" condition. Change By: ikedam Status: In Review Resolved Assignee: ikedam feng yu Resolution: Fixed Released As: copyartifact-1.42 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
[JIRA] (JENKINS-56305) Need some help with init scripts on this plugin
Title: Message Title Naresh Rayapati commented on JENKINS-56305 Re: Need some help with init scripts on this plugin Thank you Dominik Bartholdi, we have created an ecosystem internally such that there is dependency on these startup scripts. It was a small mistake caught me into this problem, I was using duplicate ids in the config, which is replacing the other config. Thank you again. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33455) Option to disable echo of executed commands
Title: Message Title
Maciej Jaros edited a comment on JENKINS-33455
Re: Option to disable echo of executed commands
I don't want the commands from {{Publish over SSH}} step to be shown in Jenkins job log.Commands which should not be shown because they can contains password contain passwords or because they are simply long and confusing.
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33455) Option to disable echo of executed commands
Title: Message Title Maciej Jaros commented on JENKINS-33455 Re: Option to disable echo of executed commands I don't want the commands from Publish over SSH step to be shown in Jenkins job log. Commands which should not be shown because they can contains password or because they are simply long and confusing. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53539) org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled
Title: Message Title Keith Yates commented on JENKINS-53539 Re: org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled This continues to occur. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47724) Pipeline with parallel jobs performance issue with EC2 slaves
Title: Message Title Mike Kozell commented on JENKINS-47724 Re: Pipeline with parallel jobs performance issue with EC2 slaves Jesse Glick I added -Dorg.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep.USE_WATCHING=true but it didn't seem to make a difference. Duration Branches Running Agents Connection Type 56s 190 6 trilead SSH 8m 3s 190 192 trilead SSH I'm also seeing a spike in load at the end of the build with and without the parameter. I should probably create new issue for it. The load average went to over 25 on the VM after the date command finished. In the build log, I saw: [Pipeline] } ... Add Comment
[JIRA] (JENKINS-31507) docker.build throw IOExceptions with some sources
Title: Message Title Jesse Glick commented on JENKINS-31507 Re: docker.build throw IOExceptions with some sources The workaround would be to avoid agent dockerfile. Run on a plain agent type and run docker commands explicitly from sh. Probably it would be best to deprecate FromFingerprintStep and its kin, since the fingerprints are not actually used anywhere, and remove their calls from Docker.groovy. Alternately, the fingerprinting steps could catch and log all exceptions, never failing. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Jesse Glick commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script I am not aware of any plans to work on this issue. I tend to doubt it is fixable in the current Pipeline execution engine (workflow-cps), beyond better reporting the error. The known workaround is to split long blocks of code into distinct methods. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title Jesse Glick commented on JENKINS-49278 Re: cat command in docker agents not detected correctly Any further behavioral changes in this area are likely to be incompatible and unlikely to be entertained. withDockerContainer was designed for “tool-only” images with no particular designated entrypoint (typically falling back to bash or something), since its entire purpose is to provide a passive container—basically a predefined filesystem layout—in which you can run sh steps. Images which expect to be running a specific process like Apache are not supported. You can use withRun, or (better) just run whatever docker commands you like directly. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56273) Jenkins leaves nodes running in GCE if the termination failed
Title: Message Title Karol Lassak commented on JENKINS-56273 Re: Jenkins leaves nodes running in GCE if the termination failed It was fixed by cleaning "lost nodes", released in 1.0.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55509) "Windows Username" on configure page is replaced on "Build" value while another value was set and saved
Title: Message Title Karol Lassak commented on JENKINS-55509 Re: "Windows Username" on configure page is replaced on "Build" value while another value was set and saved I just created PR that should fix this issue.. https://github.com/jenkinsci/google-compute-engine-plugin/pull/34 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55697) NegotiateSSO Plugin is not compatible with SECURITY-901 FIX (Upgrading to 2.160/2.150.2)
Title: Message Title Bryson Gibbons commented on JENKINS-55697 Re: NegotiateSSO Plugin is not compatible with SECURITY-901 FIX (Upgrading to 2.160/2.150.2) I think I have a workable (but unconventional) solution for this. Incorporating the fix as used in the KerberosSSO plugin is not possible, since I didn't have both the user info and request available in the same method; however, the dependency that provides the authentication handling (Waffle-JNA) wraps the request using a HttpServletRequestWrapper implementation that does allow another filter to capture that information. I have implemented an update that works this way, and it appears to work without issue on the Jenkins instance I use; I'm waiting for the Jenkins-CI Jenkins instance to build that pull request 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-3404) mix LDAP and local Hudson users
Title: Message Title Jonas Julve assigned an issue to Félix Belzunce Arcos Jenkins / JENKINS-3404 mix LDAP and local Hudson users Change By: Jonas Julve Assignee: Jonas Julve 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-3404) mix LDAP and local Hudson users
Title: Message Title Jonas Julve assigned an issue to Jonas Julve Jenkins / JENKINS-3404 mix LDAP and local Hudson users Change By: Jonas Julve Assignee: Félix Belzunce Arcos Jonas Julve 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47724) Pipeline with parallel jobs performance issue with EC2 slaves
Title: Message Title Jesse Glick commented on JENKINS-47724 Re: Pipeline with parallel jobs performance issue with EC2 slaves I would check whether -Dorg.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep.USE_WATCHING=true (JENKINS-52165) has any effect in this context. But in general I do not think there is anyone actively tracking down performance issues like 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50310) Support stop GCE instance instead of Termination
Title: Message Title Rachel Yen commented on JENKINS-50310 Re: Support stop GCE instance instead of Termination I'm closing this and moving it to: https://github.com/jenkinsci/google-compute-engine-plugin/issues 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51289) Plugin does not wait for boot script to complete
Title: Message Title Rachel Yen closed an issue as Fixed Jenkins / JENKINS-51289 Plugin does not wait for boot script to complete Change By: Rachel Yen Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50759) Unable to connect to GCE using plugin
Title: Message Title Rachel Yen commented on JENKINS-50759 Re: Unable to connect to GCE using plugin Believe your GCE credentials were not set correctly. Please refer to the following guide as an example: https://cloud.google.com/solutions/using-jenkins-for-distributed-builds-on-compute-engine Closing this as we are migrating to:https://github.com/jenkinsci/google-compute-engine-plugin/issues 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55150) [jenkins-dev] jenkins-dev:run no longer has hot reload after 2.152
Title: Message Title Daniel Beck commented on JENKINS-55150 Re: [jenkins-dev] jenkins-dev:run no longer has hot reload after 2.152 During development of https://github.com/jenkinsci/jenkins/pull/3919 (parent 0dfe346c9c1ccfcc2cca54c64f2850a2a5513d1a) I noticed that the Groovy views did not reload anymore with jenkins-dev:run. Very annoying. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56353) Can't embed hyperlink into addShortText calls for groovy postbuild plugin
Title: Message Title
Adam Mathews updated an issue
Jenkins / JENKINS-56353
Can't embed hyperlink into addShortText calls for groovy postbuild plugin
Change By:
Adam Mathews
The below call for addShortText used to work for me for adding a quick link to the build test log results, but when I tried to switch to the latest version of Jenkins then the latest groovy postbuild plugin is converting the < into & l t ; (without the spaces of course) and messes up the link. Adding that test log link into the build text is EXTREMELY useful for me, so I'd love some way to tell addShortText to NOT change my < characters.manager.addShortText("Results file: index.htm, Passed: " + Integer.toString(t.pass) + ", Failed: " + Integer.toString(t.fail))
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56353) Can't embed hyperlink into addShortText calls for groovy postbuild plugin
Title: Message Title
Adam Mathews created an issue
Jenkins / JENKINS-56353
Can't embed hyperlink into addShortText calls for groovy postbuild plugin
Issue Type:
Bug
Assignee:
Stefan Wolf
Attachments:
NewJenkinsGroovyPostbuild.JPG, OldJenkinsGroovyPostbuild.JPG
Components:
groovy-postbuild-plugin
Created:
2019-03-01 21:09
Priority:
Major
Reporter:
Adam Mathews
The below call for addShortText used to work for me for adding a quick link to the build test log results, but when I tried to switch to the latest version of Jenkins the latest groovy postbuild plugin is converting the < into & l t ; (without the spaces of course) and messes up the link. Adding that test log link into the build text is EXTREMELY useful for me, so I'd love some way to tell addShortText to NOT change my < characters. manager.addShortText("Results file: index.htm, Passed: " + Integer.toString(t.pass) + ", Failed: " + Integer.toString(t.fail))
Add Comment
[JIRA] (JENKINS-56352) Blueocean input step does not respect "discover" permission
Title: Message Title Paulo Eduardo Neves created an issue Jenkins / JENKINS-56352 Blueocean input step does not respect "discover" permission Issue Type: Bug Assignee: Unassigned Attachments: image-2019-03-01-17-52-13-309.png, image-2019-03-01-17-52-35-360.png, image-2019-03-01-18-04-56-061.png Components: blueocean-plugin Created: 2019-03-01 21:05 Environment: Ubuntu, Jenkins 2.138.3 core and libraries Priority: Major Reporter: Paulo Eduardo Neves The "Discover" role is to allow the users to know that a resource exists in Jenkins. If the Anonymous User doesn't have "Read" role and have "Discover", they are asked to login. During a pipeline it is specially useful during a input step. If the Anonymous user has the "Read" role, the step fail after the Ok button is clicked. If it doesn't have, he gets a 404 error and thinks there is an error. The "Discover permission" does not work while in Blue Ocean. If the Anonymous User has the role Discover but not the Read role, both the main job page and the input page give a 404 Not Found error. Here are the failing urls of the job "teste-aprovador": http://vrt1071:8280/blue/organizations/jenkins/teste-aprovador/activity/ http://vrt1071:8280/blue/organizations/jenkins/teste-aprovador/detail/teste-aprovador/103/pipeline/ If I go to the old interface and go to the "Paused for input" build link: http://vrt1071:8280/job/teste-aprovador/104/input/ Jenkins correctly asks me to login so I can see the page. Here is the sample configuration:
[JIRA] (JENKINS-41930) manager.addShortText requires protection of characters '<' and '>'
Title: Message Title Adam Mathews commented on JENKINS-41930 Re: manager.addShortText requires protection of characters '<' and '>' Well, thanks a lot for this fix (sarcasm). I can't embed a hyperlink for my test log 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41930) manager.addShortText requires protection of characters '<' and '>'
Title: Message Title Adam Mathews edited a comment on JENKINS-41930 Re: manager.addShortText requires protection of characters '<' and '>' Well, thanks a lot for this fix (sarcasm). I can't embed a hyperlink for my test log lt l t ; Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33455) Option to disable echo of executed commands
Title: Message Title Alex Earl commented on JENKINS-33455 Re: Option to disable echo of executed commands To be clear, do you just not want the commands echo'd, or the full stdout/stderr from the execution of the commands? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56190) Master /proc files are added twice to the support bundle
Title: Message Title Denys Digtiar updated JENKINS-56190 Jenkins / JENKINS-56190 Master /proc files are added twice to the support bundle Change By: Denys Digtiar Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56351) Cannot create new job using Bitbucket Cloud
Title: Message Title Jon Starbird updated JENKINS-56351 apologies. Happened to be talking to one of the dev managers and he had changed the permissions on the user used for Bitbucket cloud access. Issue is resolved. Jenkins / JENKINS-56351 Cannot create new job using Bitbucket Cloud Change By: Jon Starbird Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56351) Cannot create new job using Bitbucket Cloud
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-56351 Cannot create new job using Bitbucket Cloud Issue Type: Bug Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2019-03-01 19:56 Environment: Bitbucket Cloud Jenkins 2.150.3 Bitbucket Source plugin 2.4.2 Priority: Blocker Reporter: Jon Starbird Not sure where the issue is here but when attempting to create a new Pipeline in BlueOcean it is not correctly seeing our Team. It will only show the user, this was working fine and now it does not. Then it also won't let me force it or add anything either. The user being used is part of the team and hasn't changed at all not even the password. The Bitbucket permissions for the user have not changed at all either. I also tried to create one using the non-blue ocean Bitbucket Mulit branch job type and with that it will not allow me to select a Repo at all, doesn't even show the Field repository any longer. Our Jenkins server is internally available only so I cannot setup Bitbucket to push to it so this is a critical issue.
[JIRA] (JENKINS-56350) Week, Day layout incorrect
Title: Message Title Josh Nutzman created an issue Jenkins / JENKINS-56350 Week, Day layout incorrect Issue Type: Bug Assignee: Sven Schoenung Attachments: Screen Shot 2019-03-01 at 1.20.58 PM.png Components: calendar-view-plugin Created: 2019-03-01 19:24 Priority: Minor Reporter: Josh Nutzman I'm testing the calendar plugin on our test jenkins server (thus the pink background), but the result is similar on another server. Jobs for week and day view render on top of each other, at the top of the day instead of around the proper time. There is also a hover-over js error: jquery.full.js:1502 Uncaught Error: Syntax error, unrecognized _expression_: .event-id-view-job%20schedule-job-anothertest-155147130 at Function.Sizzle.error (jquery.full.js:1502) at Sizzle.tokenize (jquery.full.js:2159) at Sizzle.select (jquery.full.js:2580) at Function.Sizzle [as find] (jquery.full.js:903) at jQuery.fn.init.find (jquery.full.js:2826) at new jQuery.fn.init (jquery.full.js:2949) at jQuery (jquery.full.js:75) at a (events.js:45) at Object.e.select (events.js:77) at index.js:103
[JIRA] (JENKINS-56349) Stash Pull Request Builder can throw in StashBuildTrigger#run
Title: Message Title
Pavel Roskin updated an issue
Jenkins / JENKINS-56349
Stash Pull Request Builder can throw in StashBuildTrigger#run
Change By:
Pavel Roskin
There is a report in the Wiki about the plugin crashing in StashBuildTrigger#run[https://wiki.jenkins.io/display/JENKINS/Stash+pullrequest+builder+plugin]The documentation for Trigger#run() says:{quote}Maybe run even before [{{start(hudson.model.Item, boolean)}}|https://javadoc.jenkins.io/hudson/triggers/Trigger.html#start-J-boolean-], prepare for it.{quote}[https://javadoc.jenkins.io/hudson/triggers/Trigger.html#run--]We are definitely not prepared. I don't think running start() from run() would be a good idea, but being defensive and avoiding long chains of method calls would help.While at that, the "Build started" could be really improved, it's probably the only "happy case" INFO message from the plugin, and it's woefully non-informative. Also, make sure stop() reverts the effects of start() and makes run() fail before start() is run again.
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56349) Stash Pull Request Builder can throw in StashBuildTrigger#run
Title: Message Title Pavel Roskin created an issue Jenkins / JENKINS-56349 Stash Pull Request Builder can throw in StashBuildTrigger#run Issue Type: New Feature Assignee: Pavel Roskin Components: stash-pullrequest-builder-plugin Created: 2019-03-01 18:43 Priority: Major Reporter: Pavel Roskin There is a report in the Wiki about the plugin crashing in StashBuildTrigger#run https://wiki.jenkins.io/display/JENKINS/Stash+pullrequest+builder+plugin The documentation for Trigger#run() says: Maybe run even before start(hudson.model.Item, boolean), prepare for it. https://javadoc.jenkins.io/hudson/triggers/Trigger.html#run-- We are definitely not prepared. I don't think running start() from run() would be a good idea, but being defensive and avoiding long chains of method calls would help. While at that, the "Build started" could be really improved, it's probably the only "happy case" INFO message from the plugin, and it's woefully non-informative. Add Comment
[JIRA] (JENKINS-55918) Add support for groovy sandbox mode in environmentVariables closure
Title: Message Title
Alexander Komarov updated an issue
Jenkins / JENKINS-55918
Add support for groovy sandbox mode in environmentVariables closure
Change By:
Alexander Komarov
The "*Prepare an Environment for the run*" (environmentVariables {}) section supports a "sandbox" mode for the Groovy Script. It would be useful for the DSL plugin to allow for setting the value of this checkbox.*Use case*: I (re) generate a slightly different version of the same job every few months periodically . The Groovy Script changes slightly over time , which makes Jenkins require in-process script approval and prevents the job from running until someone approves the script and re-launches it . With sandbox mode, this would not happen. (Also, it would potentially be more secure)PR: [ https://github.com/jenkinsci/job-dsl-plugin/pull/1165 ]
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56197) SEVERE org.datadog.jenkins.plugins.datadog.DatadogQueueListener gauge java.lang.NullPointerException
Title: Message Title Datadog HQ updated JENKINS-56197 Jenkins / JENKINS-56197 SEVERE org.datadog.jenkins.plugins.datadog.DatadogQueueListener gauge java.lang.NullPointerException Change By: Datadog HQ Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56197) SEVERE org.datadog.jenkins.plugins.datadog.DatadogQueueListener gauge java.lang.NullPointerException
Title: Message Title Datadog HQ updated JENKINS-56197 Jenkins / JENKINS-56197 SEVERE org.datadog.jenkins.plugins.datadog.DatadogQueueListener gauge java.lang.NullPointerException Change By: Datadog HQ Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56197) SEVERE org.datadog.jenkins.plugins.datadog.DatadogQueueListener gauge java.lang.NullPointerException
Title: Message Title Datadog HQ commented on JENKINS-56197 Re: SEVERE org.datadog.jenkins.plugins.datadog.DatadogQueueListener gauge java.lang.NullPointerException Resolved in 0.7.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56337) Stash Pull Request Builder ignores quiet time
Title: Message Title Pavel Roskin commented on JENKINS-56337 Re: Stash Pull Request Builder ignores quiet time In review: https://github.com/jenkinsci/stash-pullrequest-builder-plugin/pull/46 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56337) Stash Pull Request Builder ignores quiet time
Title: Message Title Pavel Roskin started work on JENKINS-56337 Change By: Pavel Roskin 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56337) Stash Pull Request Builder ignores quiet time
Title: Message Title Pavel Roskin updated JENKINS-56337 Jenkins / JENKINS-56337 Stash Pull Request Builder ignores quiet time Change By: Pavel Roskin 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56348) Add "python" alias for PythonInstallation
Title: Message Title
James Howe created an issue
Jenkins / JENKINS-56348
Add "python" alias for PythonInstallation
Issue Type:
Improvement
Assignee:
Unassigned
Components:
shiningpanda-plugin
Created:
2019-03-01 16:59
Priority:
Minor
Reporter:
James Howe
Most other tool implementations provide a short name for use in pipelines (jdk, maven, etc.) but there's no python. You have to use the full quoted class name instead.
Current
tools {
'jenkins.plugins.shiningpanda.tools.PythonInstallation': 'CPython-3.6'
}
Proposed
tools {
python: 'CPython-3.6'
}
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Shevek . commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) Tempted to say this is a major or blocker as it kills our usage of Jenkins on the first non-login request. We do NOT get an hour of usability, we get NO usability on 2.150.3 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Filip Pytloun updated an issue Jenkins / JENKINS-56347 Kubernetes plugin provisioning pods twice in 1.14.6 Change By: Filip Pytloun Since 1.14.6 and it's update to kubernetes client 4.1.2, I started to observe weird behavior when plugin provisions two pods for one pod template. Second pod is exactly the same as first one but is spawned exactly 20 seconds after.I tried version 1.14.5 and it's working well (also tested 1.14.2, 1.14.0).Also it seems that SocketClosed exceptions caused by timeout on get operation became more frequent:Caused: io.fabric8.kubernetes.client.KubernetesClientException: Operation: [get] for kind: [Pod] with name: [terraform-deploy-fabric-cluster-cec-az-246-hc9xs-2z6rf] in namespace: [jenkins] failed. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56315) Add "docker" alias for DockerTool
Title: Message Title James Howe commented on JENKINS-56315 Re: Add "docker" alias for DockerTool Hopefully it doesn't collide with pipeline.agent.docker or the global docker (which also provides docker.withTool()). 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Filip Pytloun created an issue Jenkins / JENKINS-56347 Kubernetes plugin provisioning pods twice in 1.14.6 Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-03-01 16:53 Priority: Major Reporter: Filip Pytloun Since 1.14.6 and it's update to kubernetes client 4.1.2, I started to observe weird behavior when plugin provisions two pods for one pod template. Second pod is exactly the same as first one but is spawned exactly 20 seconds after. I tried version 1.14.5 and it's working well (also tested 1.14.2, 1.14.0). Also it seems that SocketClosed exceptions caused by timeout on get operation became more frequent: Caused: io.fabric8.kubernetes.client.KubernetesClientException: Operation: [get] for kind: [Pod] with name: [terraform-deploy-fabric-cluster-cec-az-246-hc9xs-2z6rf] in namespace: [jenkins] failed. Add Comment
[JIRA] (JENKINS-56315) Add "docker" alias for DockerTool
Title: Message Title
James Howe updated an issue
Jenkins / JENKINS-56315
Add "docker" alias for DockerTool
Change By:
James Howe
Most other tool implementations provide a short name for use in pipelines (jdk, maven, etc.) but there's no docker. You have to use the full quoted class name instead. {code:groovy}tools {docker: 'latest'}{code}
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56315) Add "docker" alias for DockerTool
Title: Message Title
James Howe updated an issue
Jenkins / JENKINS-56315
Add "docker" alias for DockerTool
Change By:
James Howe
Most other tool implementations provide a short name for use in pipelines (jdk, maven, etc.) but there's no docker. You have to use the full quoted class name instead. {code:groovy|title=Current} tools { 'org.jenkinsci.plugins.docker.commons.tools.DockerTool': 'latest'}{ code }{code :groovy |title=Proposed }tools {docker: 'latest'}{code}
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56315) Add "docker" alias for DockerTool
Title: Message Title
James Howe updated an issue
Jenkins / JENKINS-56315
Add "docker" alias for DockerTool
Change By:
James Howe
Most other tool implementations provide a short name for use in pipelines (jdk, maven, etc.) but there's no docker. You have to use the full quoted class name instead. {code:groovy|title=Current} tools { 'org.jenkinsci.plugins.docker.commons.tools.DockerTool': 'latest'}{ code }{code :groovy |title=Proposed }tools {docker: 'latest'}{code}
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56315) Add "docker" alias for DockerTool
Title: Message Title
James Howe updated an issue
Jenkins / JENKINS-56315
Add "docker" alias for DockerTool
Change By:
James Howe
Most other tool implementations provide a short name for use in pipelines (jdk, maven, etc.) but there's no docker. You have to use the full quoted class name instead. {code:groovy}tools {docker: 'latest'}{code}
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56346) Provide build wrapper withDockerCompose
Title: Message Title
James Howe updated an issue
Jenkins / JENKINS-56346
Provide build wrapper withDockerCompose
Change By:
James Howe
Currently I've built my own in a custom library{code :groovy }def call(Closure body) {docker.withTool('Default') {withPythonEnv('python') {sh 'pip install docker-compose'sh 'docker-compose --no-ansi up -d'try {waitUntil { script { dockerUtils.isReady() } }body()} finally {sh 'docker-compose --no-ansi down'}}}}{code}The {{isReady()}} function is a little complicated - it essentially does{code :sh }docker inspect --format '{{json .State}}' $(docker-compose ps -q){code}then parses and checks that every container has either {{Health.Status == 'healthy'}}, or {{Status == 'running'}} if there is no healthcheck.You could implement something similar, and more configurable, directly.
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56346) Provide build wrapper withDockerCompose
Title: Message Title
James Howe updated an issue
Jenkins / JENKINS-56346
Provide build wrapper withDockerCompose
Change By:
James Howe
Currently I've built my own in a custom library{code :groovy }def call(Closure body) { docker.withTool('Default') { withPythonEnv('python') {sh 'pip install docker-compose'sh 'docker-compose --no-ansi up -d'try {waitUntil { script { dockerUtils.isReady() } }body()} finally {sh 'docker-compose --no-ansi down'}}} } {code}The {{isReady()}} function is a little complicated - it essentially does{code :sh }docker inspect --format '{{json .State}}' $(docker-compose ps -q){code} then parses and checks that every container has either {{Health.Status == 'healthy'}}, or {{Status == 'running'}} if there is no healthcheck.You could implement something similar, and more configurable, directly.
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56346) Provide build wrapper withDockerCompose
Title: Message Title
James Howe created an issue
Jenkins / JENKINS-56346
Provide build wrapper withDockerCompose
Issue Type:
Improvement
Assignee:
João Galego
Components:
docker-compose-build-step-plugin
Created:
2019-03-01 16:42
Priority:
Minor
Reporter:
James Howe
Currently I've built my own in a custom library
def call(Closure body) {
withPythonEnv('python') {
sh 'pip install docker-compose'
sh 'docker-compose --no-ansi up -d'
try {
waitUntil { script { dockerUtils.isReady() } }
body()
} finally {
sh 'docker-compose --no-ansi down'
}
}
}
The isReady() function is a little complicated - it essentially does
docker inspect --format '{{json .State}}' $(docker-compose ps -q)
then parses and checks that every container has either Health.Status == 'healthy', or Status == 'running' if there is no healthcheck. You could implement something similar, and more configurable, directly.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Shevek . commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) Downgrade to 2.150.1 appears to solve the 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56343) Intermittent java.io.NotSerializableException when running scripts in parallel
Title: Message Title Alun Edwards commented on JENKINS-56343 Re: Intermittent java.io.NotSerializableException when running scripts in parallel Appears to be similar issue as https://issues.jenkins-ci.org/browse/JENKINS-46597 Although JENKINS-46597 was resolved because they fixed their underlying issue (use of a tree map), e.g. and for me I could resolve this by storing the result of the matcher in a method not marked as non-cps, for me the outstanding issues are that The issue happens inconsistently, surely the aforementioned code should always be a violation or should always pass The issue is very hard to locate. The stack trace gives no indication as to where the cause is. In my case it was a regex matcher, which is used in many places in a pipeline library we have. Even adding logging statements on every line it was still difficult, as where the code is actually triggered is (when it enters the @NonCPS method) is not where the problematic variable is. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28284) Images for Test Case trends is broken and generate exception
Title: Message Title ankur sharma commented on JENKINS-28284 Re: Images for Test Case trends is broken and generate exception Manuel Carrasco - Can you please check this, do we need to reopen this issue, or is it something else. can you please 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56345) Manage tool installation for docker compose
Title: Message Title James Howe created an issue Jenkins / JENKINS-56345 Manage tool installation for docker compose Issue Type: Improvement Assignee: João Galego Components: docker-compose-build-step-plugin Created: 2019-03-01 16:32 Priority: Minor Reporter: James Howe I guess with one of the installation options be to grab the release from github. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-28284) Images for Test Case trends is broken and generate exception
Title: Message Title ankur sharma commented on JENKINS-28284 Re: Images for Test Case trends is broken and generate exception Hi Team, I am currently getting a similar issue with Jenkins 2.15 and Performance Plugin 3.15, the graphs are not getting displayed. please find below the trace : java.lang.NoClassDefFoundError: com/mercury/ftjadin/hooks/interfaces/EventListenerListHookQTJA at javax.swing.event.EventListenerList.add(Unknown Source) at org.jfree.data.general.AbstractDataset.addChangeListener(AbstractDataset.java:126) at org.jfree.chart.plot.CategoryPlot.(CategoryPlot.java:458) at org.jfree.chart.ChartFactory.createLineChart(ChartFactory.java:1175) at hudson.plugins.performance.actions.PerformanceProjectAction.doCreateRespondingTimeChart(PerformanceProjectAction.java:149) at hudson.plugins.performance.actions.PerformanceProjectAction.createRespondingTimeChart(PerformanceProjectAction.java:429) at hudson.plugins.performance.actions.PerformanceProjectAction.doRespondingTimeGraph(PerformanceProjectAction.java:482) at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:537) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:789) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:458) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:282) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:105) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilt
[JIRA] (JENKINS-28284) Images for Test Case trends is broken and generate exception
Title: Message Title ankur sharma updated an issue Jenkins / JENKINS-28284 Images for Test Case trends is broken and generate exception Change By: ankur sharma Attachment: image-2019-03-01-16-31-33-953.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53189) Exception during Test LDAP settings in group search filter
Title: Message Title Christian Opitz commented on JENKINS-53189 Re: Exception during Test LDAP settings in group search filter Same issue here. Any workaround known? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28284) Images for Test Case trends is broken and generate exception
Title: Message Title ankur sharma updated an issue Jenkins / JENKINS-28284 Images for Test Case trends is broken and generate exception Change By: ankur sharma Attachment: image-2019-03-01-16-30-45-711.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56344) Docker compose aliases for declarative pipeline
Title: Message Title James Howe created an issue Jenkins / JENKINS-56344 Docker compose aliases for declarative pipeline Issue Type: Improvement Assignee: João Galego Components: docker-compose-build-step-plugin Created: 2019-03-01 16:30 Priority: Minor Reporter: James Howe Currently the simplest snippet you can use is this step([$class: 'DockerComposeBuilder', dockerComposeFile: 'docker-compose.yml', option: [$class: 'StartAllServices'], useCustomDockerComposeFile: false]) it would be much nicer to have aliases for the classes and defaults for the arguments dockerCompose 'startAllServices' or one for each option dockerComposeUp() dockerComposeDown 'db'
[JIRA] (JENKINS-56343) Intermittent java.io.NotSerializableException when running scripts in parallel
Title: Message Title Alun Edwards created an issue Jenkins / JENKINS-56343 Intermittent java.io.NotSerializableException when running scripts in parallel Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2019-03-01 16:22 Environment: pipeline-aggregator-view 1.8 pipeline-build-step 2.7 pipeline-github-lib 1.0 pipeline-graph-analysis 1.9 pipeline-input-step 2.9 pipeline-milestone-step 1.3.1 pipeline-model-api 1.3.4.1 pipeline-model-declarative-agent 1.1.1 pipeline-model-definition 1.3.4.1 pipeline-model-extensions 1.3.4.1 pipeline-rest-api 2.10 pipeline-stage-step 2.3 pipeline-stage-tags-metadata 1.3.4.1 pipeline-stage-view 2.10 windows-slaves 1.4 workflow-aggregator 2.6 workflow-api 2.33 workflow-basic-steps 2.14 workflow-cps 2.63 workflow-cps-global-lib 2.13 workflow-durable-task-step 2.29 workflow-job 2.31 workflow-multibranch 2.20 workflow-scm-step 2.7 workflow-step-api 2.19 workflow-support 3.2 Priority: Major Reporter: Alun Edwards I receive an intermittent java.io.NotSerializableException when running a script in parallel an exception which occurred: in field com.cloudbees.groovy.cps.impl.BlockScopeEnv.locals in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@53ce7f91 ... Caused: java.io.NotSerializableException: java.util.regex.Matcher at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:926) ... The stack trace completely masks the location of the offending code. The offending cod
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Shevek . commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) This appears to be affecting us after the update to 2.150.3 and has made jenkins unusable 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam commented on JENKINS-56114 Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy) Hi Wadeck Follonier - we ran though various jobs, screens, etc. as well and everything seems to working as expected. Thanks for your work on this and the turnaround on a 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55948) Git client 3.0.0-rc called from git parameter plugin fails, 2.x worked
Title: Message Title Malcolm Hannah commented on JENKINS-55948 Re: Git client 3.0.0-rc called from git parameter plugin fails, 2.x worked Mark Waite thank you very much for looking into this and for finding a work-around so quickly. (I should've come here sooner - I've been struggling with this on and off for weeks!) Downgrading git-client to 2.7.5 and git plugin to 3.9.3 appears to have fixed it for me. I say 'appears to' as my investigations earlier today (before the downgrades) led to some projects being 'fixed' as I stripped them down to a bare minimum example, then experimented with selecting the wrong credentials, then selecting the right credentials etc. However, I didn't manage to isolate any single particular action that fixed them. For the record, the answers to your earlier questions are: Freestyle project, https repo, master is war on non-virtual non-containerised Ubuntu, nothing relevant in the system log. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56286) Multibranch Pipeline + P4Plugin + Helix Library + Polling = Infinite Build Loop
Title: Message Title
Mykola Ulianytskyi updated an issue
Jenkins / JENKINS-56286
Multibranch Pipeline + P4Plugin + Helix Library + Polling = Infinite Build Loop
Change By:
Mykola Ulianytskyi
HelloWe have problem with Multibranch Pipeline + Modern SCM Helix Library + Polling.P4Plugin always finds changes in some streams (Polling Log has line "Changes found" but has no lines "... found change: XXX") and triggers new build.The problem appears on all streams with different delay in time.All streams have the same Jenkinsfile and Jenkins Library.All workspaces in Polling logs have unique syncID (Multibranch Pipeline was recreated several times and logs checked).The problem appears after a while, and I am not able to reproduce STR.*The problem appears only if Modern SCM Helix Library configration is used in Jenkins Library ! . **Workaround for this bug: migrate to Legacy SCM > Perforce Software > Manual Workspace*Next actions sometimes trigger the problem: * Manual Job start * Jenkins restartDeleting and re-adding of stream in "Branch Sources > Helix Streams > Include streams" with deleting of child pipeline (for build history cleanup) temporary solve the build loop but it re-appears after some time . *Library Configuration:* * Name: * Default version: now * Load implicitly: False * Allow default version to be overridden: False * Include Library changes in job recent changes: False * Retrieval method: Modern SCM * Source Code Management: Helix Library * Perforce Credentials: jenkins * Library Depot Path: //playground/jenkins-main/library/... * Multibranch Pipeline Configuration: Update #1 * * Branch Sources > Helix Streams * Perforce Credentials I have found one of possible steps to reproduce this bug : jenkins * Script Path: Jenkinsfile * Add property: (Deprecated) Suppress automatic SCM triggering * Disable: Discard old items * Include streams:{code:java} 1. Create //playground/jenkins-main stream {code} 2. Submit * //playground/jenkins-main/library/vars/foo1.groovy * {code:java}def call() {echo("foo1")}{code} * 3. Submit //playground/jenkins-main/Jenkinsfile * {code:java}pipeline {agent {node {label ( "master" none ) } } libraries {lib("foo")}options { buildDiscarder(logRotator(numToKeepStr: "10")) disableConcurrentBuilds() disableResume()quietPeriod(150) skipDefaultCheckout(true)}triggers {pollSCM("* * * * *")}stages {stage("Init") { agent {node {label("master")}} steps {checkout scm: perforce(credential: ' " perforce-ticket-jenkins ' " , populate: flushOnly(pin: '' "" , quiet: false), workspace: streamSpec(charset: ' " none ' " , format: 'bar "test1 -- kiepc2006' ${NODE_NAME}" , pinHost: true, streamName: ' " //playground/ jenkins-main' ${BRANCH_NAME}" ))echo("hello")foo1()
[JIRA] (JENKINS-56330) Expecting groovy.lang.Closure, got org.jenkinsci.plugins.workflow.cps.CpsClosure2
Title: Message Title James Howe commented on JENKINS-56330 Re: Expecting groovy.lang.Closure, got org.jenkinsci.plugins.workflow.cps.CpsClosure2 If the code is moved to a global shared library, thus bypassing the sandbox, everything works fine. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56330) Expecting groovy.lang.Closure, got org.jenkinsci.plugins.workflow.cps.CpsClosure2
Title: Message Title
James Howe edited a comment on JENKINS-56330
Re: Expecting groovy.lang.Closure, got org.jenkinsci.plugins.workflow.cps.CpsClosure2
Probably related, but it's also not possible to use ` {{ CurriedClosure ` }} with Java 8 streams, even though it should be a ` {{ @FunctionalInterface ` }} via ` {{ Runnable ` }} .{noformat}hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: java.util.stream.ReferencePipeline$Head.map() is applicable for argument types: (org.codehaus.groovy.runtime.CurriedClosure) values: [org.codehaus.groovy.runtime.CurriedClosure@6846ac99]Possible solutions: map(java.util.function.Function), max(java.util.Comparator), min(java.util.Comparator), wait(), any(), dump() at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:153) {noformat}
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56330) Expecting groovy.lang.Closure, got org.jenkinsci.plugins.workflow.cps.CpsClosure2
Title: Message Title James Howe commented on JENKINS-56330 Re: Expecting groovy.lang.Closure, got org.jenkinsci.plugins.workflow.cps.CpsClosure2 Probably related, but it's also not possible to use `CurriedClosure` with Java 8 streams, even though it should be a `@FunctionalInterface` via `Runnable`. hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: java.util.stream.ReferencePipeline$Head.map() is applicable for argument types: (org.codehaus.groovy.runtime.CurriedClosure) values: [org.codehaus.groovy.runtime.CurriedClosure@6846ac99] Possible solutions: map(java.util.function.Function), max(java.util.Comparator), min(java.util.Comparator), wait(), any(), dump() at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:153) 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55948) Git client 3.0.0-rc called from git parameter plugin fails, 2.x worked
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-55948 Git client 3.0.0-rc called from git parameter plugin fails, 2.x worked Change By: Mark Waite Summary: Git client 3.0.0-rc use by called from git parameter plugin is incompatible with git client fails, 2.x worked 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55948) Git client 3.0.0-rc use by git parameter plugin is incompatible with git client 2.x
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-55948 Git client 3.0.0-rc use by git parameter plugin is incompatible with git client 2.x Change By: Mark Waite Component/s: git-parameter-plugin Component/s: multiple-scms-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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55948) Git client 3.0.0-rc use by git parameter plugin is incompatible with git client 2.x
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-55948 Git client 3.0.0-rc use by git parameter plugin is incompatible with git client 2.x Change By: Mark Waite Summary: Git client plug 3.0.0 - in crash rc use by git parameter plugin is incompatible with git client 2.x 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56342) javax.servlet.ServletException: java.lang.NoClassDefFoundError: jenkins/triggers/SCMTriggerItem$SCMTriggerItems
Title: Message Title Sekar Purushothaman commented on JENKINS-56342 Re: javax.servlet.ServletException: java.lang.NoClassDefFoundError: jenkins/triggers/SCMTriggerItem$SCMTriggerItems This error occurs when I save the Jenkins jobs. We are using Jenkins ver. 1.533 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55948) Git client plug-in crash
Title: Message Title
Mark Waite commented on JENKINS-55948
Re: Git client plug-in crash
Malcolm Hannah I believe I've found a way to duplicate the same conditions, though I don't understand the root of the problem yet, and won't do more investigation for a while. The steps I took to duplicate the problem using the Jenkins image from my docker_lfs repository are:
Create a Freestyle job 'JENKINS-55948-cat-not-found-with-git-parameter-plugin'
Parameterized with git parameter plugin using the parameter 'USER_BRANCH' of type 'Branch' with default value 'master'
Use a private git https repository - https://github.com/MarkEWaite/bin
Set branches to build as '${USER_BRANCH}'
Run the job (in my case I ran it once successfully, then changed the repository URL and ran it a second time)
When I try to run the job, it begins to present the list of branches as candidates to choose in the parameter, then reports the following error text:
The default value has been returned
An error occurred while download data
Command "git ls-remote -h https://github.com/MarkEWaite/bin" returned status code 128:
stdout:
stderr: /tmp/jenkins-gitclient-pass3357881948490999049.sh: 3: /tmp/jenkins-gitclient-pass3357881948490999049.sh: cat: not found
error: unable to read askpass response from '/tmp/jenkins-gitclient-pass3357881948490999049.sh'
fatal: could not read Username for 'https://github.com': terminal prompts disabled
Please look at the Log
Please check the configuration
I think that indicates there is likely a bug in git client plugin 3.0.0-rc when it is called from the git parameter plugin. The git parameter plugin has not changed how it is calling the git client plugin, so I'm reasonably confident the issue is in git client plugin 3.0.0-rc. The near term solution for you is to downgrade from git client plugin 3.0.0-rc to the most recent officially released git client plugin, 2.7.4. You'll also need to downgrade the git plugin from 4.0.0-rc to 3.9.3. My apologies if your use of git client plugin 3.0.0 release candidate was unintentional. I made a mistake when I chose the version number string. I had intended for the 3.0.0-rc version of the plugin to only be visible in the experimental update center. Unfortunately, the version string I chose, '3.0.0-rc' is not hidden from the standard update center like '3.0.0-alpha' and '3.0.0-beta' are. The cat command that is used in the authentication is an intentional change in git client plugin 3.0.0 which will allow shell special characters in passwords. The previous versions of the git client plugin did not allow shell special characters in passwords.
[JIRA] (JENKINS-56342) javax.servlet.ServletException: java.lang.NoClassDefFoundError: jenkins/triggers/SCMTriggerItem$SCMTriggerItems
Title: Message Title Sekar Purushothaman created an issue Jenkins / JENKINS-56342 javax.servlet.ServletException: java.lang.NoClassDefFoundError: jenkins/triggers/SCMTriggerItem$SCMTriggerItems Issue Type: Bug Assignee: tspengler Components: hudson-wsclean-plugin Created: 2019-03-01 14:10 Environment: Production Priority: Blocker Reporter: Sekar Purushothaman Caused by: java.lang.NoClassDefFoundError: jenkins/triggers/SCMTriggerItem$SCMTriggerItems at jenkins.scm.impl.SCM2Notifier.onChange(SCM2Notifier.java:54) at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:78) at hudson.model.AbstractItem.save(AbstractItem.java:456) at hudson.model.Job.save(Job.java:162) at hudson.model.AbstractProject.save(AbstractProject.java:283) at hudson.model.AbstractItem.setDisplayName(AbstractItem.java:156) at hudson.model.Job.doConfigSubmit(Job.java:1121) at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:787) at sun.reflect.GeneratedMethodAccessor849.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:297) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:160) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:95) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:685) ... 62 more
