Yep, I would highly recommend tags to reference just the stuff you changed.
There is nothing that is going to monitor what files you edited automatically - that's a bit too complex of a problem and not a use case we're interested in. Do read http://www.ansible.com/blog/ansible-performance-tuning if you have not already. On Thu, Dec 11, 2014 at 3:18 PM, James Cammarata <[email protected]> wrote: > Hi Kevin, > > This is probably something better suited for ansible-devel, however to > answer your question we do already provide several methods for limiting the > scope of playbook runs (--tags, --start-at-task, --step, etc.). Ansible is > really very linear, even when considering role dependencies (we compile > everything down into a single list of tasks, and iterate through that), so > there's no crazy dependency resolution to fix. > > Also, there is the added complication that things on remote targets may > have changed, so in general you would not want to automatically limit the > execution of a playbook to only those parts of the play which have changed > on the controlling machine. > > While your suggestion might be technically possible, it definitely seems > overly complex for what Ansible does. If you only need to re-run a single > role or even a small subset of tasks, it is pretty trivial to create a new > playbook to do so. > > Thanks! > > > On Thu, Dec 11, 2014 at 1:48 PM, Kevin Burton <[email protected]> > wrote: > >> Has anyone done any work on using dependency graphs to speed up ansible. >> >> For example, if I have one big site.yml, and I only change an edge role, >> something small, it doesn't make sense to re-run ALL playbooks. >> >> There might be situations where this makes sense. There might be some >> API dependencies though but maybe you could hard code some exemptions for >> dependency computation. >> >> This is generally how incremental compilers work btw. No sense >> recompiling your whole app if dependencies haven't changed. >> >> -- >> 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/0ba85b46-00fc-426c-87ea-7ba54a8cc585%40googlegroups.com >> <https://groups.google.com/d/msgid/ansible-project/0ba85b46-00fc-426c-87ea-7ba54a8cc585%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- > 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/CAMFyvFhZtF%3DR3G1%3DzNtWVYXvDZdCyoj_Bq9A5OWg9_dOP-dY1Q%40mail.gmail.com > <https://groups.google.com/d/msgid/ansible-project/CAMFyvFhZtF%3DR3G1%3DzNtWVYXvDZdCyoj_Bq9A5OWg9_dOP-dY1Q%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CA%2BnsWgxxMqQwUeVCueGsUZBxpd7hw1iUKLeBrRs%3DVyc786kyPQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
