82c6dec4fa
This takes a similar approach to the extant ansible_cron_install_cron variable to disable the cron job for the cloud launcher when running under CI. If you happen to have your CI jobs when the cron job decides to fire, you end up with a harmless but confusing failed run of the cloud launcher (that has tried to contact real clouds) in the ARA results. Use the "disbaled" flag to ensure the cron job doesn't run. Using "disabled" means we can still check that the job was installed via testinfra however. Convert ansible_cron_install_cron to a similar method using disable, document the variable in the README and add a test for the run_all.sh script in crontab too. Change-Id: If4911a5fa4116130c39b5a9717d610867ada7eb1
29 lines
656 B
ReStructuredText
29 lines
656 B
ReStructuredText
Setup periodic runs of ``run_all.sh``, which runs playbooks against
|
|
bridge.o.o and all hosts.
|
|
|
|
**Role Variables**
|
|
|
|
.. zuul:rolevar:: update_cron_interval
|
|
|
|
.. zuul:rolevar:: minute
|
|
:default: 15
|
|
|
|
.. zuul:rolevar:: hour
|
|
:default: *
|
|
|
|
.. zuul:rolevar:: day
|
|
:default: *
|
|
|
|
.. zuul:rolevar:: month
|
|
:default: *
|
|
|
|
.. zuul:rolevar:: weekday
|
|
:default: *
|
|
|
|
.. zuul:rolevar:: ansible_cron_disable_job
|
|
:default: false
|
|
|
|
Disabled installed cron job. This is only useful for CI jobs
|
|
testing bridge.o.o so that the test host does not randomly run
|
|
the script during CI tests that fall during the interval.
|