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.

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

Don't auto-cycle for changes #306

Merged
merged 1 commit into from
Sep 1, 2023
Merged

Don't auto-cycle for changes #306

merged 1 commit into from
Sep 1, 2023

Conversation

jschwartzentruber
Copy link
Contributor

This means created/modified pools will not be run automatically, nor will removed/disabled pool tasks be killed.

To cycle a pool, either trigger its hook manually, or wait until the next scheduled cycle.

@tysmith
Copy link
Contributor

tysmith commented Aug 30, 2023

So in other words this is letting tasks that are running run to "completion" instead of stopping or cycling?

@jschwartzentruber
Copy link
Contributor Author

So in other words this is letting tasks that are running run to "completion" instead of stopping or cycling?

As far as I know, yes. We may get killed by Taskcluster if things change under us, but have no control over that.

This means created/modified pools will not be run automatically,
nor will removed/disabled pool tasks be killed.

To cycle a pool, either trigger its hook manually, or wait until
the next scheduled cycle.
@jschwartzentruber jschwartzentruber merged commit 62b6580 into master Sep 1, 2023
2 checks passed
@jschwartzentruber jschwartzentruber deleted the no-auto-cycle branch September 1, 2023 14:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants