Similar to GitLab, the Quboo CLI script includes support for CircleCI.
Adding Quboo to CircleCI pipelines
You can simply add a new step in your deployment pipelines in CircleCI and assign score to whoever triggered the pipeline.
In the Quboo example repository there is a script that demonstrates how you can set this up in your pipeline.
version: 2.1 jobs: build: docker: - image: maven:3.6-jdk-11 steps: - checkout - run: command: | mvn clean package release: docker: - image: alpine:3.7 steps: - checkout - run: command: | echo '^^^Not really releasing...^^^' score: docker: - image: mechero/quboo-cli:latest steps: - checkout - run: command: | quboo release "Circle CI Release example" workflows: version: 2 build_release_score: jobs: - build - release: requires: - build filters: branches: only: master - score: requires: - release filters: branches: only: master
As you see in the script, there is no reference to the player identifier there. The player is, by default, the last committer’s username. If you want to override it, this is possible by setting a value manually to the environment variable
Gamifying other processes with CircleCI
Remember that you can also use the CLI or the Score API to create your own game and give score for other actions such as contributing to documentation.