Skip to content
Matthieu Baerts edited this page May 26, 2021 · 5 revisions

Continuous Integration

Workflow

In the short/middle term, the goal is to have a Patchew instance setup to create a tag each time a new patch is sent on our mailing list. This new tag will trigger a build and results will be displayed there.

While this is being prepared, patches are validated each time the export branch is modified along with a new tag.

Jobs

Once per day, a Github Action is scheduled to sync our tree with the Netdev's net-next repo.

Each time the tree is updated, a new tag, export/<date>T<time> is created.

New tags trigger two other jobs so far:

Results

Results are also posted on our IRC channel.

Local development

The Docker image used by the public CIs can be used to create a basic kernel dev environment.

Download the kernel source code and then run these two commands to download the latest Docker image and run it:

$ docker pull mptcp/mptcp-upstream-virtme-docker:latest
$ docker run -v "${PWD}:${PWD}:rw" -w "${PWD}" --privileged --rm -it mptcp/mptcp-upstream-virtme-docker:latest <manual-normal | manual-debug | auto-normal | auto-debug | auto-all>

For more details: https://github.com/multipath-tcp/mptcp-upstream-virtme-docker

Clone this wiki locally