Warning Drone cloud stopped working for months and as the developers of Drone seemed to stop caring I'm no longer able to fully test this nor will I longer have any use of it, as a result I'm stopping all development of this plugin.

CI/CD build status:

Code coverage:

Drone plugin for deploying to nebula.

This plugin can be used to deploy applications to a nebula server, it will create\update the given nebula tasks as needed.

The below pipeline configuration demonstrates simple usage:

In addition to the .drone.yml file you will need to create a nebula.json file that contains the nebula configuration as well as the "app_name" (for app) or "cron_job_name" (for cron_job) field. Please see here for an example.

kind: pipeline type: docker name: default steps: - name: nebula_deploy image: nebulaorchestrator/drone-nebula settings: nebula_host: my-nebula-host.com nebula_job_file: nebula.json

Example configuration with values substitution:

kind: pipeline type: docker name: default steps: - name: nebula_deploy image: nebulaorchestrator/drone-nebula settings: nebula_host: my-nebula-host.com nebula_job_file: nebula.json my_image_tag: my_dynamic_image

In the nebula.json file (please note the $ before the PLUGIN_MY_IMAGE_TAG key):

{ ... "image": "myrepo/myimage:$PLUGIN_MY_IMAGE_TAG", ... }

will result in:

{ ... "image": "myrepo/myimage:my_dynamic_image", ... }

The nebula server FQDN\IP, required

The nebula configuration file location relative to the root folder of the repo, defaults to nebula.json

The nebula basic_auth username to use, defaults to None (no basic auth is used)

The nebula basic_auth password to use, defaults to None (no basic auth is used)

The nebula token_auth token to use, defaults to None (no token auth is used)

The nebula server port, defaults to 80

The nebula server protocol, defaults to "http"

The type of nebula job, "app" or "cron_job", defaults to "app"