In this directory you'll find a .drone.yml file with some basic examples of how to configure a drone pipeline:
- test: has multiple testing steps, using the shared workspace to avoid having to run npm install each time. The pipeline runs on all triggers
- build-dry-run: does a docker build dry run, it's only triggered on PRs
- push-latest-build: build the docker image and pushes it to docker hub
- release: builds a tagged docker image and pushes it to docker hub, after that publishes on npm.
These pipelines use the docker plugin and npm plugin. They make use of the following secrets which should be defined on the group or repository in your drone instance:
- docker_username
- docker_password
- npm_access_token
The pipeline uses the DRONE_REPO pipeline param for that. If you this should be different, you have several options:
- hardcode the correct repository in every pipeline
- use drone's string operations to modify the parameter