WWW-www.enlightenment.org pushed a commit to branch master.
http://git.enlightenment.org/website/www-content.git/commit/?id=9355bb7c9eea9f84f72b33ed2e92087b5d9941e2
commit 9355bb7c9eea9f84f72b33ed2e92087b5d9941e2
Author: Stefan Schmidt <ste...@datenfreihafen.org>
Date: Tue Jun 16 06:42:07 2020 -0700
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 87686419e..c5fa8c4fd 100644
--- a/pages/develop/ci.md.txt
+++ b/pages/develop/ci.md.txt
@@ -4,9 +4,9 @@
# CI Overview #
-Our CI pipeline sits on [Travis CI](https://travis-ci.org/Enlightenment/efl/)
and gets triggered by two different events.
-The first event is a git push to our git server (which gets instantly mirrored
to our Github mirror and triggers Travis).
-The second event is a daily cron build triggered directly from Travis itself
at around ~ 17:30 CEST (time can vary depending on Travis load).
+Our 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.
+
+To 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).
## Git push CI Pipeline ##
@@ -28,14 +28,14 @@ Every developer can push to their devs/$ID/ branches to
trigger these builds and
## Daily cron CI Pipeline ##
-The 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:
+The 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:
* A release ready job which runs a full ninja dist
* 3 Linux distro builds (Ubuntu latest, Ubuntu LTS, Debian stable)
- * Coverity Scan 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 -> mail to e-devel for newly detected issues
* Address sanitizer enabled build
* Exactness job running test for elementary_test
- * Codecov code coverage build run
+ * [Codecov](https://codecov.io/github/Enlightenment/efl/) code coverage
build run
* Native arm64 arch build
* Native ppc64le arch build
* Native s390x arch build
@@ -51,4 +51,4 @@ EFL testsuite (unit test suites + spec validation tests)
To 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).
## Caching: ##
-We use ccache in our builds and cache the results in the Travis caching
mechanisms to save build time.
+We use ccache in our builds and cache the results in the Travis caching
mechanisms to save build time.
\ No newline at end of file
--
