Continuous Integration Tools
Travis CI
Travis CI is a hosted continuous integration service used to build and test software projects hosted at GitHub. The point of this is that you can often discover very quickly if your commit broke something, and fix it before it becomes a problem.
As a continuous integration platform, Travis CI supports your development process by automatically building and testing code changes, providing immediate feedback on the success of the change. Travis CI can also automate other parts of your development process by managing deployments and notifications.
Configuration
Travis CI is configured by adding a file named .travis.yml, which is a YAML format text file, to the root directory of the repository. This file specifies the programming language used, the desired building and testing environment (including dependencies which must be installed before the software can be built and tested), and various other parameters.
In the .travis.yml a file you're specifying your OS, the programming language, your repo branch, the project file name and other details. Travis-CI will use the specific compilers which installed on their server to compile your code.
Building
When you run a build, Travis CI clones your GitHub repository into a brand-new virtual environment, and carries out a series of tasks to build and test your code. If one or more of those tasks fail, the build is considered broken. If none of the tasks fail, the build is considered passed and Travis CI can deploy your code to a web server or application host.
CI builds can also automate other parts of your delivery workflow. This means you can have jobs depend on each other with Build Stages, set up notifications, prepare deployments after builds and many other tasks.
Build Lifecycle of Travis CI job
A job is made of two main parts:
- install: install any dependencies required
- script: run the build script
Tutorial: https://docs.travis-ci.com/user/tutorial/