On Fri, Dec 4, 2020 at 6:37 PM David Marchand <david.march...@redhat.com> wrote: > > With the recent changes in terms of free access to the Travis CI, let's > offer an alternative with GitHub Actions. > Running jobs on ARM is not supported unless using external runners, so > this commit only adds builds for x86_64 and cross compiling for i386 and > aarch64. > > Differences with the Travis CI integration: > - Error logs are not dumped to the console when something goes wrong. > Instead, they are gathered in a "catch-all" step and attached as > artifacts. > - A cache entry is stored once and for all, but if no cache is found you > can inherit from the default branch cache. The cache is 5GB large, for > the whole git repository. > - The maximum retention of logs and artifacts is 3 months. > - /home/runner is world writable, so a workaround has been added for > starting dpdk processes. > - Ilya, working on OVS GHA support, noticed that jobs can run with > processors that don't have the same capabilities. For DPDK, this > impacts the ccache content since everything was built with > -march=native so far, and we will end up with binaries that can't run > in a later build. The problem has not been seen in Travis CI (?) but > it is safer to use a fixed "-Dmachine=default" in any case. > - Scheduling jobs is part of the configuration and takes the form of a > crontab. A build is scheduled every Monday at 0:00 (UTC) to provide a > default ccache for the week (useful for the ovsrobot). > > Signed-off-by: David Marchand <david.march...@redhat.com>
Tested-by: Ferruh Yigit <ferruh.yi...@intel.com> Acked-by: Thomas Monjalon <tho...@monjalon.net> Acked-by: Aaron Conole <acon...@redhat.com> Series applied. For the time being, we can check jobs status by checking: https://github.com/ovsrobot/dpdk/actions Next step is to update the robot to make use of https://docs.github.com/en/free-pro-team@latest/rest/reference/actions#list-workflow-runs-for-a-repository -- David Marchand
