Skip to content

Instantly share code, notes, and snippets.

@chumaknadya
Last active November 21, 2019 15:52
Show Gist options
  • Save chumaknadya/aaa37608d04f6feefd6a36b5703afa86 to your computer and use it in GitHub Desktop.
Save chumaknadya/aaa37608d04f6feefd6a36b5703afa86 to your computer and use it in GitHub Desktop.
steps:
# Update application version
- name: git-tag-and-push
image: quay.io/openware/sdk-tools:#{latest_tag} # don't forget to fill latest_tag
environment:
BOT_USERNAME: kite-bot
BOT_NAME: Kite Bot
BOT_EMAIL: kite-bot@heliostech.fr
BRANCH_NAME: ${DRONE_BRANCH}
REPO_NAME: ${DRONE_REPO}
GITHUB_API_KEY:
from_secret: kite_bot_key # don't forget to set up secret key in drone setting
commands:
- BUNDLE_GEMFILE=/sdk/Gemfile bundle exec rake --rakefile=/sdk/Rakefile ci:prebuild
when:
branch:
- master
- 2-3-stable # you need to put all stable branches here
# Build and push docker image using ".tags" file.
- name: docker-build-and-push
image: plugins/docker
settings:
username:
from_secret: quay_username
password:
from_secret: quay_password
repo: quay.io/openware/#{component_name} # don't forget to fill component name
registry: quay.io
when:
branch:
- master
- 2-3-stable # you need to put all stable branches here
# Push docs to sdk and Notify
- name: push-and-notify
image: quay.io/openware/sdk-tools:#{latest_tag} # don't forget to fill latest_tag
environment:
BOT_USERNAME: kite-bot
BOT_NAME: Kite Bot
BOT_EMAIL: kite-bot@heliostech.fr
BRANCH_NAME: ${DRONE_BRANCH}
SDK_BRANCH: ${DRONE_BRANCH}
REPO_NAME: ${DRONE_REPO}
TELEGRAM_BOT_TOKEN:
from_secret: telegram_bot_token
TELEGRAM_CHAT_ID:
from_secret: telegram_chat_id
SLACK_TOKEN:
from_secret: slack_token
SLACK_CHANNEL:
from_secret: slack_channel
GITHUB_API_KEY:
from_secret: kite_bot_key # don't forget to set up secret key in drone setting
commands:
- BUNDLE_GEMFILE=/sdk/Gemfile bundle exec rake --rakefile=/sdk/Rakefile ci:postbuild[/drone/src]
when:
branch:
- master
- 2-3-stable # you need to put all stable branches here
trigger:
event:
- push
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment