InfoQ Homepage Continuous Integration Content on InfoQ
-
Run Code Run: Hosted Continuous Integration
RunCodeRun is a hosted continuous integration service for Ruby projects on GitHub, developed by Relevance. We take a first look at the project and talked to its developer Rob Sanheim.
-
What’s Planned for Visual Studio Team System 2010
Bill Maurer, Developer Technology Specialist at Microsoft, held a conference presenting what new features Visual Studio Team System 2010 (VSTS) will have in the following key domains: Team Foundation Server, Source Control, Project Management, Testing, Development and Architecture.
-
Bamboo Continuous Integration Server Adds Amazon EC2 Build Agents
Continuous Integration (CI),test first development and daily builds are fundamental agile practices. Together they support high performance teams, but also generate a significant, often variable demand for resources. Atlassian's Bamboo CI Server 2.2 includes a feature to Run Builds Remotely in Amazon EC2.
-
Crowdsourcing JavaScript Integration Testing with Test Swarm
John Resig creator of the jQuery JavaScript library, has released Test Swarm, a platform for distributed continuous integration testing for client-side JavaScript. Frustrated with traditional JavaScript testing environments that don’t scale, John’s new project, aims to provide a systems for outsourcing browser related testing to large groups of people or communities.
-
MSBuild Extension Pack
MSBuild Extension Pack is a collection of MSBuild tasks providing reusable components to perform common build tasks. The recently released version 3.5.2.0 has over 240 tasks including WMI interaction, tokenizing files, and interaction with BizTalk.
-
CruiseControl.NET 1.4.3 Released
A new version of CruiseControl.NET, the popular .NET continuous integration server, is now available. This release includes a new ccnet.config validator and numerous enhancements to the dashboard and CCTray application.
-
Beyond Continuous Integration: Continuous Deployment
The sooner that a feature gets into production, the sooner it starts adding value. The quicker a system can change in response to user feedback, the easier it is to keep the users happy. Timothy Fitz and Joe Ludwig have recently published articles that describe practical implementations of continuous deployment, a process that reduces the release cycle from weeks to minutes.
-
Faster Test Runs With Clover's Test Optimization
The recent release of Clover 2.4 highlights a new "Test Optimization" feature that offers to speed up CI builds and allow developers to spend less time waiting for their tests to run. The feature leverages "per-test" coverage data to selectively run only the tests impacted by your code changes.
-
ThoughtWorks Releases Cruise: Continuous Integration and Release Management System
Continuous integration is an agile practice in which each code change committed is automatically built and tested, reducing the cost of bugs by catching many of them as soon as they are introduced. Today, ThoughtWorks released Cruise, extending continuous integration to application testing and deployment. Cruise runs on Windows, Mac OS X and Linux, and includes support for .NET, Java, and Ruby.
-
CM Crossroads on SCM for Small Teams
Agile brings to organizations, among other things, small teams coupled with constant change. Navigating this effectively requires understanding what this means to Software Configuration Management practices. The July edition of CM Journal's "cm//crossroads" is dedicated to helping people meet this challenge successfully.
-
Rewards to Improve Team Habits?
Sometimes teams have trouble starting new habits: writing unit tests, fix compiler warnings, not breaking the build. How do we help the team change these habits? Clint Shank designed a game to help people transition.
-
Subversion 1.5 released
Subversion, a mature open source version control system used by many open source projects, has just released version 1.5. New features include: merge tracking, sparse checkouts, and conflict resolution in the command line client.
-
Agile Version Control for Multi-Team Development
Many agree that the minimum set of Agile practices includes disciplined version control. In particular, when several development teams work in the same codebase, to ensure there's a clean, releasable version at the end of every iteration, they need a plan. Henrik Kniberg's proven scheme is a useful guide for teams. This detailed paper includes the entire method and even a cheatsheet.
-
Continuous Integration And Version Control for Databases
After asserting that one must, as a rule, always version their database work, Scott Allen detailed an approach to making the best of versioning databases. Allen presented a comprehensive, practical approach to creating a baseline, using change scripts to manage schematic revisions, controlling programmatic database objects, and handling branching and merging.
-
Does "Done" Mean "Shippable"?
There has been a lot of discussion on various agile forums and blogs about the difference between 'Done' and 'Shippable'. It might sound like both mean the same, however discussions on the lists and various blogs suggest that these are still widely misunderstood, mis-used terms. Here's a roundup of recommendations about how to handle "Done."