Is it possible do make a "historical" build? ("rebuild" a version)

Is it possible do make a "historical" build?
On time x I build a version, then I change the build configuration (e.g. add a new build step, changing some properties, ...). Is it then possible to build again with the configuration at time x? A manual change of the revision in the version control system (Subversion) would be no problem, I need "only" the original configuration of teamcity.

8 comments
Comment actions Permalink

Hello, if click a run custom build dialog and select changes tab, you can select a change list that was actual at a certain time. http://confluence.jetbrains.com/display/TCD8/Triggering+a+Custom+Build

0
Comment actions Permalink

This looks after the desired solution. (I'll try it in our test system)

Currently we use anthillpro. urbancode was acquired by IBM, therefore we are looking for an alternative.

We have the following use case:

We create a final version 1.00 build 1000. Then we omit some build numbers to create a bugfix version later.
The first alpha version 1.01 (after the final 1.00) has, for example, the build number 1200. (200 builds be omitted)

Now, if the bugfix version is created, a maintenance branch is created in the repository and the configuration at the time of build 1000 is taken to build a new version (using the build number 1001).

Is this also possible with TeamCity or is there an alternative. In our case, we need starting from the configuration at the time build 1000 at least to change the VCS URL (from trunk -> maintenance_branche).

0
Comment actions Permalink

I'm not sure I completely understand the case, but will try to answer:

Build configuration has parameter called build counter. Every build increases this value by 1.

Imagine, we start a new build configuration (master/trunk) and we set its initial build counter to 1000. After a certain time, we release a build 1.0 build 1050. Then we copy this configuration to branch and set build counter to 1051 in branch and increase build counter to 1251 in master.

Is this what you are asking?

0
Comment actions Permalink

It's almost my question.

The difference is that we want to increase the build counter to 1251 and copy at a later date the configuration. We want to create a copy only if we really have to to create a branch version.

Thus, the question is whether it is possible from a historical version (build 1051) to copy the team city configuration.

0
Comment actions Permalink

Unfortunately, TC configuration is not versioning right now (however, this feature is desired by our customers and we are moving into this direction). So, it's not possible to recover configuration settings that were actual, when build # was 1051.

There's a workaround, if don't change settings often - we have an audit, where we log all changes made to build configuration, vcs roots, etc. So, you can see what in particular was changed since that time.

Also, you can just copy and archive the configuration at a time you increase the #, so it's not visible and no builds running, until you enable it again.

0
Comment actions Permalink

Hi Sergey - thanks for the quick reply!

If changes are made in a template, they are displayed in the audit of the project? Or this should be checked in several places (project, template, ...)?

The variant with copy and archive we currently use. However, we want to reduce this effort.

0
Comment actions Permalink

Yes, changes to template are also reflected in audit.

0
Comment actions Permalink

Thank you. Not optimal, but as a workaround it should work for us.

(How can I mark the question as "answered"?)

0

Please sign in to leave a comment.