From d42bf215fedc66a9d0209c66505b8bd58375f3c5 Mon Sep 17 00:00:00 2001 From: Stefan Schmidt Date: Fri, 19 Jun 2020 05:18:49 -0700 Subject: [PATCH] Wiki page ci.md changed with summary [] by Stefan Schmidt --- pages/develop/ci.md.txt | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/pages/develop/ci.md.txt b/pages/develop/ci.md.txt index ce68a83f0..aab4b7c9e 100644 --- a/pages/develop/ci.md.txt +++ b/pages/develop/ci.md.txt @@ -16,14 +16,14 @@ Here is what happens when you push a change to e.org/efl.git: - GitHub notifies Travis CI on repo changes - Travis takes the latest change (all commits in one push, not individual commits) and starts a build - 6 different jobs are running on each push - * Native OSX build - * Windows cross build with MinGW and ewpi for deps (native build for cross tooling and a full cross build afterwards) + * Native macOS build + * Windows cross build with MinGW and [ewpi](https://github.com/vtorri/ewpi/) for dependencies (this includes a native build of tooling needed for the full cross build afterwards) * Linux build with all options (as much as possible combined) enabled - * Linux build with all options /as much as possible to have working build) disabled - * Linux build with wayland options enabled (ninja, ninja install, ninja test & example application build test) - * Linux build with default options (ninja, ninja install, ninja benchmark, ninja test & example application build test) + * Linux build with all options (as much as possible to have working build) disabled + * Linux build with wayland options enabled (this build includes ninja install, ninja test & example application build test) + * Linux build with default options (this build includes ninja install, ninja benchmark, ninja test & example application build test) -Depending on the available Travis resources such a build takes 20-30 minutes (OSX is the bottleneck). +Depending on the available Travis resources such a build takes 20-30 minutes (macOS is the bottleneck). Every developer can push to their devs/$ID/ branches to trigger these builds and check the results before putting things into Phab. ## Daily cron CI Pipeline ## @@ -32,7 +32,7 @@ The daily cron job is running at ~ 17:30 CEST (Travis is not strict on the exact * A release ready job which runs a full ninja dist * 3 Linux distro builds (Ubuntu latest, Ubuntu LTS, Debian stable) - * [Coverity Scan](https://scan.coverity.com/projects/enlightenment-foundation-libraries) run and upload for analysis -> mail to e-devel for newly detected issues + * [Coverity Scan](https://scan.coverity.com/projects/enlightenment-foundation-libraries) run and upload for analysis (a mail to e-devel will be send for newly detected issues after analysis) * Address sanitizer enabled build * Exactness job running tests on elementary_test scenarios (pixel perfect regression and integration test-suite) * [Codecov](https://codecov.io/github/Enlightenment/efl/) code coverage run (build with Travis Ubuntu Bionic distro)