[Libcg-devel] [PATCH 4/4] README.md: Transition from Travis CI to Github Actions

2020-11-30 Thread Tom Hromatka
Travis CI has now been disabled. Delete the Travis CI badge and display the Github Actions continuous integration workflow badge. Signed-off-by: Tom Hromatka --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 22360705b8c9..541fd97740d9

[Libcg-devel] [PATCH 2/4] github: Add Github Action to setup the libcgroup directory

2020-11-30 Thread Tom Hromatka
Add a Github Action to setup the libcgroup directory. This action installs the required dependencies, run bootstrap.sh, runs configure, and invokes make. Since the action is invoked locally (and not via Github Action's published action mechanism), the repository must be git cloned prior to running

[Libcg-devel] [PATCH 1/4] travis: Disable Travis CI

2020-11-30 Thread Tom Hromatka
Disable the Travis CI build by deleting the .travis.yml file. Subsequent commits will transition to using Github Actions instead. Signed-off-by: Tom Hromatka --- .travis.yml | 95 - 1 file changed, 95 deletions(-) delete mode 100644 .travis.y

[Libcg-devel] [PATCH 0/4] Switch from Travis CI to Github Actions

2020-11-30 Thread Tom Hromatka
Travis CI has changed their business model [1] and are moving away from their free support for open source projects. Additionally, Travis CI build times and delays continue to increase; I have seen libcgroup builds that used to take a couple minutes now take an hour or more. This patchset switches

[Libcg-devel] [PATCH 3/4] github: Add continuous integration workflow

2020-11-30 Thread Tom Hromatka
Add a Github Actions continuous integration workflow. This workflow runs the unit tests, the cgroup v1 functional tests, and the cgroup v2 functional tests. The code coverage results from all of the runs are collated at coveralls.io. Like Travis CI, Github Actions currently does not provide a di