Best Practice for Archiving State of Build Machine at Product Release
Our release process requires "build system, build configuration and build instructions have been frozen and archived so that the build can be completely reproduced if needed". This is trivial for an old-fashioned script-based build but not so simple for TeamCity. What is JetBrains' recommendation on how best to do this? I've found where I can "archive project" but these same build configurations will live on as we begin work on the next release. I think what I want to do is archive build configurations, not projects, but I don't see a way to do this. Any help greatly appreciated.
Please sign in to leave a comment.
Hi Karen,
There are several possibilities. The first is to create smaller projects that you can archive once a build configuration has to be archived. But the easiest possibility should be to simply enable "versioned settings". That way, once you build a release, you can also tag the commit in the VCS system, and without archiving it in TeamCity you can restore the exact state of the build configuration, which I think is what you are trying to accomplish here.