Extending the basic setup

When you exit from the command prompt or shell that started the process that we looked at previously, the Jenkins instance will stop with the exit, so for anything beyond a very quick ad hoc test, some form of initialization or process management script is highly recommended. Such a script can also be easily tailored to perform a few "nice to have" functions for you, for example, things such as these:

  • Starting up at system boot time
  • Catering to stop|start|restart|status requests
  • Redirecting console output to a log file so that you can monitor it for issues
  • Running as a background/daemon process
  • Running on a nonstandard port by setting the --httpPort= parameter, in cases where port 8080 is already used by another application ...

Get Extending Jenkins now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.

Start your free trial