Captains Log

by Target

sourcereadmeimageOriginal doc

A Drone plugin that helps organize release information in Slack

Example

kind: pipeline
name: default

steps:
- name: my-release-log-step
  image: target/captains-log:1
  settings:
    secrets: [ SLACK_TOKEN, SLACK_URL, GITHUB_TOKEN ] 
    github_owner: target
    github_repo: captains-log
    jira_team_domain: myteamnamespace

Properties

• secrets

  stringoptional

  slack and github secrets

  Default: none

• github_owner

  stringrequired

  The owner of the GitHub repository

  Default: none

• github_repo

  stringrequired

  Target repository name

  Default: none

• jira_team_domain

  stringrequired

  namespace of Jira workspace (e.g. `jira.myteamnamespace.com`)

  Default: none

• github_tag_id

  stringoptional

  regex to match on specific tags

  Default: none

• slack_channel

  stringoptional

  when using the API, you should use slack_channel to specify which room you'd like to post to. When using SLACK_URL you should not specify the room (i.e. slack_channel) because the room is already a part of the webhook.

  Default: none

• teams

  arrayoptional

  a list of teams which allows you to organize the output of Captains Log into meaningful chunks.

  Default: none

• enterprise_host

  stringoptional

  if you use Enterprise Github, this is where you would supply the custom domain.

  Default: none