[JIRA] (JENKINS-36997) sshAgent {} inside docker.image().inside {} does not work with long project name
Title: Message Title
Jesse Glick updated JENKINS-36997
Jenkins / JENKINS-36997
sshAgent {} inside docker.image().inside {} does not work with long project name
Change By:
Jesse Glick
Status:
In Review Resolved
Resolution:
Fixed
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40908) GitSCMSource: support custom remote and refspec
Title: Message Title Mark Waite commented on JENKINS-40908 Re: GitSCMSource: support custom remote and refspec No offense was taken from your decision to merge the pull request. I don't see any need to remove you from the committers or anything drastic like that. I was very pleased to see all the upvotes, since that shows people were thinking about the pull request. I didn't recognize any of the users who were upvoting the pull request, nor did I see any comments that any of the upvotes had tested the proposed pull request, so I wasn't sure how much credence I should place on those upvotes. Are you interested in assisting further with review of git plugin pull requests? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41940) Pipeline stages should be configurable with a weight property, corresponding to the number of executors the stage occupies
Title: Message Title Jesse Glick assigned an issue to Unassigned stage is only for display. I think you are talking about node. Could perhaps be supported somehow in this plugin, TBD. I think the approach is misconceived, though. Better to have a QueueTaskDispatcher which blocks off executor slots dynamically based on measured system load or something. Jenkins / JENKINS-41940 Pipeline stages should be configurable with a weight property, corresponding to the number of executors the stage occupies Change By: Jesse Glick Component/s: heavy-job-plugin Component/s: pipeline-stage-step-plugin Labels: executor pipeline stage weight Assignee: Jesse Glick Add Comment This message was sent by Atlassian
[JIRA] (JENKINS-41339) Environment variables referencing other variables broken
Title: Message Title Jesse Glick commented on JENKINS-41339 Re: Environment variables referencing other variables broken how would you set PATH to something like Fix your launcher, ~/.profile, etc. Avoid doing this from Jenkins. The fix was released in workflow-durable-task-step. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42069) Upgrade plugins without restart
Title: Message Title Daniel Beck resolved as Duplicate There should be an issue tracking this request, just cannot find it right now. I doubt this is possible near term. Jenkins / JENKINS-42069 Upgrade plugins without restart Change By: Daniel Beck Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For
[JIRA] (JENKINS-26677) Blacklist certain classes from loading in slaves
Title: Message Title Jesse Glick commented on JENKINS-26677 Re: Blacklist certain classes from loading in slaves No, this is unrelated. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41926) 100% CPU after update
Title: Message Title Daniel Beck resolved as Incomplete It's unclear how the various parts of this report are related. The thread dump also does not look like extreme activity. I recommend you ask for troubleshooting advice on the jenkinsci-users mailing list. Jenkins / JENKINS-41926 100% CPU after update Change By: Daniel Beck Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-41958) Append node not working when adding TFS to MultiScm node
Title: Message Title
Daniel Spilker commented on JENKINS-41958
Re: Append node not working when adding TFS to MultiScm node
I'm not sure why it's not working as expected, probably because of the attribute. But you do not need to use the << operator in this case. You can add sub elements by using nested blocks. Your example generates a second scm element and does not modify the existing . That may cause problems. I suggest to use an empty multiscm block that replacecs the existing scm element and then add the TFS configs.
freeStyleJob('tfs-multi-scm') {
multiscm {}
configure {
it / scm / scms {
'hudson.plugins.tfs.TeamFoundationServerScm' {
serverUrl('http://tfs:8080/tfs/MyProduct')
projectPath('$/Branch1')
cloakedPaths()
localPath('branch1')
workspaceName('Jenkins_${COMPUTERNAME}_${JOB_NAME}_Branch1')
credentialsConfigurer(class: 'hudson.plugins.tfs.model.AutomaticCredentialsConfigurer')
useUpdate('false')
}
'hudson.plugins.tfs.TeamFoundationServerScm' {
serverUrl('http://tfs:8080/tfs/MyOtherProduct')
projectPath('$/Branch2')
cloakedPaths()
localPath('branch2')
workspaceName('Jenkins_${COMPUTERNAME}_${JOB_NAME}_Branch2')
credentialsConfigurer(class: 'hudson.plugins.tfs.model.AutomaticCredentialsConfigurer')
useUpdate('false')
}
}
}
}
But this also works:
freeStyleJob('tfs-multi-scm') {
multiscm {}
configure {
it / scm / scms << 'hudson.plugins.tfs.TeamFoundationServerScm' {
serverUrl('http://tfs:8080/tfs/MyProduct')
projectPath('$/Branch1')
cloakedPaths()
localPath('branch1')
workspaceName('Jenkins_${COMPUTERNAME}_${JOB_NAME}_Branch1')
credentialsConfigurer(class: 'hudson.plugins.tfs.model.AutomaticCredentialsConfigurer')
useUpdate('false')
}
it / scm / scms << 'hudson.plugins.tfs.TeamFoundationServerScm' {
serverUrl('http://tfs:8080/tfs/MyOtherProduct')
projectPath('$/Branch2')
cloakedPaths()
localPath('branch2')
workspaceName('Jenkins_${COMPUTERNAME}_${JOB_NAME}_Branch2')
credentialsConfigurer(class: 'hudson.plugins.tfs.model.AutomaticCredentialsConfigurer')
useUpdate('false')
}
}
}
You can use the mailing list or Stack Overflow for syntax questions.
[JIRA] (JENKINS-42076) Manual workspace root reset on every sync
Title: Message Title Randy Simat created an issue Jenkins / JENKINS-42076 Manual workspace root reset on every sync Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2017/Feb/15 8:10 PM Environment: Jenkins 2.46 with P4 Plugin 1.4.14 Priority: Critical Reporter: Randy Simat It appears that all manual workspaces have their root directories reset with each sync. I have a Pipeline job read from a source controlled Jenkinsfile that references a global library resulting in 3 different clients. In each of them I am seeing the client root continually reset. Pipeline job client: jenkins-master-1.0.0-AppName Client root is set first to the proper directory = $JENKINS_HOME/workspace/JobName Client root is finally set to just $JENKINS_HOME The same behavior is exhibited in: Pipeline Jenkinsfile client: jenkins-master-1.0.0-AppName-Jenkinsfile Global library client: jenkins-master-1.0.0-Library This has resulted in hundreds or thousands of unneeded specs in the spec depot and also restricts the ability to run manual p4 commands using the “sh” build step
[JIRA] (JENKINS-41773) Copy Artifact missing dependency on Run Selector
Title: Message Title Christopher Head updated an issue Jenkins / JENKINS-41773 Copy Artifact missing dependency on Run Selector Change By: Christopher Head Environment: openjdk 1.8.0_121Jenkins 2. 45 46 Copy Artifact 1.38.1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41909) Check updates failure: CertificateExpiredException
Title: Message Title Daniel Beck commented on JENKINS-41909 Re: Check updates failure: CertificateExpiredException What mirror are you hitting? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41773) Copy Artifact missing dependency on Run Selector
Title: Message Title Christopher Head updated an issue Jenkins / JENKINS-41773 Copy Artifact missing dependency on Run Selector Change By: Christopher Head Until very recently, I never had Run Selector installed, and Copy Artifact worked just fine. Today, I updated a bunch of plugins (especially the SCM API 2 stuff) and Jenkins core, and suddenly Copy Artifact failed to initalize with an NPE:java.lang.NullPointerException at hudson.plugins.copyartifact.BuildSelectorParameter.initAliases(BuildSelectorParameter.java:156) at hudson.plugins.copyartifact.CopyArtifactPlugin.postInitialize(CopyArtifactPlugin.java:35) at hudson.PluginManager$2$1$2.run(PluginManager.java:543) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:1064) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) 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)Installing the Run Selector plugin looked like it fixed this problem. I never needed that plugin before, and Copy Artifact doesn’t have a dependency on it. There was no mention made in any release notes that I would need to add Run Selector, either. It looks now, however, like this Add Comment This message was sent by Atlassian
[JIRA] (JENKINS-41773) Copy Artifact sometimes crashes on startup
Title: Message Title Christopher Head updated an issue Jenkins / JENKINS-41773 Copy Artifact sometimes crashes on startup Change By: Christopher Head Summary: Copy Artifact missing dependency sometimes crashes on Run Selector startup Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41836) Out of memory at "exit 0" in build on Windows with IBM JVM
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-41836 Out of memory at "exit 0" in build on Windows with IBM JVM Change By: Daniel Beck Labels: exception java-ibm outofmemoryerror slave slave-agent windows Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42059) JDL Dropbox displays dropdown in wrong position on small window
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42059 JDL Dropbox displays dropdown in wrong position on small window Change By: James Dumay Sprint: panthalassa Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42064) UI doesn't show all errors
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42064 UI doesn't show all errors Change By: James Dumay Sprint: iapetus Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42064) UI doesn't show all errors
Title: Message Title James Dumay assigned an issue to Vivek Pandey Vivek Pandey we may want to cover this use case in the error step reporting. Oleg Korsak would you be able to provide a small Jenkinsfile that reproduces a similar error? Jenkins / JENKINS-42064 UI doesn't show all errors Change By: James Dumay Assignee: Vivek Pandey Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41958) Append node not working when adding TFS to MultiScm node
Title: Message Title Petrik van der Velde commented on JENKINS-41958 Re: Append node not working when adding TFS to MultiScm node Ok thanks for that. I will try those options. And next time I'll post on Stack Overflow. Sorry for the hassle. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41678) Jacoco plugin 2.1.0 ignores excludes patterns
Title: Message Title Jeremy Brown commented on JENKINS-41678 Re: Jacoco plugin 2.1.0 ignores excludes patterns Any advice on this one? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42035) Blue Ocean - Button to go between classic and blue ocean view.
Title: Message Title James Dumay resolved as Duplicate Thanks Mishal - this is on schedule to complete soon as JENKINS-38751. Jenkins / JENKINS-42035 Blue Ocean - Button to go between classic and blue ocean view. Change By: James Dumay Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options,
[JIRA] (JENKINS-41836) Out of memory at "exit 0" in build on Windows with IBM JVM
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-41836 Out of memory at "exit 0" in build on Windows with IBM JVM Change By: Daniel Beck Labels: exception java-ibm outofmemoryerror slave slave-agent windows winp Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42040) Rundetails duration counter is not reset on rerun
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42040 Rundetails duration counter is not reset on rerun Change By: James Dumay Sprint: panthalassa Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41335) Allow variables and functions to be defined within pipeline to be used in any stage
Title: Message Title R. Tyler Croy commented on JENKINS-41335 Re: Allow variables and functions to be defined within pipeline to be used in any stage The primary use-case that Liam Newman points out here, as I understand it, is not to add a bunch of scripting and variable silliness into a Declarative Jenkinsfile. But rather, there's no "middle-ground" between Declarative right now and Shared Libraries. Some of the folks at Mozilla have used the "loophole" which currently exists, and should be closed, to experiment with shared library ideas inside the Jenkinsfile. I think a methods directive would be helpful to bridge the gap betwixt a puritanical Declarative Pipeline and what should ultimately live in a Shared Library. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41225) durable-task 1.13 is failing with remote Windows accessed through Cygwin sshd.
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-41225 durable-task 1.13 is failing with remote Windows accessed through Cygwin sshd. Change By: Jesse Glick Labels: windows Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42038) Blue Ocean - Views/Folders to organizes jobs
Title: Message Title James Dumay resolved as Duplicate Thanks Mishal - this is a duplicate of JENKINS-39343. Please watch and vote for it instead. Jenkins / JENKINS-42038 Blue Ocean - Views/Folders to organizes jobs Change By: James Dumay Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more
[JIRA] (JENKINS-42076) Manual workspace root reset on every sync
Title: Message Title Randy Simat commented on JENKINS-42076 Re: Manual workspace root reset on every sync I've attached a screenshot depicting the history of the Jenkinsfile client. I have made no changes to the setup of the client itself - these were all done automatically. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41225) durable-task 1.13 is failing with remote Windows accessed through Cygwin sshd.
Title: Message Title Jesse Glick started work on JENKINS-41225 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41624) deadlock
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-41624 deadlock Change By: Daniel Beck Component/s: project-inheritance-plugin Component/s: other Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41631) Use requireUpperBoundDeps in plugin POM
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-41631 Use requireUpperBoundDeps in plugin POM Change By: Daniel Beck Component/s: plugin-pom Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41396) Declarative: Add method definition section to root pipeline block
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-41396 Declarative: Add method definition section to root pipeline block Change By: Liam Newman Summary: Declarative: Add script method definition section to root pipeline block Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42077) deleteDir() fails when files are readonly
Title: Message Title Michael Rose created an issue Jenkins / JENKINS-42077 deleteDir() fails when files are readonly Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2017/Feb/15 8:54 PM Priority: Minor Reporter: Michael Rose I am getting the following exception and I believe this is happening b/c deleteDir() is unable to delete read-only files: java.io.IOException: remote file operation failed: /jenkins/workspace/reviews/scm/build_tmp_stash at hudson.remoting.Channel@37459a74:brhel7ag: java.io.IOException: Failed to extract input stream at hudson.FilePath.act(FilePath.java:986) at hudson.FilePath.act(FilePath.java:968) at hudson.FilePath.untarFrom(FilePath.java:718) at org.jenkinsci.plugins.workflow.flow.StashManager.unstash(StashManager.java:114) at org.jenkinsci.plugins.workflow.support.steps.stash.UnstashStep$Execution.run(UnstashStep.java:64) at org.jenkinsci.plugins.workflow.support.steps.stash.UnstashStep$Execution.run(UnstashStep.java:54) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:49) at hudson.security.ACL.impersonate(ACL.java:213) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.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) Caused by: java.io.IOException: Failed to extract input stream at hudson.FilePath.readFromTar(FilePath.java:2300) at hudson.FilePath.access$400(FilePath.java:190) at hudson.FilePath$10.invoke(FilePath.java:720) at
[JIRA] (JENKINS-33024) XmlSlurper.parseText() not whitelisted
Title: Message Title Jesse Glick commented on JENKINS-33024 Re: XmlSlurper.parseText() not whitelisted Yes, things like XmlSlurper should not be used. You may use dedicated Pipeline steps, or (preferably) external tools run inside node. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41977) Login page is missing charset.
Title: Message Title Daniel Beck resolved as Not A Defect Jenkins / JENKINS-41977 Login page is missing charset. Change By: Daniel Beck Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37538) classloading issue with xerces lib
Title: Message Title Jesse Glick commented on JENKINS-37538 Re: classloading issue with xerces lib (a) Class loading hell; (b) dynamic method invocation hell. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37446) StringIndexOutOfBoundsException when editing Custom Configuration field
Title: Message Title Jesse Glick commented on JENKINS-37446 Re: StringIndexOutOfBoundsException when editing Custom Configuration field I guess you have to attach a *.diff file. Does feel like the previous millenium. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41335) Allow variables and functions to be defined within pipeline to be used in any stage
Title: Message Title Robby Pocase commented on JENKINS-41335 Re: Allow variables and functions to be defined within pipeline to be used in any stage What Liam Newman Jason Davis said. The conveniences of declarative make dropping into script from time to time fine. There will always be a need programmatic logic. Direct access in declarative would be huge for maintainability. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41527) "console" CLI command does not work with Pipeline projects
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-41527 "console" CLI command does not work with Pipeline projects Change By: Jesse Glick Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41527) "console" CLI command does not work with Pipeline projects
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-41527 "console" CLI command does not work with Pipeline projects Change By: Jesse Glick Labels: cli pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21249) Update Groovy
Title: Message Title Jesse Glick resolved as Fixed Jenkins / JENKINS-21249 Update Groovy Change By: Jesse Glick Status: Reopened Resolved Assignee: Kohsuke Kawaguchi Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41864) Illegal dates for cron entry cause 100% cpu
Title: Message Title Daniel Beck assigned an issue to Daniel Beck Jenkins / JENKINS-41864 Illegal dates for cron entry cause 100% cpu Change By: Daniel Beck Assignee: Daniel Beck Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41773) Copy Artifact sometimes crashes on startup
Title: Message Title Christopher Head updated an issue Jenkins / JENKINS-41773 Copy Artifact sometimes crashes on startup Change By: Christopher Head Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-41662 Proceed button fails Change By: James Dumay Assignee: James Dumay Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41662 Proceed button fails Change By: James Dumay It seems under some conditions the proceed button for input does not work and the UI does not automatically update to reflect this state. There needs to be some manual testing around inputs to check if we are handling errors correctly and that the state of the UI is handled appropriately in error cases.It would also be worth ensuring that under successful conditions that the UI updates correctly on proceeding with input.*Original request* Recently our inputs (with checkboxes) stopped to work. Pressing "Proceed" button does nothing, there is an error response:Error processing Input Submit request. This Run instance does not have an Input with an id of 'D875578491b444dd8bc3f26a12399d2a'.This occurs in ~90%, some success still may exist ) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-41888) the Jenkins home page take a long time to loading
Title: Message Title Daniel Beck resolved as Incomplete This is not a bug report. All the relevant information is missing. Please note that this is not a support site, but an issue tracker. Jenkins / JENKINS-41888 the Jenkins home page take a long time to loading Change By: Daniel Beck Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-41773) Copy Artifact sometimes crashes on startup
Title: Message Title Christopher Head updated an issue Jenkins / JENKINS-41773 Copy Artifact sometimes crashes on startup Change By: Christopher Head Until very recently, I never had Run Selector installed, and Copy Artifact worked just fine. Today, I updated a bunch of plugins (especially the SCM API 2 stuff) and Jenkins core, and suddenly Copy Artifact failed to initalize with an NPE:java.lang.NullPointerException at hudson.plugins.copyartifact.BuildSelectorParameter.initAliases(BuildSelectorParameter.java:156) at hudson.plugins.copyartifact.CopyArtifactPlugin.postInitialize(CopyArtifactPlugin.java:35) at hudson.PluginManager$2$1$2.run(PluginManager.java:543) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:1064) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) 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) Installing I initially thought that installing the Run Selector plugin looked like it fixed this problem . I , despite never needed that plugin needing it before , and Copy Artifact doesn’t have there not being a dependency on it . There was no mention made in any release notes that However, I would need to add have now seen the crash return one time on startup, even with Run Selector installed , either and then go away after another restart of Jenkins . It looks now, however, like this So it seems to be nondeterministic and happen during some boots but not others. Add Comment
[JIRA] (JENKINS-41663) UI tends to not update (paused for input?)
Title: Message Title James Dumay resolved as Duplicate Merging this into JENKINS-41662. Jenkins / JENKINS-41663 UI tends to not update (paused for input?) Change By: James Dumay Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42076) Manual workspace root reset on every sync
Title: Message Title Randy Simat updated an issue Jenkins / JENKINS-42076 Manual workspace root reset on every sync Change By: Randy Simat It appears that all manual workspaces have their root directories reset with each sync. I have a Pipeline job read from a source controlled Jenkinsfile that references a global library resulting in 3 different clients. In each of them I am seeing the client root continually reset. Pipeline job client: jenkins-master-1.0.0-AppName 1. Client root is set first to the proper directory = $JENKINS_HOME/workspace/JobName2. Client root is finally set to just $JENKINS_HOMEThe same behavior is exhibited in:Pipeline Jenkinsfile client: jenkins-master-1.0.0-AppName-JenkinsfileGlobal library client: jenkins-master-1.0.0-LibraryThis has resulted in hundreds or thousands of unneeded specs in the spec depot and also restricts the ability to run manual p4 commands using the “sh” build step Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this
[JIRA] (JENKINS-42070) Input buttons require page refresh
Title: Message Title James Dumay resolved as Duplicate Travis camechis thanks for reporting this issue. We had a similar report to this as part of JENKINS-41662 and it is something we will investigate shortly. Jenkins / JENKINS-42070 Input buttons require page refresh Change By: James Dumay Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-42076) Manual workspace root reset on every sync
Title: Message Title Randy Simat updated an issue Jenkins / JENKINS-42076 Manual workspace root reset on every sync Change By: Randy Simat It appears that all manual workspaces have their root directories reset with each sync. I have a Pipeline job read from a source controlled Jenkinsfile that references a global library resulting in 3 different clients. In each of them I am seeing the client root continually reset.Pipeline job client: jenkins-master-1.0.0-AppName - 1. Client root is set first to the proper directory = $JENKINS_HOME/workspace/JobName - 2. Client root is finally set to just $JENKINS_HOME The same behavior is exhibited in:Pipeline Jenkinsfile client: jenkins-master-1.0.0-AppName-JenkinsfileGlobal library client: jenkins-master-1.0.0-LibraryThis has resulted in hundreds or thousands of unneeded specs in the spec depot and also restricts the ability to run manual p4 commands using the “sh” build step Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received
[JIRA] (JENKINS-41941) Add credentials data to API for "permissions"
Title: Message Title Vivek Pandey started work on JENKINS-41941 Change By: Vivek Pandey Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-41425 Refreshing page with / in job name results in 404 Change By: James Dumay Assignee: Vivek Pandey Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35864) Step section in log sticks to result header when scrolling
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35864 Step section in log sticks to result header when scrolling Change By: James Dumay Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42055) Nested scrolling window for logs in stage steps instead of extending whole page
Title: Message Title James Dumay resolved as Duplicate Chris Wright our solution here is to make the "step header" stick to the top of the window as the log grows so it is only a quick mouse away to close. Take a look at JENKINS-35864 and let me know if this sounds good to you. Jenkins / JENKINS-42055 Nested scrolling window for logs in stage steps instead of extending whole page Change By: James Dumay Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-42076) Manual workspace root reset on every sync
Title: Message Title Randy Simat updated an issue Jenkins / JENKINS-42076 Manual workspace root reset on every sync Change By: Randy Simat Attachment: JenkinsfileExample.PNG Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35864) Step section in log sticks to result header when scrolling
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35864 Step section in log sticks to result header when scrolling Change By: James Dumay Sprint: pacific, post- release candidate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39343) Persistent search/overviews/filtered views
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39343 Persistent search/overviews/filtered views Change By: James Dumay Sprint: post-release Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41757) BUILD_NOW_TEXT is not being applied when the job is parameterized
Title: Message Title Daniel Beck updated JENKINS-41757 Jenkins / JENKINS-41757 BUILD_NOW_TEXT is not being applied when the job is parameterized Change By: Daniel Beck Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42076) Manual workspace root reset on every sync
Title: Message Title Randy Simat updated an issue Jenkins / JENKINS-42076 Manual workspace root reset on every sync Change By: Randy Simat It appears that all manual workspaces have their root directories reset with each sync. I have a Pipeline job read from a source controlled Jenkinsfile that references a global library resulting in 3 different clients. In each of them I am seeing the client root continually reset.Pipeline job client: jenkins-master-1.0.0-AppName1. Client root is set first to the proper directory = $JENKINS_HOME/workspace/JobName2. Client root is finally set to just $JENKINS_HOMEThe same behavior is exhibited in:Pipeline Jenkinsfile client: jenkins-master-1.0.0-AppName-JenkinsfileGlobal library client: jenkins-master-1.0.0-LibraryThis has resulted in hundreds or thousands of unneeded specs in the spec depot and also restricts the ability to run manual p4 commands using the “sh” build step Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this
[JIRA] (JENKINS-39462) Saved searches/views
Title: Message Title James Dumay resolved as Duplicate Consolidating this ticket into JENKINS-39343 Jenkins / JENKINS-39462 Saved searches/views Change By: James Dumay Status: Reopened Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41727) Upgrading/downgrading Jenkins needs to invalidate update site cache
Title: Message Title Daniel Beck assigned an issue to Daniel Beck Jenkins / JENKINS-41727 Upgrading/downgrading Jenkins needs to invalidate update site cache Change By: Daniel Beck Assignee: Daniel Beck Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41225) durable-task 1.13 is failing with remote Windows accessed through Cygwin sshd.
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-41225 durable-task 1.13 is failing with remote Windows accessed through Cygwin sshd. Change By: Jesse Glick Labels: regression windows Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41727) Upgrading/downgrading Jenkins needs to invalidate update site cache
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-41727 Upgrading/downgrading Jenkins needs to invalidate update site cache Change By: Daniel Beck Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42059) JDL Dropbox displays dropdown in wrong position for input screen
Title: Message Title Cliff Meyers updated an issue Jenkins / JENKINS-42059 JDL Dropbox displays dropdown in wrong position for input screen Change By: Cliff Meyers Summary: JDL Dropbox displays dropdown in wrong position on small window for input screen Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41697) StackOverflowError parsing Maven POM
Title: Message Title Daniel Beck commented on JENKINS-41697 Re: StackOverflowError parsing Maven POM until I updated Jenkins to 2.32.1 Doesn't mean anything unless you mention what version you were running before. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41225) durable-task 1.13 is failing with remote Windows accessed through Cygwin sshd.
Title: Message Title Jesse Glick assigned an issue to Ad Jenkins / JENKINS-41225 durable-task 1.13 is failing with remote Windows accessed through Cygwin sshd. Change By: Jesse Glick Assignee: Jesse Glick Ad Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41225) durable-task 1.13 is failing with remote Windows accessed through Cygwin sshd.
Title: Message Title Jesse Glick updated JENKINS-41225 Jenkins / JENKINS-41225 durable-task 1.13 is failing with remote Windows accessed through Cygwin sshd. Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39343) Persistent search/overviews/filtered views
Title: Message Title mishal shah commented on JENKINS-39343 Re: Persistent search/overviews/filtered views This would be really useful, when Jenkins has 20+ jobs. It would be great if this could be priorities. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41335) Allow variables and functions to be defined within pipeline to be used in any stage
Title: Message Title Liam Newman commented on JENKINS-41335 Re: Allow variables and functions to be defined within pipeline to be used in any stage R. Tyler Croy Yes, that. That is want See JENKINS-41396 is about. Jason DavisRobby Pocase Would method definitions be enough, do you think? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31899) plugin Dashboard View does not recognizes job names from mutli-branch-project-plugin
Title: Message Title veniamin medvedev edited a comment on JENKINS-31899 Re: plugin Dashboard View does not recognizes job names from mutli-branch-project-plugin Is there any wa way of tweaking the following codeTopLevelItem item = Jenkins.getInstance().getItem(jobName);in order to find proper name of Job nested to some Folder? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40131) "Re-run" button text needs to be translated
Title: Message Title Tom FENNELLY updated JENKINS-40131 Jenkins / JENKINS-40131 "Re-run" button text needs to be translated Change By: Tom FENNELLY Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41335) Allow variables and functions to be defined within pipeline to be used in any stage
Title: Message Title Jesse Glick commented on JENKINS-41335 Re: Allow variables and functions to be defined within pipeline to be used in any stage I think they are both a bad idea, but this is a worse one. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40606) Add ability to perform actions on branch removal
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-40606 Add ability to perform actions on branch removal could I use it in Jenkinsfile? No, because this is outside a build context. Change By: Jesse Glick Component/s: plugin-proposals Component/s: workflow-multibranch-plugin Labels: multibranch Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Stephen Connolly resolved as Fixed I claim fixed in 2.1.0 release Jenkins / JENKINS-36029 multibranch-job deleted when bitbucket communication fails Change By: Stephen Connolly Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-41976) Add support for Add-on generated HipChat v2 tokens
Title: Message Title Ben Middleton commented on JENKINS-41976 Re: Add support for Add-on generated HipChat v2 tokens OK - thanks for investigating. That makes sense. I'll see if I can create a BYO integration for this and report back. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41189) [Pipeline] Some non-CPS transformable code will not throw errors
Title: Message Title Jesse Glick commented on JENKINS-41189 Re: [Pipeline] Some non-CPS transformable code will not throw errors What is the reason for this check not occurring in non-sandbox mode? Because that is where the current implementation lies; there is no such hook without a sandbox. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39949) Pipeline script from SCM not working for TFS
Title: Message Title Robb Schiefer updated an issue Jenkins / JENKINS-39949 Pipeline script from SCM not working for TFS Change By: Robb Schiefer Component/s: tfs-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40474) Failed to change to remote directory after updating from 1.0.5 to 1.1.2
Title: Message Title René de Groot resolved as Fixed Jenkins / JENKINS-40474 Failed to change to remote directory after updating from 1.0.5 to 1.1.2 Change By: René de Groot Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41335) Allow variables and functions to be defined within pipeline to be used in any stage
Title: Message Title
Jason Davis commented on JENKINS-41335
Re: Allow variables and functions to be defined within pipeline to be used in any stage
I agree with Liam Newman (I think ). My two cents, Declarative pipelining makes a ton of sense and it feels like a more natural model than Scripted pipelining. In declarative land, though, to get the job done, I still end up needing if-then logic, to assign variables (as per this JIRA issue), using shared functions in groovy scripts – all those things need to be wrapped with script {. Really unifying the two methods back into one official "way" to pipeline, would be great for pipeline development. It'll reduce the maintenance burden on Jenkins jobs down the road too.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36121) Github Branch Source plugin trips api rate limit
Title: Message Title Paul Chubatyy commented on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit Meanwhile I've got a very hacky workaround for this issue with a pipeline script that will check github organization and create the multibranch projects for all the repositories without doing any checks. See this gist for details. Be aware that it uses Jenkins Job DSL plugin, so you will have to install it before running. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42074) Test connection should also validate check active credentials
Title: Message Title René de Groot created an issue Jenkins / JENKINS-42074 Test connection should also validate check active credentials Issue Type: New Feature Assignee: René de Groot Components: publish-over-dropbox-plugin Created: 2017/Feb/15 7:53 PM Priority: Minor Reporter: René de Groot Call /users/get_current_account to check active credentials. Check if the credentials are of the pre-1.1.1 plugin version. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37515) pipeline input blocks the executor
Title: Message Title Jesse Glick resolved as Not A Defect AFAIK that syntax in Declarative would work, but if it does not, that would be a bug report for pipeline-model-definition-plugin. Jenkins / JENKINS-37515 pipeline input blocks the executor Change By: Jesse Glick Status: Reopened Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-42071) org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified method java.lang.Boolean call org.jenkinsci.plugins.workflow.cps.CpsClosure2
Title: Message Title
Calista Bruce updated an issue
Jenkins / JENKINS-42071
org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified method java.lang.Boolean call org.jenkinsci.plugins.workflow.cps.CpsClosure2
Change By:
Calista Bruce
Running attached pipeline job and it failed when running either OSB or ADF paths. Works successfully running SOABPM. {color:red}*The following is the failing output.*{color}Started by user svcsnjenkins[Pipeline] node Running on master in /opt/jenkins/jobs/ServiceNow-FMW-Pipeline/workspace[Pipeline] { [Pipeline] echo The build value is UAT for OSB[Pipeline] echo Deployment failed org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified method java.lang.Boolean call org.jenkinsci.plugins.workflow.cps.CpsClosure2[Pipeline] echo Setting deployment status to Deploy Failed for task 599bba734fb832003354fc828110c793[Pipeline] echo finally[Pipeline] step [WS-CLEANUP] Deleting project workspace...[WS-CLEANUP] done[Pipeline] echo Service Now Write Backs initiating[Pipeline] echo Updating RM Task record : {u_state: 105}[Pipeline] httpRequest HttpMode: PUTURL: https://xx.service-now.com/api/now/table/rm_task/599bba734fb832003354fc828110c793Content-type: application/jsonAccept: application/jsonUsing authentication: ServiceNowSending request to url: https://xxx.service-now.com/api/now/table/rm_task/599bba734fb832003354fc828110c793Response Code: HTTP/1.1 200 OKSuccess code from [100‥399][Pipeline] echo Creating Deployment Log Task record : {u_deployment_object: 'NBL_SORT',u_deployment_status: 'Deploy Failed' ,u_deployment_target: 'UAT',u_deployed_by: 'brucec',u_deployment_message: 'org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified method java.lang.Boolean call org.jenkinsci.plugins.workflow.cps.CpsClosure2', u_task_number: 'RTSK0010252',u_task_sys_id: '599bba734fb832003354fc828110c793',u_deployment_tool: 'Jenkins',u_deployment_job_id: '61',u_deployment_job_name: 'ServiceNow-FMW-Pipeline'}[Pipeline] httpRequest HttpMode: POSTURL: https://xx.service-now.com/api/now/table/u_deployment_logContent-type: application/jsonAccept: application/jsonUsing authentication: ServiceNowSending request to url: https://xx.service-now.com/api/now/table/u_deployment_logResponse Code: HTTP/1.1 201 CreatedSuccess code from [100‥399][Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Finished: SUCCESS{color:red}*The following is the successful initiation.*{color} Started by user svcsnjenkins[Pipeline] node Running on master in /opt/jenkins/jobs/ServiceNow-FMW-Pipeline/workspace[Pipeline] { [Pipeline] echo The build value is UAT for SOABPM[Pipeline] build (Building SOA-UAT-Stage-Clean-Build-And-Deploy) Scheduling project: SOA-UAT-Stage-Clean-Build-And-DeployStarting building: SOA-UAT-Stage-Clean-Build-And-Deploy #160[Pipeline] echo Deployment failed hudson.AbortException: SOA-UAT-Stage-Clean-Build-And-Deploy #160 completed with status FAILURE (propagate: false to ignore)[Pipeline] echo Writing
[JIRA] (JENKINS-41156) [Pipeline] Have shell and batch steps be renameable
Title: Message Title Jesse Glick commented on JENKINS-41156 Re: [Pipeline] Have shell and batch steps be renameable You can put stage wherever you want (except when using Declarative). What a particular visualization plugin in its current implementation will or will not render is another matter. Pipeline Steps will show it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40878) Support run containers as components
Title: Message Title Jesse Glick commented on JENKINS-40878 Re: Support run containers as components I actually have no idea what you are talking about here or what you are asking for. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40908) GitSCMSource: support custom remote and refspec
Title: Message Title jbq commented on JENKINS-40908 Re: GitSCMSource: support custom remote and refspec Hi Mark! Sorry to learn that my decision to merge the PR myself has been taken as an offense. In fact I'm a committer of the git plugin of the early days, that's why I have commit rights on this repo. However if you think this is inappropriate and against new guidelines that I am maybe not aware of, feel free to revert the commit and remove me from the committers. My only wish is that the proposed change be reviewed and eventually incorporated into Jenkins. I also noticed that the PR has been upvoted 11 times so I may not be the only one. Thanks for your understanding! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39779) bitbucket notifier not configurable under pipeline
Title: Message Title David Delbecq commented on JENKINS-39779 Re: bitbucket notifier not configurable under pipeline Hello Antonio, We have moved away from pipeline and went back to regular builds where we could select credentials to use. Having a single jenkins credentials for bitbucket notfify was not an option here as each team sharing that jenkins are clearly separated at bitbucket level and tool credentials would be different for each project. Having a global bitbucket "jenkins" account was not an option. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41335) Allow variables and functions to be defined within pipeline to be used in any stage
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-41335 Allow variables and functions to be defined within pipeline to be used in any stage Change By: Andrew Bayer Summary: Allow variable variables and functions to be defined within pipeline to be used in any stage Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41335) Allow variables and functions to be defined within pipeline to be used in any stage
Title: Message Title
Andrew Bayer commented on JENKINS-41335
Re: Allow variables and functions to be defined within pipeline to be used in any stage
So the way I can see to do this currently is to first have a library step added to Pipeline (i.e., JENKINS-39450). We need that for JENKINS-38110 anyway. With that step, we can add to the Binding at runtime, so we could have something like this:
define {
def foo = "bar"
def someMethod() {
return "Hello"
}
}
...and then take the source text for define's block and pass it to the library step with a new LibraryRetriever that can output a file containing a given string rather than fetching from an SCM source as the existing retrievers do. Then we should, if I'm understanding correctly, get the variables and methods available from then on in the execution. Jesse Glick - does that sound right?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42065) "Execute HP functional tests from HP ALM" failing without reason
Title: Message Title Raghavendra Vinay commented on JENKINS-42065 Re: "Execute HP functional tests from HP ALM" failing without reason As Jenkins is hosted on Unix Server , my guess it is not able to execute "HpToolsLauncher.exe" command , So do we need to setup Jenkins on Slave machine and change run mode in Job to "Run Locally" and try to execute this ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41156) [Pipeline] Have shell and batch steps be renameable
Title: Message Title Phil McArdle commented on JENKINS-41156 Re: [Pipeline] Have shell and batch steps be renameable Looks like I wanted JENKINS-38442 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41335) Allow variables and functions to be defined within pipeline to be used in any stage
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-41335 Allow variables and functions to be defined within pipeline to be used in any stage Change By: Andrew Bayer Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41976) Add support for Add-on generated HipChat v2 tokens
Title: Message Title aldaris commented on JENKINS-41976 Re: Add support for Add-on generated HipChat v2 tokens I've been trying to read more about addons, but I always end up having the feeling that it requires having HTTP endpoints exposed by some means. I've summed up my questions here: https://answers.atlassian.com/questions/53748694/how-do-hipchat-addons-work In general though: anything that will require an exposed endpoint (such as the capabilities descriptor), will most likely never make it into the plugin. You may be able to create a BYO integration and save the obtained OAuth2 access token as a v2 credential to achieve your goals. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41335) Allow variables and functions to be defined within pipeline to be used in any stage
Title: Message Title Sam Van Oort commented on JENKINS-41335 Re: Allow variables and functions to be defined within pipeline to be used in any stage Robby Pocase If I understand your request correctly, what you are describing is better handled by functional and imperative features in vanilla AKA "scripted" pipeline. It's breaking from the declarative model because of the potential for side effects with variable declarations and shared state. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41940) Pipeline stages should be configurable with a weight property, corresponding to the number of executors the stage occupies
Title: Message Title Vitali Gontsharuk commented on JENKINS-41940 Re: Pipeline stages should be configurable with a weight property, corresponding to the number of executors the stage occupies Well, I was using the abstractions from Declarative Pipeline here. You obviously know better how this is mapped to Scripted Pipeline primitives. Concerning the approach: I have basically proposed the same functionality as currently exists for Freestyle jobs to be supported for Pipeline jobs. This is not a very fancy approach, but it is enough to get the job done in practice. If the same goal could be reached automatically, without any configuration from the user, that would be just perfect. What do you think, would it be a lot of effort to implement? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41940) Pipeline stages should be configurable with a weight property, corresponding to the number of executors the stage occupies
Title: Message Title Vitali Gontsharuk commented on JENKINS-41940 Re: Pipeline stages should be configurable with a weight property, corresponding to the number of executors the stage occupies Jesse Glick So who do you think would be an appropriate assignee for this? Thanks! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39402) Jenkins creates massive HTTP headers that blows up proxies
Title: Message Title Oliver Gondža commented on JENKINS-39402 Re: Jenkins creates massive HTTP headers that blows up proxies Jesse Glick, fixed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39402) Jenkins creates massive HTTP headers that blows up proxies
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-39402 Jenkins creates massive HTTP headers that blows up proxies Change By: Oliver Gondža Labels: 2.32. 2 3 -fixed http robustness Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41396) Declarative: Add script definition section to root pipeline block
Title: Message Title Andrew Bayer resolved as Duplicate Yup, folding this into JENKINS-41335. Jenkins / JENKINS-41396 Declarative: Add script definition section to root pipeline block Change By: Andrew Bayer Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-41335) Allow variables and functions to be defined within pipeline to be used in any stage
Title: Message Title Andrew Bayer commented on JENKINS-41335 Re: Allow variables and functions to be defined within pipeline to be used in any stage Hrm - realizing that this would end up in something like vars/foo.groovy, but then the methods and variables could only be accessed like foo.someVar or foo.someMethod() which wouldn't pass validation. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41335) Allow variables and functions to be defined within pipeline to be used in any stage
Title: Message Title Jesse Glick commented on JENKINS-41335 Re: Allow variables and functions to be defined within pipeline to be used in any stage I have several use cases where I may operate on a list or map on different stages of a pipeline. This variable may not be known ahead of time IMO if you are going to rely so heavily on script anyway, dispense with pipeline-model-definition and just write your script directly. his would make the use of Artifactory much simpler. The current plugin relies heavily on a DSL, against my advice which is to stick to plain old Step implementations using vanilla structs (or, better yet, wrappers which set the bare minimum environment necessary for non-Jenkins-specific shell/batch scripts to run). Workable in scripted Pipeline but I think it would need to be reconceptualized to be useful in Declarative. take the source text for define's block and pass it to the library step with a new LibraryRetriever that can output a file containing a given string Uh, or call evaluate? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are
