9

I can't find any example or article how can the continuous delivery pipeline look like when we are using Spring Boot + Jenkins.

In Java EE I usually do it like this:

  • Push changes to repository
  • Jenkins checks for changes every 5 minutes
  • if there was a change, Jenkins pulls the sources and run maven build
  • using wildfly maven plugin I run redeploy on server

And generally I wonder what to do in last point when I'm using Spring Boot. Application is packaged into single JAR and run in separate process so in Spring Boot there is actually no such thing like redeploy. Do I have to write some script to kill old process first and then run the new artifact? Or maybe there is something like "spring boot cli" where I could manage all running spring boot apps?

swch
  • 1,432
  • 4
  • 21
  • 37

1 Answers1

9

You need to kill old process and run new process as a service. It is all very well explained here Spring Boot application as a Service.

There is nice ssh plugin for jenkins that we use : https://wiki.jenkins-ci.org/display/JENKINS/Publish+Over+SSH+Plugin

  1. Copy jar to the server
  2. Stop old service
  3. Run new service

EDIT : Added Spring boot reference for running spring boot as a service - http://docs.spring.io/spring-boot/docs/current/reference/html/deployment-install.html @Vaelyr

Community
  • 1
  • 1
SeaBiscuit
  • 2,553
  • 4
  • 25
  • 40
  • 2
    Link to official documents as well. I am personally using it as init.d service, works nicely: http://docs.spring.io/spring-boot/docs/current/reference/html/deployment-install.html – Vaelyr Dec 02 '16 at 09:52
  • Is there any way to do paralles deployment like Tomcat container does? – NiBE Feb 13 '19 at 16:17