summaryrefslogtreecommitdiff
path: root/pages
diff options
context:
space:
mode:
authorStefan Schmidt <stefan@datenfreihafen.org>2020-06-19 05:25:21 -0700
committerwww-data <www-data@enlightenment.org>2020-06-19 05:25:21 -0700
commitfd310cc6d41f5da5686c624095bb3b7647a0167c (patch)
tree31607cdf48bf3fe5ee8b3728afc5e5f356932209 /pages
parentd42bf215fedc66a9d0209c66505b8bd58375f3c5 (diff)
Wiki page ci.md changed with summary [] by Stefan Schmidt
Diffstat (limited to 'pages')
-rw-r--r--pages/develop/ci.md.txt13
1 files changed, 11 insertions, 2 deletions
diff --git a/pages/develop/ci.md.txt b/pages/develop/ci.md.txt
index aab4b7c9e..1689f9790 100644
--- a/pages/develop/ci.md.txt
+++ b/pages/develop/ci.md.txt
@@ -24,7 +24,6 @@ Here is what happens when you push a change to e.org/efl.git:
24 * Linux build with default options (this build includes ninja install, ninja benchmark, ninja test & example application build test) 24 * Linux build with default options (this build includes ninja install, ninja benchmark, ninja test & example application build test)
25 25
26Depending on the available Travis resources such a build takes 20-30 minutes (macOS is the bottleneck). 26Depending on the available Travis resources such a build takes 20-30 minutes (macOS 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.
28 27
29## Daily cron CI Pipeline ## 28## Daily cron CI Pipeline ##
30 29
@@ -42,6 +41,10 @@ The daily cron job is running at ~ 17:30 CEST (Travis is not strict on the exact
42 41
43Depending on the available Travis resources such a build can take up to 60 minutes 42Depending on the available Travis resources such a build can take up to 60 minutes
44 43
44# CI Deatils #
45
46In addition to the overview on our CI above we will list some details of it here. It should help to understand the mechanics of it a bit better.
47
45## Testing ## 48## Testing ##
46 49
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. 50When 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.
@@ -52,4 +55,10 @@ We are increasing the test timeout to 120s from the default 30s and we are runni
52To support the various builds on Travis we have a bunch of docker images with the needed dependencies for efl pre-installed. The source for these docker images is the [ci-support-files](https://github.com/Enlightenment/ci-support-files) github repo where our Dockerfiles live. They will be automatically build on [docker hub](https://hub.docker.com/repository/docker/stefanschmidt1/ci-support-files/tags?page=1) and pulled during a Travis run (when not already cached). 55To support the various builds on Travis we have a bunch of docker images with the needed dependencies for efl pre-installed. The source for these docker images is the [ci-support-files](https://github.com/Enlightenment/ci-support-files) github repo where our Dockerfiles live. They will be automatically build on [docker hub](https://hub.docker.com/repository/docker/stefanschmidt1/ci-support-files/tags?page=1) and pulled during a Travis run (when not already cached).
53 56
54## Caching ## 57## Caching ##
55We use ccache in our builds and cache the results in the Travis caching mechanisms to save build time. \ No newline at end of file 58We use ccache in our builds and cache the results in the Travis caching mechanisms to save build time.
59
60## Developer Branches ##
61Every developer with commit access can push to their devs/$ID/ branches to trigger these builds and check the results before putting things into Phab. This has been proven useful for bigger changes without having access to all the different test environments.
62
63## Travis native vs. docker builds ##
64For most of our builds we are using docker images. This allows better control of the image as well as running them locally for debugging and testing. Some of the features we are using on Travis are only available with their native builds (namely macOS, arm64, ppc64le and s390x builds as well as nice codecov integration). We run these jobs directly on the Travis provided images to make use of this functionality. \ No newline at end of file