yuzu/mbedtls
1
0
Fork 0
mirror of https://github.com/yuzu-emu/mbedtls.git synced 2025-01-05 21:25:30 +00:00
Code Issues Packages Projects Releases Wiki Activity
mbedtls/.travis.yml

27 lines
734 B
YAML
Raw Normal View History

Travis configuration file
2014-04-17 14:16:05 +00: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 20:13:43 +00:00
compiler: gcc
Migrate to Travis' new infrastructure
2015-08-04 13:59:34 +00:00
sudo: false
Enable ccache on Travis
2015-08-04 16:06:02 +00:00
cache: ccache
Create a block list for Travis CI, and fix the Coverity email
2018-11-22 10:14:03 +00: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 20:18:58 +00: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 21:25:10 +00: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 12:09:09 +00:00
before_install:
- choco install python3
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 21:25:10 +00:00
script:
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 12:09:09 +00:00
- export
more info about python and python3 Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2020-04-26 16:56:52 +00:00
- (IFS=:; for x in $PATH; do echo "$x"; ls -l "$x"; echo; done)
- type python; python --version
- type python3; python3 --version
- python scripts/generate_psa_constants.py
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 11:12:55 +00: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 21:25:10 +00:00
Make Travis more chatty. Include the logs in the report after failing.
2016-03-21 09:22:58 +00: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 14:11:27 +00: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 20:18:58 +00:00
Updated Travis-CI config with Coverity addon
2014-05-02 14:19:04 +00: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 09:46:56 +00:00
- SEED=1
Update Coverity secure token
2019-09-10 16:22:52 +00:00
- secure: "FrI5d2s+ckckC17T66c8jm2jV6i2DkBPU5nyWzwbedjmEBeocREfQLd/x8yKpPzLDz7ghOvr+/GQvsPPn0dVkGlNzm3Q+hGHc/ujnASuUtGrcuMM+0ALnJ3k4rFr9xEvjJeWb4SmhJO5UCAZYvTItW4k7+bj9L+R6lt3TzQbXzg="
Reference in a new issue Copy permalink