Continuous Integration¶

Continous Integration (CI) is a practice of checking code repositories (typically a few times a day) to test for changes which may cause failures.

CI can be integrated into either scientific programming workflows or into code development

The most popular CI tools are:

Travis CI - fast, easy to set up, cloud based

Circle CI - fast, easy to set up, cloud based

Jenkins - free, can be hosted internally (requires server), highly customizable (plugins)

When to use CI?

building or hosting services to a community

developing versioned copies of containers for public consumption

DevOps + Data Science

Travis CI¶

Setup

Circle CI¶

Setup

Jenkins¶

Jenkins is a bit harder to set up because you need a dedicated server

Setup

GitHub Actions¶

GitHub now offers ‘actions’ which serve as an integrated CI for your repositories

Badges¶

Status badges can be embedded in a README.md. Badges let you show the state of code or documentation.

You can view a diverse list of different badges on Shields.io

Different Badge Styles¶

Now you can pass the style GET argument, to get custom styled badges same as you would for shields.io. If no argument is passed, flat is used as default.

STYLE	BADGE
flat
flat-square
for-the-badge
plastic
social

Self paced¶

Circle vs Jenkins vs Travis

Fix or improve this documentation:

On Github: Github Repo Link
Send feedback: Tutorials@CyVerse.org