Thats because puppet isn't a tool meant to build applications from source. You could do it but its one of those things where it doesn't make sense.
If you need to build from SVN, you might as well look at something like Jenkins that can monitor an SCM and pull out changes and do a bunch of things around it. Then package it up into an RPM, which puppet handles nicely from my experience. run deck might be a good solution for you on your problem in terms of deploying to one system first before the others. If you had the knowledge with writing web applications you could easily use MCollective to do that too and put a nice GUI in front of the job. On Sep 13, 2011, at 6:33 PM, Ashley Penney wrote: > can't think of any other good way to say "do a one time run of > project::build_core on the following matching nodes: x, y, z". I am really > just using rundeck for the equivalent of that. Other things I would think of > using this for is handling deploying a bunch of servers where server 1 has to > be fully provisioned before 2 and on 2 at least one service has to be up > before 3 can do its thing. It's something that's still a hassle to do well > within Puppet. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
