best practice of build life cycle (label/build/issue resolution) with TC?

Is there a common, or commonly practiced complete build life cycle used with
TeamCIty? JetBrains product seem to be a good example of what I'm looking
for information about.
A process I'd like to find out about is:

  • build (with a controlled build number, as provided by TC)

  • controlled labeling in CVS (which does not have change set numbers)

  • release to test (more than just the automated unit tests performed as part of the build)

  • automatically linking between builds and resolved/closed issues (i.e. can TC pick up information in check in of fixes against issues in JIRA?)


I hope this makes sense and that someone can shed some light on working practices.

Cheers,

Bonny

Please sign in to leave a comment.