To test locally you will need:
(you might need to increase the limit on the number of open files):
ulimit -n 102400 dune exec -- opam-repo-ci-local \ --confirm harmless \ --submission-service submission.cap \ --github-token-file token \ --capnp-address tcp:127.0.0.1:5001
Browse to http://localhost:8080 to see the web UI.
You can either set the confirm threshold (at the bottom of the web page) to allow all builds to start,
or just click on a yellow box and then on the
Start now button to start one step manually.
The analysis step will detect which packages have been changed. Then, for each supported platform it will try to install the package. If that succeeds, it will run the package’s tests, and in parallel it will find other packages that depend on this one and test them too.
The public web front-end is a separate process.
It needs a
.cap file to connect to the engine.
If you have the file for the real service, you can use that.
If you’re testing the engine locally (as shown above), you can use the
that it writes out.
dune exec -- opam-repo-ci-web --backend ./capnp-secrets/opam-repo-ci-admin.cap
Then browse to http://localhost:8090/github to see the public UI.