[
https://issues.apache.org/jira/browse/TAVERNA-938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stian Soiland-Reyes updated TAVERNA-938:
----------------------------------------
Labels: cwl docker gsoc2016 java python (was: cwl docker gsoc2016 gsoc2018
java python)
> Run cwlrunner (nested CWL workflows)
> ------------------------------------
>
> Key: TAVERNA-938
> URL: https://issues.apache.org/jira/browse/TAVERNA-938
> Project: Apache Taverna
> Issue Type: Bug
> Components: Taverna Common Activities
> Reporter: Stian Soiland-Reyes
> Priority: Major
> Labels: cwl, docker, gsoc2016, java, python
>
> Executing cwlrunner from Taverna (configured with a CWL workflow rather than
> a CWL tool) could be an interesting thing - that would be a way to include a
> CWL workflow as a nested workflow in Taverna.
> The CWL workflow can be added directly to the Workflow Bundle as-is and
> extracted to a temporary folder before running cwl-runner.
> This would also be an intermediate approach towards TAVERNA-878 as you can
> execute any cwl tool by generating a one-step cwl workflow and run cwlrunner.
> However then the user would need to have cwlrunner AND Taverna installed, so
> it would be more of an intermediate solution.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
