cli: accept workflow file location #137
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
This was referenced Jan 28, 2020
* If there is no workflow specification provided to the workflow engine, a new parameter can be passed. This is the relative path to the workflow file. This is needed for the case of running a workflow triggered by a Git provider, i.e. on commit to master, so we expect the analysis code to be present in the workflow workspace and, hence, we can load it (closes reanahub/reana#235).
mvidalgarcia
force-pushed
the
r/235-workflow-engine-to-load-workflow-spec
branch
from
5a62ea2
to
d7b2703
Compare
roksys
approved these changes
Jan 28, 2020
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.
engine, a new parameter can be passed. This is the relative
path to the workflow file. This is needed for the case of running
a workflow triggered by a Git provider, i.e. on commit to master,
so we expect the analysis code to be present in the workflow
workspace and, hence, we can load it (closes gitlab: worfklows started from GitLab using yadage failing reana#235).