-
Notifications
You must be signed in to change notification settings - Fork 0
/
.travis.yml
109 lines (88 loc) · 2.5 KB
/
.travis.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
sudo: required
dist: trusty
# Set up notification options
notifications:
email:
recipients:
- ermal@media.mit.edu
# change is when the repo status goes from pass to fail or vice versa
on_success: change
on_failure: always
# specify language
language: cpp
# specify language options
compiler: gcc
git:
depth: 3
# configure which branches to run
branches:
# whitelist
only:
- master
- /^deploy-.*$/ # regex ok
# blacklist
except:
- dontrunme
- test
# declare your environment variables
env:
# global will stay the same across all matrix possibilities (will not create additional combinations to run)
global:
- SECRET_TOKEN=k399dkkgklsk
# matrix variables will create a new build for each specified variable
matrix:
- CMAKE_BUILD_TYPE=Release CUDA=6.5-14
- CMAKE_BUILD_TYPE=Release CUDA=7.0-28
- CMAKE_BUILD_TYPE=Release CUDA=7.5-18
- CMAKE_BUILD_TYPE=Release CUDA=8.0.44-1
- CMAKE_BUILD_TYPE=Debug CUDA=6.5-14
- CMAKE_BUILD_TYPE=Debug CUDA=7.0-28
- CMAKE_BUILD_TYPE=Debug CUDA=7.5-18
- CMAKE_BUILD_TYPE=Debug CUDA=8.0.44-1
# enable services (stuff like DBs, MQs)
# services:
## begin build steps
####################
before_install:
- sudo apt-get update -qq
- sudo apt-get install -qq cmake g++ libboost-all-dev libglew-dev libpng-dev zlib1g-dev libglm-dev libsdl2-dev libassimp-dev liblog4cxx10-dev qtbase5-dev
install:
# Install the CUDA toolkit
- echo "Installing CUDA library"
- source .travis/install-cuda-trusty.sh
#before_script:
# - bower install
script:
- echo "Configuring DSCP4 cmake project"
- cd render_algorithms/dscp4/build/
- cmake .. -DCMAKE_BUILD_TYPE=${CMAKE_BUILD_TYPE}
- make
after_success:
- echo "SUCCESSFUL BUILD"
before_deploy:
# check that build passed successfully
# add the \ afterwards to tell travis it's part of the same command thanks @markhuge
#- test $TRAVIS_TEST_RESULT = 0 \
# && gulp build \
# && cd dist \
# && npm install --prod \
# && cd $TRAVIS_BUILD_DIR \
# && tar -zcvf amber-storm-$TRAVIS_BRANCH.tar.gz dist \
# && export PRODBUILDCOMPLETE=true
## Deployment options
####################
#deploy:
# # specify the deployment provider
# provider: releases
# # options for provider
# api_key:
# secure: securekeyhere
# file: myrepo-$TRAVIS_BRANCH.tar.gz
# # conditions for deployment
# on:
# condition: $PRODBUILDCOMPLETE = true
# repo: myname/myrepo
# all_branches: true
# tags: true
#after_deploy:
# - ssh git@mysite.biz "./deploy.sh $TRAVIS_BRANCH"