[JIRA] (JENKINS-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-33511
Re: env.WORKSPACE should be available within node{} in Pipeline
Code changed in jenkins User: Jesse Glick Path: src/main/resources/org/jenkinsci/plugins/workflow/cps/EnvActionImpl/Binder/help.jelly http://jenkins-ci.org/commit/workflow-cps-plugin/c10a8caa907e2452c83f2ef7fa54d81c6ac70654 Log: Merge pull request #61 from jglick/WORKSPACE-JENKINS-33511 JENKINS-33511 Doc update Compare: https://github.com/jenkinsci/workflow-cps-plugin/compare/b5b1ed0d06aa...c10a8caa907e
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-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-33511
Re: env.WORKSPACE should be available within node{} in Pipeline
Code changed in jenkins User: Jesse Glick Path: src/main/resources/org/jenkinsci/plugins/workflow/cps/EnvActionImpl/Binder/help.jelly http://jenkins-ci.org/commit/workflow-cps-plugin/b6fd3093c0cfb962f6562ec30b51efa500c721f3 Log: JENKINS-33511 $WORKSPACE and $NODE_LABELS are now available.
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-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
Liam Newman commented on JENKINS-33511
Re: env.WORKSPACE should be available within node{} in Pipeline
Jesse Glick That doesn't sound like it is fixed then. If what you describe is true, shouldn't that "withEnv" be added to the node method in the core implementation? That would provide the "env.WORKSPACE" that the original description requested.
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-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
Jesse Glick updated JENKINS-33511
Jenkins / JENKINS-33511
env.WORKSPACE should be available within node{} in Pipeline
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-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
Jesse Glick updated JENKINS-33511
Jenkins / JENKINS-33511
env.WORKSPACE should be available within node{} in Pipeline
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-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title Jesse Glick started work on JENKINS-33511 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-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
Jesse Glick edited a comment on JENKINS-33511
Re: env.WORKSPACE should be available within node{} in Pipeline
{code}env.WORKSPACE = pwd(){code}should work in any environment , master or agent . It is not safe for use inside {{parallel}} branches, though, so it is better to use{code}node { withEnv(["WORKSPACE=${pwd()}"]) {// … }}{code}
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-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
Jesse Glick commented on JENKINS-33511
Re: env.WORKSPACE should be available within node{} in Pipeline
env.WORKSPACE = pwd()
should work in any environment. It is not safe for use inside parallel branches, though, so it is better to use
node {
withEnv(["WORKSPACE=${pwd()}"]) {
// …
}
}
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-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
squalou jenkins commented on JENKINS-33511
Re: env.WORKSPACE should be available within node{} in Pipeline
on the prod environments : jenkins lts 2.7.2 (sidenote : even the 'lts' cycle has accelerated these times, just can't catch up the pace! 2.7.4 just released, we were about to update to .3) pipeline 2.2
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-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
Liam Newman commented on JENKINS-33511
Re: env.WORKSPACE should be available within node{} in Pipeline
squalou jenkins Interesting. What version of Jenkins are you using? What version of the pipeline plugins? I'll try this with my agent as well.
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-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
squalou jenkins commented on JENKINS-33511
Re: env.WORKSPACE should be available within node{} in Pipeline
I confirm : works for me with different layouts on master and slave : master : /home/jenkins/master/jobs/jobName/(etc..: builds, lastsuccessful, ...) slave /home/jenkins/slave/workspace/jobName
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-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
squalou jenkins commented on JENKINS-33511
Re: env.WORKSPACE should be available within node{} in Pipeline
I saw the comment, and I'll have to triple check on Monday because in my case it works, and I don't have the same layout on slaves and master. I'll let you know.
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-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
Liam Newman commented on JENKINS-33511
Re: env.WORKSPACE should be available within node{} in Pipeline
squalou jenkins Look at the comments earlier in the thread. One solution is platform dependent, but 'pwd()` gets the path on master not on the agent, so that only works if your master and all agents have the same directory structure.
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-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
squalou jenkins edited a comment on JENKINS-33511
Re: env.WORKSPACE should be available within node{} in Pipeline
Your example is platform dependant !(can't you hear the lament of windows agents deprived of 'sh' ?)Why not sticking to the native 'pwd' available in pipeline stntax :{code}env.WORKSPACE=pwd(){code} I use it successfully inside 'nodes' step, not on master, and in parallel context.
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-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
squalou jenkins commented on JENKINS-33511
Re: env.WORKSPACE should be available within node{} in Pipeline
Your example is platform dependant ! (can't you hear the lament of windows agents deprived of 'sh' ?) Why not sticking to the native 'pwd' available in pipeline stntax :
env.WORKSPACE=pwd()
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-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
Stephen Hassard edited a comment on JENKINS-33511
Re: env.WORKSPACE should be available within node{} in Pipeline
The following code does a good job of capturing the pwd without writing any files which causes issues when running inside the Groovy sandbox.{code: groovy java }node {env.WORKSPACE = sh(returnStdout: true, script: 'pwd').trim()}{code}
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-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
Stephen Hassard commented on JENKINS-33511
Re: env.WORKSPACE should be available within node{} in Pipeline
The following code does a good job of capturing the pwd without writing any files which causes issues when running inside the Groovy sandbox.
Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
node {
env.WORKSPACE = sh(returnStdout: true, script: 'pwd').trim()
}
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-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-33511
env.WORKSPACE should be available within node{} in Pipeline
Change By:
Jesse Glick
Component/s:
workflow-durable-task-step-plugin
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-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
Kanstantsin Shautsou commented on JENKINS-33511
Re: env.WORKSPACE should be available within node{} in Pipeline
Implemented EnvironmentContributor that depends on executor and provides slave specific var - doesn't work.
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.
