Files
galaxy/templates
John Chilton 0ad9c05af3 Conditionally force traditional workflow invocations paths through scheduling framework.
Workflow with pause modules have to be run through the new workflow scheduling plugin framework - so these will always force jobs to be queued in the background. The deployer can also now choose to have workflows scheduled this way if a workflow has a minimum number of steps (set at a very high 250 right now) or if it uses collections (currently this defaults to False). These options are meant as transient options that will disappear once all workflows a scheduled this way - but there needs to be better UI in place before making that switch as well as more testing. These options are just meant to give people running really large workflows a way to start exploring the scheduling framework option.
2014-11-13 13:47:40 -05:00
..
2012-10-11 16:36:45 -04:00