Hi, thx for the hints, Mr. Kastl and Mr. Olstad.
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. 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. So it seems that the hint from Mr. Olstad hits the bull's eye. I tested the behavior with run_once and it looks fine. Thank you once more Mr. Kastl and Mr. Olstad. Regards, Tom -- 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/2e9c7652-d835-4e72-9ef2-da04ef4f95bb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
