summaryrefslogtreecommitdiff
path: root/pages
diff options
context:
space:
mode:
authorStefan Schmidt <stefan@datenfreihafen.org>2020-06-16 07:06:49 -0700
committerwww-data <www-data@enlightenment.org>2020-06-16 07:06:49 -0700
commit5dae1b9a7d25727976829519a55d7c543cb48153 (patch)
tree857941a0f536716a91aed91d91e0d0caa1b8eb6f /pages
parentca93ebaafccc3e44e4894b16ef49a277698bf7a3 (diff)
Wiki page ci.md changed with summary [] by Stefan Schmidt
Diffstat (limited to 'pages')
-rw-r--r--pages/develop/ci.md.txt21
1 files changed, 11 insertions, 10 deletions
diff --git a/pages/develop/ci.md.txt b/pages/develop/ci.md.txt
index 94aa187c7..ea772dad7 100644
--- a/pages/develop/ci.md.txt
+++ b/pages/develop/ci.md.txt
@@ -17,11 +17,11 @@ Here is what happens when you push a change to e.org/efl.git:
17 - Travis takes the latest change (all commits in one push, not individual commits) and starts a build 17 - Travis takes the latest change (all commits in one push, not individual commits) and starts a build
18 - 6 different jobs are running on each push 18 - 6 different jobs are running on each push
19 * Native OSX build 19 * Native OSX build
20 * Windows cross build with MinGW and ewpi for deps 20 * Windows cross build with MinGW and ewpi for deps (native build for cross tooling and a full cross build afterwards)
21 * Linux build with all options (as much as possible combined) enabled 21 * Linux build with all options (as much as possible combined) enabled
22 * Linux build with all options disabled 22 * Linux build with all options /as much as possible to have working build) disabled
23 * Linux build with wayland options enabled (+ninja test, ninja install & external app header test) 23 * Linux build with wayland options enabled (ninja, ninja install, ninja test & external app header test)
24 * Linux build with default options (+ninja test, ninja install & external app header test) 24 * Linux build with default options (ninja, ninja install, ninja benchmark, ninja test & external app header test)
25 25
26Depending on the available Travis resources such a build takes 20-30 minutes (OSX is the bottleneck). 26Depending on the available Travis resources such a build takes 20-30 minutes (OSX is the bottleneck).
27Every developer can push to their devs/$ID/ branches to trigger these builds and check the results before putting things into Phab. 27Every developer can push to their devs/$ID/ branches to trigger these builds and check the results before putting things into Phab.
@@ -34,17 +34,18 @@ The daily cron job is running at ~ 17:30 CEST (Travis is not strict on the exact
34 * 3 Linux distro builds (Ubuntu latest, Ubuntu LTS, Debian stable) 34 * 3 Linux distro builds (Ubuntu latest, Ubuntu LTS, Debian stable)
35 * [Coverity Scan](https://scan.coverity.com/projects/enlightenment-foundation-libraries) run and upload for analysis -> mail to e-devel for newly detected issues 35 * [Coverity Scan](https://scan.coverity.com/projects/enlightenment-foundation-libraries) run and upload for analysis -> mail to e-devel for newly detected issues
36 * Address sanitizer enabled build 36 * Address sanitizer enabled build
37 * Exactness job running test for elementary_test 37 * Exactness job running tests on elementary_test scenarios (pixel perfect regression and integration test-suite)
38 * [Codecov](https://codecov.io/github/Enlightenment/efl/) code coverage build run 38 * [Codecov](https://codecov.io/github/Enlightenment/efl/) code coverage run (build with Travis Ubuntu Bionic distro)
39 * Native arm64 arch build 39 * Native arm64 arch (build with Travis Ubuntu Bionic distro)
40 * Native ppc64le arch build 40 * Native ppc64le arch (build with Travis Ubuntu Bionic distro)
41 * Native s390x arch build 41 * Native s390x arch (build with Travis Ubuntu Bionic distro)
42 42
43Depending on the available Travis resources such a build can take up to 60 minutes 43Depending on the available Travis resources such a build can take up to 60 minutes
44 44
45## Testing ## 45## Testing ##
46 46
47EFL testsuite (unit test suites + spec validation tests) 47When executing our ninja test on CI we have a few extra details to make it run better on potentially overloaded CI systems. We have experienced some instability when running our tests on Travis before, not all of these might still be needed.
48We are increasing the test timeout to 120s from the default 30s and we are running the test-suites in a loop which would run up to five times in case the tests are failing.
48 49
49## Docker images ## 50## Docker images ##
50 51