Aller au contenu principal
Development

Self-host Jenkins on a VPS

The veteran, endlessly extensible automation server.

Automate builds, tests and deployments with thousands of plugins and full pipeline-as-code support.

Why self-host Jenkins?

When a team already knows Jenkins or needs a specific plugin, self-hosting keeps build credentials and artefacts in-house.

How to install Jenkins

  1. 1

    Provision a VPS

    Pick a Debian/Ubuntu template and get root SSH in about a minute.

  2. 2

    Install the runtime

    Install Java + plugins (+ agents).

  3. 3

    Deploy the application

    Net what you need from the project’s official source and run it.

  4. 4

    Put it behind TLS

    Reverse-proxy with Nginx and issue a Let’s Encrypt certificate.

  5. 5

    Add it to your backups

    Include the data directory and database in your backup routine before you rely on it.

Practical tips

  • Give Jenkins its own database user with rights only on its own schema.
  • Reverse-proxy Jenkins and terminate TLS at the proxy so certificates are managed in one place.
  • Take a VPS snapshot before major upgrades so you can roll back cleanly.
  • Keep Jenkins patched — most self-hosting incidents are unpatched software.

Frequently asked questions

How much RAM does Jenkins need?
Plan on 4 GB (8 GB for many agents) for typical use; add headroom if you expect many concurrent users.
What stack does Jenkins run on?
Java + plugins (+ agents).
Can I run other things on the same VPS?
Yes — size the plan so Jenkins plus your other workloads fit in RAM with room to spare.

Looking for something else? Popular alternatives include Drone CI, Woodpecker CI, GitLab CI — browse all app guides.