BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Continuous Integration Content on InfoQ

  • Is Pipelined Continous Integration a Good Idea?

    Sometimes, when the team and/or code-base get large, the CI server starts to slow down. The cycle between builds grows and the feedback degrades – a build may take an hour or more to respond with a pass/fail, and by that time several people may have checked in their code into an already broken build. To address this issue, many teams “pipeline” their CI - but is this a good strategy?

  • Team Foundation Server 2008: Out-Of-The-Box Support for Continuous Integration

    Along with Visual Studio 2008 Microsoft will be releasing a new version of TFS (Team Foundation Server). TFS 2008 will provide extended support for Continuous Integration.

  • Review: Continous Performance Management

    Steven Haines from Quest has published an article demonstrating the use of performance analysis tools in the continuous build cycle as best practice and makes some thought provoking points about the cost of not doing so.

  • Book Excerpt: How to Improve your Continuous Testing

    Continuous Integration has become a standard development best practice - but it's not always done well. Tests take up much of an application's build time, and poorly constructed test suites can cause long builds, whereupon teams start to circumvent agreed-upon CI practices just get the time to code. InfoQ presents advice and examples in Chapter 6: Continuous Testing from a new CI book.

  • Article: Implementing Automated Governance for Coding Standards

    Most development organizations of a significant size have some form of coding standards and best practices. Simply documenting these standards and keeping them up to date can be a significant challenge and enforcing them even harder. Our organization has found that enforcing coding standards and best practices in an automated fashion through our build process has been highly effective.

  • ThoughtWorks launches CruiseControl Enterprise

    ThoughtWorks has launched a CruiseControl Enterprise project to enhance and support CruiseControl. InfoQ speaks with Paul Julius, Product Manager of CruiseControl Enterprise about the new features and the relationship between CruiseControl Enterprise and the open-source distribution.

  • Agile Tools Usefulness Debated

    The Agile Journal's April issue examined how tools are being used in Agile projects. There are articles that are pro-tools, anti-tools, and a debate between Ron Jeffries and Ryan Martens.

  • Continuous Integration Server QuickBuild 1.2 Released

    PMEase has released version 1.2 of QuickBuild, a commercial version of the open-source continuous integration server Luntbuild.

  • TeamCity 1.2 Released - Continuous Integration Server for Java and .NET

    JetBrains has released version 1.2 of TeamCity, a continuous integration server which now includes a plugin for Visual Studio 2005, along with support for Visual SourceSafe.

  • Continuous Integration Server AnthillPro 3.1 Released

    Urbancode has released AnthillPro 3.1, a commercial version of the Anthill OS open-source continuous integration server.

  • Use Test Categorization for Agile Builds

    Everyone agrees that developer testing is important, but ever-lengthening build times can discourage running these tests with optimal frequency. Andrew Glover's new IBM DeveloperWorks article outlines a strategy to use categorized tests to ensure end-to-end system soundness, including examples on how to automatically sort and run tests by category, resulting in dramatically reduced build times.

  • Gauntlet: Borland's Continous Integration server with defect isolation and trending

    Borland in early October released a beta of Gauntlet continous integration server. Like any continous integration server, Gauntlet automates build and testing but also provides change sandboxing, reporting and trending, failure correlation, replay alongside existing repositories, and easy access to build, test, and run previous project versions.

  • CruiseControl.Net 1.1 Released

    The team behind CruiseControl.Net has released version 1.1. CrusieControl.Net provides continuous integration capabilities for .NET developers. A cornerstone of Agile development, continuous integration is used to ensure that team members stay in sync and the integration issues are discovered early. This marks the first major release of CuriseControl.Net in nearly a year.

  • JetBrains Releases IntelliJ 6.0 and Team City 1.0

    Jetbrains has released version 6.0 of their IntelliJ IDE and version 1.0 of their new TeamCity continuous integration server product. IntelliJ 6.0 improves support for EJB 3.0 and adds support for several new frameworks such as GWT. TeamCity includes pre-commit testing to ensure that incoming code changes do not break the build.

  • Choosing a Continuous Integration Server

    In the first of a series of articles on continuous integration Paul Duvall compares three popular continuous integration servers, Continuum, CruiseControl, and Luntbuild. He considers criteria such as features, longevity, target environment, and ease of use.

BT