Why does TeamCity think an old build is actually the latest build

We had a power outage yesterday (no UPS on the build server unfortunately) and TeamCity thinks that the last build that ran before the outage is actually the latest build. In fact all the builds that ran before the outage are listed as more recent than all the builds that ran after the outage.

Hopefully the problem will work itself out, but is there a way of telling TeamCity to untangle itself?

Thanks,
Patrick

2 comments

Hello,

Try to restart TeamCity. If it will not help, please submit a JIRA request
with screenshot taken from your history. TeamCity sorts build by their
internal id. This sorting should correspond to the build start time. The
build start time is shown in the history while the build id is in the links
to the build pages.

--
Pavel Sher
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"



"Patrick Wilkes" <no_reply@jetbrains.com> wrote in message
news:15367947.1197342006026.JavaMail.itn@is.intellij.net...

We had a power outage yesterday (no UPS on the build server unfortunately)
and TeamCity thinks that the last build that ran before the outage is
actually the latest build. In fact all the builds that ran before the
outage are listed as more recent than all the builds that ran after the
outage.

>

Hopefully the problem will work itself out, but is there a way of telling
TeamCity to untangle itself?

>

Thanks,
Patrick



0

Hi there
Thank you, I've done that.

You are right, the internal buildId was reset (probably to zero) after the forced shutdown caused by the power outage, so all builds after the outage have lower buildIds that builds from before the outage.

Patrick

0

Please sign in to leave a comment.