TC 3.1.1 - bug fixes - what are they

Hi,

Shot in the dark...

We are running TC3.1 build 6760 with 4 build agents. We had a problem this morning where our tagged UAT build tagged the latest code, but used an old version of one of the config files. It was fixed by clicking the clean sources button for the agent. But we have clean before build selected for the build.

I don't suppose this is a problem that was fixed in 3.1.1 ?

Thanks,
Chris

6 comments
Comment actions Permalink

Doh - found the release notes - forgot to search by version number :(



Does not seem to be a bug for that problem... I guess we will need to watch the files closely to ensure changes are being picked up.

Regards,
Chris

0
Comment actions Permalink

Hello Chris,

You might be hitting this issue: http://jetbrains.net/tracker/issue/TW-5016

Best,
Andrei

CK> Doh - found the release notes - forgot to search by version number
CK> :(
CK>
CK>
CK>
CK> Does not seem to be a bug for that problem... I guess we will need
CK> to watch the files closely to ensure changes are being picked up.
CK>
CK> Regards,
CK> Chris


0
Comment actions Permalink

Hi,

Yes, that looks similar - I think there were a few concurrent changes at the same time. Although we have clean before build - so I was assuming that means all files are fully downloaded from scratch for each build or does it just mean the clean target is run?

Any news on a fix in the version 3 branch? Or is there a date for v4... or is the v4EAP sufficiently stable to use now? Obviously. as per the comments, this is quite a critical issue.

Thanks,
Chris

0
Comment actions Permalink

Chris,

TW-5016 touches several issues and apart from the known ones I mentioned in the comments (they are already fixed in the current 4.0 branch sources), the problem has not been identified. Unfortunately, with no additional data we are be unable to fix it.

If you problem reproduces, please create a new issue in our tracker with all sorts of details on it from the TeamCity version and build configuration/VCS settings to the debug logs.

Any news on a fix in the version 3 branch? Or is there a date for v4... or is the v4EAP sufficiently stable to use now? Obviously. as per the comments, this is quite a critical issue.


4.0 release is scheduled for the late fall. EAP should be quite stable, but we do not perform extensive testing of EAP releases so some not very common functionality can be broken.

--
Best regards,

Yegor Yarko
Project Manager
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

Hi,

Can the v4 installation be installed beside the v3 one?

Or installed in a way that means we can rollback...

Thanks,
Chris

0
Comment actions Permalink

Chris,

As we are introducing new features that require changing the underlying database structure, once you upgrade to 4.x branch, no downgrade is possible. For the same reason, generally, you cannot downgrade from higher TeamCity version to a lower one.

If you decide to upgrade, please backup your data before the upgrade so that you can roll back at least to the previous state.

If you just want to try TeamCity 4.x in parallel, you can create a copy of your settings/database and try it out.

--
Best regards,

Yegor Yarko
Project Manager
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0

Please sign in to leave a comment.