- 29 Jul, 2016 1 commit
-
-
Joerg Jaspert authored
use pupopt as an array quote some more places
-
- 25 Jul, 2016 1 commit
-
-
Joerg Jaspert authored
That is, everytime a run exits with a non-zero exit code (as handled by puppetgo, so puppet exit 2 -> 0), the next run starts with a delay of up to 240 seconds. That should spread out the load of repeated tries to run that overload the (already loaded) puppetmaster machine, as such helping the whole plethora of servers finally get their run done... Not nice, but works.
-
- 22 Apr, 2016 3 commits
-
-
Joerg Jaspert authored
-
Joerg Jaspert authored
-
Joerg Jaspert authored
-
- 01 Mar, 2016 1 commit
-
-
Joerg Jaspert authored
Thats a behaviour change, prior to this human meant "run, even if there is no change in git". Now it checks git changes. It also adheres to /nopuppet. Humans who want to have a run now, no matter what, can use -d as before.
-
- 19 Jan, 2016 1 commit
-
-
Joerg Jaspert authored
When /run not exist, look if /var/run or /var/lock does and then use thwt for the LOCKFILE and the store of the last git revision.
-
- 23 Nov, 2015 1 commit
-
-
Joerg Jaspert authored
Branches, as such environments, can disappear for a short while when they get rebased and "force" pushed using something like git push origin :branch && git push origin branch Machines should still use them in such a case, so only switch back to production if the branch is missing in two puppetgo runs.
-
- 27 Oct, 2015 3 commits
-
-
Joerg Jaspert authored
-
Joerg Jaspert authored
-
Joerg Jaspert authored
-