enlightenment/www-content
enlightenment
/
www-content
6
0
Fork 2
Code Issues Pull Requests Projects Releases Wiki Activity

Wiki page ci.md changed with summary [] by Stefan Schmidt

This commit is contained in:
Stefan Schmidt 2020-06-19 05:30:52 -07:00 committed by www-data
parent fd310cc6d4
commit 195e101666
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
pages/develop/ci.md.txt
View File

@ -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.
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.