I am running jenkins in a tomcat server which is in a physical VM, so if the vm goes down for any reason then i will not be able to access my jenkins site.

Is there a way to tackle the above issue, how you are running your jenkins currently in your org to make high availability possible during disasters?

Suggestions and ideas are always welcome.

CodePudding user response：

If you run your Jenkins on a physical VM then there is nothing you can do about availability. If your VM goes down then Jenkins goes down. This is a problem if your organization (like mine) regularly updates VMs which causes them to shut down. Jenkins already provides support to work around this issue (to some extent) by running Jenkins as a service which starts on startup. So if your server restarts, then Jenkins restarts as well. However, this will means that any running builds are interrupted. The better option is to move your Jenkins away from on-prem machines altogether. You can run Jenkins on almost any cloud platform by spinning up a VM and having Jenkins run on it, or you could use ready-made solutions that allow you to manage infrastructure as code on the cloud.