Here, we are presenting the process that we recommend to our customers, but feel free to adapt it to your workflow/requirements.
We need two steps : a validation one, and a deployment one.
For each branch of your code base, you need to validate that your updated documentation file is still valid and will not fail during deployment. Using the
bump validate command each time a branch is pushed will fail the build if the documentation file is not valid.
Once your branch has been merged into your main branch (generally the
master one), you will want to deploy your new documentation file and make it live. You will use the
bump deploy command.
The simplest way to use our CLI tool is to add a
Gemfile to your project. You can find an example here: https://github.com/bump-sh/bump-ci-example/blob/master/Gemfile.
If you prefer not using a
Gemfile , be sure to run
gem install bump-cli before calling the
Here are examples for integrating Bump with the most known CI products:
GitHub actions: https://github.com/bump-sh/github-action
The GitHub actions example uses a dedicated action we have specially crafted for you. You may find more information on GitHub market place.
Note that if you don't want to keep the private token and id in your code base, you should use environment variables. Our CLI automatically recognizes these 2 variables:
BUMP_ID : your documentation public id
BUMP_TOKEN : your documentation private token