Menu
What tools would you recommend for setting up CI for build and deployment of multiple websites built on DotNetNuke using SVN for source control?
We are currently looking at configuring Cruise Control to work with NAnt, NUnit, NCover and Trac as a test case. What other combinations would worth investigating?
We have full control of our development environment so using some form of CI is certain here but I would also like to convince our production services team that they can reliably deploy to the system test, uat and even production environments using these tools.
299
Source Control IntegrationSubversion functions both for source control and continuous integration, and BuildMaster supports both. The most common use-case when working with Subversion is getting the latest source code (e.g., trunk ) then building it and creating a build artifact.
Continuous integration in five stepsStart writing tests for the critical parts of your codebase. Get a CI service to run those tests automatically on every push to the main repository. Make sure that your team integrates their changes everyday. Fix the build as soon as it's broken.
The integration of Subversion with Rally Software and Jenkins gives the project management team complete control over the codes being committed in the source code repository. It also creates complete traceability for all work items in Rally Software.
Essentially, what you can do is setup a svn commit hook that sends a signal to Jenkins to kick off a build. Jenkins will then (given the right build setup) pull the freshly-committed code and run the build.
Take a look at Hudson. It's highly customizable, and, IMHO, easier than CruiseControl.
128
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
