You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a CI pipeline user I need the virtual cluster that was spun up to shut down if another CI test has not started in awhile because having virtual clusters idle can be costly.
What are the requirements for the new functionality?
The shutdown feature should run separate from the pipeline itself so that it can wait around for a bit before shutting down in case other CI test is about to start up so that the time consuming process of restarting can be avoided if it is not necessary.
Acceptance Criteria
[] Tested in a dev pipeline
Suggest a solution (optional)
Use stopCluster.py script in an cron like action within github that can check if pipeline has not ran within a 30 minute period.
The text was updated successfully, but these errors were encountered:
What new functionality do you need?
As a CI pipeline user I need the virtual cluster that was spun up to shut down if another CI test has not started in awhile because having virtual clusters idle can be costly.
What are the requirements for the new functionality?
The shutdown feature should run separate from the pipeline itself so that it can wait around for a bit before shutting down in case other CI test is about to start up so that the time consuming process of restarting can be avoided if it is not necessary.
Acceptance Criteria
Suggest a solution (optional)
Use stopCluster.py script in an cron like action within github that can check if pipeline has not ran within a 30 minute period.
The text was updated successfully, but these errors were encountered: