summaryrefslogtreecommitdiff
path: root/pages
diff options
context:
space:
mode:
authorStefan Schmidt <stefan@datenfreihafen.org>2020-06-16 06:42:07 -0700
committerwww-data <www-data@enlightenment.org>2020-06-16 06:42:07 -0700
commit9355bb7c9eea9f84f72b33ed2e92087b5d9941e2 (patch)
tree2457a95718f43c7d81fd70a5c2fea8753e3db6e6 /pages
parentb64df1b97d4894ba19893f7ea84ee7551ab0cebc (diff)
Wiki page ci.md changed with summary [] by Stefan Schmidt
Diffstat (limited to 'pages')
-rw-r--r--pages/develop/ci.md.txt14
1 files changed, 7 insertions, 7 deletions
diff --git a/pages/develop/ci.md.txt b/pages/develop/ci.md.txt
index 87686419e..c5fa8c4fd 100644
--- a/pages/develop/ci.md.txt
+++ b/pages/develop/ci.md.txt
@@ -4,9 +4,9 @@
4 4
5# CI Overview # 5# CI Overview #
6 6
7Our CI pipeline sits on [Travis CI](https://travis-ci.org/Enlightenment/efl/) and gets triggered by two different events. 7Our CI pipeline sits on [Travis CI](https://travis-ci.org/Enlightenment/efl/) and is configured with the .travis.yml file in the root of our git repo. All other CI related build scripts and data can be found in the .ci subfolder.
8The first event is a git push to our git server (which gets instantly mirrored to our Github mirror and triggers Travis). 8
9The second event is a daily cron build triggered directly from Travis itself at around ~ 17:30 CEST (time can vary depending on Travis load). 9To start our CI pipeline we have two different triggers. The first event that triggers a start of the CI pipeline is a git push to our git server (which gets instantly mirrored to our Github mirror and triggers Travis). The second trigger is a daily cron run directly from Travis itself at around ~ 17:30 CEST (time can vary depending on Travis load).
10 10
11## Git push CI Pipeline ## 11## Git push CI Pipeline ##
12 12
@@ -28,14 +28,14 @@ Every developer can push to their devs/$ID/ branches to trigger these builds and
28 28
29## Daily cron CI Pipeline ## 29## Daily cron CI Pipeline ##
30 30
31The daily cron job is running (~ 17:30 CEST, but Travis is not strict on this time). The cron job takes the current HEAD of master at the time the job starts. In addition to the 6 jobs we have for every build the cron jobs add 11 more to a total of 17 jobs: 31The daily cron job is running at ~ 17:30 CEST (Travis is not strict on the exact time). The cron job takes the current HEAD of master at the time the job starts. In addition to the 6 jobs we have for every build the cron jobs add 11 more to a total of 17 jobs:
32 32
33 * A release ready job which runs a full ninja dist 33 * A release ready job which runs a full ninja dist
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 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 test for elementary_test
38 * Codecov code coverage build run 38 * [Codecov](https://codecov.io/github/Enlightenment/efl/) code coverage build run
39 * Native arm64 arch build 39 * Native arm64 arch build
40 * Native ppc64le arch build 40 * Native ppc64le arch build
41 * Native s390x arch build 41 * Native s390x arch build
@@ -51,4 +51,4 @@ EFL testsuite (unit test suites + spec validation tests)
51To 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 and pulled during a Travis run (when not already cached). 51To 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 and pulled during a Travis run (when not already cached).
52 52
53## Caching: ## 53## Caching: ##
54We use ccache in our builds and cache the results in the Travis caching mechanisms to save build time. 54We use ccache in our builds and cache the results in the Travis caching mechanisms to save build time. \ No newline at end of file