Hi John, Would that help: > > https://gist.github.com/anonymous/5467499 > <https://gist.github.com/anonymous/5467499> > >
perfect! That's exactly what I was looking for. > Instead of downloading a Git repository and then uploading it to other > systems, > I'd rather clone/pull the repository from the other systems directly. I > guess > your environment doesn't let you do that. > Indeed, I dumbed down the problem a bit to make the question shorter. In our actual system instead of a Git repo I'm downloading from a Sonatype Nexus repository and have to perform several steps of figuring out which package and for which environment to download, generate config files and enrich them with DB settings and passwords. Tasks that for security reasons must not be done on the destination nodes directly. Until now we've been using puppet and mcollective to do so, but as possible workflows got more complex and now require human intervention (i.e. a team lead to confirm deployment on production systems) I figured a proper workflow engine makes more sense than hundreds more if-then-else clauses. Anyway, thank you again for demonstrating the use of workitem data in process definitions. Very much appreciated! Best, -- Lukas -- -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en --- You received this message because you are subscribed to the Google Groups "ruote" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
