orion icon indicating copy to clipboard operation
orion copied to clipboard

Changes to the config repository should not trigger everything

Open jschwartzentruber opened this issue 5 years ago • 1 comments

Currently any change to the configuration repository (even a README update) will cause the hook cron schedule to be recalculated for every pool, and thus everything will be cycled. We should only update Taskcluster (and cycle) pools that are actually changed.

jschwartzentruber avatar Jul 10 '20 20:07 jschwartzentruber

An easy solution to this is to use an arbitrary schedule_start, like the unix epoch, to calculate the cycle schedules from.

jschwartzentruber avatar Jul 14 '20 14:07 jschwartzentruber