I have the following example which is based on the structure that I want to use my reckfile:
Functions: defaults 'works that you can run: dev, stage, prod' end task: dev = & gt; [: Init ,: devrun ,: clean] Task: devrun does 'dev stuff' end works: platform = & gt; [: Init,: stagerun,: clean] Work: stagerun does 'staging stuff' end work: prod => [: Init ,: prodrun, clean] task: prodrun does 'output content' works in the end: init does 'init ...' end work: clears 'cleanup' end puts What tasks will always run in one order? I read somewhere that they will not, and somewhere they will do this, so I'm not sure.
Or, if you are trying to achieve, you can recommend a better way (for example
thanks
From the ROCK source code:
# Request all the work as required. Def invoke_prerequisites (task_args, invocation_chain) #: nodoc : @PreviousViewHe {| n | Prereq = application [n, @scope] prereq_args = task_args.new_scope (prereq.arg_names) prereq.invoke_with_call_chain (prereq_args, invocation_chain)} end such Seems that code normally just iterates array and predefined
However:
# Announce a job that works according to its requirements in parallel. Multitask # * does not guarantee # # (Which is then obvious when you think about it) # # Example: # Multitask: Deployed = & gt; [: Deploy_gem,: deploy_rdoc] #DIF Multitask (RGS, And block) RK :: Multitask.defi_task (RGS, A D block) and then you are right, both can be true, but if you can order your work via prefix with multitask So it can only be closed, it seems that the routine work is going on in order.
Comments
Post a Comment