I am experiencing a problem where one of my jobs is getting put into the “Queued” state when it is deployed to our Dev environment. It then stays in the Queued state until it times out. Other jobs can deploy to our Dev environment without any problems and the problem job can be deployed to other environments.
I’ve included a picture of what the Releases page shows.
Are any other deployments running (you can see on the Tasks page) when the deployment is queued? A deployment will remain queued if another deployment to of the same project to the same environment is in progress.
There are no other deployments being run to the Dev environment while project A is queued. In fact, while project A is queued, I am able to successfully deploy other projects to the Dev environment.
The next time this happens, would you be able to take a backup of your database (using Configuration -> Storage) and email the backup to me to investigate? (paul at octopusdeploy.com)
Hi - we’ve overhauled queuing and cancellation in Octopus 2.0 to make this more reliable, if you’re in a position to try the new RC just released it would be great to confirm that these issues are eliminated.