Scheduled builds disappear if scheduled too far in the future
Hi,
This was going to be a post about a scheduled build disappearing from TeamCity, but I've figured out why that happens. So instead this will be a bug report (or at least some feedback as I don't think it's the expected behavior).
Build removed from queue: 37717, comment=The build could not start and was automatically removed after 360 hours in the queue.
So any build you schedule that's over 15 days in the future will disappear from TeamCity without warning. Ideally it should not be removed at all and just run at the expected time. Otherwise you should get an error message if you're trying to schedule a build too far in the future, or you should see it as “failed” or “canceled” in the frontend if it expires.
The current behavior is a perfect recipe for questioning your sanity on a Monday morning, wondering whether you were dreaming every time you saw that build in the queue over the past few weeks.
Cheers
Please sign in to leave a comment.
Let me reproduce it and I'll get back to you with an update as soon as possible.
Best regards,
Anton
I reproduced the issue. Thank you for reporting it!
Please refer to the YouTrack issue for further details: https://youtrack.jetbrains.com/issue/TW-93043
For the workaround, it is possible to use the teamcity.buildQueue.staleBuilds.timeoutHours internal property to change the period after which the build gets deleted from the queue: https://www.jetbrains.com/help/teamcity/server-startup-properties.html#TeamCity+Internal+Properties
Please let me know if you have any additional questions.
Best regards,
Anton
Hi Anton,
Glad to hear you were able to reproduce it and thanks for the workaround!