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

Non-pooled state for resource #30

Open
mthuurne opened this issue Jan 29, 2020 · 0 comments
Open

Non-pooled state for resource #30

mthuurne opened this issue Jan 29, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@mthuurne
Copy link
Member

mthuurne commented Jan 29, 2020

When setting up a new Task Runner, you typically want to force one or more jobs to run on that Task Runner to validate the setup. This can be done with Task Runner selection. But production tasks in the factory could be automatically assigned to the new Task Runner before it's ready. So it would be useful to have a flag that indicates that a Task Runner is only available for explicit selection and should not be picked for any task that doesn't explicitly select it.

While the scenario I describe involves Task Runners, this would apply to other types of resources as well. For example during the migration from one repository to another, it would be useful to run test jobs using the new repository while production jobs keep using the old repository.

@mthuurne mthuurne added the enhancement New feature or request label Jan 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant