Setting up Continuous Integration

Setting up Continuous Integration (CI) for a JHipster application is harder than for a classic typical Spring MVC application because of the complexity associated with maintaining a build composed of 2 software stacks:

• the Java back-end code with Maven or Gradle
• the JavaScript front-end with NodeJS, NPM and Gulp

Each stack comes with its own dependency management (Maven artifacts, NPM packages) with potential conflicts to solve.

JHipster should support the following CI systems out of the box:

• Jenkins:
  • Setting up Jenkins 1
  • Setting up Jenkins 2 (recommended)
• Travis: refer to the Travis Documentation, note that a .travis.yml configuration file is generated with your application.

Moreover, the JHipster CI module provides support for other CI systems like Gitlab CI and Circle CI.