[JIRA] (TEST-114) QA TEST01
Title: Message Title MD HAYDER created an issue test / TEST-114 QA TEST01 Issue Type: Bug Assignee: Oleg Nenashev Components: foo12 Created: 2018-05-05 02:27 Environment: QA Priority: Minor Reporter: MD HAYDER QA Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-49991) Clicking the "Jenkins" link in Blue Ocean is very slow
Title: Message Title Joshua Holmer updated JENKINS-49991 Jenkins / JENKINS-49991 Clicking the "Jenkins" link in Blue Ocean is very slow Change By: Joshua Holmer Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-49991) Clicking the "Jenkins" link in Blue Ocean is very slow
Title: Message Title Joshua Holmer commented on JENKINS-49991 Re: Clicking the "Jenkins" link in Blue Ocean is very slow I've opened a PR at https://github.com/jenkinsci/blueocean-plugin/pull/1734 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-49991) Clicking the "Jenkins" link in Blue Ocean is very slow
Title: Message Title Joshua Holmer started work on JENKINS-49991 Change By: Joshua Holmer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-49991) Clicking the "Jenkins" link in Blue Ocean is very slow
Title: Message Title Joshua Holmer updated an issue Jenkins / JENKINS-49991 Clicking the "Jenkins" link in Blue Ocean is very slow Change By: Joshua Holmer Comment: I've opened a PR at https://github.com/jenkinsci/blueocean-plugin/pull/1734 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-49991) Clicking the "Jenkins" link in Blue Ocean is very slow
Title: Message Title Joshua Holmer commented on JENKINS-49991 Re: Clicking the "Jenkins" link in Blue Ocean is very slow I've opened a PR at https://github.com/jenkinsci/blueocean-plugin/pull/1734 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-37375) Pipeline build step for Websphere Deployer plugin
Title: Message Title Scott Busche commented on JENKINS-37375 Re: Pipeline build step for Websphere Deployer plugin What kind of details are you after? I want to be able to use the plugin as part of the Jenkins Pipeline scripts, when I posted this two years ago, it wasn't possible. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-32511) install/update Application(s)" to deploy ear, but ear cookies setting is recover after deploy, could not keep on session id and start application exception
Title: Message Title Greg Peters closed an issue as Postponed Sometimes this happens when the application being deployed has the same context root as the application already installed on the server. Postponing this improvement until further notice Jenkins / JENKINS-32511 install/update Application(s)" to deploy ear, but ear cookies setting is recover after deploy, could not keep on session id and start application exception Change By: Greg Peters Status: Open Closed Resolution: Postponed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because
[JIRA] (JENKINS-32511) install/update Application(s)" to deploy ear, but ear cookies setting is recover after deploy, could not keep on session id and start application exception
Title: Message Title Greg Peters updated JENKINS-32511 Jenkins / JENKINS-32511 install/update Application(s)" to deploy ear, but ear cookies setting is recover after deploy, could not keep on session id and start application exception Change By: Greg Peters Status: Reopened Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-37375) Pipeline build step for Websphere Deployer plugin
Title: Message Title Greg Peters commented on JENKINS-37375 Re: Pipeline build step for Websphere Deployer plugin Scott Busche Please provide more details Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51147) Plugin Kubernetes Continuous Deploy Plugin makes input command fail
Title: Message Title
Evan Reynolds created an issue
Jenkins / JENKINS-51147
Plugin Kubernetes Continuous Deploy Plugin makes input command fail
Issue Type:
Bug
Assignee:
Azure DevOps
Components:
kubernetes-cd-plugin
Created:
2018-05-05 00:20
Environment:
Jenkins 2.119 Kubernetes Continuous Deploy Plugin 0.2.1 Pipeline: Input Step 2.8 Ubuntu 16.04.4 LTS
Priority:
Minor
Reporter:
Evan Reynolds
When I run a kubernetesDeploy command, then an input command, it fails. If I comment out the Kubernetes command then the input command will succeed - and if I comment out the input command, the Kubernetes command succeeds. (THAT made this hard to figure out what was happening!) I replicated the issue using the following Jenkinsfile: #!/usr/bin/env groovy node { stage('Deploy') { kubernetesDeploy( kubeconfigId: "staging-credentials", configs: "config.yaml", dockerCredentials: [[credentialsId: 'credentialId']]) input "ask something" } } Input was originally in a different stage. And again, the input and the kubernetesDeploy command will work by themselves - but running them together will fail. This is the error: java.lang.UnsupportedOperationException: Refusing to marshal com.microsoft.jenkins.azurecommons.core.EnvironmentInjector$EnvironmentInjectionAction for security reasons; see https://jenkins.io/redirect/class-filter/ at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:543) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at
[JIRA] (JENKINS-51136) Jenkins UI hangs 2.117 - 2.119
Title: Message Title Olivier Lamy commented on JENKINS-51136 Re: Jenkins UI hangs 2.117 - 2.119 could help to have a threaddump collected or logs when the server hangs. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-45901) Allow common groovy annotation in Pipeline Shared Library Classes
Title: Message Title kevin brandon commented on JENKINS-45901 Re: Allow common groovy annotation in Pipeline Shared Library Classes Seems to me that in the CmpTransformer that all present annotations should just be simply added. Annotations are meant to be meta data. If they are not supported they are not supported... but the annotation themselves shouldn't disappear. I can appreciate and understand about not wanting to support functionality that those annotations are meant for; however, by not having the meta data continue with the class it cuts out the possibility that the code might want to do some reflection. For myself I was hoping to annotate methods for some AOP action that would simply the code and keep it very dry. Andrew Bayer it would rock to keep the meta! Please let me know if I am off my rocker... or if there is a way to get back to the original class to access the meta that I am trying to look for! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: Mark Waite Path: README.md pom.xml src/main/java/hudson/plugins/git/browser/AssemblaWeb.java src/main/java/hudson/plugins/git/browser/BitbucketWeb.java src/main/java/hudson/plugins/git/browser/CGit.java src/main/java/hudson/plugins/git/browser/FisheyeGitRepositoryBrowser.java src/main/java/hudson/plugins/git/browser/GitBlitRepositoryBrowser.java src/main/java/hudson/plugins/git/browser/GitLab.java src/main/java/hudson/plugins/git/browser/GitList.java src/main/java/hudson/plugins/git/browser/GitWeb.java src/main/java/hudson/plugins/git/browser/GithubWeb.java src/main/java/hudson/plugins/git/browser/Gitiles.java src/main/java/hudson/plugins/git/browser/GitoriousWeb.java src/main/java/hudson/plugins/git/browser/GogsGit.java src/main/java/hudson/plugins/git/browser/KilnGit.java src/main/java/hudson/plugins/git/browser/Phabricator.java src/main/java/hudson/plugins/git/browser/RedmineWeb.java src/main/java/hudson/plugins/git/browser/RhodeCode.java src/main/java/hudson/plugins/git/browser/Stash.java src/main/java/hudson/plugins/git/browser/TFS2013GitRepositoryBrowser.java src/main/java/hudson/plugins/git/browser/ViewGitWeb.java src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java src/main/java/jenkins/plugins/git/GitBranchSCMHead.java src/main/java/jenkins/plugins/git/GitBranchSCMRevision.java src/main/java/jenkins/plugins/git/GitRefSCMHead.java src/main/java/jenkins/plugins/git/GitRefSCMRevision.java src/main/java/jenkins/plugins/git/GitSCMBuilder.java src/main/java/jenkins/plugins/git/GitSCMHeadMixin.java src/main/java/jenkins/plugins/git/GitSCMSource.java src/main/java/jenkins/plugins/git/GitSCMSourceContext.java src/main/java/jenkins/plugins/git/GitSCMTelescope.java src/main/java/jenkins/plugins/git/traits/DiscoverOtherRefsTrait.java src/main/resources/jenkins/plugins/git/traits/DiscoverOtherRefsTrait/config.jelly src/main/resources/jenkins/plugins/git/traits/DiscoverOtherRefsTrait/help-nameMapping.html src/main/resources/jenkins/plugins/git/traits/DiscoverOtherRefsTrait/help-ref.html src/main/resources/jenkins/plugins/git/traits/DiscoverOtherRefsTrait/help.html src/main/resources/jenkins/plugins/git/traits/Messages.properties src/test/java/jenkins/plugins/git/AbstractGitSCMSourceTest.java src/test/java/jenkins/plugins/git/GitBranchSCMHeadTest.java src/test/java/jenkins/plugins/git/GitSCMFileSystemTest.java src/test/java/jenkins/plugins/git/GitSCMSourceTest.java src/test/java/jenkins/plugins/git/traits/DiscoverOtherRefsTraitTest.java src/test/resources/jenkins/plugins/git/GitBranchSCMHeadTest/testMigrationNoBuildStorm.zip src/test/resources/jenkins/plugins/git/GitBranchSCMHeadTest/testMigrationNoBuildStorm_repositories.zip http://jenkins-ci.org/commit/git-plugin/927c8295d326a755cc7443f1834d7ff9ede37ee2 Log: Merge pull request #577 from rsandell/JENKINS-48061 JENKINS-48061 Add new "Discover other refs" trait, GitBranchSCMHead and GitRefSCMHead Compare: https://github.com/jenkinsci/git-plugin/compare/bd8d2b9a9546...927c8295d326 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019.
[JIRA] (JENKINS-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: rsandell Path: src/test/java/jenkins/plugins/git/AbstractGitSCMSourceTest.java http://jenkins-ci.org/commit/git-plugin/6ffc5710f70a58e42873d2f3d94d887b557685a9 Log: JENKINS-48061 Added a test to verify we can retrieve a commit that is not on the head of a custom ref Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: rsandell Path: src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java http://jenkins-ci.org/commit/git-plugin/1340f867c7de5f2474fa3866a3d5c9f4c38fcba5 Log: JENKINS-48061 That logging might be a bit too informative Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: rsandell Path: src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java src/main/java/jenkins/plugins/git/GitSCMSourceContext.java src/main/java/jenkins/plugins/git/traits/DiscoverOtherRefsTrait.java src/main/resources/jenkins/plugins/git/traits/DiscoverOtherRefsTrait/config.jelly src/main/resources/jenkins/plugins/git/traits/DiscoverOtherRefsTrait/help-nameMapping.html src/main/resources/jenkins/plugins/git/traits/DiscoverOtherRefsTrait/help-ref.html src/main/resources/jenkins/plugins/git/traits/DiscoverOtherRefsTrait/help.html src/main/resources/jenkins/plugins/git/traits/Messages.properties src/test/java/jenkins/plugins/git/AbstractGitSCMSourceTest.java src/test/java/jenkins/plugins/git/traits/DiscoverOtherRefsTraitTest.java http://jenkins-ci.org/commit/git-plugin/75177c492f12ef59e65e118ea4b6c62daa7dd5c2 Log: JENKINS-48061 Adding DiscoverOtherRefsTrait Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: rsandell Path: src/test/java/jenkins/plugins/git/GitBranchSCMHeadTest.java http://jenkins-ci.org/commit/git-plugin/d21ba4ea1011168e53bf82feb2466295a3da118e Log: JENKINS-48061 Clean up after test Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: rsandell Path: src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java src/main/java/jenkins/plugins/git/GitBranchSCMHead.java src/main/java/jenkins/plugins/git/GitRefSCMHead.java src/main/java/jenkins/plugins/git/GitSCMBuilder.java src/test/java/jenkins/plugins/git/AbstractGitSCMSourceTest.java src/test/java/jenkins/plugins/git/GitSCMFileSystemTest.java src/test/java/jenkins/plugins/git/GitSCMSourceTest.java http://jenkins-ci.org/commit/git-plugin/d6862539704655da7158385710e1a69e4ce9b20f Log: JENKINS-48061 regrouping and more tests Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: rsandell Path: src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java http://jenkins-ci.org/commit/git-plugin/1d312b647aa7a6ab256296551863760fdb61 Log: Revert "JENKINS-48061 Non GitSCMHeadMixin should be a branch" This reverts commit 68a956f9c3180e75b8c3c1b7d43ca2f870a82e9d. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: rsandell Path: src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java src/test/java/jenkins/plugins/git/AbstractGitSCMSourceTest.java http://jenkins-ci.org/commit/git-plugin/887ac3394c48e844147de591277a0457adb345a3 Log: JENKINS-48061 retrieveRevisions Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: rsandell Path: src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java http://jenkins-ci.org/commit/git-plugin/bcd0e206edebd84a7f069bd0dd083d7b18158d6c Log: JENKINS-48061 Make the comment an actual comment Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: rsandell Path: src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java http://jenkins-ci.org/commit/git-plugin/2cc15228d0b34bfcc13d4f1e58dcd79344faaa3c Log: JENKINS-48061 Move HEAD check to top Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: rsandell Path: src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java src/main/java/jenkins/plugins/git/GitSCMSourceContext.java src/main/java/jenkins/plugins/git/traits/DiscoverOtherRefsTrait.java src/test/java/jenkins/plugins/git/AbstractGitSCMSourceTest.java http://jenkins-ci.org/commit/git-plugin/f67a66ec0900c83d6785955d32de32b1f17f4724 Log: JENKINS-48061 Retrieve other refs Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: rsandell Path: src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java http://jenkins-ci.org/commit/git-plugin/cb2e753cd81be123af628c7f502681ef6b2a9a34 Log: JENKINS-48061 Motivate withoutRefspec Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: rsandell Path: src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java src/main/java/jenkins/plugins/git/GitSCMSourceContext.java src/main/java/jenkins/plugins/git/traits/DiscoverOtherRefsTrait.java http://jenkins-ci.org/commit/git-plugin/36a307a5e128e5f47d2284317a6cf1e0cb4595e5 Log: JENKINS-48061 rename WantedOtherRefs to RefNameMapping Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: rsandell Path: src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java http://jenkins-ci.org/commit/git-plugin/191cf5562d801a0d8749c847451595271872b6a8 Log: JENKINS-48061 Resolve other ref before tag name So we don't have to check timestamps on the tag Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: rsandell Path: pom.xml src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java src/main/java/jenkins/plugins/git/GitSCMSourceContext.java src/main/java/jenkins/plugins/git/GitSCMTelescope.java http://jenkins-ci.org/commit/git-plugin/4a7cba88498ba5f5cdc1c4a76fac17fa0faa4f99 Log: JENKINS-48061 Cleaned up comments and todos Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: rsandell Path: pom.xml http://jenkins-ci.org/commit/git-plugin/0cc223cec6d13d64cf6ac4c94065afbe83b29ff8 Log: JENKINS-48061 More finageling with dependencies Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: rsandell Path: src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java http://jenkins-ci.org/commit/git-plugin/68a956f9c3180e75b8c3c1b7d43ca2f870a82e9d Log: JENKINS-48061 Non GitSCMHeadMixin should be a branch Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: rsandell Path: src/main/java/jenkins/plugins/git/GitBranchSCMHead.java http://jenkins-ci.org/commit/git-plugin/ceabe36d1f379bad4e37573a9f6094e4e06e2525 Log: JENKINS-48061 final GitBranchSCMHead.getRef let's not let anyone hijack branch for a non-branch Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: rsandell Path: src/main/java/jenkins/plugins/git/GitRefSCMHead.java src/main/java/jenkins/plugins/git/GitRefSCMRevision.java src/main/java/jenkins/plugins/git/GitSCMHeadMixin.java http://jenkins-ci.org/commit/git-plugin/79a5e1a0bbf5bb8f949c4108f059a3551d3e417e Log: JENKINS-48061 MIT headers and a todo Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: rsandell Path: src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java http://jenkins-ci.org/commit/git-plugin/ac97524ab61e1cd2caf4ef9e1419bc410f3c0658 Log: JENKINS-48061 Do something when it's a plain ref Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: rsandell Path: src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java src/main/java/jenkins/plugins/git/GitBranchSCMHead.java src/main/java/jenkins/plugins/git/GitRefSCMHead.java src/test/java/jenkins/plugins/git/AbstractGitSCMSourceTest.java http://jenkins-ci.org/commit/git-plugin/eb8f3788eac9cca440c82f2f9f9f2903f634fd39 Log: Merge commit '919b7bf3f194eefa739e68bf27e059abc002cc2a' into JENKINS-48061 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: rsandell Path: pom.xml src/test/java/jenkins/plugins/git/GitBranchSCMHeadTest.java src/test/resources/jenkins/plugins/git/GitBranchSCMHeadTest/testMigrationNoBuildStorm.zip src/test/resources/jenkins/plugins/git/GitBranchSCMHeadTest/testMigrationNoBuildStorm_repositories.zip http://jenkins-ci.org/commit/git-plugin/54115890411a10e0a853da0ad4ec3d3c214e628c Log: JENKINS-48061 Add a test for buildstorm check This required a newer ish shared libraries plugin in the test scope which required a slightly newer jenkins core Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: rsandell Path: src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java src/main/java/jenkins/plugins/git/GitBranchSCMHead.java src/main/java/jenkins/plugins/git/GitBranchSCMRevision.java src/main/java/jenkins/plugins/git/GitSCMSource.java src/main/java/jenkins/plugins/git/GitSCMTelescope.java src/test/java/jenkins/plugins/git/GitSCMFileSystemTest.java src/test/java/jenkins/plugins/git/GitSCMSourceTest.java http://jenkins-ci.org/commit/git-plugin/50e4690cd0e32c35111dfd52e6a1d26eb9995468 Log: JENKINS-48061 Introduce GitBranchSCMHead And migrate old usage of plain SCMHead Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: rsandell Path: src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java src/main/java/jenkins/plugins/git/GitBranchSCMHead.java src/main/java/jenkins/plugins/git/GitRefSCMHead.java src/main/java/jenkins/plugins/git/GitSCMHeadMixin.java src/test/java/jenkins/plugins/git/AbstractGitSCMSourceTest.java http://jenkins-ci.org/commit/git-plugin/d49fec4bb795a573112aae0bce2b979d19066eca Log: JENKINS-48061 GitSCMHeadMixin and discover all published refs Since it seems like the git protocol doesn't allow discovering unpublished refs anyway, we can do ahead and find the sha among all published refs instead Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: rsandell Path: src/main/java/jenkins/plugins/git/GitBranchSCMHead.java src/main/java/jenkins/plugins/git/GitRefSCMHead.java src/main/java/jenkins/plugins/git/GitSCMHeadMixin.java http://jenkins-ci.org/commit/git-plugin/54c5a0306b690bdf5ae2676cdaf816d6970fcd48 Log: JENKINS-48061 Use constants not literals Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Code changed in jenkins User: rsandell Path: src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java src/main/java/jenkins/plugins/git/GitRefSCMHead.java src/main/java/jenkins/plugins/git/GitRefSCMRevision.java src/main/java/jenkins/plugins/git/GitSCMBuilder.java src/test/java/jenkins/plugins/git/AbstractGitSCMSourceTest.java http://jenkins-ci.org/commit/git-plugin/2eee3e5afa0b759f124da6439bd4652bfd3399af Log: JENKINS-48061 Introduce GitRefSCMHead Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Sam Van Oort closed an issue as Done Fixed as of 2.52 release, thanks to a fortuitous community contributor who had already done the investigation. Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Change By: Sam Van Oort Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Sam Van Oort commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads Regression appears to be caused by the ReadWrite locks around the TimingFlowNodeStorage in https://github.com/jenkinsci/workflow-cps-plugin/pull/223 using a different locking order. So, that PR fixed a threading issue (ConcurrentModificationException around the FlowNodes) and introduced another one via the fix. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-49976) Serialization of ModelASTValue$1 / $2
Title: Message Title Damien Jiang commented on JENKINS-49976 Re: Serialization of ModelASTValue$1 / $2 I noticed that more "old data" warnings are still being generated; is one of my plugins out of date and generating old datatypes? When will we stop getting these warnings? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-40695) Allow running Pipeline shared library functions on executor
Title: Message Title Steven Gantz commented on JENKINS-40695 Re: Allow running Pipeline shared library functions on executor Jesse Glick We've just run into this issue in trying to build a utility library with straight groovy. Everything was working flawlessly until we started trying to manipulate files on the node from the groovy library. Is there really no valid use-case? We have a pretty large CI workflow we are developing and our Jenkinsfile is going to get large pretty quickly. The idea in outsourcing work to the groovy lib was to utilize some object hierarchies. I know this isn't a support forum, but shared libs are intended to only run on master? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Sam Van Oort commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads Nevermind a community contributor seems to have correctly identified what seems like the only plausible cause and submitted a working PR that should fix it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Change By: Sam Van Oort Labels: deadlock regression Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-31987) Deployment is completed on websphere-deployer 1.3.4, but I got error SRVE0303E on startup
Title: Message Title Greg Peters resolved as Fixed This was likely fixed by v1.6.0 Jenkins / JENKINS-31987 Deployment is completed on websphere-deployer 1.3.4, but I got error SRVE0303E on startup Change By: Greg Peters Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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
[JIRA] (JENKINS-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Sam Van Oort assigned an issue to Sam Van Oort Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Change By: Sam Van Oort Assignee: Sam Van Oort Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-31987) Deployment is completed on websphere-deployer 1.3.4, but I got error SRVE0303E on startup
Title: Message Title Greg Peters stopped work on JENKINS-31987 Change By: Greg Peters Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51123) Deadlock in CpsFlowExecution
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51123 Re: Deadlock in CpsFlowExecution Code changed in jenkins User: Laurent Goujon Path: src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java http://jenkins-ci.org/commit/workflow-cps-plugin/4bc22731f72f24c0c007f34edb0c7018db37e0b3 Log: JENKINS-51123: Fix deadlock in CpsFlowExecution A deadlock can arise if multiple threads tries to access storage simultaneously while one of them doing it from a synchronized method. The cause is that timing operation also tries to get the instance lock from inside the storage r/w lock. Solution is to change the order of locking by having the timing object wrapping the call to the r/w storage lock instead of the opposite. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51123) Deadlock in CpsFlowExecution
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51123 Re: Deadlock in CpsFlowExecution Code changed in jenkins User: Sam Van Oort Path: src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java http://jenkins-ci.org/commit/workflow-cps-plugin/34d0b82a87be5bf71ea0e5a6b14b0abe9efec5a9 Log: Merge pull request #225 from laurentgo/laurentgo/JENKINS-51123 JENKINS-51123: Fix deadlock in CpsFlowExecution Compare: https://github.com/jenkinsci/workflow-cps-plugin/compare/2358bcde8d30...34d0b82a87be *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Sam Van Oort commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads Shannon Kerr Could be we have a deadlock somewhere or thread contention – the existing threading model was full of race conditions but the synchronization may be too agressive. Shannon Kerr Björn Pedersen could we please get a full thread dump attached to this ticket from while the issue is occurring? The one that is attached doesn't include the locks. The Support core plugin is probably the easiest way to do that. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Shannon Kerr commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads We're seeing the same behavior. Just downgraded workflow-cps and workflow-job, which we hope resolves the issue. Sam Van Oort is the related to your fixes in https://issues.jenkins-ci.org/browse/JENKINS-50888? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43709) ERROR: Maven testing.xml is not a valid file
Title: Message Title Olga Buslovich edited a comment on JENKINS-43709 Re: ERROR: Maven testing.xml is not a valid file I've run into the same issue. And this seems like something to do w/ Jenkins b/c testng-failed.xml is created and I was able to re-ran the failed tests via Eclipse.+*Suite.xml:*+thread-count="5"> Here is the pom.xml I'm using: see attachedJenkins Version: 2.89.2 Maven Config: screenshot is attached for your ref. !image-2018-05-04-13-21-04-540 My CI project is completely blocked due to this issue . png! Please help me to find the problem. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43709) ERROR: Maven testing.xml is not a valid file
Title: Message Title Olga Buslovich updated an issue Jenkins / JENKINS-43709 ERROR: Maven testing.xml is not a valid file Change By: Olga Buslovich Attachment: Maven_config.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43709) ERROR: Maven testing.xml is not a valid file
Title: Message Title Olga Buslovich edited a comment on JENKINS-43709 Re: ERROR: Maven testing.xml is not a valid file I've run into the same issue. And this seems like something to do w/ Jenkins b/c testng-failed.xml is created and I was able to re-ran the failed tests via Eclipse.+*Suite.xml:*+thread-count="5"> Here is the pom.xml I'm using: see attachedJenkins Version: 2.89.2 Maven Config: !image-2018-05-04-13-21-04-540.png! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51146) Github Branch Source does not allow `#` character within branch names
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-51146 Github Branch Source does not allow `#` character within branch names Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2018-05-04 20:11 Environment: Jenkins core at least 2.73.x LTS Github Branch source 2.3.0 Priority: Minor Reporter: Alex Taylor Something happened within the update of Github branch source plugin 2.3.0 update when combined with the update to Jenkins core 2.73.x where when you have a branch with a # character in the name it will not be able to find the branch name. Steps to recreate: Create a shared library with a branch name "Branch#Test" Attach that shared library to a Jenkins instance as a global library using the github modern SCM Create a job which loads the branch by doing @Library(SharedLibrary@Branch#Test) observe the job fails with No version Branch#Test found for library GithubLibrary This issue only happens when you update the github branch source plugin to newer than 2.3.0 and have a current version of core(from my testing) which means something in the 2.3.0 release changed this behavior. Let me know if I can provide more information
[JIRA] (JENKINS-43709) ERROR: Maven testing.xml is not a valid file
Title: Message Title Olga Buslovich edited a comment on JENKINS-43709 Re: ERROR: Maven testing.xml is not a valid file I've run into the same issue. And this seems like something to do w/ Jenkins b/c testng-failed.xml is created and I was able to re-ran the failed tests via Eclipse. +*Suite.xml:*+thread-count="5"> Here is the pom.xml I'm using:see attached Jenkins Version: 2.89.2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51064) Lenient URL validator for Root URL
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51064 Re: Lenient URL validator for Root URL Code changed in jenkins User: Wadeck Follonier Path: core/src/main/java/jenkins/org/apache/commons/validator/routines/DomainValidator.java core/src/main/java/jenkins/util/UrlHelper.java core/src/test/java/jenkins/util/UrlHelperTest.java http://jenkins-ci.org/commit/jenkins/e7eec1cbe60067871689871f12a56d496abe60a2 Log: JENKINS-51064 Lenient URL validator for Root URL (#3415) JENKINS-51064 Lenient URL validator for Root URL especially with the TLDs more test cases add blank line Adjust comment Correction typo *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43709) ERROR: Maven testing.xml is not a valid file
Title: Message Title Olga Buslovich commented on JENKINS-43709 Re: ERROR: Maven testing.xml is not a valid file I've run into the same issue. And this seems like something to do w/ Jenkins b/c testng-failed.xml is created and I was able to re-ran the failed tests via Eclipse. Here is the pom.xml I'm using:see attached Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-43709) ERROR: Maven testing.xml is not a valid file
Title: Message Title Olga Buslovich updated an issue Jenkins / JENKINS-43709 ERROR: Maven testing.xml is not a valid file Change By: Olga Buslovich Attachment: POM_xml.rtf Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-13128) Artifacts Permissions Stripped
Title: Message Title SCM/JIRA link daemon commented on JENKINS-13128 Re: Artifacts Permissions Stripped Code changed in jenkins User: Matt Sicker Path: core/src/main/java/hudson/FilePath.java core/src/main/java/hudson/model/ItemGroupMixIn.java core/src/test/java/hudson/FilePathTest.java http://jenkins-ci.org/commit/jenkins/e229f37dd921812e213e34913c94b632c6e54299 Log: JENKINS-13128: Preserve copied file permissions and mtime (#3400) JENKINS-13128: Preserve copied file permissions and mtime This fixes a bug where files copied locally do not preserve file permissions or last modification time. Use IO utility methods for exception handling Fix invalid path exception propagation Revert hudson.Util *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50825) Add editor ATH coverage for deleting stages from a pipeline
Title: Message Title Karl Shultz commented on JENKINS-50825 Re: Add editor ATH coverage for deleting stages from a pipeline PR up. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50825) Add editor ATH coverage for deleting stages from a pipeline
Title: Message Title Karl Shultz updated JENKINS-50825 Jenkins / JENKINS-50825 Add editor ATH coverage for deleting stages from a pipeline Change By: Karl Shultz Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51064) Lenient URL validator for Root URL
Title: Message Title Oleg Nenashev commented on JENKINS-51064 Re: Lenient URL validator for Root URL I am calling it an issue taking the community rating feedback. It will require backporting to LTS if 2.119 is selected Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51064) Lenient URL validator for Root URL
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51064 Lenient URL validator for Root URL Change By: Oleg Nenashev Labels: lts-candidate regression Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-31661) Jenkins.rootUrl too often unset or incorrect
Title: Message Title Oleg Nenashev commented on JENKINS-31661 Re: Jenkins.rootUrl too often unset or incorrect Hit it on my instance as well. Will link the ticket to JENKINS-51064 properly Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51064) Lenient URL validator for Root URL
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51064 Lenient URL validator for Root URL Change By: Oleg Nenashev Issue Type: Improvement Bug Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51145) PowerShell pipeline step does not seem to be durable
Title: Message Title Gabriel Loewen edited a comment on JENKINS-51145 Re: PowerShell pipeline step does not seem to be durable Durability is set to max durability (MAX_SURVIVABILITY). I've updated the environment details to include those version versions . Thanks! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51145) PowerShell pipeline step does not seem to be durable
Title: Message Title Gabriel Loewen commented on JENKINS-51145 Re: PowerShell pipeline step does not seem to be durable Durability is set to max durability (MAX_SURVIVABILITY). I've updated the environment details to include those version. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51145) PowerShell pipeline step does not seem to be durable
Title: Message Title Gabriel Loewen updated an issue Jenkins / JENKINS-51145 PowerShell pipeline step does not seem to be durable Change By: Gabriel Loewen Environment: Windows Server 2016 Datacenter, Jenkins 2.107.2, Durable Task 1.22 , workflow-support 2.18, workflow-cps 2.51, workflow-job 2.21 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50412) Fingerprints logs should be less verbose
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50412 Re: Fingerprints logs should be less verbose Code changed in jenkins User: Jeff Thompson Path: core/src/main/java/hudson/model/FingerprintCleanupThread.java core/src/test/java/hudson/model/FingerprintCleanupThreadTest.java http://jenkins-ci.org/commit/jenkins/a9eafdb973d0e9697e2f7a8a3f4e3441464398f4 Log: JENKINS-50412 Fingerprints logs should be less verbose (#3373) JENKINS-50412 - Fingerprints logs should be less verbose Eliminate the logging line that says possibly trimming /var/jenkins_home/fingerprints/[...] This line fills up the fingerprints log file with repetitive, useless information. The operation it calls provides its own logging that can be turned on if detailed logging is actually needed instead of running this one repeatedly. Also, while in the area, convert a couple of FileFilter inner classes to lambdas and inline them. This reduces unnecessary boilerplate and improves clarity. In order to make this change testable, I elected to remove the final restriction on the class and annotate the class as restricted. This allows me to create unit tests for this change and also verify existing capability at the appropriate level. Watch out for varying line endings. Use a reliable check. Correct a few minor issues caught in review. Change to correct access modifier. *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment
[JIRA] (JENKINS-51145) PowerShell pipeline step does not seem to be durable
Title: Message Title Sam Van Oort commented on JENKINS-51145 Re: PowerShell pipeline step does not seem to be durable Gabriel Loewen Do you have the durability setting for the Pipeline and the versions of workflow-support, workflow-cps, and workflow-job handy? I want to make sure that doesn't relate to a bug in one of those last 3 plugins (have been doing a lot of fixes there recently). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-37485) Propagate Job params to script does nothing
Title: Message Title Ioannis Moutsatsos commented on JENKINS-37485 Re: Propagate Job params to script does nothing Dominik Bartholdi I have tried the suggestion you provided and instead I get an error: groovy.lang.MissingPropertyException: No such property: BUILD_URL for class Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51145) PowerShell pipeline step does not seem to be durable
Title: Message Title
Gabriel Loewen updated an issue
Jenkins / JENKINS-51145
PowerShell pipeline step does not seem to be durable
Change By:
Gabriel Loewen
While running a PowerShell pipeline step I triggered a graceful shutdown, while also monitoring the powershell.exe process on the Jenkins host. The PowerShell process unexpectedly crashed, and the job failed with a -1 exit code.Job definition:{code:java}node ('Windows') { powershell ''' while (1) { write-host "Testing" Start-Sleep 1 } '''}{code}Console output:{noformat}Started by user Gabriel LoewenRunning in Durability level: MAX_SURVIVABILITY[Pipeline] nodeRunning on WinHost in C:\Program Files (x86)\Jenkins\workspace\Test Durability[Pipeline] {[Pipeline] powershell[Test Durability] Running PowerShell scriptTestingTestingTestingTestingTestingTestingTestingTestingTestingTestingTestingTestingResuming build at Fri May 04 17:40:07 UTC 2018 after Jenkins restartWaiting to resume part of Test Durability #5: ???TestingWaiting to resume part of Test Durability #5: WinHost is offlineWaiting to resume part of Test Durability #5: WinHost is offlineWaiting to resume part of Test Durability #5: WinHost is offlineReady to run at Fri May 04 17:40:19 UTC 2018TestingTestingTestingTestingTesting[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: script returned exit code -1Finished: FAILURE{noformat} I ran the same test again and this time it hung, even though the PowerShell process seems to have crashed.At this point I do not know how to debug the issue, and what can be done to ensure durability in the powershell pipeline step.[~svanoort], [~teilo], let me know if you need any more details and if you can assist in this investigation.
Add Comment
[JIRA] (JENKINS-51145) PowerShell pipeline step does not seem to be durable
Title: Message Title
Gabriel Loewen updated an issue
Jenkins / JENKINS-51145
PowerShell pipeline step does not seem to be durable
Change By:
Gabriel Loewen
While running a PowerShell pipeline step I triggered a graceful shutdown, while also monitoring the powershell.exe process on the Jenkins host. The PowerShell process unexpectedly crashed, and the job failed with a -1 exit code. Job definition:{code:java}node ('Windows') { powershell ''' while (1) { write-host "Testing" Start-Sleep 1 } '''}{code}Console output:{noformat}Started by user Gabriel LoewenRunning in Durability level: MAX_SURVIVABILITY[Pipeline] nodeRunning on WinHost in C:\Program Files (x86)\Jenkins\workspace\Test Durability[Pipeline] {[Pipeline] powershell[Test Durability] Running PowerShell scriptTestingTestingTestingTestingTestingTestingTestingTestingTestingTestingTestingTestingResuming build at Fri May 04 17:40:07 UTC 2018 after Jenkins restartWaiting to resume part of Test Durability #5: ???TestingWaiting to resume part of Test Durability #5: WinHost is offlineWaiting to resume part of Test Durability #5: WinHost is offlineWaiting to resume part of Test Durability #5: WinHost is offlineReady to run at Fri May 04 17:40:19 UTC 2018TestingTestingTestingTestingTesting[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: script returned exit code -1Finished: FAILURE{noformat} I ran the same test again and this time it hung, even though the PowerShell process seems to have crashed.At this point I do not know how to debug the issue, and what can be done to ensure durability in the powershell pipeline step.[~svanoort], let me know if you need any more details and if you can assist in this investigation.
Add Comment
[JIRA] (JENKINS-51145) PowerShell pipeline step does not seem to be durable
Title: Message Title
Gabriel Loewen updated an issue
Jenkins / JENKINS-51145
PowerShell pipeline step does not seem to be durable
Change By:
Gabriel Loewen
While running a PowerShell pipeline step I triggered a graceful shutdown, while also monitoring the powershell.exe process on the Jenkins host. The PowerShell process unexpectedly crashed, and the job failed with a -1 exit code. Job definition: {code:java}node ('Windows') { powershell ''' while (1) { write-host "Testing" Start-Sleep 1 } '''}{code}Console output: {noformat}Started by user Gabriel LoewenRunning in Durability level: MAX_SURVIVABILITY[Pipeline] nodeRunning on WinHost in C:\Program Files (x86)\Jenkins\workspace\Test Durability[Pipeline] {[Pipeline] powershell[Test Durability] Running PowerShell scriptTestingTestingTestingTestingTestingTestingTestingTestingTestingTestingTestingTestingResuming build at Fri May 04 17:40:07 UTC 2018 after Jenkins restartWaiting to resume part of Test Durability #5: ???TestingWaiting to resume part of Test Durability #5: WinHost is offlineWaiting to resume part of Test Durability #5: WinHost is offlineWaiting to resume part of Test Durability #5: WinHost is offlineReady to run at Fri May 04 17:40:19 UTC 2018TestingTestingTestingTestingTesting[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: script returned exit code -1Finished: FAILURE{noformat} I ran the same test again and this time it hung, even though the PowerShell process seems to have crashed.At this point I do not know how to debug the issue, and what can be done to ensure durability in the powershell pipeline step.[~svanoort], let me know if you need any more details and if you can assist in this investigation.
Add Comment
[JIRA] (JENKINS-51145) PowerShell pipeline step does not seem to be durable
Title: Message Title
Gabriel Loewen updated an issue
Jenkins / JENKINS-51145
PowerShell pipeline step does not seem to be durable
Change By:
Gabriel Loewen
While running a PowerShell pipeline step I triggered a graceful shutdown, while also monitoring the powershell.exe process on the Jenkins host. The PowerShell process unexpectedly crashed, and the job failed with a -1 exit code. {code:java}node ('Windows') { powershell ''' while (1) { write-host "Testing" Start-Sleep 1 } '''}{code}Console output: {noformat} Started by user Gabriel LoewenRunning in Durability level: MAX_SURVIVABILITY[Pipeline] nodeRunning on WinHost in C:\Program Files (x86)\Jenkins\workspace\Test Durability[Pipeline] {[Pipeline] powershell[Test Durability] Running PowerShell script TestingTestingTestingTestingTestingTestingTestingTestingTestingTestingTestingTestingResuming build at Fri May 04 17:40:07 UTC 2018 after Jenkins restartWaiting to resume part of Test Durability #5: ???TestingWaiting to resume part of Test Durability #5: WinHost is offlineWaiting to resume part of Test Durability #5: WinHost is offlineWaiting to resume part of Test Durability #5: WinHost is offlineReady to run at Fri May 04 17:40:19 UTC 2018TestingTestingTestingTestingTesting[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: script returned exit code -1Finished: FAILURE{noformat} I ran the same test again and this time it hung, even though the PowerShell process seems to have crashed.At this point I do not know how to debug the issue, and what can be done to ensure durability in the powershell pipeline step.[~svanoort], let me know if you need any more details and if you can assist in this investigation.
Add Comment
[JIRA] (JENKINS-51145) PowerShell pipeline step does not seem to be durable
Title: Message Title
Gabriel Loewen created an issue
Jenkins / JENKINS-51145
PowerShell pipeline step does not seem to be durable
Issue Type:
Bug
Assignee:
Gabriel Loewen
Components:
durable-task-plugin
Created:
2018-05-04 18:31
Environment:
Windows Server 2016 Datacenter, Jenkins 2.107.2, Durable Task 1.22
Priority:
Major
Reporter:
Gabriel Loewen
While running a PowerShell pipeline step I triggered a graceful shutdown, while also monitoring the powershell.exe process on the Jenkins host. The PowerShell process unexpectedly crashed, and the job failed with a -1 exit code.
node ('Windows') {
powershell '''
while (1) {
write-host "Testing"
Start-Sleep 1
}
'''
}
Console output:
Testing
Testing
Testing
Testing
Testing
Testing
Testing
Testing
Testing
Testing
Testing
Testing
Resuming build at Fri May 04 17:40:07 UTC 2018 after Jenkins restart
Waiting to resume part of Test Durability #5: ???
Testing
Waiting to resume part of Test Durability #5: WinHost is offline
Waiting to resume part of Test Durability #5: WinHost is offline
Waiting to resume part of Test Durability #5: WinHost is offline
Ready to run at Fri May 04 17:40:19 UTC 2018
Testing
Testing
Testing
Testing
Testing
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: script returned
[JIRA] (JENKINS-51144) Parameters given to seed job via pipeline jobDsl don't show up as "Build Variables" in downstream's currentBuild.upstreamBuilds
Title: Message Title Aaron Marasco commented on JENKINS-51144 Re: Parameters given to seed job via pipeline jobDsl don't show up as "Build Variables" in downstream's currentBuild.upstreamBuilds Linking to JENKINS-51038 because if that was fixed, I wouldn't have to be doing this history-wandering via currentBuild.upstreamBuilds... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51144) Parameters given to seed job via pipeline jobDsl don't show up as "Build Variables" in downstream's currentBuild.upstreamBuilds
Title: Message Title Aaron Marasco created an issue Jenkins / JENKINS-51144 Parameters given to seed job via pipeline jobDsl don't show up as "Build Variables" in downstream's currentBuild.upstreamBuilds Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2018-05-04 18:13 Environment: EnvInject 2.1.5 Job DSL 1.69 Jenkins 2.107.2 Priority: Major Reporter: Aaron Marasco I have a pipeline that calls a job dsl that calls a pipeline. We'll call them "job1", "launcher", and "job2." The idea is that I can manually run "launcher" from the Jenkins GUI, or if somebody checked a box on "job1" then it will call the launcher for you. In the job1, I use: jobDsl targets: "launcher_for_testing.groovy", lookupStrategy: 'JENKINS_ROOT', // Default I think additionalParameters: [ 'GIT_SELECTED_BRANCH': BRANCH_NAME, ], removedJobAction: 'DISABLE', sandbox: true In the launcher dsl script, I can access the "GIT_SELECTED_BRANCH" variable. If manually launched, it is a parameter of the job via the Jenkins GUI and everything is fine. If it is launched via job1, it works fine too, until... After it does a bunch of stuff to work around JENKINS-51038... def my_job =
[JIRA] (JENKINS-51136) Jenkins UI hangs 2.117 - 2.119
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51136 Jenkins UI hangs 2.117 - 2.119 Change By: Oleg Nenashev Labels: hanging jetty regression ui Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51136) Jenkins UI hangs 2.117 - 2.119
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51136 Jenkins UI hangs 2.117 - 2.119 Change By: Oleg Nenashev Labels: hanging regression ui Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51136) Jenkins UI hangs 2.117 - 2.119
Title: Message Title Oleg Nenashev commented on JENKINS-51136 Re: Jenkins UI hangs 2.117 - 2.119 Just to make sure, does it happen on versions before 2.117? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51136) Jenkins UI hangs 2.117 - 2.119
Title: Message Title Oleg Nenashev commented on JENKINS-51136 Re: Jenkins UI hangs 2.117 - 2.119 BTW, I would bet that it is caused by Jetty upgrade in 2.117. https://jenkins.io/changelog/#v2.117 FYI Olivier Lamy Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51136) Jenkins UI hangs 2.117 - 2.119
Title: Message Title Oleg Nenashev commented on JENKINS-51136 Re: Jenkins UI hangs 2.117 - 2.119 Justin Carpenter Running Jenkins on Solaris may be a problem for core maintainers. Are there any system logs? Please also enable stapler tracing and provide the report for newly opened pages. https://wiki.jenkins.io/display/JENKINS/Figuring+out+URL+binding+of+Stapler Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-47501) 2 pods are started instead of 1 after update to version 1.1
Title: Message Title Aiman Alsari commented on JENKINS-47501 Re: 2 pods are started instead of 1 after update to version 1.1 Just to update: I have found a suitable workaround. The premature call to terminate seems to come from the OnceRetentionStrategy. So if you set "idleMinutes: 1" in your podTemplate, it will use a different retention strategy. Unfortunately this means your containers get re-used so you can't guarantee the clean state of them, but it's better than nothing. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-44128) Pass custom parameters to job-dsl via pipeline step jobDsl
Title: Message Title Aaron Marasco commented on JENKINS-44128 Re: Pass custom parameters to job-dsl via pipeline step jobDsl For folks wandering here by searches, the final implemented keyword in those diffs is "additionalParameters", not "params" as originally requested in the ticket description. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-33900) save/apply button is missing when editing mutibranch jobs created inside a github organization folder
Title: Message Title Zack Snyder commented on JENKINS-33900 Re: save/apply button is missing when editing mutibranch jobs created inside a github organization folder Jesse Glick How do I trigger (or configure) a nightly build (build every midnight) via blue ocean? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51085) Reload config
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51085 Re: Reload config Code changed in jenkins User: Luca Milanesio Path: src/main/java/org/jenkins/plugins/statistics/gatherer/util/Logback.java src/main/java/org/jenkins/plugins/statistics/gatherer/util/LogbackFactory.java src/main/java/org/jenkins/plugins/statistics/gatherer/util/LogbackImpl.java src/main/java/org/jenkins/plugins/statistics/gatherer/util/URLSha.java src/test/java/org/jenkins/plugins/statistics/gatherer/util/LogbackAbstractTest.java src/test/java/org/jenkins/plugins/statistics/gatherer/util/LogbackFactoryTest.java src/test/java/org/jenkins/plugins/statistics/gatherer/util/LogbackFixture.java src/test/java/org/jenkins/plugins/statistics/gatherer/util/LogbackImplTest.java http://jenkins-ci.org/commit/statistics-gatherer-plugin/969edba3f9d91773e1cc515edfebaa8595e61be8 Log: JENKINS-51085 Auto-refresh LOGBack config when changed When the logback XML configuration has changed, reload the in-memory logger transparently. If the reload fails, keep the existing well-known configuration. Change-Id: I99392adc2c9e316946d985c88f0a10dc1c09 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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
[JIRA] (JENKINS-51143) List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs
Title: Message Title Wolfgang Kiendl updated an issue Jenkins / JENKINS-51143 List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs Change By: Wolfgang Kiendl Summary: List view section: Job statuses Statuses Filter on disabled doesn't work for pipeline jobs Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51143) List view section: Job statuses Filter on disabled doesn't work for pipeline jobs
Title: Message Title Wolfgang Kiendl created an issue Jenkins / JENKINS-51143 List view section: Job statuses Filter on disabled doesn't work for pipeline jobs Issue Type: Bug Assignee: Timothy Bingaman Components: pipeline, sectioned-view-plugin, view-job-filters-plugin Created: 2018-05-04 16:11 Environment: System Properties Name ↓ Value awt.toolkit sun.awt.windows.WToolkit com.sun.management.jmxremote.authenticate false com.sun.management.jmxremote.port 9005 com.sun.management.jmxremote.ssl false executable-war K:\JENKINS\jenkins.war file.encoding Cp1252 file.encoding.pkg sun.io file.separator \ hudson.consoleTailKB 1024 hudson.Functions.autoRefreshSeconds 60 hudson.lifecycle hudson.lifecycle.WindowsServiceLifecycle hudson.matrix.MatrixConfiguration.useShortWorkspaceName true hudson.model.DirectoryBrowserSupport.CSP sandbox; default-src 'none'; img-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; hudson.model.ParametersAction.keepUndefinedParameters true hudson.model.Slave.workspaceRoot WS hudson.plugins.tmpcleaner.TmpCleanWork.days 1 hudson.plugins.tmpcleaner.TmpCleanWork.minutes 720 java.awt.graphicsenv sun.awt.Win32GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.awt.windows.WPrinterJob java.class.path K:\JENKINS\jenkins.war java.class.version 52.0 java.endorsed.dirs D:\sApps\java\jdks\1.8\jre\lib\endorsed java.ext.dirs D:\sApps\java\jdks\1.8\jre\lib\ext;C:\windows\Sun\Java\lib\ext java.home D:\sApps\java\jdks\1.8\jre java.io.tmpdir C:\windows\TEMP\ java.library.path D:\sApps\java\jdks\1.8\bin;C:\windows\Sun\Java\bin;C:\windows\system32;C:\windows;D:\sApps\NetWorker\nsr\bin;D:\sApps\SVN_1.8;C:\ProgramData\Oracle\Java\javapath;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;D:\sApps\java\jdks\1.8\BIN;D:\DEV\CI\TOOLS\BIN;D:\DEV\CI\TOOLS\CYGWIN\x64\bin;D:\sApps\Git-2.x\cmd;;. java.net.preferIPv4Stack true java.rmi.server.randomIDs true java.runtime.name Java(TM) SE Runtime Environment java.runtime.version 1.8.0_131-b11 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.8 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.8.0_131 java.vm.info mixed mode java.vm.name Java HotSpot(TM) 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.8 java.vm.vendor Oracle Corporation java.vm.version 25.131-b11
[JIRA] (JENKINS-44910) Error: EACCES: permission denied, mkdir '/home/jenkins/.npm' in container
Title: Message Title Xin Meng commented on JENKINS-44910 Re: Error: EACCES: permission denied, mkdir '/home/jenkins/.npm' in container someone said add env to the docker https://stackoverflow.com/questions/42743201/npm-install-fails-in-jenkins-pipeline-in-docker/42957034?utm_medium=organic_source=google_rich_qa_campaign=google_rich_qa Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51085) Reload config
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51085 Re: Reload config Code changed in jenkins User: Luca Milanesio Path: src/main/java/org/jenkins/plugins/statistics/gatherer/util/Logback.java src/main/java/org/jenkins/plugins/statistics/gatherer/util/LogbackFactory.java src/main/java/org/jenkins/plugins/statistics/gatherer/util/LogbackImpl.java src/main/java/org/jenkins/plugins/statistics/gatherer/util/URLSha.java src/test/java/org/jenkins/plugins/statistics/gatherer/util/LogbackAbstractTest.java src/test/java/org/jenkins/plugins/statistics/gatherer/util/LogbackFactoryTest.java src/test/java/org/jenkins/plugins/statistics/gatherer/util/LogbackFixture.java src/test/java/org/jenkins/plugins/statistics/gatherer/util/LogbackImplTest.java http://jenkins-ci.org/commit/statistics-gatherer-plugin/ab42965e2dabcced67712248d16e8950ab7d47bd Log: JENKINS-51085 Auto-refresh LOGBack config when changed When the logback XML configuration has changed, reload the in-memory logger transparently. If the reload fails, keep the existing well-known configuration. Change-Id: I99392adc2c9e316946d985c88f0a10dc1c09 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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
[JIRA] (JENKINS-50548) Shared Library should be allowed to declare reusable stages
Title: Message Title
Marcelo Luiz Onhate edited a comment on JENKINS-50548
Re: Shared Library should be allowed to declare reusable stages
Hello,As a suggestion you can use the (not well documented) feature that loads scripts on the fly.this will load the libs from the same repository and branch you are checking out, it will go to folder {color:red}/vars/{color} and load all .groovy files. { color:red noformat } library identifier: "setup@$BRANCH_NAME", retriever: legacySCM(scm) { color noformat } {noformat}/- vars/- deploy.groovy- setup.groovy{noformat}The name of the .groovy script will become a step on pipeline, as you can see the steps *setup* and *deploy*. {code:java}#!groovyscript {library identifier: "setup@$BRANCH_NAME", retriever: legacySCM(scm)}pipeline {stages {stage('Setup & Deploy') {steps {setup()deploy()}}}}{code}{color:red}setup.groovy{color}{code:java}#!/usr/bin/env groovydef call() {sh "echo 'YEAH'"sh "some/other/script.sh"}{code}{color:red}deploy.groovy{color}{code:java}#!/usr/bin/env groovydef call() {def props = readProperties file: 'environment.env'env.PROP_1 = props['PROP_1']sh "script/that/uses/PROP_1"}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google 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-50548) Shared Library should be allowed to declare reusable stages
Title: Message Title
Marcelo Luiz Onhate edited a comment on JENKINS-50548
Re: Shared Library should be allowed to declare reusable stages
Hello,As a suggestion you can use the (not well documented) feature that loads scripts on the fly. {code:java}#!groovyscript {library identifier: "setup@$BRANCH_NAME", retriever: legacySCM(scm)}pipeline {stages {stage('Setup & Deploy') {steps {setup()deploy()}}}}{code} this will load the libs from the same repository and branch you are checking out, it will go to folder {color:red}/vars/{color} and load all .groovy files.{noformat}library identifier: "setup@$BRANCH_NAME", retriever: legacySCM(scm){noformat}{noformat}/- vars/- deploy.groovy- setup.groovy{noformat}The name of the .groovy script will become a step on pipeline, as you can see the steps *setup* and *deploy*. { code:java}#!groovyscript {library identifier: "setup@$BRANCH_NAME", retriever: legacySCM(scm)}pipeline {stages {stage('Setup & Deploy') {steps {setup()deploy()}}}}{code}{ color:red}setup.groovy{color}{code:java}#!/usr/bin/env groovydef call() {sh "echo 'YEAH'"sh "some/other/script.sh"}{code}{color:red}deploy.groovy{color}{code:java}#!/usr/bin/env groovydef call() {def props = readProperties file: 'environment.env'env.PROP_1 = props['PROP_1']sh "script/that/uses/PROP_1"}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-50548) Shared Library should be allowed to declare reusable stages
Title: Message Title
Marcelo Luiz Onhate commented on JENKINS-50548
Re: Shared Library should be allowed to declare reusable stages
Hello, As a suggestion you can use the (not well documented) feature that loads scripts on the fly. this will load the libs from the same repository and branch you are checking out, it will go to folder /vars/ and load all .groovy files. library identifier: "setup@$BRANCH_NAME", retriever: legacySCM(scm)
/
- vars/
- deploy.groovy
- setup.groovy
The name of the .groovy script will become a step on pipeline, as you can see the steps setup and deploy.
#!groovy
script {
library identifier: "setup@$BRANCH_NAME", retriever: legacySCM(scm)
}
pipeline {
stages {
stage('Setup & Deploy') {
steps {
setup()
deploy()
}
}
}
}
setup.groovy
#!/usr/bin/env groovy
def call() {
sh "echo 'YEAH'"
sh "some/other/script.sh"
}
deploy.groovy
#!/usr/bin/env groovy
def call() {
def props = readProperties file: 'environment.env'
env.PROP_1 = props['PROP_1']
sh "script/that/uses/PROP_1"
}
Add Comment
[JIRA] (JENKINS-27299) Refactor Disable Build feature out of AbstractProject for Pipeline Compatibility
Title: Message Title Daniel Beck commented on JENKINS-27299 Re: Refactor Disable Build feature out of AbstractProject for Pipeline Compatibility Might be https://plugins.jenkins.io/view-job-filters if you're using that, but core's List view also has a boolean flag to only include enabled jobs. Either, or both. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51094) Custom WAR Packager - Support building with LATEST versions from Incrementals repo
Title: Message Title Jesse Glick commented on JENKINS-51094 Re: Custom WAR Packager - Support building with LATEST versions from Incrementals repo I would rather recommend the BOM pin a version, keeping the WAR packager simpler and deterministic, and have JENKINS-50953 offer the change in configuration. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-27299) Refactor Disable Build feature out of AbstractProject for Pipeline Compatibility
Title: Message Title Wolfgang Kiendl commented on JENKINS-27299 Re: Refactor Disable Build feature out of AbstractProject for Pipeline Compatibility For a normal pipeline job I now have the button and can disable it, however it does not appear in views that filter on disabled jobs (List View section, Job Statuses Filter). Is this another bug that should be reported separately because it probably belongs to another component? If so, could you give me a hint which component this might belong to? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50953) Tool to offer incremental updates
Title: Message Title Jesse Glick commented on JENKINS-50953 Re: Tool to offer incremental updates Example of BOM load/save code. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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.
