O'Reilly logo

Jenkins Continuous Integration Cookbook by Alan Berg

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

Configuring Jetty for integration tests

Jenkins plugins that keep a history of tests are normally consumers of the data generated within Maven builds. For Maven to automatically run integration, performance, or functional tests, it will need to hit a live test server. You have two main choices:

  1. Deploy your artifacts, such as .war files, to a live server. You can do this using the Maven-wagon plugin (http://mojo.codehaus.org/wagon-maven-plugin/), or through a Jenkins plugin, such as an aptly named deploy plugin (https://wiki.jenkins-ci.org/display/JENKINS/Deploy+Plugin).
  2. Run the lightweight Jetty server within the build. This simplifies your infrastructure. However, the server will be run as part of a Jenkins Job, consuming the potentially scarce ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required