mirror of
https://github.com/josmo/drone-rancher.git
synced 2026-06-04 18:24:22 +08:00
Joachim Hill-Grannec
36 lines
1.7 KiB
Markdown
Executable File
36 lines
1.7 KiB
Markdown
Executable File
Use the rancher plugin to upgrade a service in [rancher](http://rancher.com).
|
|
|
|
The following parameters are used to configure this plugin:
|
|
|
|
- `url` - url to your rancher server, including protocol and port
|
|
- `access_key` - rancher api access key
|
|
- `secret_key` - rancher api secret key
|
|
- `service` - name of rancher service to act on
|
|
- `docker_image` - new image to assign to service, including tag (`drone/drone:latest`)
|
|
- `sidekick` - sidekick name and docker image separated by space, multiple declaration supported
|
|
- `start_first` - start the new container before stopping the old one, defaults to `true`
|
|
- `confirm` - auto confirm the service upgrade if successful, defaults to `false`
|
|
- `timeout` - the maximum wait time in seconds for the service to upgrade, default to `30`
|
|
- `interval_millis` - the upgrade interval in milli seconds, defaults to `1000`
|
|
- `batch_size` - the upgrade batch size, defaults to `1`
|
|
|
|
The following is a sample Rancher configuration in your `.drone.yml` file:
|
|
|
|
```yaml
|
|
deploy:
|
|
rancher:
|
|
image: pelotech/drone-rancher
|
|
url: https://example.rancher.com
|
|
access_key: 1234567abcdefg
|
|
secret_key: abcdefg1234567
|
|
service: drone/drone
|
|
sidekick: nginx nginx:latest
|
|
sidekick: node node:latest
|
|
docker_image: drone/drone:latest
|
|
```
|
|
|
|
if you want to add secrets for the access_key and secret_key it's RANCHER_ACCESS_KEY and RANCHER_SECRET_KEY
|
|
|
|
|
|
Note that if your `service` is part of a stack, you should use the notation `stackname/servicename` as this will make sure that the found service is part of the correct stack. If no stack is specified, this plugin will update the first service with a matching name which may not be what you want.
|