mbedtls/.travis.yml

language: c
compiler: gcc
sudo: false
cache: ccache

jobs:
  include:
    - name: Windows
      os: windows
      before_install:
        - choco install python --version=3.5.4
      env:
        - PATH=/c/Python35:/c/Python35/Scripts:$PATH
      script:
        - echo "$PATH"
        - ls -l /c/Python35 /c/Python35/Scripts
        - type python; type python3; type python.exe; type python3.exe
        - python scripts/generate_psa_constants.py
        - sleep 5 # Give time for logs to catch up
        - scripts/windows_msbuild.bat v141 # Visual Studio 2017

after_failure:
- tests/scripts/travis-log-failure.sh

env:
  global:
    - SEED=1
    - secure: "FrI5d2s+ckckC17T66c8jm2jV6i2DkBPU5nyWzwbedjmEBeocREfQLd/x8yKpPzLDz7ghOvr+/GQvsPPn0dVkGlNzm3Q+hGHc/ujnASuUtGrcuMM+0ALnJ3k4rFr9xEvjJeWb4SmhJO5UCAZYvTItW4k7+bj9L+R6lt3TzQbXzg="
Travis configuration file 2014-04-17 16:16:05 +02:00			`language: c`
Travis: don't test with both gcc and clang In practice, we hardly ever get different outcomes, so there is no gain in running tests with different compilers. Experimentally, with the builds and tests we currently do and with the compiler versions on a Travis Ubuntu 16.04, gcc jobs are significantly faster than clang jobs (13 min vs 24 min). So use gcc. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com> 2020-04-21 22:13:43 +02:00			`compiler: gcc`
Migrate to Travis' new infrastructure 2015-08-04 15:59:34 +02:00			`sudo: false`
Enable ccache on Travis 2015-08-04 18:06:02 +02:00			`cache: ccache`
Create a block list for Travis CI, and fix the Coverity email 2018-11-22 11:14:03 +01:00
Travis: split the build into three parallel jobs Split the build between: * Basic checks * A build in the default configuration with extensive tests * Builds in other configurations with less testing The intent is to have one shorter job with basic tests, and two longer jobs that take roughly the same amount of time (split as evenly as possible while keeping an easy-to-understand separation). Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com> 2020-04-21 22:18:58 +02:00			`jobs:`
			`include:`
Travis: add a build with Visual Studio on Windows Travis now offers a Windows environment. Do a build with Visual Studio. This brings diversity into the Travis CI which otherwise only uses GCC and Clang. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com> 2020-04-25 23:25:10 +02:00			`- name: Windows`
			`os: windows`
Travis: Windows: install Python 3 and run generate_psa_constants.py Travis Windows machines currently don't have Python 3 preinstalled. We need it to run scripts/generate_psa_constants.py which is needed to build mbedTLS.sln. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com> 2020-04-26 14:09:09 +02:00			`before_install:`
found python Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com> 2020-04-26 20:11:53 +02:00			`- choco install python --version=3.5.4`
			`env:`
			`- PATH=/c/Python35:/c/Python35/Scripts:$PATH`
Travis: add a build with Visual Studio on Windows Travis now offers a Windows environment. Do a build with Visual Studio. This brings diversity into the Travis CI which otherwise only uses GCC and Clang. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com> 2020-04-25 23:25:10 +02:00			`script:`
Grrrr Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com> 2020-04-26 20:30:05 +02:00			`- echo "$PATH"`
			`- ls -l /c/Python35 /c/Python35/Scripts`
			`- type python; type python3; type python.exe; type python3.exe`
Oh? Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com> 2020-04-26 20:36:57 +02:00			`- python scripts/generate_psa_constants.py`
			`- sleep 5 # Give time for logs to catch up`
Travis: Windows: target Visual Studio 2017 Only the Visual Studio 2017 toolset is currently preinstalled on Travis. Use this, instead of our solution's default which is VS 2010. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com> 2020-04-26 13:12:55 +02:00			`- scripts/windows_msbuild.bat v141 # Visual Studio 2017`
Travis: add a build with Visual Studio on Windows Travis now offers a Windows environment. Do a build with Visual Studio. This brings diversity into the Travis CI which otherwise only uses GCC and Clang. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com> 2020-04-25 23:25:10 +02:00
Make Travis more chatty. Include the logs in the report after failing. 2016-03-21 10:22:58 +01:00			`after_failure:`
Fixes Travis post-mortem script dump following review Changes made: * Added copyright and project statement * Limited size of each file to dump to 1Mbyte * Changed name of script 2016-04-10 16:11:27 +02:00			`- tests/scripts/travis-log-failure.sh`
Travis: split the build into three parallel jobs Split the build between: * Basic checks * A build in the default configuration with extensive tests * Builds in other configurations with less testing The intent is to have one shorter job with basic tests, and two longer jobs that take roughly the same amount of time (split as evenly as possible while keeping an easy-to-understand separation). Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com> 2020-04-21 22:18:58 +02:00
Updated Travis-CI config with Coverity addon 2014-05-02 16:19:04 +02:00			`env:`
			`global:`
Fix the proxy seed in Travis runs This is what we do in Jenkins, so it only makes sense to do it here as well. This will avoid random failures for no other reason than the proxy was dropping all the messages due to an unlucky PRNG seed. See https://docs.travis-ci.com/user/environment-variables/ for syntax 2019-02-27 10:46:56 +01:00			`- SEED=1`
Update Coverity secure token 2019-09-10 18:22:52 +02:00			`- secure: "FrI5d2s+ckckC17T66c8jm2jV6i2DkBPU5nyWzwbedjmEBeocREfQLd/x8yKpPzLDz7ghOvr+/GQvsPPn0dVkGlNzm3Q+hGHc/ujnASuUtGrcuMM+0ALnJ3k4rFr9xEvjJeWb4SmhJO5UCAZYvTItW4k7+bj9L+R6lt3TzQbXzg="`