[JIRA] (JENKINS-56551) Documentation says CSRF is enabled by default on 2.x but that's not the case.
Title: Message Title Anthony Kamau updated an issue Jenkins / JENKINS-56551 Documentation says CSRF is enabled by default on 2.x but that's not the case. Change By: Anthony Kamau I've just deployed Jenkins v2.150.3 and noticed a few issues crop up after first login. One item was CSRF which is stated to be enabled by default on v2.x according to the [documentation|[https://wiki.jenkins.io/display/JENKINS/CSRF+Protection] . ]!image-2019-03-14-12-13-18-565.png|width=598,height=64! 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-56535) Caused: java.io.IOException: Unexpected termination of the channel for Azure Agents
Title: Message Title Azure DevOps started work on JENKINS-56535 Change By: Azure DevOps 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-52850) Credentials helper does not work for BasicSSHUserPrivateKey
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-52850 Re: Credentials helper does not work for BasicSSHUserPrivateKey There is not support for credentials binding of SSH Credentials in the environment block of declarative pipeline. The SSHCredentials would need to implement a CredentialsBindingHandler. 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-52850) Credentials helper does not work for BasicSSHUserPrivateKey
Title: Message Title Allan BURDAJEWICZ updated an issue Jenkins / JENKINS-52850 Credentials helper does not work for BasicSSHUserPrivateKey Change By: Allan BURDAJEWICZ Component/s: ssh-credentials-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40703) Support injection of maven-gpg-plugin:sign config params in Maven Settings files
Title: Message Title Steve Todorov edited a comment on JENKINS-40703 Re: Support injection of maven-gpg-plugin:sign config params in Maven Settings files [~cleclerc] do you know what is the state of this issue? We are currently preparing some jobs which will be using the `maven-gpg-plugin` to sign maven artifacts. However the only way this would ever work is by doing `mvn release:perform -Darguments=-Dgpg.passphrase=thephrase` and passing the password via the CLI is something we would like to avoid.Can't there just be a `Maven passphrase` credential type for this case kind which results you can add in adding a server Id with a the credentials section and then from the ` Config File Management ` ? (like in you can add the [examples|http://maven.apache.org/plugins/maven-gpg-plugin/usage.html] of maven's gpg plugin) `serverid` to use the defined credentials? 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-40703) Support injection of maven-gpg-plugin:sign config params in Maven Settings files
Title: Message Title Steve Todorov commented on JENKINS-40703 Re: Support injection of maven-gpg-plugin:sign config params in Maven Settings files Cyrille Le Clerc do you know what is the state of this issue? We are currently preparing some jobs which will be using the `maven-gpg-plugin` to sign maven artifacts. However the only way this would ever work is by doing `mvn release:perform -Darguments=-Dgpg.passphrase=thephrase` and passing the password via the CLI is something we would like to avoid. Can't there just be a `Maven passphrase` credential type for this case which results in adding a server Id with a `` ? (like in the examples of maven's gpg plugin) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56535) Caused: java.io.IOException: Unexpected termination of the channel for Azure Agents
Title: Message Title Jie Shen commented on JENKINS-56535 Re: Caused: java.io.IOException: Unexpected termination of the channel for Azure Agents Thanks for reporting the issue here. I think this issue may be relevant with https://github.com/jenkinsci/jenkins/blob/1c9eb43283e7321ee4d3a0e1e9995453493ff04a/core/src/main/java/hudson/model/Slave.java#L496-L500 . The agent does not set up connection with master successfully. Do you choose SSH to connect to slave? The code is not enough robust for now. I think we should set timeout and retry strategy for setting up the connection. 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-56548) Support Joining Domains for Azure VM Plugin
Title: Message Title Jie Shen commented on JENKINS-56548 Re: Support Joining Domains for Azure VM Plugin Thanks for reporting the issue here. We will put this into our plan. 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-56548) Support Joining Domains for Azure VM Plugin
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-56548 Support Joining Domains for Azure VM Plugin Change By: Jie Shen Assignee: Azure DevOps Jie Shen 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-56383) BlueOcean pipeline UI fails to render stages past the first parallel stage after I upgraded the plugins
Title: Message Title Josh McDonald commented on JENKINS-56383 Re: BlueOcean pipeline UI fails to render stages past the first parallel stage after I upgraded the plugins Pull request to fix the regression (and extra tests) is here: https://github.com/jenkinsci/blueocean-plugin/pull/1933 - give it a few days as most of the reviewers are away from the office right now. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Josh McDonald commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step Pull request to fix the regression (and extra tests) is here: https://github.com/jenkinsci/blueocean-plugin/pull/1933 - give it a few days as most of the reviewers are away from the office right now. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56551) Documentation says CSRF is enabled by default on 2.x but that's not the case.
Title: Message Title Anthony Kamau created an issue Jenkins / JENKINS-56551 Documentation says CSRF is enabled by default on 2.x but that's not the case. Issue Type: Bug Assignee: Unassigned Attachments: image-2019-03-14-12-13-18-565.png, Selection_999(131).png Components: core Created: 2019-03-14 01:16 Environment: Jenkins v2.150.3 on Kubernetes as detailed here: https://goo.gl/gzqdAN Priority: Minor Reporter: Anthony Kamau I've just deployed Jenkins v2.150.3 and noticed a few issues crop up after first login. One item was CSRF which is stated to be enabled by default on v2.x according to the [documentation|https://wiki.jenkins.io/display/JENKINS/CSRF+Protection.] Add Comment
[JIRA] (JENKINS-56402) Declarative Pipeline shows SUCCESS even though job FAILED
Title: Message Title Lakshya Kapoor commented on JENKINS-56402 Re: Declarative Pipeline shows SUCCESS even though job FAILED I am also glad to confirm that currentBuild.currentResult in v1.3.7-beta1 works as it did in v1.3.4.1. Thanks 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-56326) Git fetch in a later Pipeline stage fails when master received new revisions in the meantime
Title: Message Title Mark Waite commented on JENKINS-56326 Re: Git fetch in a later Pipeline stage fails when master received new revisions in the meantime Running two agents on the same computer or same file system with the same directory for both agents is a mistake. It creates many problems as the two agents each assume they have complete control of the workspace. If you're allowed to temporarily mark either agent C or agent D as offline, that should be enough to confirm that the problem is not visible when a single agent is controlling 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56550) Credentials fail if password has dollar sign ($) in it
Title: Message Title John Rocha created an issue Jenkins / JENKINS-56550 Credentials fail if password has dollar sign ($) in it Issue Type: Bug Assignee: Unassigned Components: credentials-plugin Created: 2019-03-13 21:20 Environment: Windows 8.1 Jenkins 2.150.3 Priority: Major Reporter: John Rocha Using Credentials with the Parameterized Remote Trigger plugin. Created Credentials Scope Global Username build Password $SecretP@ssword ID Default
[JIRA] (JENKINS-52420) [JEP-200] Can't serialize class
Title: Message Title Dale King commented on JENKINS-52420 Re: [JEP-200] Can't serialize class but I assume that it is related to instances of "com.google.common.collect.Multimap"... or not. The class itself is permitted in the core: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/jenkins/security/whitelisted-classes.txt It is related specifically to instances of "com.google.common.collect.ImmutableListMultimap", which does NOT appear in the whitelist 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-52420) [JEP-200] Can't serialize class
Title: Message Title
Dale King edited a comment on JENKINS-52420
Re: [JEP-200] Can't serialize class
It was mentioned that the stack trace was incomplete, if it helps here is a complete one: { { code:java} Error when executing always post condition:java.io.IOException: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class org.jenkinsci.plugins.workflow.job.WorkflowRun at hudson.XmlFile.write(XmlFile.java:200) at org.jenkinsci.plugins.workflow.support.PipelineIOUtils.writeByXStream(PipelineIOUtils.java:30) at org.jenkinsci.plugins.workflow.job.WorkflowRun.save(WorkflowRun.java:1256) at org.jenkinsci.plugins.docker.commons.fingerprint.DockerFingerprintAction.addToRun(DockerFingerprintAction.java:145) at org.jenkinsci.plugins.docker.commons.fingerprint.DockerFingerprints.addRunFacet(DockerFingerprints.java:242) at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:194) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:229) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20) at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:135) at org.jenkinsci.plugins.docker.workflow.Docker.node(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:66) at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:123) at dockerBuild.call(/var/jenkins_home/jobs/dsl-small-app/jobs/arc-maturity-events/jobs/build/branches/Perform-PITest-in-Jenkins/builds/5/libs/jenkins-pipeline-library/vars/dockerBuild.groovy:64) at org.jenkinsci.plugins.docker.workflow.Docker.withRegistry(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:41) at ___cps __cps . transform___ transform__ (Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) at sun.reflect.GeneratedMethodAccessor372.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ClosureBlock.eval(ClosureBlock.java:46) at com.cloudbees.groovy.cps.Next.step(Next.java:83) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163) at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122) at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261) at
[JIRA] (JENKINS-52420) [JEP-200] Can't serialize class
Title: Message Title
Dale King edited a comment on JENKINS-52420
Re: [JEP-200] Can't serialize class
It was mentioned that the stack trace was incomplete, if it helps here is a complete one: {{ Error when executing always post condition:java.io.IOException: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class org.jenkinsci.plugins.workflow.job.WorkflowRun at hudson.XmlFile.write(XmlFile.java:200) at org.jenkinsci.plugins.workflow.support.PipelineIOUtils.writeByXStream(PipelineIOUtils.java:30) at org.jenkinsci.plugins.workflow.job.WorkflowRun.save(WorkflowRun.java:1256) at org.jenkinsci.plugins.docker.commons.fingerprint.DockerFingerprintAction.addToRun(DockerFingerprintAction.java:145) at org.jenkinsci.plugins.docker.commons.fingerprint.DockerFingerprints.addRunFacet(DockerFingerprints.java:242) at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:194) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:229) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20) at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:135) at org.jenkinsci.plugins.docker.workflow.Docker.node(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:66) at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:123) at dockerBuild.call(/var/jenkins_home/jobs/dsl-small-app/jobs/arc-maturity-events/jobs/build/branches/Perform-PITest-in-Jenkins/builds/5/libs/jenkins-pipeline-library/vars/dockerBuild.groovy:64) at org.jenkinsci.plugins.docker.workflow.Docker.withRegistry(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:41) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) at sun.reflect.GeneratedMethodAccessor372.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ClosureBlock.eval(ClosureBlock.java:46) at com.cloudbees.groovy.cps.Next.step(Next.java:83) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163) at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122) at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163) at
[JIRA] (JENKINS-52420) [JEP-200] Can't serialize class
Title: Message Title
Dale King edited a comment on JENKINS-52420
Re: [JEP-200] Can't serialize class
It was mentioned that the stack trace was incomplete, if it helps here is a complete one: {{ Error when executing always post condition: }} {{ java.io.IOException: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class org.jenkinsci.plugins.workflow.job.WorkflowRun }} {{ at hudson.XmlFile.write(XmlFile.java:200) }} {{ at org.jenkinsci.plugins.workflow.support.PipelineIOUtils.writeByXStream(PipelineIOUtils.java:30) }} {{ at org.jenkinsci.plugins.workflow.job.WorkflowRun.save(WorkflowRun.java:1256) }} {{ at org.jenkinsci.plugins.docker.commons.fingerprint.DockerFingerprintAction.addToRun(DockerFingerprintAction.java:145) }} {{ at org.jenkinsci.plugins.docker.commons.fingerprint.DockerFingerprints.addRunFacet(DockerFingerprints.java:242) }} {{ at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:194) }} {{ at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:229) }} {{ at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) }} {{ at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) }} {{ at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) }} {{ at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) }} {{ at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20) }} {{ at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar: [ file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:135 |file:///var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:135] ) }} {{ at org.jenkinsci.plugins.docker.workflow.Docker.node(jar: [ file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:66 |file:///var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:66] ) }} {{ at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar: [ file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:123 |file:///var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:123] ) }} {{ at dockerBuild.call(/var/jenkins_home/jobs/dsl-small-app/jobs/arc-maturity-events/jobs/build/branches/Perform-PITest-in-Jenkins/builds/5/libs/jenkins-pipeline-library/vars/dockerBuild.groovy:64) }} {{ at org.jenkinsci.plugins.docker.workflow.Docker.withRegistry(jar: [ file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:41 |file:///var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:41] ) }} {{ at ___cps.transform___(Native Method) }} {{ at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57) }} {{ at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) }} {{ at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) }} {{ at sun.reflect.GeneratedMethodAccessor372.invoke(Unknown Source) }} {{
[JIRA] (JENKINS-52420) [JEP-200] Can't serialize class
Title: Message Title
Dale King edited a comment on JENKINS-52420
Re: [JEP-200] Can't serialize class
It was mentioned that the stack trace was incomplete, if it helps here is a complete one: {{ Error when executing always post condition: }} {{ java.io.IOException: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class org.jenkinsci.plugins.workflow.job.WorkflowRun }} {{ at hudson.XmlFile.write(XmlFile.java:200) }} {{ at org.jenkinsci.plugins.workflow.support.PipelineIOUtils.writeByXStream(PipelineIOUtils.java:30) }} {{ at org.jenkinsci.plugins.workflow.job.WorkflowRun.save(WorkflowRun.java:1256) }} {{ at org.jenkinsci.plugins.docker.commons.fingerprint.DockerFingerprintAction.addToRun(DockerFingerprintAction.java:145) }} {{ at org.jenkinsci.plugins.docker.commons.fingerprint.DockerFingerprints.addRunFacet(DockerFingerprints.java:242) }} {{ at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:194) }} {{ at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:229) }} {{ at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) }} {{ at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) }} {{ at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) }} {{ at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) }} {{ at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20) }} {{ at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar: [ file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:135 |file:///var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:135] ) }} {{ at org.jenkinsci.plugins.docker.workflow.Docker.node(jar: [ file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:66 |file:///var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:66] ) }} {{ at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar: [ file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:123 |file:///var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:123] ) }} {{ at dockerBuild.call(/var/jenkins_home/jobs/dsl-small-app/jobs/arc-maturity-events/jobs/build/branches/Perform-PITest-in-Jenkins/builds/5/libs/jenkins-pipeline-library/vars/dockerBuild.groovy:64) }} {{ at org.jenkinsci.plugins.docker.workflow.Docker.withRegistry(jar: [ file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:41 |file:///var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:41] ) }} {{ at ___cps.transform___(Native Method) }} {{ at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57) }} {{ at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) }} {{ at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) }} {{ at sun.reflect.GeneratedMethodAccessor372.invoke(Unknown Source) }} {{
[JIRA] (JENKINS-52420) [JEP-200] Can't serialize class
Title: Message Title Dale King commented on JENKINS-52420 Re: [JEP-200] Can't serialize class It was mentioned that the stack trace was incomplete, if it helps here is a complete one: Error when executing always post condition: java.io.IOException: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class org.jenkinsci.plugins.workflow.job.WorkflowRun at hudson.XmlFile.write(XmlFile.java:200) at org.jenkinsci.plugins.workflow.support.PipelineIOUtils.writeByXStream(PipelineIOUtils.java:30) at org.jenkinsci.plugins.workflow.job.WorkflowRun.save(WorkflowRun.java:1256) at org.jenkinsci.plugins.docker.commons.fingerprint.DockerFingerprintAction.addToRun(DockerFingerprintAction.java:145) at org.jenkinsci.plugins.docker.commons.fingerprint.DockerFingerprints.addRunFacet(DockerFingerprints.java:242) at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:194) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:229) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20) at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:135) at org.jenkinsci.plugins.docker.workflow.Docker.node(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:66) at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:123) at dockerBuild.call(/var/jenkins_home/jobs/dsl-small-app/jobs/arc-maturity-events/jobs/build/branches/Perform-PITest-in-Jenkins/builds/5/libs/jenkins-pipeline-library/vars/dockerBuild.groovy:64) at org.jenkinsci.plugins.docker.workflow.Docker.withRegistry(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:41) at __cps.transform__(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) at sun.reflect.GeneratedMethodAccessor372.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ClosureBlock.eval(ClosureBlock.java:46) at com.cloudbees.groovy.cps.Next.step(Next.java:83) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163) at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122) at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163) at
[JIRA] (JENKINS-56549) Error building MOS sp-rewrite prject
Title: Message Title Ann Hohisel created an issue Jenkins / JENKINS-56549 Error building MOS sp-rewrite prject Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2019-03-13 20:04 Environment: MOS sp-rewrite Priority: Major Reporter: Ann Hohisel Stack trace java.lang.UnsupportedOperationException: Refusing to marshal net.sf.json.JSONObject for security reasons; see https://jenkins.io/redirect/class-filter/ at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:546) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:263) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:250) Caused: java.lang.RuntimeException: Failed to serialize org.jenkinsci.plugins.mesos.MesosSlaveInfo#slaveAttributes for class org.jenkinsci.plugins.mesos.MesosSlaveInfo at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:254) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:222) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:208) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:149) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at
[JIRA] (JENKINS-56548) Support Joining Domains for Azure VM Plugin
Title: Message Title Phillip Chen created an issue Jenkins / JENKINS-56548 Support Joining Domains for Azure VM Plugin Issue Type: New Feature Assignee: Azure DevOps Components: azure-vm-agents-plugin Created: 2019-03-13 19:35 Priority: Minor Reporter: Phillip Chen Currently the Azure VM plugin does not support joining the VMs to domains upon creation (only local admins), it would be helpful if we can get this option by default. On the other hand, attempting to join the VM to domains manually would require joining certain vnets and setting DNS servers for these VMs, but the plugin would then deprovision\delete the VMs upon reboot of the VM, not sure if it was intended behavior from the plugin. Example logs below: Feb 25, 2019 4:07:29 PM INFO com.microsoft.azure.vmagent.AzureVMAgent deprovision AzureVMAgent: deprovision: Deprovision called for agent nodes-tea6e560, for reason: Unknown reason Add Comment
[JIRA] (JENKINS-56512) Add function for Artifactory Version to org.jfrog.hudson.pipeline.common.types.ArtifactoryServer
Title: Message Title Adam Brousseau commented on JENKINS-56512 Re: Add function for Artifactory Version to org.jfrog.hudson.pipeline.common.types.ArtifactoryServer The first few times I tried to publish build info on my OSS server it failed. A few days later it appears to work fine. I still cannot see build or artifact properties on the UI and the retention doesn't seem to work but at least now its allowing me to publish it without failing. I no longer require this feature so feel free to close. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Sriniva Pothala edited a comment on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 We are seeing the same problem as well in version 1.14.8 but it was intermittent. I am unable to reproduce it when its not happening. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Sriniva Pothala commented on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 We are seeing the same problem as well in version 1.14.8 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-55388) multibranch pipeline deleting history and building unexpectedly
Title: Message Title jpschewe commented on JENKINS-55388 Re: multibranch pipeline deleting history and building unexpectedly I just had a build do this again. I looked at the scan repository log and it said no changes for the branch. However it could be that the scanning happened after the build started. Is there some logging I can turn on to see the results of all scans over time and catch the error? 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-56547) Pipeline Stage View Plugin: Stage shows as completed even when its not
Title: Message Title Bhamidi Kishore created an issue Jenkins / JENKINS-56547 Pipeline Stage View Plugin: Stage shows as completed even when its not Issue Type: Bug Assignee: Sam Van Oort Attachments: BlueOcean_Pipeline_View.png, Pipeline_Stage_View.png, Pipeline_Stage_View_Hovering.png Components: pipeline-stage-view-plugin Created: 2019-03-13 18:12 Priority: Minor Reporter: Bhamidi Kishore Pipeline Stage View Plugin shows stage as completed even when it's not. Stage view is showing - green colour for the stage displays how much time it took displays "Success" message when hoving on the stage But checking the actual build logs shows the stage was still in progress. Add Comment
[JIRA] (JENKINS-52636) Gerrit triggered jobs getting delayed
Title: Message Title Darrien Glasser edited a comment on JENKINS-52636 Re: Gerrit triggered jobs getting delayed Update, we've been debugging this issue, and it seems like the Replication Plugin may be (somehow) interfering with the missed events playback plugin/event trigger.We're not entirely certain, but it almost looks like the event trigger (that sends builds to Jenkins) is receiving replication events and gets stuck trying to understand what to do with them.We will continue investigating. Disabling the replication plugin reduces our backlog queue to 0 and events are perfectly streamed to 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52636) Gerrit triggered jobs getting delayed
Title: Message Title Darrien Glasser commented on JENKINS-52636 Re: Gerrit triggered jobs getting delayed Update, we've been debugging this issue, and it seems like the Replication Plugin may be (somehow) interfering with the missed events playback plugin/event trigger. We're not entirely certain, but it almost looks like the event trigger (that sends builds to Jenkins) is receiving replication events and gets stuck trying to understand what to do with them. We will continue investigating. 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-55075) Pipeline: If job fails it will run again on next poll.
Title: Message Title Karl Wirth commented on JENKINS-55075 Re: Pipeline: If job fails it will run again on next poll. Note for Dev - Please can we look at this on as a priority. 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-55622) P4 plugin keeps triggering new build on the same change when polling enabled
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-55622 P4 plugin keeps triggering new build on the same change when polling enabled 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Michel Zanini commented on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults Yes Nick Jones, I used as init script. And is true that you might be hiding other logs like mentioned by JD Friedrikson. I don't see it as a major issue to hide more. But need to keep this in mind. Anyway, its the only workaround that can be done. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55829) Expose AbstractCIBase#disabledAdministrativeMonitors as internal API
Title: Message Title Nisarg Shah commented on JENKINS-55829 Re: Expose AbstractCIBase#disabledAdministrativeMonitors as internal API Oleg Nenashev Can you please review the PR : https://github.com/jenkinsci/jenkins/pull/3873 Changes have been made according to the suggestions and now it looks fine !! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52669) IndexOutOfBoundsException after upgrade to 1.2.3
Title: Message Title
Sébastien Gautrin edited a comment on JENKINS-52669
Re: IndexOutOfBoundsException after upgrade to 1.2.3
I encountered the same issue recently with one artifact. I got multiple artifacts from a multi-module maven project that are released to nexus by another job, then several similar scripted pipeline jobs for deploying different artifacts, with all of them using an Artifact parameter with the same artifact configured.With one of them, I encounter this error (whether using the job parameter or a hardcoded version, the configured version in the step being overriden by the job parameter anyway according to the log “Overriding configured version ... with version ... from build parameter”).The {{IndexOutOfBoundException}} itself comes from a mistake in the code in [ReleasedVersionRangeResolver|https://github.com/jenkinsci/repository-connector-plugin/blob/master/src/main/java/org/jvnet/hudson/plugins/repositoryconnector/aether/ReleasedVersionRangeResolver.java] : before accessing the first entry in {{vs}} collection, there is a check on {{versions}} collection instead of the filtered {{vs}} collection; with a test on the filtered collection, the method would return {{null}} instead of raising an exception, though this would possibly raise an exception down the line anyway. In my case and the OP's though, we should not even enter this method though , as we specify a single version and not a version range: I've yet to identify why in this case I end up there, while I do not with other artifacts. Edit: I might have found the cause: in the final pom of my artifact, I do have a dependency defined as a range, and the corresponding artifact is not present on the same repository (the artifact I want is on a private repository, the ranged dependency is on central); I cannot confirm yet this is the cause, but it seems likely considering the error occurs within {{Aether.resolve}} and the dependencies collection.[~vlastimil_dolejs] do you also happen to have a dependency with a version range on the artifact you encounter the error with? (check the {{pom.xml}} of the artifact version on your repository)However, considering this plugin, we should probably ignore dependencies or the requested artifact, should we not?
Add Comment
[JIRA] (JENKINS-56453) git command line fails with http 502
Title: Message Title Mark Waite closed an issue as Not A Defect Jenkins / JENKINS-56453 git command line fails with http 502 Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56453) git command line fails with http 502
Title: Message Title Mark Waite updated JENKINS-56453 Jenkins / JENKINS-56453 git command line fails with http 502 Change By: Mark Waite Resolution: Won't Fix Status: Resolved In Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56453) git command line fails with http 502
Title: Message Title Mark Waite updated JENKINS-56453 Jenkins / JENKINS-56453 git command line fails with http 502 Change By: Mark Waite Status: In Review Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56295) multibranch jobs triggering repeatedly
Title: Message Title Karl Wirth commented on JENKINS-56295 Re: multibranch jobs triggering repeatedly Hi Nancy Belser, I've sent you a direct email with my findings. I'll update here if my solution works. 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-52669) IndexOutOfBoundsException after upgrade to 1.2.3
Title: Message Title Sébastien Gautrin commented on JENKINS-52669 Re: IndexOutOfBoundsException after upgrade to 1.2.3 I encountered the same issue recently with one artifact. I got multiple artifacts from a multi-module maven project that are released to nexus by another job, then several similar scripted pipeline jobs for deploying different artifacts, with all of them using an Artifact parameter with the same artifact configured. With one of them, I encounter this error (whether using the job parameter or a hardcoded version, the configured version in the step being overriden by the job parameter anyway according to the log “Overriding configured version ... with version ... from build parameter”). The IndexOutOfBoundException itself comes from a mistake in the code in ReleasedVersionRangeResolver : before accessing the first entry in vs collection, there is a check on versions collection instead of the filtered vs collection; with a test on the filtered collection, the method would return null instead of raising an exception, though this would possibly raise an exception down the line anyway. In my case and the OP's though, we should not even enter this method though, as we specify a single version and not a version range: I've yet to identify why in this case I end up there, while I do not with other artifacts. 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-56453) git command line fails with http 502
Title: Message Title Carsten Hilber resolved as Won't Fix Jenkins / JENKINS-56453 git command line fails with http 502 Change By: Carsten Hilber Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56453) git command line fails with http 502
Title: Message Title Carsten Hilber commented on JENKINS-56453 Re: git command line fails with http 502 Ok, found it. You were right about the settings beeing different between Jenkins and the bash. When building, jenkins loaded some proxy configuration that were set in a .gitconfig for the Jenkins user. When removing this, everything ran as expected. Thanks a bunch for your prompt support, Mark. Carsten 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-39998) Token expansion of a config file not happening
Title: Message Title Jon Freedam commented on JENKINS-39998 Re: Token expansion of a config file not happening This is total nonsense - suggesting installing a plugin to copy an environment variable set by another plugin in order to get a credential injected into a file. This should just work. 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-56260) Active Choices Reactive Parameter is showing sometimes empty list
Title: Message Title Madhavi Katreddy commented on JENKINS-56260 Re: Active Choices Reactive Parameter is showing sometimes empty list Here are the versions: Jenkins (2.150.3) Active Choices Plug-in (2.1) The same issue is happening for the ACs which are querying the artifactory to get the list of artifacts. I do have same script for the fallback. The script is working fine if I click on apply -> save without changes. The issue is happening only if there are any changes to the groovy script which may not be related to the ACs. Thanks 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-37008) Jenkins vSphere cloud plugin does not expose guest info to pipeline
Title: Message Title Szymon Bielawski commented on JENKINS-37008 Re: Jenkins vSphere cloud plugin does not expose guest info to pipeline I confirm the issue, can't seem to pass anything to the host. 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-56546) Pod Yaml in Jenkinsfile not being honored
Title: Message Title Daníel P created an issue Jenkins / JENKINS-56546 Pod Yaml in Jenkinsfile not being honored Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin, pipeline Created: 2019-03-13 14:24 Environment: Running in Kubernetes on Debian Stretch nodes Using the jenkins/jenkins:lts-alpine docker image Installed plugins: Bitbucket Branch Source Plugin (cloudbees-bitbucket-branch-source): 2.4.2 Kubernetes Credentials Plugin (kubernetes-credentials): 0.4.0 REST API for Blue Ocean (blueocean-rest): 1.13.2 Autofavorite for Blue Ocean (blueocean-autofavorite): 1.2.3 Pipeline: API (workflow-api): 2.33 Kubernetes plugin (kubernetes): 1.14.8 Pipeline: Nodes and Processes (workflow-durable-task-step): 2.29 Pipeline implementation for Blue Ocean (blueocean-pipeline-api-impl): 1.13.2 Matrix Project Plugin (matrix-project): 1.14 i18n for Blue Ocean (blueocean-i18n): 1.13.2 Common API for Blue Ocean (blueocean-commons): 1.13.2 Credentials Binding Plugin (credentials-binding): 1.18 Personalization for Blue Ocean (blueocean-personalization): 1.13.2 MapDB API Plugin (mapdb-api): 1.0.9.0 Pipeline SCM API for Blue Ocean (blueocean-pipeline-scm-api): 1.13.2 LDAP Plugin (ldap): 1.20 Git client plugin (git-client): 2.7.6 Config API for Blue Ocean (blueocean-config): 1.13.2 Credentials Plugin (credentials): 2.1.18 Pipeline: Shared Groovy Libraries (workflow-cps-global-lib): 2.13 Git plugin (git): 3.9.3 AnsiColor (ansicolor): 0.6.2 GitHub plugin (github): 1.29.4 Pipeline: GitHub Groovy Libraries (pipeline-github-lib): 1.0 Docker Commons Plugin (docker-commons): 1.13 JUnit Plugin (junit): 1.27 Pipeline: REST API Plugin (pipeline-rest-api): 2.10 REST Implementation for Blue Ocean (blueocean-rest-impl): 1.13.2 Subversion Plug-in (subversion): 2.12.1 Pipeline: Stage View Plugin (pipeline-stage-view): 2.10 SSH Slaves plugin (ssh-slaves): 1.29.4 Folders Plugin (cloudbees-folder): 6.7 Server Sent Events (SSE) Gateway Plugin (sse-gateway): 1.17 OWASP Markup Formatter Plugin (antisamy-markup-formatter): 1.5 Variant Plugin (variant): 1.2 Pipeline: Groovy (workflow-cps): 2.64 _javascript_ GUI Lib: Moment.js bundle plugin (momentjs): 1.1.1 Bitbucket Pipeline for Blue Ocean (blueocean-bitbucket-pipeline): 1.13.2 Git Pipeline for Blue Ocean (blueocean-git-pipeline): 1.13.2 Script Security Plugin (script-security): 1.54 Plain Credentials Plugin (plain-credentials): 1.5 Command Agent Launcher Plugin (command-launcher): 1.3 Events API for Blue Ocean (blueocean-events): 1.13.2 Display URL for Blue Ocean (blueocean-display-url): 2.2.0 Lockable Resources plugin
[JIRA] (JENKINS-55439) Update Remoting in the Remoting Kafka client to the recent version
Title: Message Title Pham Vu Tuan updated JENKINS-55439 Federico Naum Thanks for the contribution, I will close this ticket. Jenkins / JENKINS-55439 Update Remoting in the Remoting Kafka client to the recent version Change By: Pham Vu Tuan Status: In Review Resolved Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55439) Update Remoting in the Remoting Kafka client to the recent version
Title: Message Title Pham Vu Tuan started work on JENKINS-55439 Change By: Pham Vu Tuan 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-55439) Update Remoting in the Remoting Kafka client to the recent version
Title: Message Title Pham Vu Tuan updated JENKINS-55439 Jenkins / JENKINS-55439 Update Remoting in the Remoting Kafka client to the recent version Change By: Pham Vu Tuan Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56545) Depedencies of the plugin must not leak on the API
Title: Message Title Tigran Tch created an issue Jenkins / JENKINS-56545 Depedencies of the plugin must not leak on the API Issue Type: Improvement Assignee: rsandell Components: pipeline-utility-steps-plugin Created: 2019-03-13 14:08 Priority: Minor Reporter: Tigran Tch Hello, I notice that pipeline-utility-steps-plugin/src/main/java/org/jenkinsci/plugins/pipeline/utility/steps/maven/ReadMavenPomStep.java is returning the following org.apache.maven.model.Model This is part of org.apache.maven:maven-model artifact and should not be expose. This means that all the user of your plugin have a hard dependency on the version of the maven-model. Why it is not part of the pipeline-utility own api ? Add Comment
[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title JD Friedrikson commented on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults This will keep you from seeing other CPS-related warnings. 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-40456) First time builds are not reporting to Bitbucket
Title: Message Title 030 030 commented on JENKINS-40456 Re: First time builds are not reporting to Bitbucket I created another plugin, see https://github.com/030/golang-bitbucket-cloud-build-status-notifier 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-54723) EC2 Plugin: Include tags in created EBS volumes
Title: Message Title kruczku commented on JENKINS-54723 Re: EC2 Plugin: Include tags in created EBS volumes Hey, any news on that? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56544) failFast option for parallel stages sets build status to ABORTED when failure is inside of a nested parallel stage
Title: Message Title Ray Kivisto updated an issue Jenkins / JENKINS-56544 failFast option for parallel stages sets build status to ABORTED when failure is inside of a nested parallel stage Change By: Ray Kivisto Environment: Fresh Jenkins LTS 2.150.3 install'recommended' plugins, including [Pipeline: Declarative Plugin|https://plugins.jenkins.io/pipeline-model-definition] version 1.3.6 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56544) failFast option for parallel stages sets build status to ABORTED when failure is inside of a nested parallel stage
Title: Message Title Ray Kivisto created an issue Jenkins / JENKINS-56544 failFast option for parallel stages sets build status to ABORTED when failure is inside of a nested parallel stage Issue Type: Improvement Assignee: Andrew Bayer Attachments: Jenkinsfile, log, test.png Components: pipeline-model-definition-plugin Created: 2019-03-13 13:37 Priority: Minor Reporter: Ray Kivisto Symptom With a Pipeline using parallel stages with failFast true enabled, when a nested stage fails, the final build result is showing as ABORTED instead of FAILURE A similar bug was recently fixed JENKINS-55459 which corrected the build status result when using non-nested parallel stages with failFast true enabled, but it seems it did not catch the case where a nested stage inside of one of the parallel stages fails. Evidence The fix for JENKINS-55459 was delivered under version 1.3.5 of the Pipeline: Declarative Plugin, I am testing version 1.3.6. I started up a brand new Jenkins LTS 2.150.3 instance, with the 'recommended' plugins, including Pipeline: Declarative Plugin version 1.3.6 I ran the testcase inside of JENKINS-55459 and the build status is correctly marked as failed, so the fix from JENKINS-55459 was correct. When I run the attached Jenkinsfile , the build still shows as ABORTED: ... ERROR: script returned exit code 1 Finished: ABORTED Here is the full log: log I expected the build status to be marked as FAILURE, not ABORTED. Hypothesis I believe the fix from JENKINS-55459
[JIRA] (JENKINS-56526) Cannot get excludeMessage to work
Title: Message Title Ulli Hafner commented on JENKINS-56526 Re: Cannot get excludeMessage to work The reason is that maven warnings do not have a message. The matching lines are set into the description attribute. I'm not sure if it makes more sense to change that and set the message property or if it would be better to match message and description by the filter. 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-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Nick Jones commented on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults Never mind – I realized what you're describing is the technique documented at https://wiki.jenkins.io/display/JENKINS/Post-initialization+script. I've created an init.groovy in $JENKINS_HOME with the content from Michel Zanini's last comment, bounced my Jenkins instance, and am no longer seeing this log spam. Thanks! 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-56543) Unable to execute the plink.exe file from build
Title: Message Title suryatheja A commented on JENKINS-56543 Re: Unable to execute the plink.exe file from build This issue is not related with any plugin file. Just to raise a request purpose updated the was-builder-plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56543) Unable to execute the plink.exe file from build
Title: Message Title suryatheja A created an issue Jenkins / JENKINS-56543 Unable to execute the plink.exe file from build Issue Type: Bug Assignee: Daniel Petisme Components: was-builder-plugin Created: 2019-03-13 13:24 Environment: Development(POC) Priority: Major Reporter: suryatheja A Hi Team, We are using plink.exe file for run the Websphere deployment scripts. But when i execute the pink command getting below error. Error: D:\Jenkins\workspace\TestforWASDeployment>plink.exe -i D:\WASDeployment\Automation\scripts\PuTTY\Key_for_remotrehost.ppk appad...@s300s045.autoexpr.com -m D:\WASDeployment\Automation\scripts\DeployInput.bat 'plink.exe' is not recognized as an internal or external command, operable program or batch file. Note: As per google suggests for above error, we have updated plink.exe path file in environment variables . After update the path also getting same issue Best Regards, Suryatheja Ambati Add Comment
[JIRA] (JENKINS-50298) Use p4trust file if credential's Trust fingerprint is blank
Title: Message Title Igor Milos commented on JENKINS-50298 Re: Use p4trust file if credential's Trust fingerprint is blank Hello, is this fixing this issue going to be put in the road map? 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-56542) Build Token Root delays 1000 times longer than expected
Title: Message Title Zeki Yureti created an issue Jenkins / JENKINS-56542 Build Token Root delays 1000 times longer than expected Issue Type: Bug Assignee: Unassigned Components: build-token-root-plugin Created: 2019-03-13 13:15 Environment: Jenkins LTS 2.150.3 Lots of plugins including Build Token Root Plugin (version 1.4) Windows Server 2016 / Windows 10 Priority: Minor Reporter: Zeki Yureti We are using the Build Token Root Plugin (version 1.4) to trigger builds with a HTTP GET request, and have noticed that when we pass a delay parameter, the actual delay (shown in the build queue) is significantly longer than requested. http://server:8080/buildByToken/buildWithParameters?job=ajobname=thetoken=value=900sec delay=900sec => 10 days delay=30sec => 8 hr delay=1sec => 16 min It looks like those were 1000 times longer than they should have been. 90 seconds = 10.4 days 3 seconds = 8.3 hours 1000 seconds = 16.6 mins My guess is that this is related to JENKINS-44052 (passing a value in milliseconds to a function expecting seconds)
[JIRA] (JENKINS-56539) Multijob Retry Rules: failure doesn't match the rules
Title: Message Title Sasha Miroshnychenko commented on JENKINS-56539 Re: Multijob Retry Rules: failure doesn't match the rules While I'm fairly confident that this issue caused by an implicit misconfiguration on my end, there is still some kind of magic plugin behavior as well... I decided to double check the job configuration UI and noticed this Normally, this would never happen since all my ~1k jobs are configured with JJB, like this (multijob) - job: name: My_Pipeline node: pipeline project-type: multijob parameters: - string: name: my_param wrappers: - timestamps builders: - multijob: name: Example subjob condition: SUCCESSFUL projects: - name: paralleled_executor current-parameters: true kill-phase-on: NEVER retry: max-retry: 1 strategy-path: "/var/lib/jenkins/rules/retry_any_failure.txt" As you can see strategy-path: "/var/lib/jenkins/rules/retry_any_failure.txt" that is being obviously mentioned in multijob logs 00:57:40 Finished Build : #321: [PR-123] of Job : paralleled_executor with status : FAILURE 00:57:40 Scanning failed job console output using parsing rule file /var/lib/jenkins/rules/retry_any_failure.txt. 00:57:40 Failed the build, the failure doesn't match the rules. ... in reality, doesn't match to the rule from the global jenkins configuration: UnstableOrFailure: /var/lib/jenkins/rules/retry_unstable_failure.txt which is: > cat /var/lib/jenkins/rules/retry_unstable_failure.txt Finished: (FAILURE|UNSTABLE) I ended up adding 4th rule with that desired rule-file ... and after re-uploading job it shows proper rule (Any) from job configuration UI. Add Comment
[JIRA] (JENKINS-56525) Add Filters to Assign Roles page
Title: Message Title Kevin Delord updated an issue Jenkins / JENKINS-56525 Add Filters to Assign Roles page Change By: Kevin Delord Labels: gsoc-2019-project-idea user-experience 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-56539) Multijob Retry Rules: failure doesn't match the rules
Title: Message Title Sasha Miroshnychenko updated an issue Jenkins / JENKINS-56539 Multijob Retry Rules: failure doesn't match the rules Change By: Sasha Miroshnychenko Attachment: retry_any.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56540) Allow manual authentication against AD
Title: Message Title Ivan Fernandez Calvo closed an issue as Won't Do please see JENKINS-55065 Jenkins / JENKINS-56540 Allow manual authentication against AD Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56541) Failure to serialize object corrupts the Groovy in-memory model
Title: Message Title Allan BURDAJEWICZ updated an issue Jenkins / JENKINS-56541 Failure to serialize object corrupts the Groovy in-memory model Change By: Allan BURDAJEWICZ Issue Type: Bug Improvement 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-56326) Git fetch in a later Pipeline stage fails when master received new revisions in the meantime
Title: Message Title Raphael Reitzig commented on JENKINS-56326 Re: Git fetch in a later Pipeline stage fails when master received new revisions in the meantime If the error occurs on agent D and it is the same host as agent C, are those two agents using a shared directory for their workspace? I checked the workspaces list via the Jenkins UI. Agents C and D indeed use the same path (not conclusive) and the content seems to be identical, down to change dates of the files. So yes, this may indeed be the case. Not sure how to get perfect confirmation (again, no admin access on any of those machines) but it seems worth trying out for reproduction. That said, would that even be proper usage? Seems to me that using the same workspaces on two different agents is inviting trouble, even though you wouldn't notice unless parallel stages are used. 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-56541) Failure to serialize object corrupts the Groovy in-memory model
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-56541 Failure to serialize object corrupts the Groovy in-memory model Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-03-13 11:03 Environment: Jenkins 2.150.x Priority: Major Reporter: Allan BURDAJEWICZ Issue When executing a pipeline script with non-serializable objects (non whitelisted since JEP-200) that results in the creation of a Groovy proxy class, the script fails Caused by: java.lang.UnsupportedOperationException: Refusing to marshal ToolLocationNodeProperty$ToolLocation1_groovyProxy for security reasons; see https://jenkins.io/redirect/class-filter/ This was caused by the following line: def toolLocationProperty = new ToolLocationNodeProperty(toolLocation as List) While the solution is to fix the script, in that case: def toolLocationProperty = new ToolLocationNodeProperty([toolLocation])
[JIRA] (JENKINS-56539) Multijob Retry Rules: failure doesn't match the rules
Title: Message Title Sasha Miroshnychenko updated an issue Jenkins / JENKINS-56539 Multijob Retry Rules: failure doesn't match the rules Change By: Sasha Miroshnychenko Attachment: image-2019-03-13-12-55-35-279.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56526) Cannot get excludeMessage to work
Title: Message Title
Andreas Zeiler commented on JENKINS-56526
Re: Cannot get excludeMessage to work
Hi, I think I'm running into the same issue here. The following problem occur with the warnings-ng-plugin: I'm building our documentation through a pipeline script and I get a doxygen generated log named "doxygen-warnings.log". In Jenkinsfile I've configured to look for recordIssues filters: [excludeMessage('.*warning: no uniquely matching class member found for*.'), excludeFile('.*\\/BLABLA\\/.*|.*\\/BLABLA\\/.*|.*\\/STM32F4xx\\/.*')], tools: [doxygen(pattern: 'doxygen-warnings.log')] I used the "Pipeline Syntax Generator" for this line. Unfortunatelly, the Plugin does not find anything. Even when I search some parts of the message in the plugin when viewing the summary. The output of doxygen which I want to filter looks like this: /home/jenkins/workspace/Documentation_SCM/Src/HAL_PCBA/Conf/com_conf.cpp:13: warning: no uniquely matching class member found for template <> template <> const hal_pcba::Uart1::SingleConfig Uart1::configuration(hal_uc::Uart::Baudrate::BAUD_38400, hal_uc::Uart::WordLength::LEN_9, hal_uc::Uart::StopBits::BIT_1, hal_uc::Uart::Parity::EVEN, hal_uc::Uart::Mode::TX_RX, hal_uc::Uart::FlowControl::NONE, hal_uc::Uart::Oversampling::X16) /home/jenkins/workspace/Documentation_SCM/Src/HAL_PCBA/Conf/com_conf.cpp:27: warning: no uniquely matching class member found for template <> template <> const hal_pcba::UartRxPin::SingleConfig hal_pcba::UartRxPin::configuration(hal_uc::Uart::Pin::IoMode::ALTERNATIVE_PP, hal_pcba::UartInstance) /home/jenkins/workspace/Documentation_SCM/Src/HAL_PCBA/Conf/com_conf.cpp:35: warning: no uniquely matching class member found for template <> template <> const hal_pcba::UartTxPin::SingleConfig hal_pcba::UartTxPin::configuration(hal_uc::Uart::Pin::IoMode::ALTERNATIVE_PP, hal_pcba::UartInstance) When I test my RegEx at https://regex101.com/ I get the right results. Do I need any special RegEx Magic? Is this a known Bug? Kind regards Andreas
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56540) Allow manual authentication against AD
Title: Message Title Pablo Gomez created an issue Jenkins / JENKINS-56540 Allow manual authentication against AD Issue Type: Improvement Assignee: Ivan Fernandez Calvo Components: saml-plugin Created: 2019-03-13 10:41 Priority: Minor Reporter: Pablo Gomez Hi, we were using before the AD plugin for authentication and recently we decided to switch to SAML to use our ADFS IdP. The SAML plugin works perfectly and we are able to authenticate through SAML. Problem is some people wants to use a service account to access to Jenkins. Currently it is not possible to log in in Jenkins with an user different from your personal one. Would it be possible to allow direct username and password authentication instead of SAML? Add Comment
[JIRA] (JENKINS-56539) Multijob Retry Rules: failure doesn't match the rules
Title: Message Title Sasha Miroshnychenko created an issue Jenkins / JENKINS-56539 Multijob Retry Rules: failure doesn't match the rules Issue Type: Bug Assignee: Unassigned Attachments: image-2019-03-13-11-50-08-020.png Components: multijob-plugin Created: 2019-03-13 10:30 Environment: Jenkins ver. 2.107.2 Multijob 1.31 Priority: Minor Reporter: Sasha Miroshnychenko Here is how it configured: Here is how the concerning rule looks like > ls -la /var/lib/jenkins/rules/ total 32 drwxrwxr-x. 2 jenkins jenkins 4096 Dec 24 12:21 . drwxr-xr-x. 40 jenkins jenkins 12288 Mar 13 09:53 .. -rw-rw-r--. 1 jenkins jenkins 3 Jul 12 2017 retry_any_failure.txt -rw-rw-r--. 1 jenkins jenkins18 Jul 12 2017 retry_failure.txt -rw-rw-r--. 1 jenkins jenkins29 Dec 24 12:21 retry_unstable_failure.txt -rw-rw-r--. 1 jenkins jenkins19 Jul 12 2017 retry_unstable.txt > cat /var/lib/jenkins/rules/retry_any_failure.txt .* The concerning behavior is the following: 00:57:40 Finished Build : #321: [PR-123] of Job : paralleled_executor with status : FAILURE 00:57:40 Scanning failed job
[JIRA] (JENKINS-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Brandon Belcher commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN We've been error-free for a week now after this fix. Thank you! 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-54722) add backlink to gerrit code review to overview page for every build
Title: Message Title ansib updated an issue Jenkins / JENKINS-54722 add backlink to gerrit code review to overview page for every build Change By: ansib Just like the gerrit trigger plugin, it would be great, if the there is a backlink at a Jira the Jenkins overview page for every build to the corresponding gerrit code review.like this!image-2018-11-20-11-27-10-363.png!and this (there is a link to the gerrit review behind the "Triggered by Gerrit" Label!image-2018-11-20-11-27-37-115.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54722) add backlink to gerrit code review to overview page for every build
Title: Message Title ansib updated an issue Jenkins / JENKINS-54722 add backlink to gerrit code review to overview page for every build Change By: ansib Just like the gerrit trigger plugin, it would be great, if the there is a backlink at a Jira the Jenkins overview page for every build to the corresponding gerrit code review.like this!image-2018-11-20-11-27-10-363.png!and this (there is a link to the gerrit review behind the "Triggered by Gerrit" Label!image-2018-11-20-11-27-37-115.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54722) add backlink to gerrit code review to overview page for every build
Title: Message Title ansib updated an issue Jenkins / JENKINS-54722 add backlink to gerrit code review to overview page for every build Change By: ansib Just like the gerrit trigger plugin, it would be great, if there the is a backlink at the Jenkins a Jira overview page for every build to the corresponding gerrit code review.like this!image-2018-11-20-11-27-10-363.png!and this (there is a link to the gerrit review behind the "Triggered by Gerrit" Label!image-2018-11-20-11-27-37-115.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56538) Jenkins declarative pipelines sometimes is skipping "Checkout SCM"
Title: Message Title
Andrius Semionovas updated an issue
Jenkins / JENKINS-56538
Jenkins declarative pipelines sometimes is skipping "Checkout SCM"
Change By:
Andrius Semionovas
Stacktrace:{code:java}java.nio.file.NoSuchFileException: /var/lib/jenkins/workspace/android_master@4/Dockerfile at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214) at java.nio.file.Files.newByteChannel(Files.java:361) at java.nio.file.Files.newByteChannel(Files.java:407) at java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:384) at java.nio.file.Files.newInputStream(Files.java:152) at hudson.FilePath.read(FilePath.java:1974) at org.jenkinsci.plugins.workflow.steps.ReadFileStep$Execution.run(ReadFileStep.java:104) at org.jenkinsci.plugins.workflow.steps.ReadFileStep$Execution.run(ReadFileStep.java:94) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Finished: FAILURE{code}This failure happens randomly only in parallel builds. Builds are launching on the same job. Script:{code:java}builds["Country $country"] = { build job: env.JOB_NAME, parameters: [ string(name: 'COUNTRY', value: country), booleanParam(name: 'APK', value: true), ]}{code} I found "SCM Checkout" was skipped in case of failure. I added two screenshots for the same parallel jobs. {code:java} [Pipeline] Start of Pipeline [Pipeline] nodeRunning node Running on [ Jenkins |https://jenkins.vinted.net/computer/(master)/] in /var/lib/jenkins/workspace/android_master@4 [Pipeline] { [Pipeline] stage [Pipeline] { (Declarative: Agent Setup)[Pipeline] isUnix[Pipeline] readFile[Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // node [Pipeline] stage [Pipeline] { (Declarative: Post Actions) [Pipeline] script [Pipeline] {[Pipeline] } [Pipeline] // script Error when executing always post condition:{code} At the end of the build, I am cleaning everything with:{code:java}cleanWs(){code}The problem appeared for the first time after upgrading to 2.150.2 LT with all plugins (to that date) Also, another stacktrace accompany this error, but I am not sure if it is related:{code:java}Error when executing always post condition: java.lang.NullPointerException: Cannot invoke method startsWith() on null object at org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:91) at
[JIRA] (JENKINS-52396) Integration with Blue Ocean?
Title: Message Title Karl Wirth commented on JENKINS-52396 Re: Integration with Blue Ocean? Hi Drew Waranis. Thanks for your interest in the plugin. I'll make sure the product managers see this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56538) Jenkins declarative pipelines sometimes is skipping "Checkout SCM"
Title: Message Title Andrius Semionovas created an issue Jenkins / JENKINS-56538 Jenkins declarative pipelines sometimes is skipping "Checkout SCM" Issue Type: Bug Assignee: Unassigned Attachments: failing.png, success.png Components: pipeline Created: 2019-03-13 09:49 Environment: Jenkins ver. 2.150.2 LT Pipeline: 2.6 (other related plugins are latest to this day) Labels: pipeline docker scmworkflow Priority: Major Reporter: Andrius Semionovas Stacktrace: java.nio.file.NoSuchFileException: /var/lib/jenkins/workspace/android_master@4/Dockerfile at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214) at java.nio.file.Files.newByteChannel(Files.java:361) at java.nio.file.Files.newByteChannel(Files.java:407) at java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:384) at java.nio.file.Files.newInputStream(Files.java:152) at hudson.FilePath.read(FilePath.java:1974) at
[JIRA] (JENKINS-56537) Gitlab ID could not be found but is set and works
Title: Message Title
Estrada Matthieu updated an issue
Jenkins / JENKINS-56537
Gitlab ID could not be found but is set and works
Change By:
Estrada Matthieu
I've updated my Jenkins installation to 2.150 and also plugins. I've set Gitlab token in Jenkins configuration and connection works without problem when I click on "Test connection" button.When I launch a pipeline Job, repository is correctly pulled but I've the following warning in concole console output:{code:java}Warning: CredentialId "RENO-Gitlab" could not be found.{code}Here is my pipeline code:{code:groovy} checkout([ $class: 'GitSCM',branches: [[name: "origin/dev"]],userRemoteConfigs: [[credentialsId: 'RENO-Gitlab', url: 'git@mygitlab.group/project.git']]]){code}So the Job starts well and works but this warning is displayed.
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-56537) Gitlab ID could not be found but is set and works
Title: Message Title Estrada Matthieu created an issue Jenkins / JENKINS-56537 Gitlab ID could not be found but is set and works Issue Type: Bug Assignee: Unassigned Attachments: Screenshot from 2019-03-13 10-42-15.png Components: credentials-plugin Created: 2019-03-13 09:43 Environment: Jenkins ver. 2.150.3 Credentials Plugin 2.1.18 Labels: plugin Priority: Minor Reporter: Estrada Matthieu I've updated my Jenkins installation to 2.150 and also plugins. I've set Gitlab token in Jenkins configuration and connection works without problem when I click on "Test connection" button. When I launch a pipeline Job, repository is correctly pulled but I've the following warning in concole output: Warning: CredentialId "RENO-Gitlab" could not be found. Here is my pipeline code: checkout([ $class: 'GitSCM', branches: [[name: "origin/dev"]], userRemoteConfigs: [[credentialsId:
[JIRA] (JENKINS-56482) custom name variable seems to not working
Title: Message Title Jie Shen resolved as Won't Fix Jenkins / JENKINS-56482 custom name variable seems to not working Change By: Jie Shen Status: Reopened Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56482) custom name variable seems to not working
Title: Message Title Jie Shen updated JENKINS-56482 Jenkins / JENKINS-56482 custom name variable seems to not working Change By: Jie Shen Status: In Progress Fixed but Unreleased Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56482) custom name variable seems to not working
Title: Message Title Jie Shen updated JENKINS-56482 Jenkins / JENKINS-56482 custom name variable seems to not working Change By: Jie Shen Resolution: Won't Fix Status: Fixed but Unreleased 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56535) Caused: java.io.IOException: Unexpected termination of the channel for Azure Agents
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-56535 Caused: java.io.IOException: Unexpected termination of the channel for Azure Agents Change By: Jie Shen Assignee: Azure DevOps Jie Shen 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-56536) currentBuild.currentResult not set to failed
Title: Message Title Felix Retter created an issue Jenkins / JENKINS-56536 currentBuild.currentResult not set to failed Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2019-03-13 08:37 Environment: Jenkins: 2.168 and 2.167 System related: awt.toolkit sun.awt.windows.WToolkit BUILD_TIMESTAMP 2019-03-13 08:59:17 CET executable-war D:\temp\jenkinsSlave\jenkins.war file.encoding Cp1252 file.encoding.pkg sun.io file.separator \ java.awt.graphicsenv sun.awt.Win32GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.awt.windows.WPrinterJob java.class.path D:\temp\jenkinsSlave\jenkins.war java.class.version 52.0 java.endorsed.dirs C:\Program Files (x86)\Java\jre1.8.0_201\lib\endorsed java.ext.dirs C:\Program Files (x86)\Java\jre1.8.0_201\lib\ext;C:\WINDOWS\Sun\Java\lib\ext java.home C:\Program Files (x86)\Java\jre1.8.0_201 java.library.path c:\program files (x86)\common files\oracle\java\javapath;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;c:\program files (x86)\common files\oracle\java\javapath;c:\program files (x86)\common files\etas\3rdparty4.0\;c:\program files (x86)\vector vflash 3.5\bin\;c:\python27\;c:\python27\scripts;c:\program files (x86)\vector vflash 3.1\bin\;c:\program files (x86)\vector vflash 2.7\bin\;c:\testwell\ctc;c:\programdata\oracle\java\javapath;c:\program files (x86)\intel\icls client\;c:\program files\intel\icls client\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\wbem;C:\WINDOWS\system32\windowspowershell\v1.0\;c:\program files\intel\intel(r) management engine components\dal;c:\program files (x86)\intel\intel(r) management engine components\dal;c:\program files\intel\intel(r) management engine components\ipt;c:\program files (x86)\intel\intel(r) management engine components\ipt;c:\program files\intel\wifi\bin\;c:\program files\common files\intel\wirelesscommon\;c:\program files (x86)\gnu\gnupg\pub;c:\program files (x86)\gitextensions\;d:\work_general\junctions\path_to_mingw\bin;c:\program files\microsoft sql server\110\tools\binn\;c:\program files (x86)\common files\etas\3rdparty1.0;c:\program files\tortoisesvn\bin;c:\program files\git\cmd;c:\program files\tortoisegit\bin;c:\program files\putty\;C:\WINDOWS\system32\openssh\;C:\Program Files (x86)\MATLAB\R2006a\bin;C:\Program Files (x86)\MATLAB\R2006a\bin\win32;D:\work_general\junctions\Silver\bin;D:\Software\python27;C:\Users\fretter\AppData\Local\Microsoft\WindowsApps;D:\Software\apache-ant-1.10.1\bin;D:\work_general\junctions\path_to_mingw\bin;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;;. java.runtime.name Java(TM) SE Runtime
[JIRA] (JENKINS-56535) Caused: java.io.IOException: Unexpected termination of the channel for Azure Agents
Title: Message Title Muhammad Faizan ul haq created an issue Jenkins / JENKINS-56535 Caused: java.io.IOException: Unexpected termination of the channel for Azure Agents Issue Type: Bug Assignee: Azure DevOps Components: azure-vm-agents-plugin Created: 2019-03-13 08:26 Environment: Jenkins 2.138.2 Azure VM Plugin: 0.7.5 Priority: Blocker Reporter: Muhammad Faizan ul haq We are experiencing this problem quite extensively only on our autoscaled agents. The agent get disconnected during the execution of a job and gets deleted in azure as well. This gives us no time to login to VM and see the agent logs. The job continues to hold the agent even though it is "disconnected" in jenkins and actual VM is already deleted. The Jenkins Agent logs shows: Connection was broken java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2681) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3156) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:862) at java.io.ObjectInputStream.(ObjectInputStream.java:358) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49) at hudson.remoting.Command.readFrom(Command.java:140) at hudson.remoting.Command.readFrom(Command.java:126) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63) Caused: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77) and we looked at logs on jenkins server and found this: 2019-03-12T13:04:28.614306215Z INFO: AzureVMCloud:
[JIRA] (JENKINS-49301) The Move action does not move job config history also
Title: Message Title Jochen A. Fürbacher started work on JENKINS-49301 Change By: Jochen A. Fürbacher 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-52396) Integration with Blue Ocean?
Title: Message Title Drew Waranis commented on JENKINS-52396 Re: Integration with Blue Ocean? Also commenting to keep this fresh. We also need Perforce support in Blue Ocean. 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-56509) Retrieving a username/password credential
Title: Message Title Carl Bourne closed an issue as Not A Defect Asked question in Jenkins mailing lists. Jenkins / JENKINS-56509 Retrieving a username/password credential Change By: Carl Bourne 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Fidal Castro Arivalagan edited a comment on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file We too noticed the same issue with Windows slaves under Jenkins version 2.150.3. Workaround mentioned by Aaron Nelson wasn't working because the next git clone identifies ".git" directory as suspicious.I am able to replicate this issue with "Freestyle" job with below configurations. # SCM - Git checkout # Build Environment - Delete workspace before build starts # Build Trigger - For every 15 mins ( H/15 * * * * ( # Build - This is not important for this testing.As Bart explained, we are not able to delete the workspace/directory manually as well. Only way is to restart the Jenkins slave process.Workaround:Use "Delete workspace when build is done" in post build section apart of Build Environment. But this doesn't suit some use cases though. Why do Jenkins process use the workspace even after the build completes ? I see especially all these cases are throwing error with .git/objects/pack/ is in use 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-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Fidal Castro Arivalagan commented on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file We too noticed the same issue with Windows slaves under Jenkins version 2.150.3. Workaround mentioned by Aaron Nelson wasn't working because the next git clone identifies ".git" directory as suspicious. I am able to replicate this issue with "Freestyle" job with below configurations. SCM - Git checkout Build Environment - Delete workspace before build starts Build Trigger - For every 15 mins ( H/15 * * * * ( Build - This is not important for this testing. As Bart explained, we are not able to delete the workspace/directory manually as well. Only way is to restart the Jenkins slave process. Workaround: Use "Delete workspace when build is done" in post build section apart of Build Environment. But this doesn't suit some use cases though. Why do Jenkins process use the workspace even after the build completes ? I see especially all these cases are throwing error with .git/objects/pack/ is in use 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-56509) Retrieving a username/password credential
Title: Message Title Oleg Nenashev commented on JENKINS-56509 Re: Retrieving a username/password credential It is better to ask such questions in the DEveloper mailing list. https://jenkins.io/mailing-lists/ 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-56525) Add Filters to Assign Roles page
Title: Message Title Oleg Nenashev commented on JENKINS-56525 Re: Add Filters to Assign Roles page Kevin Delord yes, it would be an interesting feature. Pull requests will be definitely reviewed and integreated for it We are also trying to have a GSoC project for Role Strategy user experience: https://jenkins.io/projects/gsoc/2019/project-ideas/role-strategy-ux/ . Maybe somebody of the students will be also interested to implement it if you do not have time for it in short-term. 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-56525) Add Filters to Assign Roles page
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-56525 Add Filters to Assign Roles page Change By: Oleg Nenashev Labels: user-experience 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-56525) Add Filters to Assign Roles page
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-56525 Add Filters to Assign Roles page Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-56527) Add support for JCasC
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-56527 Add support for JCasC Change By: Oleg Nenashev Labels: jcasc-compatibility 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-50331) JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-50331 Re: JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen There are some clue about how to fix this in https://social.msdn.microsoft.com/Forums/vstudio/en-US/2ace3851-8e1c-4aee-8e2d-192b0810213a/tfs-sdk-leak?forum=tee 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-56534) NUnit Plugin complains (falsely) about clocks out of sync
Title: Message Title Carlos Garcia created an issue Jenkins / JENKINS-56534 NUnit Plugin complains (falsely) about clocks out of sync Issue Type: Bug Assignee: Unassigned Attachments: in_sync.png Components: nunit-plugin Created: 2019-03-13 06:39 Environment: Jenkins master installed on CentOS. Agents are running on several Virtual Machines (Windows) on a Ubuntu Linux host Priority: Major Reporter: Carlos Garcia Since few days, nunit-plugin started to complain about clocks being out of sync after the test report is generated correctly. In fact, initially it was right, clocks drifted about 4 or 5 seconds and I took the measures to avoid that (they syncronize with an NTP server every hour, just to assure the synchronization throghout the day). However, nunit-plugin still complains, and now all the clocks are synchronized. This is the exact message I get: Recording NUnit tests results ERROR: Step ‘Publish NUnit test result report’ failed: Clock on this slave is out of sync with the master, and therefore I can't figure out what test results are new and what are old. Please keep the slave clock in sync with the master. There are two things that can be wrong here: The message, since it is basically false (clocks are NOT out of sync) The way this plugin checks the synchronization between the clocks Also, as a side note, in my
[JIRA] (JENKINS-56533) SCM sync status logs appear in jenkins pages
Title: Message Title Hemanth Kumar created an issue Jenkins / JENKINS-56533 SCM sync status logs appear in jenkins pages Issue Type: Bug Assignee: Craig Rodrigues Attachments: jenkins_error.PNG Components: scm-sync-configuration-plugin Created: 2019-03-13 06:37 Environment: prod Priority: Major Reporter: Hemanth Kumar Hi Team, We found scm sync logs coming in jenkins UI in all tabs and even manage plugins shows the logs, so even plugin updates not able to view. Add Comment
