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:18:49 -07:00 committed by www-data
parent 310c8af1d4
commit d42bf215fe
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -16,14 +16,14 @@ Here is what happens when you push a change to e.org/efl.git:
- GitHub notifies Travis CI on repo changes
- Travis takes the latest change (all commits in one push, not individual commits) and starts a build
- 6 different jobs are running on each push
* Native OSX build
* Windows cross build with MinGW and ewpi for deps (native build for cross tooling and a full cross build afterwards)
* Native macOS build
* Windows cross build with MinGW and [ewpi](https://github.com/vtorri/ewpi/) for dependencies (this includes a native build of tooling needed for the full cross build afterwards)
* Linux build with all options (as much as possible combined) enabled
* Linux build with all options /as much as possible to have working build) disabled
* Linux build with wayland options enabled (ninja, ninja install, ninja test & example application build test)
* Linux build with default options (ninja, ninja install, ninja benchmark, ninja test & example application build test)
* Linux build with all options (as much as possible to have working build) disabled
* Linux build with wayland options enabled (this build includes ninja install, ninja test & example application build test)
* Linux build with default options (this build includes ninja install, ninja benchmark, ninja test & example application build test)
Depending on the available Travis resources such a build takes 20-30 minutes (OSX is the bottleneck).
Depending on the available Travis resources such a build takes 20-30 minutes (macOS is the bottleneck).
Every developer can push to their devs/$ID/ branches to trigger these builds and check the results before putting things into Phab.
## Daily cron CI Pipeline ##
@ -32,7 +32,7 @@ The daily cron job is running at ~ 17:30 CEST (Travis is not strict on the exact
* A release ready job which runs a full ninja dist
* 3 Linux distro builds (Ubuntu latest, Ubuntu LTS, Debian stable)
* [Coverity Scan](https://scan.coverity.com/projects/enlightenment-foundation-libraries) 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 (a mail to e-devel will be send for newly detected issues after analysis)
* Address sanitizer enabled build
* Exactness job running tests on elementary_test scenarios (pixel perfect regression and integration test-suite)
* [Codecov](https://codecov.io/github/Enlightenment/efl/) code coverage run (build with Travis Ubuntu Bionic distro)