-
Notifications
You must be signed in to change notification settings - Fork 1
/
.binstar.yml
73 lines (65 loc) · 2.61 KB
/
.binstar.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
## The package attribute specifies a binstar package namespace to build the package to.
## This can be specified here or on the command line
package: openmm-dev
## You can also specify the account to upload to,
## you must be an admin of that account, this
## defaults to your user account
user: omnia
#===============================================================================
# Build Matrix Options
# These options may be a single item, a list or empty
# The resulting number of builds is [platform * engine * env]
#===============================================================================
## The platforms to build on.
## platform defaults to linux-64
platform:
- linux-64
# - linux-32
## The engine are the inital conda packages you want to run with
engine:
- python=2.7
- python=3.3
- python=3.4
## The env param is an environment variable list
# env:
# - MY_ENV=A CC=gcc
# - MY_ENV=B
#===============================================================================
# Script options
# These options may be broken out into the before_script, script and after_script
# or not, that is up to you
#===============================================================================
## Run before the script
before_script:
- echo "before_script!"
## Put your main computations here!
script:
- echo "This is my binstar build!"
# - conda install --yes --quiet conda-build jinja2
- conda update --quiet --yes -n root conda-build
- conda install --quiet --yes -c https://conda.binstar.org/anaconda llvm
- conda config --add channels https://conda.binstar.org/omnia
- conda build --quiet .
## This will run after the script regardless of the result of script
## BINSTAR_BUILD_RESULT=[succcess|failure]
# after_script:
# - echo "The build was a $BINSTAR_BUILD_RESULT" | tee artifact1.txt
## This will be run only after a successful build
# after_success:
# - echo "after_success!"
## This will be run only after a build failure
# after_failure:
# - echo "after_failure!"
#===============================================================================
# Build Results
# Build results are split into two categories: artifacts and targets
# You may omit either key and stiff have a successful build
# They may be a string, list and contain any bash glob
#===============================================================================
## Build Targets: Upload these files to your binstar package
## build targets may be a list of files (globs allows) to upload
## The special build targets 'conda' and 'pypi' may be used to
## upload conda builds
## e.g. conda is an alias for /opt/anaconda/conda-bld/<os-arch>/*.tar.bz2
build_targets:
- conda