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

config files need standardized output-dir #385

Closed
nsjake opened this issue Jul 26, 2016 · 1 comment
Closed

config files need standardized output-dir #385

nsjake opened this issue Jul 26, 2016 · 1 comment
Assignees
@jvivian

Comments

@nsjake
Copy link

nsjake commented Jul 26, 2016

Either have both output-dir and s3-output-dir or one output-dir for both on every pipeline config
@jvivian
Copy link
Collaborator

jvivian commented Jul 26, 2016

Deferring to simplicity — Will only have one output dir.

jvivian added a commit that referenced this issue Jul 26, 2016
@jvivian
Standardize output-dir (resolves #385)
59c50cd
jvivian added a commit that referenced this issue Jul 26, 2016
@jvivian
Standardize output-dir (resolves #385)
765b2ce
jvivian added a commit that referenced this issue Jul 27, 2016
@jvivian
Standardize output-dir (resolves #385)
556463a
hannes-ucsc added a commit that referenced this issue Jul 27, 2016
@hannes-ucsc
Merge pull request #386 from /issues/377-disable-encryption-for-stati…
112e668 
…c-inputs

Disable encryption for static inputs (resolves #377, resolves #385, resolves #383)
@jvivian jvivian closed this as completed in 440282c Aug 1, 2016
jvivian added a commit that referenced this issue Aug 1, 2016
@jvivian
Merge pull request #398 from /issues/377-378-383-385-389-391-396-cp-t…
007088e 
…o-master

Cherrypick to master (resolves #377, resolves #378, resolves #383, resolves #385, resolves #389, resolves #391, resolves #396)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jvivian jvivian

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jvivian @nsjake