WWW-www.enlightenment.org pushed a commit to branch master.
http://git.enlightenment.org/website/www-content.git/commit/?id=195e1016664f309888c7a0039fd96d1fa3812d58
commit 195e1016664f309888c7a0039fd96d1fa3812d58
Author: Stefan Schmidt <ste...@datenfreihafen.org>
Date: Fri Jun 19 05:30:52 2020 -0700
Wiki page ci.md changed with summary [] by Stefan Schmidt
---
pages/develop/ci.md.txt | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/pages/develop/ci.md.txt b/pages/develop/ci.md.txt
index 1689f9790..d456fb48d 100644
--- a/pages/develop/ci.md.txt
+++ b/pages/develop/ci.md.txt
@@ -41,7 +41,7 @@ The daily cron job is running at ~ 17:30 CEST (Travis is not
strict on the exact
Depending on the available Travis resources such a build can take up to 60
minutes
-# CI Deatils #
+# CI Details #
In 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.
@@ -61,4 +61,8 @@ We use ccache in our builds and cache the results in the
Travis caching mechanis
Every 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.
## Travis native vs. docker builds ##
-For 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
+For 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.
+
+## Travis fold and timers ##
+In our scripts we make use of travis_fold and travis_time_* bash functions (we
export them in .travis.yml) to allow us to fold particular parts of the logs
neatly on the webui. The travis_time* calls allow us to log the spent time for
each of these sections which gives a good overview where we spend time in our
build.
+
--
