Do I need a domain name for Jenkins?

Yes. Jenkins is used by the whole team and receives the webhooks of your Git repositories: it must answer over HTTPS on a stable name. No need to buy one: every ServOrbit VPS comes with a free subdomain (jenkins.{dns_slug}.servorbit-dns.com) with an HTTPS certificate. You can also use a subdomain of one of your domains.

Where do I find the initial administrator password?

It is shown in your client area, on the page of the installed application. Jenkins writes it on first start to the secrets/initialAdminPassword file of its data volume. It only unlocks the setup wizard: you then create your own administrator account.

Can my builds use Docker?

Not on the controller installed by the Marketplace: for security, the VPS's Docker socket is not mounted into it. Connect a build agent over SSH (a second VPS, for example) with Docker installed, and target it in your Jenkinsfile with a label. This is also the practice recommended by the Jenkins project.

How do I back up and update Jenkins?

All configuration, jobs, plugins and history live in the jenkins-home volume: back it up regularly. To update, change the image tag in the application's docker-compose.yml to the new LTS release, then run docker compose pull and docker compose up -d.

Kick off a software project quickly.

Jenkins

Jenkins — your open-source CI/CD server on a VPS: Jenkinsfile pipelines, Git webhooks and over 2,000 plugins, with no per-minute build billing.

2 GB minimum RAM 2 vCPU Port 8104 In validation

In validation

Automatic installation for this solution is ready and currently going through our tests on a real server. Ordering will open as soon as validation is complete.

Source code

Tech stack

DockerJenkinsJava 21

Minimum RAM2 GB minimum

Minimum CPU2 vCPU

Default port8104

Compatible OSChoice of Linux distributions

Jenkins is the most widely used open-source automation server (MIT licence) for continuous integration and delivery. It pulls your code from Git, runs the build, the tests and the analysis, then publishes the artifact or deploys the application, on every push or on a schedule. Pipelines are written in a Jenkinsfile versioned with the code, and over 2,000 plugins connect it to GitHub, GitLab, Gitea, Docker, Kubernetes, SonarQube or Slack.

Hosting it on your own VPS removes the per-minute build billing of hosted CI services: your pipelines run as much as needed, your deployment secrets stay on your server, and you choose the agents that execute the builds. Jenkins suits a team industrialising its deployments as well as a company that must keep its code and credentials in-house.

Key features

Pipelines as code — a declarative Jenkinsfile, versioned in the repository, describes the build, test and deployment stages.

Webhook triggers — every push or pull request on GitHub, GitLab or Gitea starts the matching pipeline.

Multibranch — every branch or pull request found in the repository automatically gets its own pipeline.

Over 2,000 plugins — Git, Docker, Kubernetes, SonarQube, Slack, e-mail notifications, test reports.

Build agents — builds run on dedicated machines, connected over SSH, to keep the controller isolated.

Central credentials — SSH keys, tokens and passwords stored encrypted and injected into the pipeline without appearing in clear text.

When to use this solution?

1

Test every pull request

On every pull request, Jenkins builds the project, runs the unit tests and the static analysis, then reports the result on the pull request: broken code no longer reaches the main branch.

2

Deploy to production automatically

A merge into the main branch builds the Docker image, pushes it to your registry and deploys the application to your servers over SSH, with a manual approval step if you want one.

3

Automate scheduled tasks

Backups, nightly reports, certificate renewals or synchronisations: a scheduled job replaces scattered crontabs and keeps the history of every run.

Deploy Jenkins on your VPS

Guide optimized for ServOrbit Cloud VPS.

01

Create the VPS and choose the address

Order an Ubuntu 24.04 VPS with 2 GB of RAM (4 GB if your builds run on the same server). Jenkins requires a domain: its interface is shared by the team and your Git repositories send it their webhooks, so it must answer over HTTPS on a stable name. It opens on a subdomain of one of your domains, or on the VPS's free subdomain (jenkins.{dns_slug}.servorbit-dns.com), HTTPS included. No need to buy a domain name.

02

Install Jenkins from the Marketplace

In your client area, select Jenkins, choose the address and click Install. The script deploys Jenkins LTS in Docker, keeps its data in a dedicated volume and configures the nginx reverse proxy over HTTPS.

03

Log in for the first time

Open https://your-domain: Jenkins asks for the initial administrator password. Copy it from your client area ("Reveal" button), then install the suggested plugins and create your administrator account. The initial password only works once.

04

Check the Jenkins URL

On the wizard's "Instance Configuration" screen, keep the HTTPS address of your domain as the Jenkins URL. It is the one used in notification links and the one your repositories call for webhooks.

05

Create your first pipeline

Click "New Item", choose "Multibranch Pipeline", enter your repository URL and its credentials, then add a Jenkinsfile at the root of the repository. Finally, point the repository webhook to https://your-domain so that every push starts a build.

Frequently asked questions

GitHub Actions is convenient for a repository hosted on GitHub, but build minutes are billed beyond the quota and secrets live at GitHub. Jenkins runs on your VPS: no minute quota, secrets at home, and it works with GitHub, GitLab, Gitea or an internal Git server. In return, you take care of its maintenance.

Complementary solutions

Development

Jenkins isn't orderable yet.