[JIRA] (JENKINS-41086) Performance plugin support in dsl plugin
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-41086 Performance plugin support in dsl plugin Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-41086) Performance plugin support in dsl plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41086 Re: Performance plugin support in dsl plugin Code changed in jenkins User: Andrey Pokhilko Path: src/main/java/hudson/plugins/performance/PerformancePublisher.java src/test/java/hudson/plugins/performance/PerformancePublisherTest.java src/test/java/hudson/plugins/performance/constraints/ConstraintTest.java http://jenkins-ci.org/commit/performance-plugin/a670083b8e07768d02dcafd6e8b279fb5ff58633 Log: Merge pull request #82 from daspilker/JENKINS-41086 JENKINS-41086 avoid wildcard in @DataBoundConstructor Compare: https://github.com/jenkinsci/performance-plugin/compare/2c37d5350b30...a670083b8e07 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-41086) Performance plugin support in dsl plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41086 Re: Performance plugin support in dsl plugin Code changed in jenkins User: Daniel Spilker Path: src/main/java/hudson/plugins/performance/PerformancePublisher.java src/test/java/hudson/plugins/performance/PerformancePublisherTest.java src/test/java/hudson/plugins/performance/constraints/ConstraintTest.java http://jenkins-ci.org/commit/performance-plugin/062b2150527bfa21cb7a22ed136aeba00b0422e7 Log: avoid wildcard in @DataBoundConstructor [FIXES JENKINS-41086] Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42319) Broken method compareTo method of Run
Title: Message Title Alexander A created an issue Jenkins / JENKINS-42319 Broken method compareTo method of Run Issue Type: Task Assignee: Alexander A Components: core Created: 2017/Feb/25 8:59 AM Priority: Major Reporter: Alexander A Current implementation relies on fact that users always compare run objects with same parent. But this is not always the case. As result TreeSet can not be safely used with Run objects from different parents. Add Comment This message was sent by Atlassian JIRA (v7
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Mark Grills commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Hi Stefan, refer my comments above. This fixed it for us. Cheers Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-39482) GitHub commit status not working with GitHubCommitStatusSetter on first build of branch in multi-branch pipeline
Title: Message Title Kirill Merkushev commented on JENKINS-39482 Re: GitHub commit status not working with GitHubCommitStatusSetter on first build of branch in multi-branch pipeline JENKINS-41795 is not related to this issue. How it works with defaults - pipeline is a just text for jenkins and jenkins knows nothing about content of the script before first evaluation. Status step tries to find defined repos with dedicated jenkins api. But when jenkins dont know about script content - it can't provide info about repos to the status setter step. As a workaround for short-living jobs you can define repo with manual provider (as in Peter Springsteen's example) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42010) Issue with executing PTC-MKS integrity SI commands in jenkins
Title: Message Title PTC ALM commented on JENKINS-42010 Re: Issue with executing PTC-MKS integrity SI commands in jenkins Hi Sudarshan, There is a recent problem posed on the PTC community which is an exact same problem that you're facing. https://www.ptcusercommunity.com/message/479748 You could follow the suggestion given in the thread above and give your problem a try. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42320) pipeline shared library changes repeatedly trigger failing jobs
Title: Message Title Paul Thomas created an issue Jenkins / JENKINS-42320 pipeline shared library changes repeatedly trigger failing jobs Issue Type: Bug Assignee: Unassigned Components: workflow-cps-global-lib-plugin Created: 2017/Feb/25 11:59 AM Environment: Jenkins 2.47 plugin 2.6 Priority: Minor Reporter: Paul Thomas Making an update to a shared library (accessed via git) causes all jobs using the library and SCM polling to re-build (see JENKINS-41497). If the build fails, the job is repeatedly re-built. It's annoying that it triggers at all, but it should definitely only do it once. Add Comment
[JIRA] (JENKINS-42321) Run ansible via durable step infrastructure
Title: Message Title Anton Lundin created an issue Jenkins / JENKINS-42321 Run ansible via durable step infrastructure Issue Type: Bug Assignee: Jean-Christophe Sirot Components: ansible-plugin Created: 2017/Feb/25 12:29 PM Priority: Major Reporter: Anton Lundin One of the awesome features with Jenkins pipeline is that you can restart your jenkins istance on the fly, thanks to CPS and durable steps. On the other hand, ansible-plugin doesn't run ansible via durable step, so that process dies when you restart jenkins. If you have really long running deploys, its really nice to be able to restart your jenkins instance meanwhile. Add Comment
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Stefan Walter commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Hi Mark Grills, thanks a lot for your suggestion. It seems that this solved our issues. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-39515) Failed to install Go 1.7.3
Title: Message Title Christopher Orr closed an issue as Won't Fix Since the archive files have apparently been fixed for the current and future Go releases, there's not really anything to be done here. Of course, Jenkins could handle this type of .gz file better, but that's a matter for the linked upstream issue. If anybody needs to install the previous Go releases, they should use the "install from local archive" functionality. Jenkins / JENKINS-39515 Failed to install Go 1.7.3 Change By: Christopher Orr Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-27499) Global config page is broken when loaded before the tool installer data has been fetched
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27499 Re: Global config page is broken when loaded before the tool installer data has been fetched Code changed in jenkins User: Christopher Orr Path: src/main/java/org/jenkinsci/plugins/golang/GolangInstaller.java src/main/resources/org/jenkinsci/plugins/golang/GolangInstaller/config.groovy http://jenkins-ci.org/commit/golang-plugin/207027e5164d90c2cce988faeaa566db37eab321 Log: [FIX JENKINS-27499] Don't break tool config page if version metadata is missing. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-27499) Global config page is broken when loaded before the tool installer data has been fetched
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-27499 Global config page is broken when loaded before the tool installer data has been fetched Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-34345) Add pipeline support
Title: Message Title Christopher Orr resolved as Fixed This plugin worked anyway with the 'tool' step, but I've now added a symbol, so the tool can be referred to as 'go', rather than its fully qualified class name. Jenkins / JENKINS-34345 Add pipeline support Change By: Christopher Orr Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+un
[JIRA] (JENKINS-34345) Add pipeline support
Title: Message Title Christopher Orr closed an issue as Fixed Released in version 1.2 of the plugin. Jenkins / JENKINS-34345 Add pipeline support Change By: Christopher Orr Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-27499) Global config page is broken when loaded before the tool installer data has been fetched
Title: Message Title Christopher Orr closed an issue as Fixed Released in version 1.2 of the plugin. Jenkins / JENKINS-27499 Global config page is broken when loaded before the tool installer data has been fetched Change By: Christopher Orr Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-31598) Bump commons-collections lib from 3.2.1 to 3.2.2
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31598 Re: Bump commons-collections lib from 3.2.1 to 3.2.2 Code changed in jenkins User: PJ Fanning Path: core/pom.xml test/src/test/java/jenkins/security/Security218CliTest.java http://jenkins-ci.org/commit/jenkins/46d3f2e1d0bee7098e630d9c6913fe25bb2b3753 Log: JENKINS-31598 upgrade commons-collections due to CVE against v3.2.1 (#2761) JENKINS-31598 upgrade commons-collections due to CVE against v3.2.1 Fix broken tests Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42322) Fail to rm a container started with inside {}
Title: Message Title
Kevin REMY created an issue
Jenkins / JENKINS-42322
Fail to rm a container started with inside {}
Issue Type:
Bug
Assignee:
Unassigned
Components:
docker-workflow-plugin
Created:
2017/Feb/25 7:29 PM
Environment:
Jenkins 2.46 Debian GNU/Linux 7.8 / Docker 1.13.1 Docker worflow plugin 1.10
Labels:
plugin
Priority:
Major
Reporter:
Kevin REMY
Hi, I've recently upgraded the docker workflow plugin from 1.8 to 1.10, in 1.8 my pipeline worked perfectly well, It uses 2 external containers and 1 where actions are done into. In 1.10 I have the following error on the container launched with .inside { } method : $ docker stop --time=1 6b4b512400884e660dc4cd4eda6e9b3d7c358317f08a1c46399b5253ec7e1b02 $ docker rm -f 6b4b512400884e660dc4cd4eda6e9b3d7c358317f08a1c46399b5253ec7e1b02 ERROR: Timeout after 10 seconds And the job, fail with java.io.IOException: Failed to rm container '6b4b512400884e660dc4cd4eda6e9b3d7c358317f08a1c46399b5253ec7e1b02'. at org.jenkinsci.plugins.docker.workflow.client.DockerClient.rm(DockerClient.java:158) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.stop(DockerClient.java:145) at org.jenkinsci.plugins.docker.workflow.WithContainerStep.destroy(WithContainerStep.java:107) at org.jenkinsci.plugins.docker.workflow.WithContainerStep.access$400(WithContainerStep.java:74) at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Callback.finished(WithContainerStep.java:302) at org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback$TailCall.onSuccess(BodyExecutionCallback.java:114) at org.jenkinsci.plugins.workflow.cps
[JIRA] (JENKINS-37899) Git client does not call CredentialsProvider.snapshot() when adding credentials to a SmartCredentialsProvider that will be used on a remote instance
Title: Message Title Cyrille Le Clerc commented on JENKINS-37899 Re: Git client does not call CredentialsProvider.snapshot() when adding credentials to a SmartCredentialsProvider that will be used on a remote instance > I'm still unable to make the git plugin work with a passphrase protected ssh private key on a local or a remote agent. I think I understand. Here are my tests SSH Key Build on Result Private Key=Enter directly, passphrase=no master Private Key=Enter directly, passphrase=yes master Private Key=Enter directly, passphrase=yes remote build agent via ssh Private Key=From a file on Jenkins master, passphrase=yes remote build agent via ssh Environment Git client plugin (git-client): 2.3.0-SNAPSHOT -> latest from github Ant Plugin (ant): 1.2 OWASP Markup Formatter Plugin (antisamy-markup-formatter): 1.1 Credentials Plugin (credentials): 2.1.12 CVS Plug-in (cvs): 2.11 Display URL API (display-url-api): 1.1.1 External Monitor Job Type Plugin (external-monitor-job): 1.4 GIT server Plugin (git-server): 1.7 Git plugin (git): 3.0.5 Javadoc Plugin (javadoc): 1.1 JUnit Plugin (junit): 1.20 LDAP Plugin (ldap): 1.11 Mailer Plugin (mailer): 1.19 Matrix Authorization Strategy Plugin (matrix-auth): 1.1 Matrix Project Plugin (matrix-project): 1.8 Maven Integration plugin (maven-plugin): 2.7.1
[JIRA] (JENKINS-37899) Git client does not call CredentialsProvider.snapshot() when adding credentials to a SmartCredentialsProvider that will be used on a remote instance
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-37899
Re: Git client does not call CredentialsProvider.snapshot() when adding credentials to a SmartCredentialsProvider that will be used on a remote instance
> I'm still unable to make the git plugin work with a passphrase protected ssh private key on a local or a remote agent. I think I understand. Here are my tests , is it what you mean? || SSH Key || Build on || Result ||| Private Key=Enter directly, passphrase=no | master | (/) || Private Key=Enter directly, passphrase=yes | master | (/) || Private Key=Enter directly, passphrase=yes | remote build agent via ssh | (/) || Private Key=From a file on Jenkins master, passphrase=yes | remote build agent via ssh | (x) | | Private Key=From a file on Jenkins master, passphrase=no | remote build agent via ssh | (/) | Environment{noformat}Git client plugin (git-client): 2.3.0-SNAPSHOT -> latest from githubAnt Plugin (ant): 1.2OWASP Markup Formatter Plugin (antisamy-markup-formatter): 1.1Credentials Plugin (credentials): 2.1.12CVS Plug-in (cvs): 2.11Display URL API (display-url-api): 1.1.1External Monitor Job Type Plugin (external-monitor-job): 1.4GIT server Plugin (git-server): 1.7Git plugin (git): 3.0.5Javadoc Plugin (javadoc): 1.1JUnit Plugin (junit): 1.20LDAP Plugin (ldap): 1.11Mailer Plugin (mailer): 1.19Matrix Authorization Strategy Plugin (matrix-auth): 1.1Matrix Project Plugin (matrix-project): 1.8Maven Integration plugin (maven-plugin): 2.7.1PAM Authentication plugin (pam-auth): 1.1SCM API Plugin (scm-api): 2.0.7Script Security Plugin (script-security): 1.13SSH Credentials Plugin (ssh-credentials): 1.12SSH Slaves plugin (ssh-slaves): 1.9Structs Plugin (structs): 1.5Subversion Plug-in (subversion): 1.54Translation Assistance plugin (translation): 1.10Windows Slaves Plugin (windows-slaves): 1.0Pipeline: SCM Step (workflow-scm-step): 1.14.2Pipeline: Step API (workflow-step-api): 1.14.2{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37899) Git client does not call CredentialsProvider.snapshot() when adding credentials to a SmartCredentialsProvider that will be used on a remote instance
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-37899
Re: Git client does not call CredentialsProvider.snapshot() when adding credentials to a SmartCredentialsProvider that will be used on a remote instance
> I'm still unable to make the git plugin work with a passphrase protected ssh private key on a local or a remote agent.Here are my tests, is it what you mean?|| SSH Key || Build on || Result ||| Private Key=Enter directly, passphrase=no | master | (/) || Private Key=Enter directly, passphrase=yes | master | (/) || Private Key=Enter directly, passphrase=yes | remote build agent via ssh | (/) || Private Key=From a file on Jenkins master, passphrase=yes | remote build agent via ssh | ( x / ) || Private Key=From a file on Jenkins master, passphrase=no | remote build agent via ssh | (/) |Environment{noformat}Git client plugin (git-client): 2.3.0-SNAPSHOT -> latest from githubAnt Plugin (ant): 1.2OWASP Markup Formatter Plugin (antisamy-markup-formatter): 1.1Credentials Plugin (credentials): 2.1.12CVS Plug-in (cvs): 2.11Display URL API (display-url-api): 1.1.1External Monitor Job Type Plugin (external-monitor-job): 1.4GIT server Plugin (git-server): 1.7Git plugin (git): 3.0.5Javadoc Plugin (javadoc): 1.1JUnit Plugin (junit): 1.20LDAP Plugin (ldap): 1.11Mailer Plugin (mailer): 1.19Matrix Authorization Strategy Plugin (matrix-auth): 1.1Matrix Project Plugin (matrix-project): 1.8Maven Integration plugin (maven-plugin): 2.7.1PAM Authentication plugin (pam-auth): 1.1SCM API Plugin (scm-api): 2.0.7Script Security Plugin (script-security): 1.13SSH Credentials Plugin (ssh-credentials): 1.12SSH Slaves plugin (ssh-slaves): 1.9Structs Plugin (structs): 1.5Subversion Plug-in (subversion): 1.54Translation Assistance plugin (translation): 1.10Windows Slaves Plugin (windows-slaves): 1.0Pipeline: SCM Step (workflow-scm-step): 1.14.2Pipeline: Step API (workflow-step-api): 1.14.2{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42322) Fail to rm a container started with inside {}
Title: Message Title
Kevin REMY updated an issue
Jenkins / JENKINS-42322
Fail to rm a container started with inside {}
Change By:
Kevin REMY
Hi,I've recently upgraded the docker workflow plugin from 1.8 to 1.10, in 1.8 my pipeline worked perfectly well, It uses 2 external containers and 1 where actions are done into.In 1.10 I have the following error on the container launched with .inside { } method :$ docker stop --time=1 6b4b512400884e660dc4cd4eda6e9b3d7c358317f08a1c46399b5253ec7e1b02$ docker rm -f 6b4b512400884e660dc4cd4eda6e9b3d7c358317f08a1c46399b5253ec7e1b02ERROR: Timeout after 10 secondsAnd the job, fail with {{ java.io.IOException: Failed to rm container '6b4b512400884e660dc4cd4eda6e9b3d7c358317f08a1c46399b5253ec7e1b02'. at org.jenkinsci.plugins.docker.workflow.client.DockerClient.rm(DockerClient.java:158) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.stop(DockerClient.java:145) at org.jenkinsci.plugins.docker.workflow.WithContainerStep.destroy(WithContainerStep.java:107) at org.jenkinsci.plugins.docker.workflow.WithContainerStep.access$400(WithContainerStep.java:74) at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Callback.finished(WithContainerStep.java:302) at org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback$TailCall.onSuccess(BodyExecutionCallback.java:114) at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter.receive(CpsBodyExecution.java:362) at com.cloudbees.groovy.cps.Outcome.resumeFrom(Outcome.java:73) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:146) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:165) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:328) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:80) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:240) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:228) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPo
[JIRA] (JENKINS-42322) Fail to rm a container started with inside {}
Title: Message Title
Kevin REMY updated an issue
Jenkins / JENKINS-42322
Fail to rm a container started with inside {}
Change By:
Kevin REMY
Hi,I've recently upgraded the docker workflow plugin from 1.8 to 1.10, in 1.8 my pipeline worked perfectly well, It uses 2 external containers and 1 where actions are done into.In 1.10 I have the following error on the container launched with .inside { } method :$ docker stop --time=1 6b4b512400884e660dc4cd4eda6e9b3d7c358317f08a1c46399b5253ec7e1b02$ docker rm -f 6b4b512400884e660dc4cd4eda6e9b3d7c358317f08a1c46399b5253ec7e1b02ERROR: Timeout after 10 secondsAnd the job, fail with { { code: java }java .io.IOException: Failed to rm container '6b4b512400884e660dc4cd4eda6e9b3d7c358317f08a1c46399b5253ec7e1b02'. at org.jenkinsci.plugins.docker.workflow.client.DockerClient.rm(DockerClient.java:158) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.stop(DockerClient.java:145) at org.jenkinsci.plugins.docker.workflow.WithContainerStep.destroy(WithContainerStep.java:107) at org.jenkinsci.plugins.docker.workflow.WithContainerStep.access$400(WithContainerStep.java:74) at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Callback.finished(WithContainerStep.java:302) at org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback$TailCall.onSuccess(BodyExecutionCallback.java:114) at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter.receive(CpsBodyExecution.java:362) at com.cloudbees.groovy.cps.Outcome.resumeFrom(Outcome.java:73) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:146) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:165) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:328) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:80) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:240) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:228) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.conc
[JIRA] (JENKINS-42322) Fail to rm a container started with inside {}
Title: Message Title
Kevin REMY updated an issue
Jenkins / JENKINS-42322
Fail to rm a container started with inside {}
Change By:
Kevin REMY
Hi,I've recently upgraded the docker workflow plugin from 1.8 to 1.10, in 1.8 my pipeline worked perfectly well, It uses 2 external containers and 1 where actions are done into.In 1.10 I have the following error on the container launched with .inside { } method : {code:bash} $ docker stop --time=1 6b4b512400884e660dc4cd4eda6e9b3d7c358317f08a1c46399b5253ec7e1b02$ docker rm -f 6b4b512400884e660dc4cd4eda6e9b3d7c358317f08a1c46399b5253ec7e1b02ERROR: Timeout after 10 seconds {code} And the job, fail with {code:java}java.io.IOException: Failed to rm container '6b4b512400884e660dc4cd4eda6e9b3d7c358317f08a1c46399b5253ec7e1b02'. at org.jenkinsci.plugins.docker.workflow.client.DockerClient.rm(DockerClient.java:158) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.stop(DockerClient.java:145) at org.jenkinsci.plugins.docker.workflow.WithContainerStep.destroy(WithContainerStep.java:107) at org.jenkinsci.plugins.docker.workflow.WithContainerStep.access$400(WithContainerStep.java:74) at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Callback.finished(WithContainerStep.java:302) at org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback$TailCall.onSuccess(BodyExecutionCallback.java:114) at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter.receive(CpsBodyExecution.java:362) at com.cloudbees.groovy.cps.Outcome.resumeFrom(Outcome.java:73) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:146) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:165) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:328) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:80) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:240) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:228) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at
[JIRA] (JENKINS-42323) NodeJS plugin 1.1.2 -- PATH not including node + npm
Title: Message Title Jeff Blaine created an issue Jenkins / JENKINS-42323 NodeJS plugin 1.1.2 -- PATH not including node + npm Issue Type: Bug Assignee: Unassigned Components: nodejs-plugin Created: 2017/Feb/25 10:03 PM Environment: Jenkins 2.32.2 LTS NodeJS Plugin 1.1.2 Priority: Critical Reporter: Jeff Blaine I see other issues here that report of conflicts with EnvInject and/or MultiJob. Both are required for our company's usage. Simple functional test job in Jenkins configured as: [*] Provide Node & npm bin/ folder to PATH Execute Shell Script echo $PATH which node which npm npm install -g bower Fails to include appropriate NodeJS installation in PATH: Started by user Charles Blaine [EnvInject] - Loading node environment variables. Building remotely on etc-jenkins-rh7-1 (rh7 rhel7 ruby20) in workspace /var/lib/jenkins/workspace/R701-Data/BowerTest [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Done [BowerTest] $ /bin/bash -xe /tmp/hudson2605021362659101820.sh + echo /usr/local/bin:/usr/bin /usr/local/b
[JIRA] (JENKINS-42310) MAVEN and MATRIX are not linted in some defects
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42310 Re: MAVEN and MATRIX are not linted in some defects Code changed in jenkins User: Victor Martinez Path: src/main/java/org/jenkins/ci/plugins/jenkinslint/check/ArtifactChecker.java http://jenkins-ci.org/commit/jenkinslint-plugin/cf799aa076f59571f5ff4e38c17d8f8dbd3c Log: JENKINS-42310 Artifact Lint defect support Maven and Matrix projects Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42310) MAVEN and MATRIX are not linted in some defects
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42310 Re: MAVEN and MATRIX are not linted in some defects Code changed in jenkins User: Victor Martinez Path: src/test/java/org/jenkins/ci/plugins/jenkinslint/check/NullSCMCheckerTestCase.java http://jenkins-ci.org/commit/jenkinslint-plugin/41f434542d170df192fb9e03f2a9b6c56a73d6e2 Log: JENKINS-42310 Added Test cases for the NullSCM Lint defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42310) MAVEN and MATRIX are not linted in some defects
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42310 Re: MAVEN and MATRIX are not linted in some defects Code changed in jenkins User: Victor Martinez Path: src/main/java/org/jenkins/ci/plugins/jenkinslint/check/TimerTriggerChecker.java http://jenkins-ci.org/commit/jenkinslint-plugin/fc5ecdea507752b7fb2f8b6518905079ec4136fb Log: JENKINS-42310 TimerTrigger Lint defect support Maven and Matrix projects Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42310) MAVEN and MATRIX are not linted in some defects
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42310 Re: MAVEN and MATRIX are not linted in some defects Code changed in jenkins User: Victor Martinez Path: src/main/java/org/jenkins/ci/plugins/jenkinslint/check/NullSCMChecker.java http://jenkins-ci.org/commit/jenkinslint-plugin/6770f331bf72227e78f43435a4ad07aa076f7e38 Log: JENKINS-42310 NullSCM Lint defect support Maven and Matrix projects Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42310) MAVEN and MATRIX are not linted in some defects
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42310 Re: MAVEN and MATRIX are not linted in some defects Code changed in jenkins User: Victor Martinez Path: src/main/java/org/jenkins/ci/plugins/jenkinslint/check/GitRefChecker.java http://jenkins-ci.org/commit/jenkinslint-plugin/ece383c0fca8267db54c6c7dc907920e77471a63 Log: JENKINS-42310 GitRef Lint defect support Maven and Matrix projects Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42310) MAVEN and MATRIX are not linted in some defects
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42310 Re: MAVEN and MATRIX are not linted in some defects Code changed in jenkins User: Victor Martinez Path: src/test/java/org/jenkins/ci/plugins/jenkinslint/check/JavadocCheckerTestCase.java http://jenkins-ci.org/commit/jenkinslint-plugin/dfad147f6c7db6861bbb4f9f2843b1fbc21bcfed Log: JENKINS-42310 Added Test cases for the Javadoc Lint defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42310) MAVEN and MATRIX are not linted in some defects
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42310 Re: MAVEN and MATRIX are not linted in some defects Code changed in jenkins User: Victor Martinez Path: src/main/java/org/jenkins/ci/plugins/jenkinslint/check/JavadocChecker.java http://jenkins-ci.org/commit/jenkinslint-plugin/55b5e4c70d0460a50531f96680d678706b574833 Log: JENKINS-42310 Javadoc Lint defect support Maven and Matrix projects Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42310) MAVEN and MATRIX are not linted in some defects
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42310 Re: MAVEN and MATRIX are not linted in some defects Code changed in jenkins User: Victor Martinez Path: src/test/java/org/jenkins/ci/plugins/jenkinslint/check/JobAssignedLabelCheckerTestCase.java http://jenkins-ci.org/commit/jenkinslint-plugin/d6b777507369020ff3a4eeca10234eb0ab98b4f7 Log: JENKINS-42310 Changed Test Cases names Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42310) MAVEN and MATRIX are not linted in some defects
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42310 Re: MAVEN and MATRIX are not linted in some defects Code changed in jenkins User: Victor Martinez Path: src/test/java/org/jenkins/ci/plugins/jenkinslint/check/ArtifactCheckerTestCase.java http://jenkins-ci.org/commit/jenkinslint-plugin/a90bc61e7a0638eb415be30bcfcccb340d936f51 Log: JENKINS-42310 Added Test cases for the Artifact Lint defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42310) MAVEN and MATRIX are not linted in some defects
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42310 Re: MAVEN and MATRIX are not linted in some defects Code changed in jenkins User: Victor Martinez Path: src/test/java/org/jenkins/ci/plugins/jenkinslint/check/TimerTriggerCheckerTestCase.java http://jenkins-ci.org/commit/jenkinslint-plugin/a93a619cdb480bc339b63ab0c01c30551b0ade2d Log: JENKINS-42310 Added Test cases for the TimerTrigger Lint defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42310) MAVEN and MATRIX are not linted in some defects
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42310 Re: MAVEN and MATRIX are not linted in some defects Code changed in jenkins User: Victor Martinez Path: src/test/java/org/jenkins/ci/plugins/jenkinslint/check/GitRefCheckerTestCase.java http://jenkins-ci.org/commit/jenkinslint-plugin/57f1fd66cca96685a8745593ceb2c26c819fb923 Log: JENKINS-42310 Added Test cases for the GitRef Lint defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42310) MAVEN and MATRIX are not linted in some defects
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42310 Re: MAVEN and MATRIX are not linted in some defects Code changed in jenkins User: Victor Martinez Path: src/main/java/org/jenkins/ci/plugins/jenkinslint/check/GitShallowChecker.java http://jenkins-ci.org/commit/jenkinslint-plugin/ac23bed3356a55e3f56b57bec813eec7139bd0fb Log: JENKINS-42310 Git Shallow Lint defect support Maven and Matrix projects Compare: https://github.com/jenkinsci/jenkinslint-plugin/compare/eaca2a7b473d...ac23bed3356a Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42310) MAVEN and MATRIX are not linted in some defects
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42310 Re: MAVEN and MATRIX are not linted in some defects Code changed in jenkins User: Victor Martinez Path: src/test/java/org/jenkins/ci/plugins/jenkinslint/check/GitShallowCheckerTestCase.java http://jenkins-ci.org/commit/jenkinslint-plugin/03de2c265e5c348e672c82cd576672ac25f628f7 Log: JENKINS-42310 Added Test cases for the GitShallow Lint defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42310) MAVEN and MATRIX are not linted in some defects
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42310 Re: MAVEN and MATRIX are not linted in some defects Code changed in jenkins User: Victor Martinez Path: src/main/java/org/jenkins/ci/plugins/jenkinslint/check/ArtifactChecker.java src/main/java/org/jenkins/ci/plugins/jenkinslint/check/CleanupWorkspaceChecker.java src/main/java/org/jenkins/ci/plugins/jenkinslint/check/GitRefChecker.java src/main/java/org/jenkins/ci/plugins/jenkinslint/check/GitShallowChecker.java src/main/java/org/jenkins/ci/plugins/jenkinslint/check/JavadocChecker.java src/main/java/org/jenkins/ci/plugins/jenkinslint/check/JobAssignedLabelChecker.java src/main/java/org/jenkins/ci/plugins/jenkinslint/check/JobDescriptionChecker.java src/main/java/org/jenkins/ci/plugins/jenkinslint/check/NullSCMChecker.java src/main/java/org/jenkins/ci/plugins/jenkinslint/check/TimerTriggerChecker.java src/test/java/org/jenkins/ci/plugins/jenkinslint/check/ArtifactCheckerTestCase.java src/test/java/org/jenkins/ci/plugins/jenkinslint/check/CleanupWorkspaceCheckerTestCase.java src/test/java/org/jenkins/ci/plugins/jenkinslint/check/GitRefCheckerTestCase.java src/test/java/org/jenkins/ci/plugins/jenkinslint/check/GitShallowCheckerTestCase.java src/test/java/org/jenkins/ci/plugins/jenkinslint/check/GradleWrapperCheckerTestCase.java src/test/java/org/jenkins/ci/plugins/jenkinslint/check/GroovySystemExitCheckerTestCase.java src/test/java/org/jenkins/ci/plugins/jenkinslint/check/HardcodedScriptCheckerTestCase.java src/test/java/org/jenkins/ci/plugins/jenkinslint/check/JavadocCheckerTestCase.java src/test/java/org/jenkins/ci/plugins/jenkinslint/check/JobAssignedLabelCheckerTestCase.java src/test/java/org/jenkins/ci/plugins/jenkinslint/check/JobDescriptionCheckerTestCase.java src/test/java/org/jenkins/ci/plugins/jenkinslint/check/NullSCMCheckerTestCase.java src/test/java/org/jenkins/ci/plugins/jenkinslint/check/TimeoutCheckerTestCase.java src/test/java/org/jenkins/ci/plugins/jenkinslint/check/TimerTriggerCheckerTestCase.java http://jenkins-ci.org/commit/jenkinslint-plugin/926d5705e9b8ff4a1e7227ee668d0fd95a09d417 Log: Merge pull request #12 from jenkinsci/maven_matrix_support JENKINS-42310 Fixed lint defects which didn't support Maven and Matrix projects Compare: https://github.com/jenkinsci/jenkinslint-plugin/compare/ced83f2a19a9...926d5705e9b8 Add Comment
[JIRA] (JENKINS-42324) String parameter values aren't updated from the template
Title: Message Title kenorb created an issue Jenkins / JENKINS-42324 String parameter values aren't updated from the template Issue Type: Bug Assignee: Joel Johnson Components: ez-templates-plugin Created: 2017/Feb/26 12:09 AM Environment: Jenkins ver. 2.43, EZ Templates v1.2.5 Priority: Minor Reporter: kenorb I've a String Parameter with Default Value provided in the template. I've also existing job using that template. Once the default value has been changed in the template, it doesn't reflect the changes in the job which using that template. Re-saving job doesn't help either. As for workaround only removing that parameter from the job, then it's recreated correctly. Add Comment
[JIRA] (JENKINS-41449) Get lint issues via API call
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41449 Re: Get lint issues via API call Code changed in jenkins User: Victor Martinez Path: .gitignore src/main/java/org/jenkins/ci/plugins/jenkinslint/JenkinsLintAction.java src/main/java/org/jenkins/ci/plugins/jenkinslint/model/AbstractCheck.java src/main/java/org/jenkins/ci/plugins/jenkinslint/model/AbstractSlaveCheck.java src/main/java/org/jenkins/ci/plugins/jenkinslint/model/InterfaceCheck.java src/main/java/org/jenkins/ci/plugins/jenkinslint/model/InterfaceSlaveCheck.java src/main/java/org/jenkins/ci/plugins/jenkinslint/model/Job.java src/main/java/org/jenkins/ci/plugins/jenkinslint/model/Lint.java src/main/java/org/jenkins/ci/plugins/jenkinslint/model/Slave.java src/main/resources/org/jenkins/ci/plugins/jenkinslint/JenkinsLintAction/index.jelly src/test/java/org/jenkins/ci/plugins/jenkinslint/JenkinsLintActionTestCase.java http://jenkins-ci.org/commit/jenkinslint-plugin/24925a418e732e33d42d53898417cb62efecc4f1 Log: JENKINS-41449 RestAPI feature based on hashes RestAPI feature: creating a list of elements with some hierarchy RestAPI feature: refreshing data when quering through the api otherwise it will keep the previous run which means null when it hasn't been requested through the UI RestAPI feature: fixing bug when creating a list of elements with some hierarchy Deprecated public api and created an alternative one based on Hashes Added some test api cases Added Rest API test cases Excluding evil macosx files Removed wrong size method Using the class name rather than the package+class name, then those data structures amp correctly Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42324) String parameter values aren't updated from the template
Title: Message Title kenorb updated an issue Jenkins / JENKINS-42324 String parameter values aren't updated from the template Change By: kenorb I've a String Parameter with Default Value provided in the template. I've also existing job using that template. Once the default value has been changed in the template, it doesn't reflect the changes in the job which using that template. Re-saving job doesn't help either. As for workaround only removing that parameter from the job, then it's recreated correctly. I believe the same problem happens with Choice Parameter on changes in the template. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42268) Enable Knowledge Database analyser
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42268 Re: Enable Knowledge Database analyser Code changed in jenkins User: Victor Martinez Path: pom.xml src/main/java/org/jenkins/ci/plugins/jenkinslint/check/BFAChecker.java src/test/java/org/jenkins/ci/plugins/jenkinslint/check/BFACheckerTestCase.java http://jenkins-ci.org/commit/jenkinslint-plugin/24fa8f0d6e76d145015e54d9c90fcf1868a47fa1 Log: JENKINS-42268 Initial approach to detect whether BFA has been installed and enabled in every job unless using the control comment to force some way of declaring why it was not enabled JENKINS-42268 Added Maven and Matrix projects Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-37899) Git client does not call CredentialsProvider.snapshot() when adding credentials to a SmartCredentialsProvider that will be used on a remote instance
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37899 Re: Git client does not call CredentialsProvider.snapshot() when adding credentials to a SmartCredentialsProvider that will be used on a remote instance Code changed in jenkins User: Mark Waite Path: src/main/java/org/jenkinsci/plugins/gitclient/RemoteGitImpl.java http://jenkins-ci.org/commit/git-client-plugin/e75b299c645b2155f693897754bb6a16501a3117 Log: Merge pull request #235 from cyrille-leclerc/JENKINS-37899 JENKINS-37899 RemoteGitImpl: Take a snapshot of the credentials before passing them to the git client proxy Compare: https://github.com/jenkinsci/git-client-plugin/compare/196ed5dbb394...e75b299c645b Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-37899) Git client does not call CredentialsProvider.snapshot() when adding credentials to a SmartCredentialsProvider that will be used on a remote instance
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37899 Re: Git client does not call CredentialsProvider.snapshot() when adding credentials to a SmartCredentialsProvider that will be used on a remote instance Code changed in jenkins User: Cyrille Le Clerc Path: src/main/java/org/jenkinsci/plugins/gitclient/RemoteGitImpl.java http://jenkins-ci.org/commit/git-client-plugin/0381412bdd3ea7639cc6cdbb708fd03dc6a38339 Log: JENKINS-37899 RemoteGitImpl: Take a snapshot of the credentials before passing them to the git client proxy We need to snapshot of the credentials before passing them to the git client proxy so that the credentials are snapshotted before being serialised and transferred to the build agent through Jenkins remoting. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42282) stage label blinks and changes visible part
Title: Message Title James Dumay assigned an issue to James Dumay Jenkins / JENKINS-42282 stage label blinks and changes visible part Change By: James Dumay Assignee: James Dumay Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42282) stage label blinks and changes visible part
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42282 stage label blinks and changes visible part Change By: James Dumay Sprint: 1.0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42123) No feedback when clicking "connect" when entering Github access key
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-42123 No feedback when clicking "connect" when entering Github access key Change By: James Dumay Assignee: James Dumay Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42123) No feedback when clicking "connect" when entering Github access key
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42123 No feedback when clicking "connect" when entering Github access key Change By: James Dumay Priority: Critical Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-37437) Pipeline integration for OWASP checker
Title: Message Title Steve Springett started work on JENKINS-37437 Change By: Steve Springett Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42313) Default Value not honoured
Title: Message Title Ebrahim Moshaya updated an issue Jenkins / JENKINS-42313 Default Value not honoured Change By: Ebrahim Moshaya Summary: Default Value no not honoured Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-37437) Pipeline integration for OWASP checker
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37437 Re: Pipeline integration for OWASP checker Code changed in jenkins User: stevespringett Path: src/main/java/org/jenkinsci/plugins/DependencyCheck/AbstractDependencyCheckBuilder.java src/main/java/org/jenkinsci/plugins/DependencyCheck/DependencyCheckBuilder.java src/main/java/org/jenkinsci/plugins/DependencyCheck/DependencyCheckExecutor.java src/main/java/org/jenkinsci/plugins/DependencyCheck/DependencyCheckUpdateOnlyBuilder.java src/main/resources/org/jenkinsci/plugins/DependencyCheck/Messages.properties http://jenkins-ci.org/commit/dependency-check-plugin/8f780e9071b05291102cbe0c22bd17ce6a2caedd Log: Adding support for Pipeline via SimpleBuildStep. Fixed several issues with getters and general cleanup. JENKINS-37437 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42325) Remove deprecated Maven artifact support in Dependency-Check Build step
Title: Message Title Steve Springett created an issue Jenkins / JENKINS-42325 Remove deprecated Maven artifact support in Dependency-Check Build step Issue Type: Task Assignee: Steve Springett Components: dependency-check-jenkins-plugin Created: 2017/Feb/26 5:56 AM Priority: Minor Reporter: Steve Springett Experimental support for analyzing Maven artifacts from the Jenkins plugin was introduced on June 23, 2014. This feature never quite worked right nor was there any incentive for it to be improved since the official Dependency-Check Maven plugin did a far better job. This feature was deprecated on August 3, 2015 with a note stating that it will be removed in a future release. This ticket is to track the complete removal of this feature. Add Comment
[JIRA] (JENKINS-42325) Remove deprecated Maven artifact support in Dependency-Check Build step
Title: Message Title Steve Springett started work on JENKINS-42325 Change By: Steve Springett Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42325) Remove deprecated Maven artifact support in Dependency-Check Build step
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42325 Re: Remove deprecated Maven artifact support in Dependency-Check Build step Code changed in jenkins User: stevespringett Path: src/main/java/org/jenkinsci/plugins/DependencyCheck/AbstractDependencyCheckBuilder.java src/main/java/org/jenkinsci/plugins/DependencyCheck/DependencyCheckBuilder.java src/main/java/org/jenkinsci/plugins/DependencyCheck/Options.java src/main/java/org/jenkinsci/plugins/DependencyCheck/maven/MavenArtifactRecorder.java src/main/resources/org/jenkinsci/plugins/DependencyCheck/DependencyCheckBuilder/config.jelly src/main/resources/org/jenkinsci/plugins/DependencyCheck/DependencyCheckBuilder/config.properties src/main/webapp/help-scanpath-maven.html http://jenkins-ci.org/commit/dependency-check-plugin/b3596600f6a6bc2d1bf0c4bcbe4be86568e68dbf Log: Removing support for deprecated and old experimental native maven scanning. JENKINS-42325 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42325) Remove deprecated Maven artifact support in Dependency-Check Build step
Title: Message Title Steve Springett resolved as Done Jenkins / JENKINS-42325 Remove deprecated Maven artifact support in Dependency-Check Build step Change By: Steve Springett Status: In Progress Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42325) Remove deprecated Maven artifact support in Dependency-Check Build step
Title: Message Title Steve Springett closed an issue as Done Feature removed Jenkins / JENKINS-42325 Remove deprecated Maven artifact support in Dependency-Check Build step Change By: Steve Springett Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42326) How to get commit report of the branches on weekly basis using jenkins and stash/git?
Title: Message Title NAGA SAKETH JALIGAMA created an issue Jenkins / JENKINS-42326 How to get commit report of the branches on weekly basis using jenkins and stash/git? Issue Type: New Feature Assignee: Mark Waite Components: git-plugin Created: 2017/Feb/26 6:13 AM Priority: Critical Reporter: NAGA SAKETH JALIGAMA I want to get a commit report for a repository in stash, the report should display author name,commit id, date,comments,branch,jiraid etc . It should run daily and send pdf/csv file as an email to a group of people. how can i do this with jenkins. Add Comment
[JIRA] (JENKINS-38623) Jenkins 2 cli failes with "java.io.IOException: Unexpected termination of the channel"
Title: Message Title Jon B commented on JENKINS-38623 Re: Jenkins 2 cli failes with "java.io.IOException: Unexpected termination of the channel" I have this problem too. I'm using the latest Jenkins 2 Docker image. I can't figure out how to set the keep alive timeout. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-42327) Add support for defining declarative pipeline templates in shared libraries
Title: Message Title Abir M created an issue Jenkins / JENKINS-42327 Add support for defining declarative pipeline templates in shared libraries Issue Type: New Feature Assignee: Andrew Bayer Components: pipeline-model-definition-plugin, workflow-cps-global-lib-plugin Created: 2017/Feb/26 7:17 AM Priority: Minor Reporter: Abir M With the 1.0 release of model definition, we are defining the entire pipeline job as code. However, there is no standard as far as I am aware for sharing multiple Jenkinsfile(s) in an organization in git repository. There is definitely a use case for this, along with [ existing examples ](https://github.com/fabric8io/fabric8-jenkinsfile-library). This would be a logical extension for shared libraries and the [directory structure](https://jenkins.io/doc/book/pipeline/shared-libraries/#directory-structure) perhaps by adding a 'pipelines/' folder. These could appear in a drop down when creating a pipeline job (not multibranch). One way would be to have a 'Pipeline Script from Library' option similar to the 'Pipeline Script from SCM' option. A future extension could be to automatically generate Jenkins jobs from pipelines in a library. Right now, this can be done using the CLI as used in [this github project](https://github.com/kitconcept/jenkins-pipeline-examples). 1) Create [a template skeleton XML](https://github.com/kitconcept/jenkins-pipeline-examples/blob/master/job-templates/pipeline.xml) with the Git repo and the pipeline definition file paths embedded. 2) Import as a pipeline job: java -jar jenkins-cli.jar -s http://localhost:8080 create-job pipeline < /home/vagrant/jenkins-pipeline-examples/pipeline.xml
[JIRA] (JENKINS-42327) Add support for defining declarative pipeline templates in shared libraries
Title: Message Title
Abir M updated an issue
Jenkins / JENKINS-42327
Add support for defining declarative pipeline templates in shared libraries
Change By:
Abir M
With the 1.0 release of model definition, we are defining the entire pipeline job as code. However, there is no standard as far as I am aware for sharing multiple Jenkinsfile(s) in an organization in git repository. There is definitely a use case for this, along with [ existing examples ]( | https://github.com/fabric8io/fabric8-jenkinsfile-library ) ] .This would be a logical extension for shared libraries and the [directory structure ]( | https://jenkins.io/doc/book/pipeline/shared-libraries/#directory-structure ) ] perhaps by adding a 'pipelines/' folder. These could appear in a drop down when creating a pipeline job (not multibranch). One way would be to have a 'Pipeline Script from Library' option similar to the 'Pipeline Script from SCM' option.A future extension could be to automatically generate Jenkins jobs from pipelines in a library. Right now, this can be done using the CLI as used in [this github project ]( | https://github.com/kitconcept/jenkins-pipeline-examples ) ] . 1) Create [a template skeleton pipeline XML ]( | https://github.com/kitconcept/jenkins-pipeline-examples/blob/master/job-templates/pipeline.xml ) ] with the Git repo and the pipeline definition file paths embedded.2) Import as a pipeline job:{{java -jar jenkins-cli.jar -s http://localhost:8080 create-job pipeline < /home/vagrant/jenkins-pipeline-examples/pipeline.xml}}
Add Comment
[JIRA] (JENKINS-42327) Add support for defining declarative pipeline templates in shared libraries
Title: Message Title
Abir M updated an issue
Jenkins / JENKINS-42327
Add support for defining declarative pipeline templates in shared libraries
Change By:
Abir M
With the 1.0 release of model definition, we are defining the entire pipeline job as code. However, there is no standard as far as I am aware for sharing multiple Jenkinsfile(s) in an organization in git repository. There is definitely a use case for this, along with [ existing examples | https://github.com/fabric8io/fabric8-jenkinsfile-library].This would be a logical extension for shared libraries and the [directory structure|https://jenkins.io/doc/book/pipeline/shared-libraries/#directory-structure] perhaps by adding a 'pipelines/' folder. These could appear in a drop down when creating a pipeline job (not multibranch). One way would be to have a 'Pipeline Script from Library' option similar to the 'Pipeline Script from SCM' option.A future extension could be to automatically generate Jenkins jobs from pipelines in a library. Right now, this can be done using the CLI as used in [this github project|https://github.com/kitconcept/jenkins-pipeline-examples]. 1) Create [a template pipeline XML|https://github.com/kitconcept/jenkins-pipeline-examples/blob/master/job-templates/pipeline.xml] with the Git repo and the pipeline definition file paths embedded.2) Import as a pipeline job:{{java -jar jenkins-cli.jar -s http://localhost:8080 create-job pipeline < /home/vagrant/jenkins-pipeline-examples/pipeline.xml}}
Add Comment
This message was sent by Atlassian JI
[JIRA] (JENKINS-42327) Add support for defining declarative pipeline templates in shared libraries
Title: Message Title
Abir M updated an issue
Jenkins / JENKINS-42327
Add support for defining declarative pipeline templates in shared libraries
Change By:
Abir M
With the 1.0 release of model definition, we are defining the entire pipeline job as code. However, there is no standard as far as I am aware for sharing multiple Jenkinsfile(s) in an organization in git repository. There is definitely a use case for this, along with [existing examples|https://github.com/fabric8io/fabric8-jenkinsfile-library].This would be a logical extension for shared libraries and the [directory structure|https://jenkins.io/doc/book/pipeline/shared-libraries/#directory-structure] perhaps by adding a 'pipelines/' folder. These could appear in a drop down when creating a pipeline job (not multibranch). One way would be to have a 'Pipeline Script from Library' option similar to the 'Pipeline Script from SCM' option.A future extension could be to automatically generate Jenkins jobs from pipelines in a library. Right now, this can be done using the CLI as used in [this github project|https://github.com/kitconcept/jenkins-pipeline-examples]. 1) Create [a template pipeline XML|https://github.com/kitconcept/jenkins-pipeline-examples/blob/master/job-templates/pipeline.xml] with the Git repo and the pipeline definition file paths embedded.2) Import as a pipeline job:{{java -jar jenkins-cli.jar -s http://localhost:8080 create-job pipeline < /home/vagrant/jenkins- pipeline -examples/pipeline .xml}}
Add Comment
This message was sent by Atlassian J
