aboutsummaryrefslogtreecommitdiff
path: root/docs/markdown
diff options
context:
space:
mode:
authorChristoph Reiter <reiter.christoph@gmail.com>2020-11-26 09:22:32 +0100
committerNirbheek Chauhan <nirbheek@centricular.com>2021-01-09 08:43:49 +0530
commit50aee9c77b64e9d79b7035c9c53e6ff880122865 (patch)
tree79e1d4128aa671c70d0300957d9172223ca1b927 /docs/markdown
parent3aef33a99a718d8fed36539c109a14c984e0923b (diff)
downloadmeson-50aee9c77b64e9d79b7035c9c53e6ff880122865.zip
meson-50aee9c77b64e9d79b7035c9c53e6ff880122865.tar.gz
meson-50aee9c77b64e9d79b7035c9c53e6ff880122865.tar.bz2
CI: Move all remaining jobs from travis-ci to GHA
Some changes: * Set HOME to /root, since github mounts its own HOME and 'wine' (because of permissions) and 'dub' (can't find packages) don't like that. * Remove the seccomp option, doesn't seem to be needed.
Diffstat (limited to 'docs/markdown')
-rw-r--r--docs/markdown/Contributing.md2
-rw-r--r--docs/markdown/MesonCI.md7
2 files changed, 0 insertions, 9 deletions
diff --git a/docs/markdown/Contributing.md b/docs/markdown/Contributing.md
index 07ddc88..c9cebee 100644
--- a/docs/markdown/Contributing.md
+++ b/docs/markdown/Contributing.md
@@ -362,8 +362,6 @@ Meson uses several continuous integration testing systems that have slightly
different interfaces for indicating a commit should be skipped.
Continuous integration systems currently used:
-- [Travis-CI](https://docs.travis-ci.com/user/customizing-the-build#skipping-a-build)
- allows `[skip ci]` anywhere in the commit messages.
- [Azure Pipelines](https://docs.microsoft.com/en-us/azure/devops/pipelines/scripts/git-commands?view=vsts&tabs=yaml#how-do-i-avoid-triggering-a-ci-build-when-the-script-pushes)
allows `***NO_CI***` in the commit message.
- [Sider](https://sider.review)
diff --git a/docs/markdown/MesonCI.md b/docs/markdown/MesonCI.md
index 73b979b..00fd1ff 100644
--- a/docs/markdown/MesonCI.md
+++ b/docs/markdown/MesonCI.md
@@ -5,13 +5,6 @@ the CI setup used for testing Meson itself. The Meson
project uses multiple CI platforms for covering a wide
range of target systems.
-## Travis CI
-
-The travis configuration file is the `.travis.yml` in the
-the project root. This platform tests cross compilation and
-unity builds on a [linux docker image](#docker-images) and
-on OSX.
-
## GitHub actions
The configuration files for GitHub actions are located in