My recent project has included a fair number of technologies integrated into our automated build and packaging scripts. Up until this project, I've been using MSBuild target names such as:
RecreateDb, Build, Package, DeployK2, TestSP
On this project we have SQL, K2 Blackpearl, SharePoint, Word 2007 Add-Ins, and a few other bits and pieces, and as each of them has their own pieces which need to be build, packaged, deployed and tested, using the above conventions started to become somewhat confusing so I created the following namespace convention in naming the MSBuild Targets:
(Technology)-(Action)
So for example, we now have:
Db-Recreate
K2-Build, SP-Build, Word-Build
K2-Package, SP-Package, Word-Package, Db-Package
K2-Deploy, SP-Deploy
K2-Test, SP-Test
Here, Package refers to creating a single file containing all the software for that component, so it's usually either a .zip file, a SharePoint .wsp or an .msi. Deploy refers to taking that package and deploying it to the relevant runtime environment.
I made these changes after writing posts My Favourite MSBuild Targets #2: RecreateDb, My Favourite MSBuild Targets #3: DeployReports and My Favourite MSBuild Targets #4: DeployK2, and now favour these new conventions for their clarity, ability to be easily guessed if they are forgotten and the way they mirror class/method naming in code.
I'd be interested to see what other naming conventions people are using in their scripts.