Skip to main content

Jenkins Hosting on Hostim.dev

Jenkins is an open-source automation server. It builds, tests and deploys your code. You describe the steps in a Jenkinsfile in your repository, or click jobs together in the web interface. More than 2,000 plugins connect it to Git hosts, chat tools, cloud providers and build tools.

Jenkins is one Java process, the controller. It keeps all its state as files in one directory, JENKINS_HOME. It needs no database.

Self-host Jenkins with Docker Compose (minimal)​

services:
jenkins:
image: jenkins/jenkins:2.580.2-lts-jdk21
restart: unless-stopped
volumes:
- jenkins_home:/var/jenkins_home
ports:
- "127.0.0.1:8080:8080"
- "50000:50000"

volumes:
jenkins_home:

On the first start Jenkins prints an initial admin password to the log (docker compose logs jenkins). Open port 8080, enter the password, install plugins and create your admin user. Port 50000 is for agents that connect over plain TCP. You can drop it if your agents connect over WebSocket. For HTTPS you need a reverse proxy with a certificate in front of port 8080. More stacks are in our Docker Compose library.


Deploy Jenkins on Hostim.dev (One-Click)

The hosted route: no VPS, no proxy, no certificates. The template runs the official LTS image with a persistent volume for JENKINS_HOME, a domain and HTTPS.

Try it Yourself

Guest project runs for 1 hour. Log in to save and extend to 5 days.

Why Host Jenkins on Hostim.dev?​

  • One-click Docker deployment of the official LTS image
  • Jobs, build history, plugins and credentials on a persistent volume
  • Automatic HTTPS and domain, WebSocket agents work out of the box
  • The setup wizard and plugin installs work as on any other server

What's included​

ResourceDetails
Appjenkins/jenkins:2.580.2-lts-jdk21 Docker image
Volume/var/jenkins_home (all Jenkins data)
DatabaseNone. Jenkins stores everything as files
DomainFree *.hostim.dev subdomain
SSLLet’s Encrypt (auto-enabled)
Port8080

The template sets no environment variables. Jenkins is configured in its web interface, and the configuration is saved to the volume.

How to Deploy​

  1. Go to your Hostim.dev dashboard.
  2. Click Create Project → Use a Template.
  3. Select Jenkins.
  4. Choose a resource plan.
  5. Deploy.
  6. Open the app's logs and copy the password under "Please use the following password to proceed to installation".
  7. Open the app URL and paste the password.
  8. Click Install suggested plugins, or pick your own.
  9. Create your admin user. Keep the Jenkins URL the wizard suggests: it is your app URL.

Do the setup right after the deploy. Until you finish the wizard, the initial password is the only login. It is also in the file /var/jenkins_home/secrets/initialAdminPassword.


FAQ​

Where does Jenkins store its data?

Everything is in /var/jenkins_home, on a persistent volume: the configuration, jobs, build logs, installed plugins, users and credentials. We installed plugins, ran a pipeline that clones a Git repository, and then restarted the app four times. The jobs, the build history, the plugins and the login were all still there.

Can I run builds on the controller?

Yes. The controller has 2 executors by default, so small jobs run without any agent. The Jenkins project recommends separate agents for anything serious, because builds on the controller can read its files and use its memory. A build that runs out of memory can take Jenkins down with it.

How do I connect agents?

Use inbound agents over WebSocket. Port 50000 is not exposed, but WebSocket runs over the normal HTTPS port. In Jenkins, go to Manage Jenkins → Nodes → New Node, create a permanent agent, select Launch agent by connecting it to the controller and tick Use WebSocket. Then run the command Jenkins shows on the agent machine. Agents that Jenkins reaches over SSH also work, if Jenkins can reach the agent's SSH port. They need the SSH Build Agents plugin.

Can I use Docker in my pipelines?

Not on the controller. The container has no Docker daemon, so steps like agent { docker ... } or docker build fail there. Run them on an agent that has Docker installed.

How much memory does Jenkins get?

Java caps its heap at 25% of the container memory by default. On a plan with 2 GB that is 512 MB, which is enough for a small setup. With many plugins or jobs, choose a larger plan, or give Java a larger share with the variable JAVA_OPTS=-XX:MaxRAMPercentage=50. Builds on the controller use memory outside the heap, so leave room for them.

How do I use my own domain?

Add the domain to the app in the Hostim.dev dashboard and point a DNS record at it. HTTPS is set up for it automatically. Then go to Manage Jenkins → System and change Jenkins URL to the new address. Jenkins uses it for links in emails and build status messages.

How do I back up Jenkins?

Back up the volume. /var/jenkins_home holds all your data. The workspace folder in it holds build checkouts and build files. The next build checks the code out again, so you can usually leave it out of a backup.

How do I update Jenkins?

The template pins an LTS release. Read the LTS upgrade guide, back up the volume, change the image tag to a newer -lts-jdk21 tag and redeploy. Then update your plugins in Manage Jenkins → Plugins. Jenkins cannot update itself in this image, because the Jenkins program file is read-only. Plugin updates in the web interface work and are saved on the volume.


Alternatives​

  • Woodpecker CI — lightweight CI with YAML pipelines in containers
  • Gitea Actions / Forgejo Actions — CI built into your Git server
  • GitHub Actions / GitLab CI — hosted CI next to your repository
  • Node-RED — low-code flow editor for automations (guide)

Source + Docs​


Looking for something else? Browse all templates →


Try it now​

Deploy Jenkins Now – in less than 60 seconds