How to Deploy OneDev with Docker and Set Up CI/CD in 15 Minutes

In this tutorial, you will deploy OneDev on your own server with Docker and run your first CI/CD pipeline — end to end, in under 15 minutes. No cloud account required, no credit card, just your own machine.

Step 1: Run OneDev with Docker

OneDev ships as a single Docker image with zero external dependencies — no separate database, no Redis, no object storage. Create a directory and start it:

mkdir -p ~/onedev && cd ~/onedev
docker run -d --name onedev \
  -p 8080:8080 \
  -v ./data:/data \
  1dev/server:latest

That is it. After the first boot, open http://your-server:8080, create the administrator account, and OneDev is ready. All data — repositories, builds, boards — lives in the ./data volume, so backups are a simple copy.

Step 2: Create a Project and Enable CI

Click New Project, give it a name, and push an existing repository to it. Then add a .onedev-buildspec.yml file at the root to define your pipeline:

version: 1
jobs:
  - name: build
    steps:
      - !Checkout
      - !BuildImage
        dockerfile: Dockerfile
        tag: my-app:${buildVersion}

Commit and push — OneDev automatically detects the build spec and runs the job. The built image is published straight to the built-in package registry, which doubles as a private Docker registry.

Step 3: Let AI Review Your Pull Requests

Open a pull request and OneDev's built-in AI review kicks in automatically. It comments on potential bugs, suggests fixes, and flags risky changes — right inside the diff view. You can configure how aggressive the review is per project, or disable it entirely.

Recommended Hardware

For a small team, the minimum is plenty. The recommended spec comfortably handles active CI workloads plus the AI review engine.