concept continuous integration in category java

appears as: continuous integration, continuous integration
The Well-Grounded Java Developer

This is an excerpt from Manning's book The Well-Grounded Java Developer.

Table 7.2. Project areas suited for domain-specific, dynamic, and stable layers

Name

Example problem domains

Domain-specific Build, continuous integration, continuous deployment Dev-ops Enterprise Integration Pattern modeling Business rules modeling
Dynamic Rapid web development Prototyping Interactive administrative and user consoles Scripting Tests (such as for test- and behavior-driven development)
Stable Concurrent code Application containers Core business functionality

Continuous integration is where individuals in a development team integrate their work frequently, following the mantra of “commit early, commit often.” Each developer will commit their code to version control at least daily, and the CI server will run regular automated builds to detect integration errors as quickly as possible.[2] Feedback is often displayed to the team with a happy/sad display on a large screen.

JUnit in Action, Second Edition

This is an excerpt from Manning's book JUnit in Action, Second Edition.

  • Integration platform— This platform builds the application from its various components (which may have been developed by different teams) and ensures that they all work together. This step is extremely valuable, because problems are often discovered here. It’s so valuable that we want to automate it. It’s then called continuous integration (see http://www.martinfowler.com/articles/continuousIntegration.html) and can be achieved by automatically building the application as part of the build process (more on that in chapter 11 and later).
  • The reason is to make you understand that continuous integration is an important concept in the modern software development lifecycle and that it makes absolutely no difference which tool you use, but it makes a great difference whether you use CI or not.

    GWT in Practice

    This is an excerpt from Manning's book GWT in Practice.

    Last, but not least, there is formal testing support. GWT gives you a means to test your code by writing test cases either as Java or as JavaScript. We���ll cover this in more detail in chapter 8, which is devoted to testing and other aspects of code quality, such as continuous integration.

    In this chapter, we’re going to follow up on some of the tasks related to building, packaging, and deploying that we addressed in the last chapter, with a focus on testing and automating builds. Along with testing, we’ll also touch on benchmarking in a GWT context. Once we have all the pieces in place, we’ll work through a sample project that utilizes Maven and a continuous integration (CI) server, in order to take full advantage of the complete process. All of these concepts go hand in hand because testing and metrics should ideally be part of an automated build process that’s CI managed.

    The concepts of testing, benchmarking, and continuous integration are fairly well accepted tenets in any good software development practice, regardless of language or technology. Even though we cannot hope to cover these broad subjects comprehensively in a single chapter, we’ll go into some detail on the general principles, and we’ll focus on getting these things working with a GWT project.

    Armed with an understanding of what it takes to support and configure code coverage in GWT, the next step is to automate the process. An automated build that includes tests, coverage data, and reports is critical when it comes to continuous integration.

    Continuous integration (CI) is something we’ll tackle in section 8.3 of this chapter, but before we get there we need to be running a build process that will work in a CI environment. Most CI products support a variety of build tools, with Ant and Maven being the most widely used. For GWTTestMe, as we have done with other projects up to this point, we’re going to use Maven 2 and the GWT-Maven plugin.