forked from letsencrypt/boulder
-
Notifications
You must be signed in to change notification settings - Fork 0
/
.travis.yml
59 lines (48 loc) · 1.17 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
language: go
go:
- 1.5.2
addons:
hosts:
- le.wtf
apt:
packages:
- lsb-release
- python-dev
- python-virtualenv
- gcc
- libaugeas0
- libssl-dev
- libffi-dev
- ca-certificates
- rsyslog
mariadb: "10.0"
sudo: false
services:
- rabbitmq
matrix:
fast_finish: true
# Only build pushes to the master branch, PRs, and branches beginning with
# `test-`. You should not push branches beginning with `test-` to the
# letsencrypt repository, but this is a convenient way to push branches to your
# own fork of the repostiroy to ensure Travis passes before submitting a PR.
# For instance, you might run:
# git push myremote branchname:test-branchname
branches:
only:
- master
- /^test-.*$/
before_install:
- travis_retry test/travis-before-install.sh
# Override default Travis install command to prevent it from adding
# Godeps/_workspace to GOPATH. When that happens, it hides failures that should
# arise from importing non-vendorized paths.
install:
- true
env:
global:
- LETSENCRYPT_PATH=$HOME/letsencrypt
matrix:
- RUN="integration vet lint fmt migrations"
- RUN="unit"
script:
- bash test.sh