ocurrent/mirage-ci

Ocurrent-based CI for MirageOS

OCurrent

OCurrent allows you to specify a workflow / pipeline for keeping things up-to-date.

For example, the pipeline shown above fetches the head of a GitHub repository's master branch, builds it, runs the tests, and deploys the binary if the tests pass. When a new commit is pushed, it runs the pipeline again.

Another use might be to keep the GitHub build status of each PR in your Git repository showing the result of fetching, building and testing the PR's head commit. If the head commit changes, the result must be recalculated.

An OCurrent pipeline is written using an OCaml eDSL. When OCurrent evaluates it, it records the inputs used (e.g. the current set of open PRs and the head of each one), monitors them, and automatically recalculates when an input changes.

Larger uses of OCurrent include the OCaml Docker base image builder and ocaml-ci, which is the CI that tests this repository itself.

Documentation

The OCurrent docs contains user documentation and examples. In particular, you might like to start by reading about the example pipelines or how to write your own plugins.

For technical docs, see the API Documentation.

Licensing

OCurrent is licensed under the Apache License, Version 2.0. See LICENSE for the full license text.

mirage-ci's Issues

Make the local CI work without network access

Right now the local CI will clone remote Git repositories on startup. It would be nice to allow running the CI without network access on local repositories instead. That'll help if we would want to write e2 tests too.

Parse color codes in logs page

Example: https://ci.mirage.io/pipelines/pr-1393-mirage-4-mirage-mirage/pr-1393-mirage-4-mirage-mirage-a45593da89d2f6f1427c31f591f05158b75a364e/x86_64-debian-10-4.13/2023-02-07/110013-ocluster-build-6f89fa

[01;2m�[01;35m2023-02-07 11:02.34 ---> saved as "cbba9511e46ef57631453d5b88aeed1ed6de6fa87b6f0dcb3da9328657d73fa4"�[0m

�[01;34m/: (user (uid 1000) (gid 1000))�[0m

�[01;34m/: (workdir /home/opam)�[0m

�[01;34m/home/opam: (run (shell "sudo chown opam:opam /home/opam"))�[0m
�[01;2m�[01;35m2023-02-07 11:02.37 ---> saved as "0afede13af6ea6d75cbfcfb80353059bc4fd4eea40a723ef627f0c4946f2e079"�[0m

Escape code should be parsed and transformed into html like current_web does

Application and Operational Metrics

Placeholder until someone has time to produce an issue like ocurrent/ocaml-docs-ci#94 or ocurrent/ocaml-ci#820

Restart stuck/timeout jobs automatically

Seems there's a workaround in ocaml-doc-ci that we could re-use: ocurrent/ocaml-docs-ci#125

maintenance -- vendored things, and code documentation

hey,

I finally discovered this repository, and it's a bit unclear to me why there are so many things in vendor that seem to be released as well.

another question: what and in which configuration is this service deployed (where?)?

Self update deployer error

The self update deployment fails with this builds error:

2023-02-10 01:26.02: Exec: "docker" "build" "-f" "/tmp/git-checkout4d10508/Dockerfile" 
                           "--iidfile" "/tmp/git-checkout4d10508/docker-iid" 
                           "--" "/tmp/git-checkout4d10508"
ERROR: BuildKit is enabled but the buildx component is missing or broken.
       Install the buildx component to build images with BuildKit:
       https://docs.docker.com/go/buildx/
2023-02-10 01:26.02: Job failed: Docker build exited with status 1

I've switched off the self update since the deployment is already handled by ocurrent-deployer here https://deploy.ci3.ocamllabs.io/?repo=ocurrent/mirage-ci&