Project Import from TC 9.0 to TC 9.1.4 version

I found that if you try and import from any version other than the target version it'll ask you to update and re-export the projects/settings.

Hello Syed and Tim,

Tim is right. If you want to import projects from server to another, the versions of the source and target TeamCity servers have to be the same. For more details see the section in documentation.

Hello Alina,

Do the versions have to match *exactly*, i.e. all three parts of the version number must match, or is it sufficient that, say, the first two parts match?

Thanks,
Mike

Hi Mike,

Only major and minor versions should be the same (X and Y in X.Y.Z TeamCity version). I've update the documentation.

Thanks Alina.

Given the potential incompatibiilty of a backup created with TeamCity version X1.Y1.<don't-care> when importing into TeamCity version X2.Y2.<don't-care>, it would seem advisable that for each backup we make, we record the version number of TeamCity that was used to create the backup. Perhaps a good idea would be to have the default "Backup file" name in the UI to include the TeamCity X.Y(.Z) version numbers?

Mike

Hi Mike,

The most common case is to restore from the latest backup. Version.txt file is stored in the backup, so you can check the backed up TeamCity version. At the same time you can configure a custom backup name in TeamCity UI or when calling it via REST API.

Will it work for you?

As long as we can identify the version that created the backup - which we will be able to do via the Version.txt file - then that should be adequate for now I think. I suspect we will need to look at automating the backups via the REST API, so we will revisit this then.

Thanks.

Yes, it's recommended to perform the backup process regularly, e.g. automated via REST API.