The weird thing here is that at the moment you open the Scheduled Task Manager the task suddenly finishes and Octopus continues it's deployment process with the next step. The deployment of Octopus is blocked because of the 'running' state of the task. Although the status is 'running' we can see in the logging the console application has finished it's process and stopped running but the task still keeps the status 'running' for a long time (console app finishes in seconds but the task stays open for more than 10 minutes, sometimes 50 minutes or more). We have a long standing problem with Octopus being unable to disable the scheduled task because according to the status the task is 'running'. During deployment Octopus disables all scheduled tasks before deploying several console applications as scheduled tasks. In our organization Octopus is used to deploy on-premise web applications and background tasks on a Windows Server.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |