Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Changes to the config repository should not trigger everything #86

Open
jschwartzentruber opened this issue Jul 10, 2020 · 1 comment
Open

Changes to the config repository should not trigger everything #86

jschwartzentruber opened this issue Jul 10, 2020 · 1 comment
Labels
enhancement fuzzing-decision

Comments

@jschwartzentruber
Copy link
Contributor

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
Copy link
Contributor Author

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

@jschwartzentruber jschwartzentruber transferred this issue from MozillaSecurity/fuzzing-tc Jan 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement fuzzing-decision
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jschwartzentruber