RIOT-OS/RIOT
RIOT-OS/RIOT
1
0
Fork 0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2024-12-29 04:50:03 +01:00
Code Releases Activity
26f9f7fa2d
RIOT/.travis.yml

39 lines
1.8 KiB
YAML
Raw Normal View History

Add basic travis-ci integration This PR adds the basic integration for [Travis CI][tci]. The config file `.travis.yml` tells the server to setup the basic build system, and run `compile_test.py`. If not all examples and tests could be built, then the Travis CI integration adds a warning to "merge" button on the bottom of the Github page. Of course this integration makes little sense until #1049 is resolved, because new bugs and old bugs cannot be told apart. Also (of course) only because everything still builds, a PR still can intruduce a multitude of runtime errors. This integrations is meant to work additionally to our Jenkings. Users can activate the test in their own RIOT forks to run the test before opening a PR to master. [tci]: https://travis-ci.org/
2014-04-11 17:06:25 +02:00
language: c
Travis: enable apt caching This should speed up the installation process a bit.
2014-09-20 13:20:30 +02:00
cache: apt
tests: limit concurrency level Some Travis CI machines have 32 CPUs. This sets our concurrency level to 33. Travis CI kills our buildtest for obvious reasons. This PR limits the concurrency level to 8 on Travis CI.
2014-08-21 19:37:06 +02:00
env:
travis: add static tests as a matrix build target
2015-02-24 00:17:28 +01:00
- NPROC_MAX=8 BUILDTEST_MCU_GROUP=static-tests
CI: split up Cortex-M4 in two groups
2015-12-03 17:38:24 +01:00
- NPROC_MAX=8 BUILDTEST_MCU_GROUP=cortex_m4_2
- NPROC_MAX=8 BUILDTEST_MCU_GROUP=cortex_m4_1
CI: split up Cortex-M0 in two groups
2015-12-07 10:28:34 +01:00
- NPROC_MAX=8 BUILDTEST_MCU_GROUP=cortex_m0_2
- NPROC_MAX=8 BUILDTEST_MCU_GROUP=cortex_m0_1
travis reorder mcu groups
2015-09-04 12:58:52 +02:00
- NPROC_MAX=8 BUILDTEST_MCU_GROUP=x86
- NPROC_MAX=8 BUILDTEST_MCU_GROUP=cortex_m3_2
- NPROC_MAX=8 BUILDTEST_MCU_GROUP=cortex_m3_1
tests/travis: split buildtests into MCU groups.
2015-02-06 03:36:16 +01:00
- NPROC_MAX=8 BUILDTEST_MCU_GROUP=avr8
- NPROC_MAX=8 BUILDTEST_MCU_GROUP=msp430
- NPROC_MAX=8 BUILDTEST_MCU_GROUP=arm7
tests: limit concurrency level Some Travis CI machines have 32 CPUs. This sets our concurrency level to 33. Travis CI kills our buildtest for obvious reasons. This PR limits the concurrency level to 8 on Travis CI.
2014-08-21 19:37:06 +02:00
Add basic travis-ci integration This PR adds the basic integration for [Travis CI][tci]. The config file `.travis.yml` tells the server to setup the basic build system, and run `compile_test.py`. If not all examples and tests could be built, then the Travis CI integration adds a warning to "merge" button on the bottom of the Github page. Of course this integration makes little sense until #1049 is resolved, because new bugs and old bugs cannot be told apart. Also (of course) only because everything still builds, a PR still can intruduce a multitude of runtime errors. This integrations is meant to work additionally to our Jenkings. Users can activate the test in their own RIOT forks to run the test before opening a PR to master. [tci]: https://travis-ci.org/
2014-04-11 17:06:25 +02:00
before_install:
travis: exit before before_install phase
2015-05-26 19:28:44 +02:00
- source ./dist/tools/pr_check/check_labels.sh
- test -z "$TRAVIS_PULL_REQUEST" || test "$BUILDTEST_MCU_GROUP" = "static-tests" || check_gh_label "Ready for CI build" || exit 1
Add basic travis-ci integration This PR adds the basic integration for [Travis CI][tci]. The config file `.travis.yml` tells the server to setup the basic build system, and run `compile_test.py`. If not all examples and tests could be built, then the Travis CI integration adds a warning to "merge" button on the bottom of the Github page. Of course this integration makes little sense until #1049 is resolved, because new bugs and old bugs cannot be told apart. Also (of course) only because everything still builds, a PR still can intruduce a multitude of runtime errors. This integrations is meant to work additionally to our Jenkings. Users can activate the test in their own RIOT forks to run the test before opening a PR to master. [tci]: https://travis-ci.org/
2014-04-11 17:06:25 +02:00
- echo 'deb http://us.archive.ubuntu.com/ubuntu trusty main restricted universe multiverse' | sudo tee /etc/apt/sources.list.d/trusty.list > /dev/null
- echo 'deb http://us.archive.ubuntu.com/ubuntu trusty-backports main restricted universe multiverse' | sudo tee -a /etc/apt/sources.list.d/trusty.list > /dev/null
- echo 'deb http://us.archive.ubuntu.com/ubuntu trusty-security main restricted universe multiverse' | sudo tee -a /etc/apt/sources.list.d/trusty.list > /dev/null
- echo 'deb http://us.archive.ubuntu.com/ubuntu trusty-updates main restricted universe multiverse' | sudo tee -a /etc/apt/sources.list.d/trusty.list > /dev/null
- sudo add-apt-repository -y ppa:terry.guo/gcc-arm-embedded
- sudo apt-get update
install:
Travis: merge install commands
2014-09-22 10:54:26 +02:00
- >
tests/travis: split buildtests into MCU groups.
2015-02-06 03:36:16 +01:00
sudo apt-get install $(./dist/tools/travis-scripts/get-pkg-list.py)
setup git committer info in Travis pkg/ Makefiles based on `Makefile.git` fail in Travis when attempting to apply patches with `git am` because no committer info is set. This patch adds a dummy Travis username and mail in the 'install' step to satisfy git.
2014-07-07 23:48:02 +02:00
- git config --global user.email "travis@example.com"
- git config --global user.name "Travis CI"
Add basic travis-ci integration This PR adds the basic integration for [Travis CI][tci]. The config file `.travis.yml` tells the server to setup the basic build system, and run `compile_test.py`. If not all examples and tests could be built, then the Travis CI integration adds a warning to "merge" button on the bottom of the Github page. Of course this integration makes little sense until #1049 is resolved, because new bugs and old bugs cannot be told apart. Also (of course) only because everything still builds, a PR still can intruduce a multitude of runtime errors. This integrations is meant to work additionally to our Jenkings. Users can activate the test in their own RIOT forks to run the test before opening a PR to master. [tci]: https://travis-ci.org/
2014-04-11 17:06:25 +02:00
script:
tests/travis: split buildtests into MCU groups.
2015-02-06 03:36:16 +01:00
- ./dist/tools/travis-scripts/build_and_test.sh
Add basic travis-ci integration This PR adds the basic integration for [Travis CI][tci]. The config file `.travis.yml` tells the server to setup the basic build system, and run `compile_test.py`. If not all examples and tests could be built, then the Travis CI integration adds a warning to "merge" button on the bottom of the Github page. Of course this integration makes little sense until #1049 is resolved, because new bugs and old bugs cannot be told apart. Also (of course) only because everything still builds, a PR still can intruduce a multitude of runtime errors. This integrations is meant to work additionally to our Jenkings. Users can activate the test in their own RIOT forks to run the test before opening a PR to master. [tci]: https://travis-ci.org/
2014-04-11 17:06:25 +02:00
notifications:
email: false
Copy Permalink