Continuous Integration

When using Continuous Integration environments such as CircleCI, Travis CI, Jenkins, etc. you need to provide some things before using the Bojagi CLI.

For example you don't need to specify any Git and GitHub related information to the CLI commands because we can get them automatically with the CI provided environment variables.

This currently works with the following CI tools:

  • CircleCI
  • GitHub Actions
  • GitLab CI
  • Jenkins
  • TeamCity
  • TravisCI

In the future this list might get bigger.

Preparing your CI environment

To use the Bojagi CLI on your Continuous Integration environment you first need to expose the BOJAGI_SECRET of the repository. This is done with the BOJAGI_SECRET environment variable:

export BOJAGI_SECRET=my-super-secret-key-123

This secret you can get from the settings page of your repository or (when nothing is uploaded yet) on the main repository page on the bojagi webapp.

This secret needs to be added to the environmental variables of your CI environment. Please also make sure it is not visible in the logs, as this secret can be used to override the components in the corresponding repository later and should not be visibly exposed.

Using the CLI

After that you can use the CLI in your CI tool. For more information about this, read the CLI section.

← .bojagirc