class Danger::Drone
### CI
Setup
With Drone
you run the docker images yourself, so you will want to add ‘bundle exec danger` at the end of your `.drone.yml`.
```shell build: image: golang commands: - ... - bundle exec danger ```
### Token Setup
As this is self-hosted, you will need to expose the ‘DANGER_GITHUB_API_TOKEN` as a secret to your builds:
Drone
secrets: readme.drone.io/usage/secret-guide/ NOTE: This is a new syntax in DroneCI 0.6+
“‘yml
build: image: golang secrets: - DANGER_GITHUB_API_TOKEN commands: - ... - bundle exec danger
“‘
Public Class Methods
Source
# File lib/danger/ci_source/drone.rb, line 49 def initialize(env) if self.class.validates_as_ci_post_06?(env) self.repo_slug = "#{env['DRONE_REPO_OWNER']}/#{env['DRONE_REPO_NAME']}" self.repo_url = env["DRONE_REPO_LINK"] if self.class.validates_as_ci_post_06?(env) elsif self.class.validates_as_ci_pre_06?(env) self.repo_slug = env["DRONE_REPO"] self.repo_url = GitRepo.new.origins end self.pull_request_id = env["DRONE_PULL_REQUEST"] end
Source
# File lib/danger/ci_source/drone.rb, line 37 def self.validates_as_ci?(env) validates_as_ci_post_06?(env) or validates_as_ci_pre_06?(env) end
Source
# File lib/danger/ci_source/drone.rb, line 62 def self.validates_as_ci_post_06?(env) env.key? "DRONE_REPO_OWNER" and env.key? "DRONE_REPO_NAME" end
Check if this build is valid for CI
with drone 0.6 or later
Source
# File lib/danger/ci_source/drone.rb, line 67 def self.validates_as_ci_pre_06?(env) env.key? "DRONE_REPO" end
Checks if this build is valid for CI
with drone 0.5 or earlier
Source
# File lib/danger/ci_source/drone.rb, line 41 def self.validates_as_pr?(env) env["DRONE_PULL_REQUEST"].to_i > 0 end
Public Instance Methods
Source
# File lib/danger/ci_source/drone.rb, line 45 def supported_request_sources @supported_request_sources ||= [Danger::RequestSources::GitHub, Danger::RequestSources::GitLab] end