sorted by: recent | see : popular

Content Tagged with ContinuousIntegration + subversion

Building a software product involves many complex processes, roles and deliverables, which need to be managed to fit together. Streamlining these processes is a major effort, particularly when there are many people involved. A truly comprehensive software configuration management (SCM) solution manages not just the simple versioning of your source code files - it also facilitates support for Continuous Integration, accurate and predictable build management, provides the ability to deploy the end result as well as offering approval processes and manages the complex run-time dependencies of many applications today.

You can setup continuous integration and automated deployment for your web application using CruiseControl.NET, Subversion, MSBuild and Robocopy. I will show you how you can automatically build the entire solution, email build report to developers and QA, deploy latest code in IIS all using CruiseControl.NET every N minutes.

Although many development teams use version-control systems to manage code changes, they can struggle when developers code off the same code base, in parallel. In this Automation for the people installment, automation expert Paul Duvall shows how to effectively tag, branch, and merge source code using the open source, freely available Subversion version-control system.

SVN Revision Labeller is a plugin for CruiseControl.NET that allows you to generate CruiseControl labels for your builds, based upon the revision number of your Subversion working copy. This can be customised with a prefix and/or major/minor version numbers.

Pulse is an automated build server that is simple to set up and easy to use while providing advanced features such as distributed builds as well as many other productivity enhancements.

Brian Liles, 20080908. I’m doing this with a Ruby on Rails slant, but the ideas presented here are applicable to other situations: 1. Upgrade Test::Unit, 2. Try out some TDD, 3. Upgrade your fixtures, 4. Install (and learn and use) a SCM, 5. Investigate Continuous Integration, 6. Know your code, 7. Automate your deployments, 8. Collect some statistics, 9. Read other people’s code, 10. Blog about it