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

Allow per-environment idling (instead of per-project) #980

Closed
tobybellwood opened this issue Mar 21, 2019 · 1 comment · Fixed by #985
Closed

Allow per-environment idling (instead of per-project) #980

tobybellwood opened this issue Mar 21, 2019 · 1 comment · Fixed by #985
Assignees

Comments

@tobybellwood
Copy link
Member

Currently Lagoon only allows you to idle environments on a per-project basis - i.e. all on or all off.

It'd be great to be able to set individual environments to non-idle (e.g. for cron testing etc as per #949, or for running larger test plans) - this would also give us more ability to mitigate the costs involved in projects with multiple environments.

@tobybellwood
Copy link
Member Author

woohoo! nice work @twardnw 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants