All builds yields 'This build is outdated' (4.5)

After changing the build number format (not the counter) of a build configuration all my configurations now get the
This build is outdated  status when Running.

No database entries are created any more.
Reverting back to old build number format does not fix the issue.

I run the default 'out of the box' database.

Any ideas on how to fix this?

Cheers

10 comments
Comment actions Permalink

Could you please submit a bug report to http://jetbrains.net/tracker and attach teamcity-server.log and teamcity-vcs.log files?

0
Comment actions Permalink

Uanble to log on to tracker. Always Disconnected.
Updated to IE8 today. Related?

Anyway, logs attached here:

Cheers



Attachment(s):
logs.zip
0
Comment actions Permalink

Do you experience problem with builds having ClearCase VCS roots?

0
Comment actions Permalink

These days I sort of run VCS free, because I am not able to get ClearCase VCS to work.





 


http://www.jetbrains.net/devnet/message/5236820#5236820

So, I sort of just use TC as a manual build trigger and build-report+artifact presenter.

Build repors are OK, output from my command line script are OK, also the builds they produce, but the builds/Run don't show up in TC.

Cheers

0
Comment actions Permalink

Could you please provide a screenshot of build configuration home directory with a running build marked as outdated?

0
Comment actions Permalink

Enclosed.
Note blue highlight build number format change.
Have tried restoring to original.
Affects all build configurations.
Counter is with red undeline.
Blue arrow points to notifier saying the build is outdated - refer to 4.2.2 when howering mouse over yellow triangle.
When Run finishes, [all history] is unchanged. No trace of build #19

Cheers



Attachment(s):
Capture.JPG
0
Comment actions Permalink

Hello Ole,

  Could you please provide value of buildId for builds like on screenshot? You can get buildId value from the link to build results.

  Another question is are there chances that the build in the history was built with VCS root attached and now VCS root is not attached?

  Regards,
  KIR

0
Comment actions Permalink

This is the link to the build logs during the Run:buildId=7

http://argo-bot:8111/viewLog.html?tab=buildLog&buildTypeId=bt13&buildId=7&all=true

Yes, I have detached several VCS roots after upgrading to 4.5 since all my VCS connections failed after that upgrade. (ClearCase dynamic views)
http://www.jetbrains.net/devnet/message/5236820#5236820

Any way to recover, or should I reinstall?

Update: guess the 'Build outdated' is not the root cause, because not all build configs get this warning, but no changes are made to the History (aka database).
My last recorded build was april 29. so that is when updates stopped.

Cheers

0
Comment actions Permalink

Hello Ole,

  It looks that there is really something strange has happened with your database.
  Looks like at some moment, build counter was reset to 1. And since than, all builds got invalid buildId.
  I suggest you to wipe current build history (no need to re-create build configurations).

  To cleanup the database, follow these steps:

  1. Backup your artifacts from .BuildServer/system/artifacts directory, if needed
  2. Remove .BuildServer/system/[artifacts|messages|changes|buildserver.*] files and directories
  3. Restart TeamCity. You configurations will remain, but you'll have to recreate user accounts and build history will be empty.


  Kind regards,
  KIR


0
Comment actions Permalink

That did the trick.

Don't know why this happened, but it could of course be related to the fact that our Linux box crashed a week back.
Anyhow, this is maybe a good point in time to set up a mysql instead

Cheers

0

Please sign in to leave a comment.