This repository has been archived by the owner on Aug 13, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 12
Add support for run constraints #45
Milestone
Comments
Hey! This functionality can be reproduced like this:
and running like this:
This may not be specific enough for this use-case, but I thought I'd mention it anyway |
Hey @ninjabear - that's really neat. An emergent property of Factotum! I think we need to keep this as a feature however, because otherwise we have to mutate all of our factfiles to add this check... |
jbeemster
added a commit
that referenced
this issue
Nov 29, 2016
jbeemster
added a commit
that referenced
this issue
Dec 5, 2016
jbeemster
added a commit
that referenced
this issue
Dec 12, 2016
jbeemster
added a commit
that referenced
this issue
Dec 15, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is the idea that Factotum should only execute if a "run constraint" specified on the CLI resolves to true.
This is a powerful feature (taken from Snowplow's internal executor), which lets you have the same Factotum invocation in the cron on multiple boxes, but only one box will execute the job.
Example cronfile:
To start with, we only allow one constraint, and the only allowed constraint is
host
, and the implied check is==
.The text was updated successfully, but these errors were encountered: