container timeout (for sandboxes)
Job timeout implemented since f19328b8
We should have something similar for sandboxes because many users forget to shut them down (eg: as of 2018-09-12 we have ~15 sandbox runnings, many of them for weeks).
- what should done about a sandbox that times out? dropping the sandbox would be a harsh because users may have pending changes in them, committing a draft/private version (not visible by other users) would be a more acceptable solution
- user should receive a warning email before the sandbox is shut down (eg: « if no action from you, the sandbox will closed and committed as version xxxxxx »)
To upload designs, you'll need to enable LFS. More information