I'm trying to make a playbook wich contains a simply command that build a project and then send's the compilation result to a server. Since when you use the simple command form of ansible the playbook node that sended the command doesnt recieve the result if the command has finished or not. So sometimes the next tasks of the playbook starts even before that grunt build command finished so that make's copy only the half of the files wich creates a lot of problems. Having grunt integrated with ansible will solve that problem because the playbook node would wait till the tasks of grunt build finish so the next task would do it's work correctly.
Of course we can put adelay but this it's only a patch and no 100%secure to use on pro environment. El viernes, 14 de junio de 2013, 16:22:18 (UTC+2), Shahar Kedar escribió: > > I was thinking of implementing a Grunt <http://gruntjs.com/>module and > contributing it to the core modules. Is contributing a core module as > simple as developing (following the guideline of course) and sending a pull > request? > If it is, where should I put it? We use Grunt for packaging, but it's > multi-purpose. Could also go into web_infrastructure or a new category > called "build_tools". > > Anything else I should know before I start coding? > > Thanks, > Shahar > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/261d07ac-ed1d-48a8-b46e-e132a0a1f561%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
