[JIRA] (JENKINS-57173) Issue with Darcs SCM plugin saving build records
Title: Message Title Sven Strittmatter commented on JENKINS-57173 Re: Issue with Darcs SCM plugin saving build records The used Darcs command is darcs changes --xml-output --summary. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title Norbert Weiß commented on JENKINS-57244 Re: java.io.NotSerializableException: The calling thread Thread has no associated channel As far as I understand there is some work in progress to fix the issue in the maven-plugin code. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57341) Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11
Title: Message Title Francisco Fernández updated an issue Jenkins / JENKINS-57341 Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11 Change By: Francisco Fernández Labels: java11 java11-devtools-compatibility triaged Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199116.1557144976000.19302.1557216900289%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55549) CppCheck Cannot load sidepanel.jelly
Title: Message Title gico prasico commented on JENKINS-55549 Re: CppCheck Cannot load sidepanel.jelly Hi we are having the same issue, that prevents us to see the TestLink report: org.jenkins-ci.main:jenkins-war:2.164.2 TestLink Plugin 3.16 TestLink 1.9.16 org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/plugins/testlink/WEB-INF/lib/testlink.jar!/hudson/plugins/testlink/TestLinkResult/index.jelly:6:57: No page found 'sidepanel.jelly' for class hudson.plugins.testlink.TestLinkResult at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:124) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57350) Migrate email tests from mailtrap.io service to a container
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-57350 Migrate email tests from mailtrap.io service to a container Issue Type: Task Assignee: Oliver Gondža Components: acceptance-test-harness Created: 2019-05-07 07:00 Priority: Major Reporter: Oliver Gondža This has been a long term tech-debth but with the service changing the definition of the free plan every now and then, we should better be free of such dependency. This month, the service started sending notifications we are running out of message number quota. On a first glance, mailhog has a container[1] and there are some bindings for java[2], albeit unreleased. [1] https://hub.docker.com/r/mailhog/mailhog/ [2] https://github.com/tomphp/java-mailhog-client Add Comment
[JIRA] (JENKINS-57173) Issue with Darcs SCM plugin saving build records
Title: Message Title Sven Strittmatter started work on JENKINS-57173 Change By: Sven Strittmatter Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55139) ansicolor 0.6.0 shows terminal escape sequences in console log
Title: Message Title David Aldrich commented on JENKINS-55139 Re: ansicolor 0.6.0 shows terminal escape sequences in console log I am seeing the same behaviour as Robin Verduijn. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196206.1544605559000.19287.1557215580351%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57334) "Run on planned host" from Build section not working
Title: Message Title Anda Sorina Laakso commented on JENKINS-57334 Re: "Run on planned host" from Build section not working This exception "java.lang.IllegalArgumentException: HTTP host may not be null" indicates that your host url is not correctly formed. Please check that again. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Arman Tursynbekov commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub I observed behavior that Jenkins will ignore PR if that PR has conflicting files. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.19221.1557215401275%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57195) Scan organization fails with FileNotFoundException
Title: Message Title Giorgio Sironi commented on JENKINS-57195 Re: Scan organization fails with FileNotFoundException It wasn't deterministic as I've seen the correct behavior happening with some private repos too. If I had some pointers on which logs to look at or turn on, I could create sample repos to try to collect more information on the error (assuming it would reproduce). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198949.1556274194000.19300.1557216180131%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57351) Support authentication as GitHub App
Title: Message Title Andreas Sieferlinger created an issue Jenkins / JENKINS-57351 Support authentication as GitHub App Issue Type: New Feature Assignee: Unassigned Components: github-branch-source-plugin Created: 2019-05-07 08:21 Priority: Minor Reporter: Andreas Sieferlinger To my understanding currently the github-branch-source plugins always requires GitHub user credentials / tokens to authenticate. I'd suggest to add authenticating Jenkins to GitHub as a GitHub App too. Why is this better than the current way: GitHub Apps can be granted very fine grained permissions GitHub Apps can be added either to a whole org, or just to selected repos The app uses a key pair to then get temporary credentials, so leaked creds to user are only valid for a short period of time Higher API limits! (probably the most important one for bigger orgs) This is specifically NOT about authenticating users against GitHub, but for Authenticating Jenkins itself against GitHub References: https://developer.github.com/apps/differences-between-apps/
[JIRA] (JENKINS-57181) Jenkins ALM disconnection
Title: Message Title Anda Sorina Laakso commented on JENKINS-57181 Re: Jenkins ALM disconnection This sounds more like an ALM issue rather than Jenkins plugin. I will contact someone from the ALM team and get back to you once i have news on it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53767) Offer plugin management tooling
Title: Message Title Oleg Nenashev commented on JENKINS-53767 Re: Offer plugin management tooling Just an update here, we will have a GSoC project for it this year: https://summerofcode.withgoogle.com/projects/#5741119520899072 The format is yet to be defined, but it will be handled under the Platform SIG umbrella. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53767) Offer plugin management tooling
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-53767 Offer plugin management tooling Change By: Oleg Nenashev Labels: gsoc-2019 gsoc - 2019- project-idea Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57327) changeView option ignored, not added to client spec
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-57327 changeView option ignored, not added to client spec Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199099.1557004231000.19305.1557217920162%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57327) changeView option ignored, not added to client spec
Title: Message Title Karl Wirth commented on JENKINS-57327 Re: changeView option ignored, not added to client spec Hi Aaron Miller. Thanks for highlighting this. I'll test it here and update the job with my findings. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199099.1557004231000.19307.1557217920195%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50715) Pipeline fails with NPE due to Blue Ocean favorites
Title: Message Title Christian Häussler commented on JENKINS-50715 Re: Pipeline fails with NPE due to Blue Ocean favorites Could that help as a Workaround? -DBLUEOCEAN_FEATURE_AUTOFAVORITE_ENABLED=false Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57171) Permissive script security plugin is broken after updating to script security 1.58
Title: Message Title Oliver Gondža commented on JENKINS-57171 Re: Permissive script security plugin is broken after updating to script security 1.58 Thanks, I managed to reproduce the problem introduced between script-security-1.57 and script-security-1.58. Let me see what we can do. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title
roel postelmans commented on JENKINS-39203
Re: All stages show up as UNSTABLE when only one stage should
I'v created a shared library, which contains an API to get the failed stages: https://github.com/roel0/jenkins-util-scripts You can then easily print out that data, or email it , or post it on slack or ... Example usage:
try {
super_stage("stage1") {
}
super_stage("stage2") {
error "oei"
}
} catch(e) {
}
println "Failed stages: ${get_failed_stages().join(',')}"
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.19309.1557219184966%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57352) Test connection fails and also unable to get K8s pods via Jenkins using service account
Title: Message Title
Harsha GV updated an issue
Jenkins / JENKINS-57352
Test connection fails and also unable to get K8s pods via Jenkins using service account
Change By:
Harsha GV
*PS: Jenkins is deployed in K8s and not using openshift [ doe do not intend to]*Provisioning of K8s pods from Kubernetes Jenkins plugin using the my cloud credentials is failing, hence created service account using below command:{code:java}kubectl -n mynamespace create serviceaccount jenkins{code}Then tried Test Connection from K8s-plugin, but connection failed with below error:{code:java}Error testing connection https://api.k8s2.apac.cloud.net:6443: Failure executing: GET at: https://api.k8s2.apac.cloud.net:6443/api/v1/namespaces/mynamespace/pods. Message: Forbidden!Configured service account doesn't have access. Service account may have been revoked. pods is forbidden: User "system:serviceaccount:mynamespace:default" cannot list resource "pods" in API group "" in the namespace "mynamespace": Unexpected user-id: system:serviceaccount:mynamespace:default.{code}Also when jenkins triggered to run in labeled k8s pods, fails with below error:{code:java}Failed to count the # of live instances on Kubernetesio.fabric8.kubernetes.client.KubernetesClientException: Failure executing: GET at: https://api.k8s2.apac.cloud.net:6443/api/v1/namespaces/mynamespace/pods?labelSelector=jenkins%3Dslave. Message: Forbidden!Configured service account doesn't have access. Service account may have been revoked. pods is forbidden: User "system:anonymous" cannot list resource "pods" in API group "" in the namespace "mynamespace": Unexpected user-id: system:anonymous. at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:472) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:409) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:381) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:344) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:328) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.list(BaseOperation.java:584) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.list(BaseOperation.java:49) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.addProvisionedSlave(KubernetesCloud.java:493) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.provision(KubernetesCloud.java:448) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:715) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:320) at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:61) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:809) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at
[JIRA] (JENKINS-57352) Test connection fails and also unable to get K8s pods via Jenkins using service account
Title: Message Title
Harsha GV updated an issue
Jenkins / JENKINS-57352
Test connection fails and also unable to get K8s pods via Jenkins using service account
Change By:
Harsha GV
*PS: Jenkins is deployed in K8s and not using openshift [doe not intend to]* Provisioning of K8s pods from Kubernetes Jenkins plugin using the my cloud credentials is failing, hence created service account using below command: PS: Jenkins is deployed in K8s {code :java }kubectl -n mynamespace create serviceaccount jenkins{code} Then tried Test Connection from K8s-plugin, but connection failed with below error:{code :java }Error testing connection https://api.k8s2.apac.cloud.net:6443: Failure executing: GET at: https://api.k8s2.apac.cloud.net:6443/api/v1/namespaces/mynamespace/pods. Message: Forbidden!Configured service account doesn't have access. Service account may have been revoked. pods is forbidden: User "system:serviceaccount:mynamespace:default" cannot list resource "pods" in API group "" in the namespace "mynamespace": Unexpected user-id: system:serviceaccount:mynamespace:default.{code} Also when jenkins triggered to run in labeled k8s pods, fails with below error:{code :java }Failed to count the # of live instances on Kubernetesio.fabric8.kubernetes.client.KubernetesClientException: Failure executing: GET at: https://api.k8s2.apac.cloud.net:6443/api/v1/namespaces/mynamespace/pods?labelSelector=jenkins%3Dslave. Message: Forbidden!Configured service account doesn't have access. Service account may have been revoked. pods is forbidden: User "system:anonymous" cannot list resource "pods" in API group "" in the namespace "mynamespace": Unexpected user-id: system:anonymous. at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:472) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:409) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:381) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:344) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:328) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.list(BaseOperation.java:584) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.list(BaseOperation.java:49) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.addProvisionedSlave(KubernetesCloud.java:493) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.provision(KubernetesCloud.java:448) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:715) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:320) at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:61) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:809) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at
[JIRA] (JENKINS-57272) lrs file is not found on Jenkins working directory but job finish successfully
Title: Message Title
Omer Kenan updated an issue
Jenkins / JENKINS-57272
lrs file is not found on Jenkins working directory but job finish successfully
Change By:
Omer Kenan
This issue is rarely occurred: Started by user unknown or anonymousRunning in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] stage[Pipeline] { (LR)[Pipeline] nodeRunning on 10.199.143.201 in C:\Jtest\workspace\LR_PP[Pipeline] {[Pipeline] loadRunnerTestRunning LoadRunner Scenario step[LR_PP] $ C:\Jtest\workspace\LR_PP\HpToolsLauncher.exe -paramfile props01052019143742586.txt"Started..." File/Folder not found: 'C:\Jtest\SLA\SLArts.lrs'No valid tests were found. Fix the test paths.Run build testsUnhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object. at HpToolsLauncher.Launcher.CreateRunner(TestStorageType runType, JavaProperties ciParams, Boolean initialTestRun) at HpToolsLauncher.Launcher.Run() at HpToolsLauncher.Program.Main(String[] args)Recording test resultsNone of the test reports contained any resultRunResultRecorder: didn't find any test results to record[Pipeline] }[Pipeline] // node[Pipeline] }[Pipeline] // stage[Pipeline] End of Pipeline * Finished: SUCCESS *
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the
[JIRA] (JENKINS-57272) lrs file is not found on Jenkins working directory but job finish successfully
Title: Message Title
Omer Kenan updated an issue
Jenkins / JENKINS-57272
lrs file is not found on Jenkins working directory but job finish successfully
Change By:
Omer Kenan
This issue is rarely occurred:Started by user unknown or anonymousRunning in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] stage[Pipeline] { (LR)[Pipeline] nodeRunning on 10.199.143.201 in C:\Jtest\workspace\LR_PP[Pipeline] {[Pipeline] loadRunnerTestRunning LoadRunner Scenario step[LR_PP] $ C:\Jtest\workspace\LR_PP\HpToolsLauncher.exe -paramfile props01052019143742586.txt"Started..." * File/Folder not found: 'C:\Jtest\SLA\SLArts.lrs' * No valid tests were found. Fix the test paths.Run build testsUnhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object. at HpToolsLauncher.Launcher.CreateRunner(TestStorageType runType, JavaProperties ciParams, Boolean initialTestRun) at HpToolsLauncher.Launcher.Run() at HpToolsLauncher.Program.Main(String[] args)Recording test resultsNone of the test reports contained any resultRunResultRecorder: didn't find any test results to record[Pipeline] }[Pipeline] // node[Pipeline] }[Pipeline] // stage[Pipeline] End of Pipeline*Finished: SUCCESS*
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the
[JIRA] (JENKINS-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Carlos Sanchez updated JENKINS-56347 Jenkins / JENKINS-56347 Kubernetes plugin provisioning pods twice in 1.14.6 Change By: Carlos Sanchez Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197933.1551459214000.19693.1557231721464%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57353) Cleanup FindBugs issues in Jenkinsfile Runner
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-57353 Cleanup FindBugs issues in Jenkinsfile Runner Issue Type: Bug Assignee: Unassigned Components: jenkinsfile-runner Created: 2019-05-07 12:40 Labels: findbugs Priority: Minor Reporter: Oleg Nenashev After the update to the recent Parent POM in TODO, there are some failing FindBugs checks in Jenkinsfile Runner modules. It would be great to clean them up. Acceptance criteria: All FindBugs warnings are fixed or suppressed with a justification FindBugs failOnError is reenabled in the pom.xml Add Comment
[JIRA] (JENKINS-40991) No signature of method: groovy.util.Node.div()... error in configure block
Title: Message Title
Anthony Green edited a comment on JENKINS-40991
Re: No signature of method: groovy.util.Node.div()... error in configure block
This bug is breaking all use of I managed a work around to the configure block with the job dsl plugin when the jobs are stored in source control and executed from the workspace / being interpreted as a div() command.. def removeJvmOptions = { node -> node.remove(node.get(jvmOptions)[0])}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177723.1484136081000.19598.1557226080139%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Oliver Gondža commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. I have backported this to be picked up by 2.164.3 during tomorrows release. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198841.164806000.19688.1557231540190%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50715) Pipeline fails with NPE due to Blue Ocean favorites
Title: Message Title Mark Waite commented on JENKINS-50715 Re: Pipeline fails with NPE due to Blue Ocean favorites Thanks for that pointer Christian Häussler! I have enough jobs in my Jenkins server that I find the Blue Ocean autofavorite plugin more of a hindrance than a help. You've now given me a setting that may avoid me getting favorites that aren't actually my favorites. JENKINS-47214 describes that property. It is also mentioned in the plugin release notes for release 1.2.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189812.1523357354000.19708.1557232201911%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57352) Test connection fails and also unable to get K8s pods via Jenkins using service account
Title: Message Title Harsha GV created an issue Jenkins / JENKINS-57352 Test connection fails and also unable to get K8s pods via Jenkins using service account Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-05-07 10:54 Environment: Jenkins in K8s Labels: kubernetes kubernetes-plugin Priority: Minor Reporter: Harsha GV Provisioning of K8s pods from Kubernetes Jenkins plugin using the my cloud credentials is failing, hence created service account using below command: PS: Jenkins is deployed in K8s kubectl -n mynamespace create serviceaccount jenkins Then tried Test Connection from K8s-plugin, but connection failed with below error: Error testing connection https://api.k8s2.apac.cloud.net:6443: Failure executing: GET at: https://api.k8s2.apac.cloud.net:6443/api/v1/namespaces/mynamespace/pods. Message: Forbidden!Configured service account doesn't have access. Service account may have been revoked. pods is forbidden: User "system:serviceaccount:mynamespace:default" cannot list resource "pods" in API group "" in the namespace "mynamespace":
[JIRA] (JENKINS-57352) Test connection fails and also unable to get K8s pods via Jenkins using service account
Title: Message Title Carlos Sanchez commented on JENKINS-57352 Re: Test connection fails and also unable to get K8s pods via Jenkins using service account looks like it is picking the default service account, but I've never seen the "Unexpected user-id" error How do you configure the service account in jenkins? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199130.1557226492000.19630.1557229560133%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50433) unable to load shared library from gerrit pull request branch
Title: Message Title
Taras Kostyuk commented on JENKINS-50433
Re: unable to load shared library from gerrit pull request branch
Setting additional cloning behavior in Manage Jenkins -> Configure system for the shared library like allows to get the library loaded by adding
def lib = library("egp-cicd@${LIB_GERRIT_REFSPEC}"
to the pipeline where LIB_GERRIT_REFSPEC is like refs/changes/78/386678/1
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189489.1522158981000.19570.155740199%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57181) Jenkins ALM disconnection
Title: Message Title Anda Sorina Laakso commented on JENKINS-57181 Re: Jenkins ALM disconnection Just sent by email a new version of the plugin. Upload it in Jenkins and next run the tests. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198932.1556196435000.19587.1557225840317%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57272) lrs file is not found on Jenkins working directory but job finish successfully
Title: Message Title Omer Kenan updated an issue Jenkins / JENKINS-57272 lrs file is not found on Jenkins working directory but job finish successfully Change By: Omer Kenan Priority: Critical Minor Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199038.1556711462000.19622.1557227640192%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40991) No signature of method: groovy.util.Node.div()... error in configure block
Title: Message Title Anthony Green edited a comment on JENKINS-40991 Re: No signature of method: groovy.util.Node.div()... error in configure block This bug is breaking all use of the configure block with the job dsl plugin when the jobs are stored in source control and executed from the workspace Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177723.1484136081000.19555.1557221640477%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57352) Test connection fails and also unable to get K8s pods via Jenkins using service account
Title: Message Title
Harsha GV updated an issue
Jenkins / JENKINS-57352
Test connection fails and also unable to get K8s pods via Jenkins using service account
Change By:
Harsha GV
*PS: Jenkins is deployed in K8s and not using openshift [do not intend to]*Provisioning of K8s pods from Kubernetes Jenkins plugin using the my cloud credentials is failing, hence created service account using below command:{code:java}kubectl -n mynamespace create serviceaccount jenkins{code}Then after selecting service account authentication credentials tried Test Connection from *_Test Connection_* in K8s-plugin cloud configuration page , but connection failed with below error:{code:java}Error testing connection https://api.k8s2.apac.cloud.net:6443: Failure executing: GET at: https://api.k8s2.apac.cloud.net:6443/api/v1/namespaces/mynamespace/pods. Message: Forbidden!Configured service account doesn't have access. Service account may have been revoked. pods is forbidden: User "system:serviceaccount:mynamespace:default" cannot list resource "pods" in API group "" in the namespace "mynamespace": Unexpected user-id: system:serviceaccount:mynamespace:default.{code}Also when jenkins triggered to run in labeled k8s pods, fails with below error:{code:java}Failed to count the # of live instances on Kubernetesio.fabric8.kubernetes.client.KubernetesClientException: Failure executing: GET at: https://api.k8s2.apac.cloud.net:6443/api/v1/namespaces/mynamespace/pods?labelSelector=jenkins%3Dslave. Message: Forbidden!Configured service account doesn't have access. Service account may have been revoked. pods is forbidden: User "system:anonymous" cannot list resource "pods" in API group "" in the namespace "mynamespace": Unexpected user-id: system:anonymous. at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:472) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:409) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:381) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:344) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:328) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.list(BaseOperation.java:584) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.list(BaseOperation.java:49) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.addProvisionedSlave(KubernetesCloud.java:493) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.provision(KubernetesCloud.java:448) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:715) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:320) at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:61) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:809) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at
[JIRA] (JENKINS-50433) unable to load shared library from gerrit pull request branch
Title: Message Title Taras Kostyuk updated an issue Jenkins / JENKINS-50433 unable to load shared library from gerrit pull request branch Change By: Taras Kostyuk Attachment: Screen Shot 2019-05-07 at 12.35.44.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189489.1522158981000.19562.1557221820427%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57321) Cannot set diferent shebang in shell in Docker in pipeline
Title: Message Title Ovidiu-Florin Bogdan closed an issue as Not A Defect Jenkins / JENKINS-57321 Cannot set diferent shebang in shell in Docker in pipeline Change By: Ovidiu-Florin Bogdan Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199091.1556886771000.19595.1557225900486%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57321) Cannot set diferent shebang in shell in Docker in pipeline
Title: Message Title Ovidiu-Florin Bogdan commented on JENKINS-57321 Re: Cannot set diferent shebang in shell in Docker in pipeline I have tried just now. It works. I didn't think the newline after """ gets into the executed script. Thank you Carlos Sanchez. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199091.1556886771000.19593.1557225900458%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53560) "Cannot stop sshd service" when provisioning Azure Windows nodes
Title: Message Title Jie Shen commented on JENKINS-53560 Re: "Cannot stop sshd service" when provisioning Azure Windows nodes Nick Jones PR created https://github.com/jenkinsci/azure-vm-agents-plugin/pull/146 . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194040.1536849004000.19568.1557222180216%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57281) Details Tab (in Details View)
Title: Message Title Nils Engelbrecht started work on JENKINS-57281 Change By: Nils Engelbrecht Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199047.1556742712000.19585.1557223920231%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40991) No signature of method: groovy.util.Node.div()... error in configure block
Title: Message Title
Anthony Green edited a comment on JENKINS-40991
Re: No signature of method: groovy.util.Node.div()... error in configure block
I managed a work around to the / being interpreted as a div() command.. def removeJvmOptions = { node -> node.remove(node.get(jvmOptions)[0])}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177723.1484136081000.19603.1557226140137%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-57096 The latest debian installers 2.164+ do not work with java 11. Change By: Oliver Gondža Labels: 2.164.3-fixed java11 java11-compatibility jenkins triaged Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198841.164806000.19682.1557231360238%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Sebastian Wojas commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error Mark Waite when you're planning to release fixed version of git-plugin ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186841.1511861183000.19729.1557232620396%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Sebastian Wojas edited a comment on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error [~markewaite] when you're planning to release fixed version (3.0, not beta) of git-plugin ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186841.1511861183000.19752.1557232740505%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Liam Newman commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub Arman Tursynbekov Could you open a new issue for that, it is probably not related to this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.20028.1557238921175%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57356) Spaces in workspace path
Title: Message Title Steve Springett created an issue Jenkins / JENKINS-57356 Spaces in workspace path Issue Type: Bug Assignee: Assaf hefetz Components: snyk-security-plugin Created: 2019-05-07 15:36 Priority: Major Reporter: Steve Springett If a Jenkins workspace contains a space, execution of the Snyk plugin will fail with the following: Installing Snyk Security tool (version 'latest') Testing for known issues... > /var/lib/jenkins/tools/io.snyk.jenkins.tools.SnykInstallation/Latest_Version/node_modules/.bin/snyk test --json --severity-threshold=high --project-name=myapp-android Error result: = DEBUG INFORMATION START = [COULD NOT RUN gradle -v] >>> command: /var/lib/jenkins/workspace/myapp - android/gradlew snykResolvedDepsJson -q --build-file build.gradle --no-daemon -Dorg.gradle.parallel= -I /tmp/tmp-11153lDMTd6CV2URC-init.gradle >>> exit code: 127 >>> stdout: >>> stderr: /bin/sh: 1: /var/lib/jenkins/workspace/myapp: not found = DEBUG INFORMATION END = Add Comment
[JIRA] (JENKINS-57347) Performance degradation running pipeline step sh on remote agents
Title: Message Title Nancy Robertson commented on JENKINS-57347 Re: Performance degradation running pipeline step sh on remote agents Ivan Fernandez Calvo I tried setting the property, then disconnected and reconnected my agent. It makes no measurable difference. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199122.1557175676000.20250.1557244860264%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57357) NullPointerException due to non-backwars compatibility in hudson.plugins.EC2.SlaveTemplate.
Title: Message Title Adrien Tateno created an issue Jenkins / JENKINS-57357 NullPointerException due to non-backwars compatibility in hudson.plugins.EC2.SlaveTemplate. Issue Type: Bug Assignee: FABRIZIO MANFREDI Attachments: image-2019-05-07-10-52-22-920.png Components: ec2-plugin Created: 2019-05-07 16:00 Environment: Jenkins 2.172, ec2-plugin master (likely as of 2f348aa519338aac64dd19954b0b41a62a8ea6fc) Priority: Major Reporter: Adrien Tateno Upon upgrading the ec2-plugin to master and restarting Jenkins, the EC2 nodes begin to fail connecting with the following exception This is likely due to the recent change that allows configuring the strategy for determining the hostname/IP address of the node https://github.com/jenkinsci/ec2-plugin/pull/329. https://wiki.jenkins.io/display/JENKINS/Hint+on+retaining+backward+compatibility suggests that it is necessary to define a readResolve() method when deprecating fields (in this case the boolean fields usePrivateDnsName connectUsingPublicIp) because when objects are loaded from XML their constructors are not invoked. What likely happened here, is that the newly defined connectionStrategy was null when loaded from XML, causing the hostname/IP address determination to fail at instance startup time. Matt Sicker Daniel Garzon
[JIRA] (JENKINS-57314) P4 Sync to label after sync to head without deleting non labeled files
Title: Message Title
Jose Valverde commented on JENKINS-57314
Re: P4 Sync to label after sync to head without deleting non labeled files
Hi Karl Wirth, I'm trying to change my job to run a P4Groovy, and I've created an example as in the link you've shared, and i'm getting the following error:
[Pipeline] End of Pipeline
ERROR: P4: Task Exception: Invalid credentials
This is my test code:
node("my_node") {
// Define workspace
def ws = [$class: 'StreamWorkspaceImpl',
charset: 'none', format: 'jenkins-${JOB_NAME}',
pinHost: false, streamName: '//my_workspace']// Create object
def p4 = p4 (credential: 'my_client', workspace: manualSpec(charset: 'none', cleanup: false, name: 'jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}', pinHost: false, spec: clientSpec(allwrite: false, backup: true, changeView: '', clobber: true, compress: false, line: 'LOCAL', locked: false, modtime: false, rmdir: false, serverID: '', streamName: '', type: 'WRITABLE', view: 'my_workspace')))
p4.run('sync','...')
}
Please note that "my_client" is the same using in other working jobs. Is there any additional configuration needed on my job, rather then what is on the shared link (de-select groovy sandbox) ? Thanks for the help!
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] (JENKINS-57355) Question - Unable to find an option to publish the video file
Title: Message Title Rakesh Nambiar created an issue Jenkins / JENKINS-57355 Question - Unable to find an option to publish the video file Issue Type: Bug Assignee: Unassigned Components: jenkinsfile-runner-test-framework Created: 2019-05-07 15:28 Priority: Trivial Reporter: Rakesh Nambiar After the Test execution, I have the video file in the target folder. But I am not finding any suitable plug-in or option to publish it. I tried the archive option, but it wasn't useful. Please consider this as a question and advise. Add Comment
[JIRA] (JENKINS-57343) RTC: Jenkins checks out subdirs of a component instead of checking it out as one whole dir
Title: Message Title Zichuan Zou updated an issue Jenkins / JENKINS-57343 RTC: Jenkins checks out subdirs of a component instead of checking it out as one whole dir Change By: Zichuan Zou Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199118.1557152823000.19874.1557237840279%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57308) Update for Sonar 6 LTS (icons, links)
Title: Message Title Georg Henzler updated JENKINS-57308 Jenkins / JENKINS-57308 Update for Sonar 6 LTS (icons, links) Change By: Georg Henzler Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199077.1556809915000.19876.1557237900274%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Josh Soref commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub Liam Newman: I don't think it helped Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.20170.1557243601537%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56918) Groovy Class Files Not Copied Over To View Code Coverage
Title: Message Title Pavol Briatka commented on JENKINS-56918 Re: Groovy Class Files Not Copied Over To View Code Coverage Hello, I think I had a similar issue. I could not see Kotlin files in Jenkins when I checked Jacoco coverage (error message: "Error while reading the sourcefile!") but I managed to solve it by putting the following line to my Jenkinsfile jacoco step configuration: sourceInclusionPattern: '*/.*' Now both Java and Kotlin files are showed in reports. I checked the source code for JacocoPublisher where I found that the default value for String sourceInclusionPattern is indeed "*/.java" but you can rewrite it either in post-build actions tab in Jenkins or in your Jenkinsfile (depending on your implementation). The above mentioned implementation will include all files from your source code (defined as sourcePattern) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198593.1554476525000.20240.1557244080214%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50462) Artifacts tab presents everything as a flat list, making navigation time consuming
Title: Message Title Simon L-G commented on JENKINS-50462 Re: Artifacts tab presents everything as a flat list, making navigation time consuming Having the same issue. Is there any known workarounds other than switching to the old UI? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189521.1522249108000.20242.1557244560652%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56996) null permission lookup when pull-request's origin repo/branch is deleted on github
Title: Message Title Liam Newman commented on JENKINS-56996 Re: null permission lookup when pull-request's origin repo/branch is deleted on github Christian Höltje Please try this version: https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/github-branch-source/2.5.2-rc835.5125eb8241d3/ It should make you scan not fail due to issues with one PR. NOTE: PRs that experience errors will be marked "orphaned" (and possibly deleted depending on your orphan strategy). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198693.1555102536000.20102.1557239760131%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46385) Error while clicks on 'Open' links from Slack
Title: Message Title Rakesh Nambiar commented on JENKINS-46385 Re: Error while clicks on 'Open' links from Slack Kurt Madel any thought on this, please? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184649.1503488206000.20160.1557243060323%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45018) Slave getting disconnected frequently
Title: Message Title Rakesh Nambiar commented on JENKINS-45018 Re: Slave getting disconnected frequently Any update on this, please? Oleg Nenashev did you find any solution? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183106.149803334.20158.1557243060300%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57309) Ensure Generic JS portlet does not XSS-encode JS
Title: Message Title Georg Henzler updated JENKINS-57309 Jenkins / JENKINS-57309 Ensure Generic JS portlet does not XSS-encode JS Change By: Georg Henzler Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199078.1556809991000.19882.1557237900391%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57354) Remove obsolete Alerts from SonarQube portlet
Title: Message Title Georg Henzler updated JENKINS-57354 Jenkins / JENKINS-57354 Remove obsolete Alerts from SonarQube portlet Change By: Georg Henzler Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199133.1557236182000.19883.1557237900402%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57327) changeView option ignored, not added to client spec
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-57327 changeView option ignored, not added to client spec Change By: Karl Wirth Labels: P4_SUPPORT plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199099.1557004231000.19866.1557237600361%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57304) Multiple "idle" entries on Build Executor Status for non-existant executors
Title: Message Title Patrick Rose commented on JENKINS-57304 Re: Multiple "idle" entries on Build Executor Status for non-existant executors It looks like they've gone now (and we're updated to 1.746). I don't know whether it was fixed by the upgrade or the fact that the system would have been rebooted. May as well close this unless you can think of a reason to keep it open? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199072.1556795988000.19885.1557238080109%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57304) Multiple "idle" entries on Build Executor Status for non-existant executors
Title: Message Title Oleg Nenashev commented on JENKINS-57304 Re: Multiple "idle" entries on Build Executor Status for non-existant executors Fine with me. OTOH I do not see any patch which would fix the problem in the recent releases Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199072.1556795988000.20162.1557243240126%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57357) NullPointerException due to non-backwars compatibility in hudson.plugins.EC2.SlaveTemplate.
Title: Message Title Adrien Tateno updated an issue Jenkins / JENKINS-57357 NullPointerException due to non-backwars compatibility in hudson.plugins.EC2.SlaveTemplate. Change By: Adrien Tateno Attachment: Screen Shot 2019-05-07 at 9.23.19 AM.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199136.1557244845000.20259.1557245400824%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57357) NullPointerException due to non-backwars compatibility in hudson.plugins.EC2.SlaveTemplate.
Title: Message Title
Adrien Tateno updated an issue
Jenkins / JENKINS-57357
NullPointerException due to non-backwars compatibility in hudson.plugins.EC2.SlaveTemplate.
Change By:
Adrien Tateno
Upon upgrading the ec2-plugin to master and restarting Jenkins, the EC2 nodes begin to fail connecting with the following exception {{ ! image- Screen Shot 2019-05-07 -10-52-22-920 at 9 . 23.19 AM. png |thumbnail ! }} This is likely due to the recent change that allows configuring the strategy for determining the hostname/IP address of the node [https://github.com/jenkinsci/ec2-plugin/pull/329].[https://wiki.jenkins.io/display/JENKINS/Hint+on+retaining+backward+compatibility] suggests that it is necessary to define a {{readResolve()}} method when deprecating fields (in this case the boolean fields {{usePrivateDnsName connectUsingPublicIp}}) because when objects are loaded from XML their constructors are not invoked.What likely happened here, is that the newly defined {{connectionStrategy}} was null when loaded from XML, causing the hostname/IP address determination to fail at instance startup time. [~jvz][~dgarzon]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-57357) NullPointerException due to non-backwars compatibility in hudson.plugins.EC2.SlaveTemplate.
Title: Message Title Adrien Tateno updated an issue Jenkins / JENKINS-57357 NullPointerException due to non-backwars compatibility in hudson.plugins.EC2.SlaveTemplate. Change By: Adrien Tateno Attachment: image-2019-05-07-10-52-22-920.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199136.1557244845000.20263.1557245460108%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37508) Can't see where "Exported variables" get defined
Title: Message Title
Daniel Hoerner reopened an issue
Same problem here. I have NOT installed the Tool Envoronment plugin. Added following to the Custom Tool Definition: Exported Paths: "C:\Program Files\nodejs" But I can not see this path when running the "set" command of Windows durring build:
// node('VS2017') {
stage('Preparing Build machine...')
{
tool name: 'npm 6.4.1', type: 'com.cloudbees.jenkins.plugins.customtools.CustomTool'
}
echo "Current Environment:"
bat 'set'
}
Jenkins / JENKINS-37508
Can't see where "Exported variables" get defined
Change By:
Daniel Hoerner
Resolution:
Not A Defect
Status:
Resolved Reopened
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57181) Jenkins ALM disconnection
Title: Message Title Govind Sureka edited a comment on JENKINS-57181 Re: Jenkins ALM disconnection I have not received the mail. Please resend it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198932.1556196435000.19834.1557236160649%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57354) Remove obsolete Alerts from SonarQube portlet
Title: Message Title Georg Henzler created an issue Jenkins / JENKINS-57354 Remove obsolete Alerts from SonarQube portlet Issue Type: Improvement Assignee: Georg Henzler Components: mashup-portlets-plugin Created: 2019-05-07 13:36 Priority: Minor Reporter: Georg Henzler Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199133.1557236182000.19839.1557236220340%40Atlassian.JIRA. For more options, visit
[JIRA] (JENKINS-37508) Can't see where "Exported variables" get defined
Title: Message Title Daniel Hoerner updated an issue Jenkins / JENKINS-37508 Can't see where "Exported variables" get defined Change By: Daniel Hoerner Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173616.1471513906000.19842.1557236220517%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32996) Jenkins use different RTC Build Toolkit path as the one set in system configure
Title: Message Title Wolf Molnar reopened an issue I have this problem too. The Master is running on Linux and the slave is running on Windows. I use the RTC-BuildSystem-Toolkit-Win64-6.0.6 and the toolkit is not installed on the Master, just on the slave When I use Windows Master alone and install toolkit then it work fine, Jenkins / JENKINS-32996 Jenkins use different RTC Build Toolkit path as the one set in system configure Change By: Wolf Molnar Resolution: Cannot Reproduce Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168320.1455716302000.19869.1557237660766%40Atlassian.JIRA.
[JIRA] (JENKINS-57314) P4 Sync to label after sync to head without deleting non labeled files
Title: Message Title Jose Valverde commented on JENKINS-57314 Re: P4 Sync to label after sync to head without deleting non labeled files Hi Karl Wirth, My mistake, indeed I have my jenkins credentials on the fcredentials options not my workspace name. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199083.1556813511000.19851.1557237240134%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57327) changeView option ignored, not added to client spec
Title: Message Title
Karl Wirth commented on JENKINS-57327
Re: changeView option ignored, not added to client spec
Hi Aaron Miller, Strangely mine works.
checkout perforce(credential: 'JenkinsMaster',
populate: forceClean(have: false,
parallel:
[
enable: false,
minbytes: '1024',
minfiles: '1',
threads: '4'
],
pin: '',
quiet: false),
workspace: manualSpec(charset: 'none',
cleanup: false,
name: 'jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}-changeview',
pinHost: false,
spec: clientSpec(allwrite: false,
backup: true,
changeView: '//depot/Project1/...@307',
clobber: true,
compress: false,
line: 'LOCAL',
locked: false,
modtime: false,
rmdir: false,
serverID: '',
streamName: '',
type: 'WRITABLE',
view: '//depot/Project1/... //jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}-changeview/...')))
You can see that '307' is the CL I have set for my 'changeview'. In the job output I see it correctly syncing 307:
P4 Task: syncing files at change: 307
... p4 sync /var/lib/jenkins/ANOTHER_SLAVE/workspace/PipelineEditor/...@307
Note - The latest CL is '363' on this path:
$ p4 changes -m1 //depot/Project1/...
Change 363 on 2019/04/08 by super@test_ws 'Submit of ./f363'
Can you please try a simple test where your checkout step is the only one in the code from a fresh job. Do you still see the same bug?
Add Comment
[JIRA] (JENKINS-46305) Jenkins Slave FATAL: command execution failed
Title: Message Title Ricky Tan resolved as Fixed this was already fixed. just need to increase the ELB idle timeout value Jenkins / JENKINS-46305 Jenkins Slave FATAL: command execution failed Change By: Ricky Tan Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184561.1503206898000.20097.1557239340507%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46305) Jenkins Slave FATAL: command execution failed
Title: Message Title Ricky Tan updated an issue Jenkins / JENKINS-46305 Jenkins Slave FATAL: command execution failed Change By: Ricky Tan Comment: this was already fixed. just need to increase the ELB idle timeout value Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184561.1503206898000.20100.1557239400224%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46305) Jenkins Slave FATAL: command execution failed
Title: Message Title Ricky Tan commented on JENKINS-46305 Re: Jenkins Slave FATAL: command execution failed this was already fixed. just need to increase the ELB idle timeout value Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184561.1503206898000.20094.1557239340457%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50433) unable to load shared library from gerrit pull request branch
Title: Message Title Sorin Sbarnea updated JENKINS-50433 Closing as I am no longer using jenkins so I cannot reproduce it (or the fix) Jenkins / JENKINS-50433 unable to load shared library from gerrit pull request branch Change By: Sorin Sbarnea Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189489.1522158981000.20117.1557241440907%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21336) ADMINISTER should not imply RUN_SCRIPTS
Title: Message Title Matt Sicker assigned an issue to Unassigned Jenkins / JENKINS-21336 ADMINISTER should not imply RUN_SCRIPTS Change By: Matt Sicker Assignee: Matt Sicker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.152900.1389394038000.20125.1557241680930%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34313) SAXParseException from parallel SCM checkout
Title: Message Title Wolfgang Issovits commented on JENKINS-34313 Re: SAXParseException from parallel SCM checkout Is there a chance to get a new release of the plugin with this fix included? That would be great as this issue is really problematic for larger parallel pipelines. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.169867.1460993343000.20128.1557241680988%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57161) ec2 plugin locks queue until excessWorkload is 0
Title: Message Title Adrien Tateno commented on JENKINS-57161 Re: ec2 plugin locks queue until excessWorkload is 0 Proposed fix: https://github.com/jenkinsci/ec2-plugin/pull/346 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198911.1556047726000.20257.1557245160174%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57173) Issue with Darcs SCM plugin saving build records
Title: Message Title Sven Strittmatter commented on JENKINS-57173 Re: Issue with Darcs SCM plugin saving build records Did this issue start occuring after upgrading your Jenkins? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198924.1556132083000.19779.1557234900154%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Mark Waite edited a comment on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error [~sebawo] when I've resolved the blocking bugs that are identified in the [git client plugin 3.0 milestone| https://github.com/jenkinsci/ git - client - plugin 3.0 / milestone /1 ] and in the [git plugin 4.0 milestone|https://github.com/jenkinsci/git-plugin/milestone/3]. You're welcome to help test the beta versions and report your results of testing the beta versions. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186841.1511861183000.19804.1557235441260%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Mark Waite commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error Sebastian Wojas when I've resolved the blocking bugs that are identified in the [git client plugin 3.0 milestone|git client plugin 3.0 milestone] and in the git plugin 4.0 milestone. You're welcome to help test the beta versions and report your results of testing the beta versions. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186841.1511861183000.19802.1557235441237%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37508) Can't see where "Exported variables" get defined
Title: Message Title
Daniel Hoerner edited a comment on JENKINS-37508
Re: Can't see where "Exported variables" get defined
Same problem here.I have NOT installed the Tool Envoronment plugin.Added following to the Custom Tool Definition:Exported Paths: "C:\Program Files\nodejs" I using the custom tool installer durring the runtime at the Build VM (See Preparing Build machine stage) But I can not see this path when running the "set" command of Windows durring build: {code:java}// node('VS2017') {stage('Preparing Build machine...'){ tool name: 'npm 6.4.1', type: 'com.cloudbees.jenkins.plugins.customtools.CustomTool' }echo "Current Environment:"bat 'set'}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173616.1471513906000.19846.1557236340143%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57314) P4 Sync to label after sync to head without deleting non labeled files
Title: Message Title Karl Wirth commented on JENKINS-57314 Re: P4 Sync to label after sync to head without deleting non labeled files Hi Jose Valverde, Sorry 'credential' is a typo. That should be your Jenkins credential not the workspace name. For example: def p4 = p4 (credential: 'myJenkinsCrentialName',workspace: ... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199083.1556813511000.19849.1557236640122%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31437) attach properties to resources, inject properties at build time
Title: Message Title Emmanuel Ruhnau commented on JENKINS-31437 Re: attach properties to resources, inject properties at build time I need that too. Any update ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.166301.144683029.19853.1557237480471%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32996) Jenkins use different RTC Build Toolkit path as the one set in system configure
Title: Message Title Wolf Molnar commented on JENKINS-32996 Re: Jenkins use different RTC Build Toolkit path as the one set in system configure Jenkins ver. 2.150.3 Team Concert Plugin 1.2.0.5 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168320.1455716302000.19881.1557237900365%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32996) Jenkins use different RTC Build Toolkit path as the one set in system configure
Title: Message Title Wolf Molnar commented on JENKINS-32996 Re: Jenkins use different RTC Build Toolkit path as the one set in system configure The slave has a custom path of toolkit and Avoid using build toolkit on Master (experimental) is checked but It still use master path. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168320.1455716302000.19891.1557238680152%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Liam Newman edited a comment on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub [~synalogik], [~amirbarkal], [~dbsanfte], [~soar]If anyone is interested in trying it, I have an experimental version of the github-branch-source-plugin using okttp3. https://drive.google.com/file/d/1VreeBlIG0RCbSI80wW2BBOmcVT9ZySNW/view?usp=sharing -Removed- If you have a test/staging Jenkins on which your are comfortable trying this out it would be helpful to know if this issue would be fixed by this upgrade. The code can be seen at https://github.com/jenkinsci/github-branch-source-plugin/pull/223 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.19896.1557238801477%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Liam Newman commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub Josh Soref, Ebrahim Moshaya, Amir Barkal, David Sanftenberg, Aleksey Smyrnov Here's the updated plugin with okio (thanks Josh!). https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/github-branch-source/2.5.2-rc836.bde357341ecd/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.19962.1557238861709%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44313) Conditional Plugin - Build status NOT changing if my conditional flow PASS
Title: Message Title Rakesh Nambiar closed an issue as Fixed Closing the issue as this cannot be fixed Jenkins / JENKINS-44313 Conditional Plugin - Build status NOT changing if my conditional flow PASS Change By: Rakesh Nambiar Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182118.149502116.20149.1557243000336%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56918) Groovy Class Files Not Copied Over To View Code Coverage
Title: Message Title
Pavol Briatka edited a comment on JENKINS-56918
Re: Groovy Class Files Not Copied Over To View Code Coverage
Hello, I think I had a similar issue. I could not see Kotlin files in Jenkins when I checked Jacoco coverage (error message: _"Error while reading the sourcefile!"_) but I managed to solve it by putting the following line to my Jenkinsfile jacoco step configuration: {code:java} sourceInclusionPattern: '**/*.*' \{code} Now both Java and Kotlin files are showed in reports. I checked the source code for JacocoPublisher where I found that the default value for String sourceInclusionPattern is indeed \{code:java} "**/*.java" \{code} but you can rewrite it either in post-build actions tab in Jenkins or in your Jenkinsfile (depending on your implementation).The above mentioned implementation will include all files from your source code (defined as sourcePattern)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198593.1554476525000.20266.1557246000295%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57173) Issue with Darcs SCM plugin saving build records
Title: Message Title Mike Sollanych commented on JENKINS-57173 Re: Issue with Darcs SCM plugin saving build records Hah. We have traced this to a nasty Unicode character in a commit from 2009 - for whatever reason the SCM plugin pulls the entire history of the repo, which actually takes quite a while to run. I think Darcs has some functions for limiting this in the time domain, so if you are working on the plugin that'd be something to consider adding in. We're going to see if we can find a way to remove the byte. Darcs itself should be escaping it, e.g. as an ` ` or similar, but I suppose it's too edgy of a case for that. We upgrade Jenkins regularly and this issue reared its head as a part of the recent trust / serializer changes, but I think may have been an issue even beforehand. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198924.1556132083000.20351.1557253020145%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title
Craig Rodrigues edited a comment on JENKINS-55287
Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head
I encountered this:{noformat}Creating placeholder flownodes because failed loading originals. java.io.IOException: Tried to load head FlowNodes for execution Owner[DEV/Porx-07/82:DEV/Porx-07 #82] but FlowNode was not found in storage for head id:FlowNodeId 1:121 at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.initializeStorage(CpsFlowExecution.java:679) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(CpsFlowExecution.java:716) at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(WorkflowRun.java:664) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(WorkflowRun.java:526) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:57) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:501) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:483) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:381) at hudson.model.RunMap.getById(RunMap.java:205) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.run(WorkflowRun.java:901) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:912) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:65) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:57) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl.onLoaded(FlowExecutionList.java:178) at jenkins.model.Jenkins.(Jenkins.java:989) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:233) Finished: FAILURE {noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57361) pipelines get lost of project when renaming projects
Title: Message Title Geert Nijs created an issue Jenkins / JENKINS-57361 pipelines get lost of project when renaming projects Issue Type: Bug Assignee: Unassigned Components: jenkinsfile-runner Created: 2019-05-07 19:31 Environment: linux centos, jenkins 2.164.2 Priority: Major Reporter: Geert Nijs to reproduce: create a project a create a pipeline x, that has an " build job: 'a' entry this works rename project a to b (via advanced settings) pipeline still work, but script still has build job 'a' entry (? somewhere the id must have been saved change pipeline build job to build job 'b' -> doesn't run anymore: error: can't find b
[JIRA] (JENKINS-56918) Groovy Class Files Not Copied Over To View Code Coverage
Title: Message Title
Pavol Briatka edited a comment on JENKINS-56918
Re: Groovy Class Files Not Copied Over To View Code Coverage
Hello, I think I had a similar issue. I could not see Kotlin files in Jenkins when I checked Jacoco coverage (error message: _"Error while reading the sourcefile!"_) but I managed to solve it by putting the following line to my Jenkinsfile jacoco step configuration:{code:java} sourceInclusionPattern: '**/*.*' \ {code} Now both Java and Kotlin files are showed in reports. I checked the source code for JacocoPublisher where I found that the default value for String sourceInclusionPattern is indeed \{code: set to copy only java }"**/*.java"\{code} files but you can rewrite it either in post-build actions tab in Jenkins or in your Jenkinsfile (depending on your implementation). The above mentioned implementation will include all files from your source code (defined as sourcePattern)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198593.1554476525000.20269.1557246120233%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57357) NullPointerException due to non-backwards compatibility in hudson.plugins.EC2.SlaveTemplate.
Title: Message Title Adrien Tateno updated an issue Jenkins / JENKINS-57357 NullPointerException due to non-backwards compatibility in hudson.plugins.EC2.SlaveTemplate. Change By: Adrien Tateno Summary: NullPointerException due to non- backwars backwards compatibility in hudson.plugins.EC2.SlaveTemplate. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199136.1557244845000.20271.1557246780115%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57358) NPE in SwarmScmSource#getTags
Title: Message Title Stuart Rowe created an issue Jenkins / JENKINS-57358 NPE in SwarmScmSource#getTags Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2019-05-07 16:48 Environment: p4-plugin 1.9.7 Priority: Major Reporter: Stuart Rowe SwarmScmSource#getPathsInBranch can return null in certain cases. In the case I debugged, I had reviewed a branch from a Swarm project which still had an open review. Add Comment
[JIRA] (JENKINS-57359) Info upgrade version
Title: Message Title Davide Calò created an issue Jenkins / JENKINS-57359 Info upgrade version Issue Type: Improvement Assignee: Unassigned Components: xcode-plugin Created: 2019-05-07 17:51 Priority: Minor Reporter: Davide Calò Dear, there is a way to set that for each build, tool increases the version and build number in info.plist? Thanks, Davide Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-48087) URLTrigger Plugin causes stack trace on pipeline job
Title: Message Title Juan Carlos Perez Castellanos edited a comment on JENKINS-48087 Re: URLTrigger Plugin causes stack trace on pipeline job I have also face this issue also . Freestyle project works great but pipeline fails. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186651.1510930655000.20334.1557252240384%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
