use a lock file for the atomic continuous composes.
with the lockfile if a compose runs over five minutes the new one stomps on the old and things are unhappy Signed-off-by: Dennis Gilmore <ausil@fedoraproject.org>
This commit is contained in:
parent
052b9b400a
commit
e8bbcb7a59
1 changed files with 1 additions and 1 deletions
|
@ -1,4 +1,4 @@
|
|||
# continous delivery of atomic host
|
||||
MAILTO=releng-cron@lists.fedoraproject.org
|
||||
*/15 * * * * root TMPDIR=`mktemp -d /tmp/atomic-cd.XXXXXX` && cd $TMPDIR && git clone https://pagure.io/releng.git && cd releng && LANG=en_US.UTF-8 ./scripts/build-test-ostree
|
||||
*/15 * * * * root TMPDIR=`mktemp -d /tmp/atomic-cd.XXXXXX` && cd $TMPDIR && git clone https://pagure.io/releng.git && cd releng && LANG=en_US.UTF-8 /usr/local/bin/lock-wrapper atomic-cd ./scripts/build-test-ostree
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue