Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

PipelineBuildRequest should allow the user to save pipeline outputs in specified locations #116

Closed
brimoor opened this issue Jul 21, 2018 · 1 comment
Closed

PipelineBuildRequest should allow the user to save pipeline outputs in specified locations #116

brimoor opened this issue Jul 21, 2018 · 1 comment
Assignees
@brimoor
Labels
feature Work on a feature request

Comments

@brimoor
Copy link
Contributor

brimoor commented Jul 21, 2018 •
edited
Loading

eta.core.builder.PipelineBuildRequest should allow the user to optionally specify paths to write copies of the pipeline outputs.

We should also add flags to eta build to control whether the intermediate outputs are retained.
@brimoor brimoor added the feature Work on a feature request label Jul 21, 2018
@brimoor brimoor changed the title PipelineBuildRequest should allow the user to specify a directory into which to copy the pipeline outputs PipelineBuildRequest should allow the user to optionally specify filepaths (including names) to copy the outputs Jul 21, 2018
@brimoor brimoor changed the title PipelineBuildRequest should allow the user to optionally specify filepaths (including names) to copy the outputs PipelineBuildRequest should allow the user to save pipeline outputs in specified locations Jul 21, 2018
@brimoor brimoor self-assigned this Jul 21, 2018
@brimoor
Copy link
Contributor Author

brimoor commented Aug 3, 2018

See #130.

@brimoor brimoor closed this as completed Aug 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@brimoor brimoor

Labels
feature Work on a feature request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@brimoor