views:

34

answers:

0

Hey guys,

I'm wondering if anyone can provide any constructive feedback about the current deploy procedure we use where I work:

  • We have three copies of the code in seperate Mercurial repositories: Dev, PP (Pre-Production) and Live. Changes are made on Dev, pushed to PP for User Acceptance Testing then pushed to Live once accepted.
  • Builds are done using TeamCity to created a precompiled version, changes are not made by hand (everything has to go into source control). The builds are provided as zip archives as artifacts in TeamCity. Class libraries are build on demand and linked into the main build as dependencies, Bin files are only kept in source control where we don't have source code.
  • Builds are copied to live enviroments by hand using RemoteDesktop, and unzipped. web.config files are kept from build to build and edited by hand when needed (Live passwords etc. are not kept in source control)

The current things I think are missing are proper Unit- and Integration-testing (ideally using NUnit and something like selenium), but I'd like to see what the community thinks.