Give users the ability to manage stuck builds
The information in this post is accurate as of the published date . Please make sure to check any linked documentation within the post for changes/updates.
I've been with Platform.sh for a year now and we have several projects.
By major the main aggravation is stuck builds. It goes against the initial premise of resting assured that a deployment will go well. I have to say that because of this every time we go live we hold our breath to ensure there are no "stuck" processes.
While several times the reason for these stuck builds might be with the client (long running cron processes etc) it's still no excuse to have to call support.
In my view there should be two things happening:
- The build/deployment process should be able to cancel itself. For example if the build is stuck because of a cron process it should just timeout and cancel itself. The fact that it gets stuck and you have to call support doesn't make sense to me.
- Users should be able to stop these stuck builds. A simple command in the CLI or something should be enough.
Seriously hope you guys look into this soon, because it's getting to a point where we question if this Platform is the right fit for us.
Thanks
-
+1
8 -
+1
1 -
+1
1 -
+1
1 -
+1
1 -
Hello
1
Please sign in to leave a comment.
Comments
6 comments