When a new deployment is triggered, Fuse dispatches a DeploySite job. However, there was previously no way to monitor the deployment—for example, if the deployment script ran too long without marking the deployment as successful.
To address this, I improved the job to actively monitor the deployment status.
First, if the deployment is marked as deployed, Fuse deletes the job.
If the deployment is still in progress, Fuse releases the job to check the deployment status again after 30 seconds.
To handle long-running deployments, I decided that any deployment created more than 10 minutes ago is considered stale. In this case, Fuse fails the deployment job.
I like this approach because I can use the same DeploySite job to both monitor the deployment and run the server deployment script.
I also kept the Job class simple by moving status checks to the Deploy model. I especially like the isStale method name, as it clearly describes stale deployments and simply checks if the deployment was created more than 10 minutes ago.
To address this, I improved the job to actively monitor the deployment status.
First, if the deployment is marked as deployed, Fuse deletes the job.
If the deployment is still in progress, Fuse releases the job to check the deployment status again after 30 seconds.
To handle long-running deployments, I decided that any deployment created more than 10 minutes ago is considered stale. In this case, Fuse fails the deployment job.
I like this approach because I can use the same DeploySite job to both monitor the deployment and run the server deployment script.
I also kept the Job class simple by moving status checks to the Deploy model. I especially like the isStale method name, as it clearly describes stale deployments and simply checks if the deployment was created more than 10 minutes ago.