orion
                                
                                 orion copied to clipboard
                                
                                    orion copied to clipboard
                            
                            
                            
                        Changes to the config repository should not trigger everything
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.
An easy solution to this is to use an arbitrary schedule_start, like the unix epoch, to calculate the cycle schedules from.