We have a database tester build that first clones a database before it runs the tests. We would like to prevent this build from being stopped/cancelled by a user. The problem is, if the build is cancelled/stopped manually during the cloning process it leaves the DB in a bad way and requires DBA intervention.
Is there a way to prevent a build step from being cancelled/stopped?