Hi, Glad the run_once works for you.
On 07.02.17 09:27 'Tom Bartsch' via Ansible Project wrote: > The hints from Mr. Kastl are not suitable for my purpose because > I'm calling the playbook only with the product name and only one > time. But I am not sure you got my approach. You do not need to call the playbook multiple times, even if it contains two plays. > Also I want to create the jobs don't matter if they are exist > or not. The reason is that it's possible that I changed something > in the config.xml of an maybe existing job. So if I call the > playbook I want it to change also the existing jobs to deliver my > changes to jenkins. But doesn't this mean that the jobs exist multiple times in jenkins, with different parameters? Johannes -- 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 ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/6e240266-c876-28ae-778a-dde165e30327%40ojkastl.de. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
