45 | | 'Checkout'. |
46 | | This is straightforward and simply pulls the latest source into the |
47 | | build directory. |
| 42 | * Checkout: Checks out the latest source into the build directory. |
| 43 | * Build: Uses MSBUILD to build the project, using a custom logger (see [http://confluence.public.thoughtworks.org/display/CCNETCOMM/Improved+MSBuild+Integration here]) and an .xsl file to make the output from the logger useful (based on the msbuild2ccnet.xsl file mentioned on the link) |
| 44 | * Smoke Test: Uses [http://www.codesourcery.com/qmtest qmtest] to run a database of tests, and report the results via bitten. The tests themselves are [http://www.autoitscript.com/autoit3 AutoIt] scripts. |
| 45 | * Package: Finally, if all the above succeeds, use [http://nsis.sourceforge.net/Main_Page NSIS] to create an install package that can be deployed on the target system. |
49 | | 'Build' |
50 | | Here I use MSBUILD to build my project, using a custom logger (see |
51 | | http://confluence.public.thoughtworks.org/display/CCNETCOMM/Improved+MSBuild+Integration) |
52 | | and a .xsl file to make the output from the logger pretty (This is |
53 | | based on the msbuild2ccnet.xsl file mentioned on the link) |
54 | | |
55 | | 'Document' |
56 | | I plan to use doxygen to auto generate documentation from my source |
57 | | code here |
58 | | |
59 | | 'Smoke Test' |
60 | | Using a tool called qmtest (here-http://www.codesourcery.com/qmtest) I |
61 | | have created a database of tests to run. The results are fed back |
62 | | into bitten. |
63 | | The tests themselves are AutoIt (http://www.autoitscript.com/autoit3/) |
64 | | scripts. |
65 | | |
66 | | 'Package' |
67 | | Finally, if all the above succeeds, I use NSIS (http:// |
68 | | nsis.sourceforge.net/Main_Page) to create an install package that can |
69 | | be deployed on the target system. |
70 | | |