SonarQube

• There are quality gates which all modules should pass:
  

Jenkins

The whole process (build, test, release, and deployment process) is automated by Jenkins. Each change in GitHub will initiate the CI process(branch push, pull request). Maven artifacts and NPM packages are stored in Nexus repository. There is a collaboration between AWS, Nexus and Jenkins which allows CI system automatically build environments which is used for testing and demonstrating purposes. The are 4 commonly used (but there are a lot more) environments:

• folio-testing - built from the latest master branch of the UI code. Job starts every hour. See Jenkins job.
• folio-snapshot - built from frontend master branch and latest version of backend modules that meet the dependency requirements of the frontend. Job starts every day at about 03:00 UTC. Jenkins job.
• folio-snapshot-stable - uses the alias of 'folio-snapshot' + integration and regression tests. Recommended for demos/acceptance testing.
• folio-latest
  

Other automation jobs can be found in Automation' folder 

Notifications about the build status will come into #folio-ci Slack channel. 

Here is the view of Jenkins folders:

Docker

Vagrant