This means that a Jenkins deployment script will pull code from GitHub, build it using the JDK, and publish it locally rather than to some remote server. In this example, Jenkins, the JDK, and Couchbase Server will all reside on the same machine. There are a few requirements that need to be met in order to be successful with this guide. We’re going to start slow to get a better understanding. To be clear, I won’t be explaining how to use the Couchbase Connect 2016 application, which I’m calling GitTalent, with Jenkins as it is a bit more complicated. So how did I leverage Jenkins deploy this Java application? We’re going to see how to create a JAR file using Jenkins, resulting in a continuous deployment pipeline that includes building and deploying to a server. In case you haven’t seen it, the keynote demonstration given at Couchbase Connect 2016 used Jenkins to build and redeploy the Java backend and Angular frontend every time a change was detected on GitHub.
Lately I’ve been working a lot with Jenkins to run Java JAR files for continuous deployment of one of my applications.
