-
Notifications
You must be signed in to change notification settings - Fork 250
How to mark a build as bad
Teletraan allows engineers to perform deployment by themselves. This is great for productivity. However, sometimes issues are not being able to be caught until the build has been successfully deployed. As services are deployed by different engineers, the bad build can go out because of the lack of automated communication channels. We want to have a way to let engineers be able to label a build as bad build. All the following deployments on this commit or subsequent commits will have a clear (warning) message until the issue has been fixed and confirmed.
In the Build Details page, a button is created to mark a build as bad build. Click the button. The build can be marked as Bad.
After submit, this build and all the subsequent builds on the same build name and branch will be treated as bad builds until one build has been tagged as good.
For all bad builds, there is a banner saying the build is bad and the Mark Build As Good button will be available. Once the issue has been fixed. Engineers can set the build containing the fixed commits to be good.