Skip to main content
Jump to: navigation, search

Jetty/Release Checklist


Complete these steps to determine whether a staged release is set to go.


Download the staged releases for jetty(x, x+1):

wget[reponumber]/org/eclipse/jetty/jetty-distribution/[jetty-version]/ jetty-distribution-7.[jetty-minor-version].tar.gz
You must perform the following steps for each release that you are testing.

Testing Jetty

1. Extract the release(s) to a directory of your choice.

2. Start jetty.

cd [installdir] ; java -jar start.jar OPTIONS=rewrite etc/jetty-rewrite.xml etc/jetty-ssl.xml

No exceptions? Good. Proceed. Otherwise investigate.

3. Open http://localhost:8080/ in your favourite browser.

You should see the test.war webapp.

4. Go through ALL the tests and verify that everything works fine.

5. Verify that hot deployment works.

touch [pathToJettyDistribution]/contexts/test.xml

6. Verify that test.war is redeployed in STDOUT.

Testing CometD

1. clone git://

git clone git://

2.Edit pom.xml and update jetty-version and repository URL to match the current staged release.

      <id>Jetty Staging</id>

3. Build cometd.

mvn clean install

4. Be patient.

5. Run the loadtest as it is described here: Keep the default values, but make sure that you raise the client setting to 1000. We might change the default to 1000 (currently 100). Run the loadtest until JIT compilation time is close to zero value (after about 10k calls).

Make sure that performance results are reasonably fast.

6. Deploy cometd.war to the webapps directory of the jetty-distribution tested above.

cp cometd-demo/target/cometd-demo-[version].war [pathToJetty]/jetty-distribution-[jetty-version]/webapps/

7. Start jetty and make sure there are no exceptions.

cd [pathToJetty] && java -jar start.jar

8. Go through all pages of the demo and test them.


9. All tests green? Yeeeaaaaay!

Back to the top