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
There's been some discussion of adding a feature to the Cloud to edit the 'run timeout' which is statically set to 90 minutes beyond the last ping from the App.
When this timeout is editable from the project settings, the App should have to ability to error when that timeout is reached and exit so that CI resources are not wasted in this case for users and there is clarity on the status of the run.
Why is this needed?
If this error is not provided, the run will continue for as long as it runs and print our the results of the run as if nothing had changed. The Cloud however would show the spec and the run as timed out.
Other
No response
The text was updated successfully, but these errors were encountered:
What would you like?
There's been some discussion of adding a feature to the Cloud to edit the 'run timeout' which is statically set to 90 minutes beyond the last ping from the App.
When this timeout is editable from the project settings, the App should have to ability to error when that timeout is reached and exit so that CI resources are not wasted in this case for users and there is clarity on the status of the run.
Why is this needed?
If this error is not provided, the run will continue for as long as it runs and print our the results of the run as if nothing had changed. The Cloud however would show the spec and the run as timed out.
Other
No response
The text was updated successfully, but these errors were encountered: