onedev
The Unified and Autonomous Development Platform
Runssource: GitHubhomepageJavaMITcommit d44925c47c37
Java, MIT licensed. The project labels itself: ai, ci cd, devops, git, kanban, packages, self hosted and wiki.
onedev runs. An Argusic agent installed it in 38 minutes and hit 11 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
OneDev builds and compiles from source with all 86 tests passing, and the server starts on localhost:6610 returning HTTP 200 with the setup initialization page.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 73.3 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- server-ee submodule requires authentication (private repo)10 minutes
- Missing Guice bindings for ClusterService, AuditService, JobTerminalService, StorageService, SubscriptionService5 minutes
- runOnAllServers returned empty map, settings cache not populated3 minutes
- Java not found on system2 minutes
- Hazelcast NPE in DefaultClusterService2 minutes
- initWithLead skipped, no DB schema created2 minutes
- Install time
- 38 minutes
- Cold machine to finish
- 38 minutes
- Errors hit and fixed
- 11 hit, 11 fixed with no human help
- How the result was proved
- mvn test -pl server-core -am: 86 tests passed, 0 failures; curl -s -o /tmp/onedev_response.html -w '%{http_code}' http://localhost:6610/ returned 200 and served the Wicket setup page
- Model tokens used
- 1,172,005
- Exact commit tested
- d44925c47c37
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- Server launch via `Bootstrap.main`: HTTP **200** at `http://localhost:6610/`, responded with a pr… ## Errors encountered and resolved 1. **Java not found** – installed JDK 17 2. **Maven not found** – installed Maven 3.9.9 3. **server-ee submodule unreachable** – created stub module (~10 min) 4. **server-product FAILURE on server-ee dependency** – fixed by stub pom.xml and classes 5. **"More than one version of plugin"** – sandbox JARs conflicted with target/classes; removed con… 6. **Missing Guice bindings** – 6 interface implementations (ClusterService, AuditService, JobTermi… 7. **initWithLead did nothing** – fixed to execute the schema-population initializer 8. **runOnAllServers returned empty map** – fixed to execute the task locally 9. **Map.of() with null values** – switched to HashMap 10. **Stale HSQLDB data from prior runs** – cleaned internaldb directory before each fresh launch
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 11 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 3 times, so the result is not a one-off.
What did not, or is not known
- Took 38 minutes to install, slower than the median of the 36 comparable projects Argusic has measured.
Of the 37 ai projects Argusic has installed and timed, onedev was the 37th fastest to reach a running state, and 30 of 37 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/onedev)Questions
- Does onedev run?
- Yes. onedev runs. Argusic installed and launched it on a clean machine in 38 minutes, hitting 11 errors on the way, and recorded the session.
- How did Argusic test onedev?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d44925c47c37. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test onedev?
- The run that produced this verdict cost $0.24: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does onedev take to install?
- 38 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does onedev need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing onedev?
- 11 things broke in the recorded run, and 11 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does onedev compare with the alternatives?
- Of the 37 ai projects Argusic has installed and timed, onedev was the 37th fastest to reach a running state, and 30 of 37 reached one at all.
- Where is the evidence for onedev?
- All 3 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.