Continuous Delivery Blueprint
Continuous Delivery using Subversion, Jenkins and RapidDeploy to configure and deploy the JPetStore application to WebSphere ND
This demonstration is designed to detect a code change in Subversion to trigger a build in Jenkins. Here are the steps demonstrated:
Here is a summary of what this demo will achieve.
- Change the CSS of the JPetStore application to change the background colour.
- Configure Jenkins Job to detect this change and initiate a build
- Following the successful build, configure the Jenkins job to perform a post-build step to call a RapidDeploy project (Copy-JPetstore-To-RapidDeploy) to copy the built artifact (ear file) from the Jenkins build location to the RapidDeploy server.
- Call a post-build action to create a package for the WebSphere-85-Configure-Deploy-JPetstore-40.
- Call a post-build action to deploy the created package for the WebSphere-85-Configure-Deploy-JPetstore-40 to the WebSphere cell
- See the change in the running JPetstore application
If the WebSphere cluster does not exist, it is created. If it exists, it is updated.
The server in the project is Linux, but can be cloned to Windows if required.
The project is preconfigured with three target environments, Dev, Test and Prod.
Specific configuration items are changed between environments, by use of Data Dictionary items.
- A Jenkins server preconfigured with the RapidDeploy plugin for Jenkins (v3.7).
- An SCM tool such as Subversion with JPetstore or another application configured
- A running WebSphere 8.5 Cell on Linux with a Deployment Manager and a federated nodeagent. Ideally this will have been created using the previous WebSphere demo projects.
- You will have run the previous demo, and have the WebSphere-85-Configure-Deploy-JPetstore-40 already configured for your WebSphere cell, in your RapidDeploy instance. This project will be successfully deploying the JPetstore ear file, or another application, to your WebSphere cell.
- You will need to import the Copy-JPetstore-To-RapidDeploy-40.zip project into your instance of RapidDeploy.
Please follow the RapidDeploy v4.0 – Part 6: Continuous Delivery with Subversion, Jenkins and RapidDeploy YouTube video, in order to see how to configure this for yourself. If you are using a different SCM tool or application, you can still use the demo, but some of your configuration may differ slightly.