Skip to content

[JENKINS-41854] Recontextualizing FilePath on demand#86

Merged
dwnusbaum merged 8 commits into
jenkinsci:masterfrom
jglick:DynamicContext-JENKINS-41854
Jun 3, 2019
Merged

[JENKINS-41854] Recontextualizing FilePath on demand#86
dwnusbaum merged 8 commits into
jenkinsci:masterfrom
jglick:DynamicContext-JENKINS-41854

Conversation

@jglick

@jglick jglick commented May 31, 2019

Copy link
Copy Markdown
Member

@jglick
jglick requested a review from dwnusbaum May 31, 2019 17:55
@jglick

jglick commented May 31, 2019

Copy link
Copy Markdown
Member Author

On hold as in jenkinsci/workflow-support-plugin#95 (comment).

getContext().get(TaskListener.class).getLogger().println("Running in " + dir);
getContext().newBodyInvoker()
.withContext(dir)
// TODO perhaps should just be moved into workflow-durable-task-step?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 from me, I think it would make sense to keep all core steps that manipulate FilePath in the same plugin. Want to do that now or just leave it as a TODO?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

all core steps that manipulate FilePath

There are many other steps in this plugin which consume it, including for example PwdStep which you could see as the counterpart to PushdStep. This just happens to be the only one in this plugin which binds it. So, not sure there is a benefit, other than avoiding the need for FilePathDynamicContext to be used across plugin boundaries. No strong feeling at this point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants