Ghost/.github/workflows/canary.yml
Daniel Lockyer 84bfbae282
Extracted canary build to separate workflow
no issue

- by extracting it to a different workflow that uses the
  `workflow_dispatch` trigger, we can manually run a build, but also
  trigger it from Admin so we can always stay up-to-date
2021-06-01 17:04:16 +01:00

43 lines
1.3 KiB
YAML

name: Canary Build
on: workflow_dispatch
env:
FORCE_COLOR: 1
jobs:
canary:
runs-on: ubuntu-18.04
name: Canary
steps:
- uses: actions/checkout@v2
with:
fetch-depth: 0
submodules: true
- uses: actions/setup-node@v2
with:
node-version: '14.16.1'
- name: Set up Git
run: |
git config --global pull.rebase true
git config --global user.name "Ghost CI"
git config --global user.email "ghost@example.com"
- run: yarn
- run: grunt main
- run: echo "ghost_hash=$(git rev-parse --short HEAD)" >> $GITHUB_ENV
- run: echo "ghost_admin_hash=$(git rev-parse --short HEAD)" >> $GITHUB_ENV
working-directory: core/client
- run: if [ -n "$(git status --porcelain)" ]; then git add core/client content/themes/casper && git commit -m "Updated Ghost-Admin and Casper"; fi
- run: npm version preminor --preid="pre.$ghost_hash.$ghost_admin_hash"
- run: npm version preminor --preid="pre.$ghost_hash.$ghost_admin_hash"
working-directory: core/client
- run: grunt release --skip-update
- uses: actions/upload-artifact@v2
with:
name: ghost-canary
path: .dist/release/*
retention-days: 7