Add ExecutionContext#getWorkingDirectory()
#3815
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Any recipe can always call `ExecutionContext#getWorkingDirectory()` to get a working directory private to that recipe instance, where the recipe can store files. These files will be managed by that recipe for the entire recipe run, at the end of which the directory is automatically deleted again.
Also add some unit tests
…ectoryExecutionContext
The idea is to not require subclassing for that use case.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Any recipe can always call
ExecutionContext#getWorkingDirectory()to get a working directory private to that recipe instance, where the recipe can store files. These files will be managed by that recipe for the entire recipe run, at the end of which the directory is automatically deleted again.