j2ee-rest-jersey-jetty-tomcat-maven-jenkinsfile

Proving ground for J2EE 7 RESTful web services. Jersey will provide grunt for REST. Jetty local development but Tomcat for Integration testing. Maven build framework with Jenkins organising. If that is not enough then SonarQube and Jacoco for code coverage.

If you just want to play with and extend the JAX-RS REST hello world example then install Developer Tools, download sources and go have fun
If you want to have fun with Jenkins 2.x Pipeline then install Deployment Pipeline tools.
If you want to have fun with Jenkins 2.x Pipeline Jenkinsfile or Zero-downtime Deployment (and Rollback) in Tomcat then you need:
- to fork this repository to edit your Jenkinsfile
- the Developer tools
- the Deployment tools
This plaground was setup in July 2016
Please do send me fixes for my stupid errors.
I did not automate the install of Deployment Pipeline tools. Vagrant and Puppet poc work has been covered in my other projects.
- https://github.com/lastnitescurry/dctm-vagrant-puppet
- https://github.com/lastnitescurry/documentum71

Development

Once you have the sources downloaded and developer tools setup execute the follow to compile and run on Jetty for local development

mvn clean compile jetty:run

NOTE: For hot reload to work, Eclipse->Project->Build Automatically should be enabled

The helloworld REST service will be availabe on:

http://localhost:9998/app/hello

and the default index.jsp will respond on:

http://localhost:9998

To do a SonarQube analysis use:

mvn clean test sonar:sonar

And to build a distribution package:

mvn clean package

Developer Tools

Deployment Pipeline

The following tools are used in my hello world deployment pipeline:

I use the following custom launcher scripts for the tools:

F:\Apps\Nexus\NexusRunner.cmd
F:\Apps\SonarQube\sonarqube-5.6.1\bin\windows-x86-64\StartSonar.bat
F:\Apps\Tomcat\TomcatRunner.cmd
F:\Apps\Jenkins\JenkinsRunner.cmd

Applications use their default ports hence are available on:

Applications are used as is except for Jenkins which needs to be informed of where tools are located:

JDK
Maven
- Use M3 as maven client name
Git Client

You need to configure at least one job in jenkins! I have two. One for inline pipeline script and one reading pipeline script from source code control

Once everything is configured, build and deploy war files to tomcat via your jenkins job(s). The app will be available on:

florisjanssens / j2ee-rest-jersey-jetty-tomcat-maven-jenkinsfile Goto Github PK