- This file is intend to be a sample of
.travis.yml
file for the Travis-CI.
-
CI here stands for Continuous Integration
-
The Wikipedia describes as follows:
...CI is the practice of merging all developers' working copies to a shared mainline several times a day.
-
To my understanding, when integrating a new work, the code base integrity must be confirmed.
-
As CI may execute a number of tasks such as building, testing, and merging several times a day, certain level of automation is desirable.
-
For example, Jenkins, an open source project, can be employed to automate the CI/CD.
What is the Travis-CI.org?
- Also from the Wikipedia:
Travis-CI is a hosted CI service used to build and test software project hosted at GitHub.
- The company HQ is located in Berlin, Germany.
-
When a developer
git push
s to a Travis-CI-enabled GitHub repository, Travis-CI would build and test the software. -
Travis-CI would search for this
.travis-ci.yml
file at the root of the repository. -
This
.travis-ci.yml
file would describe the procedures to build and test the software. -
.yml
means YAML format.
-
One possible way to simplify the
.travis.yml
file is to write several shell script files describing subsections of the procedure :before_install
,install
, andscript
-
For example, to run a
my_before_install.sh
file, one may consider adding following lines to the.travis.yml
file.
before_install:
- . my_before_install.sh
- Also consider using
pip install --requirement <file>
[ref] - This repo includes a simple (untested) python script converting
conda
recipe yaml files topip
requirement files - At first, please start small