TryGhost/Ghost
1
0
Fork 0
mirror of https://github.com/TryGhost/Ghost.git synced 2024-12-27 21:03:29 +03:00
Code Issues Projects Releases Wiki Activity
708d26a1a4
Ghost/.github/workflows/canary.yml

46 lines
1.3 KiB
YAML
Raw Normal View History

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 19:04:16 +03:00
name: Canary Build
on: workflow_dispatch
env:
FORCE_COLOR: 1
jobs:
canary:
runs-on: ubuntu-18.04
name: Canary
steps:
Update actions/checkout action to v3
2022-03-01 21:52:51 +03:00
- uses: actions/checkout@v3
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 19:04:16 +03:00
with:
fetch-depth: 0
submodules: true
Update actions/setup-node action to v3
2022-02-25 12:13:29 +03:00
- uses: actions/setup-node@v3
Disabled `FORCE_COLOR` on `setup-node` GitHub Action refs https://github.com/TryGhost/Ghost/pull/13716 refs https://github.com/actions/setup-node/issues/317#issuecomment-929694556 - the `setup-node` GitHub Action seems to use a shell command to get the cache path, but these are colorised when `FORCE_COLOR` is enabled - this causes the Action to fail to read the path correctly - the comment referenced above suggests to remove `FORCE_COLOR` but it's nice to have colored output for our tests - instead, I'm disabling the environment variable on the `setup-node` action so it still works - I've tested with the referenced PR and this unblocks dependency caching 🎉
2021-11-25 11:07:45 +03:00
env:
FORCE_COLOR: 0
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 19:04:16 +03:00
with:
🔥 Added support for Node 16 refs https://github.com/TryGhost/Toolbox/issues/71 - Node 16 is now LTS so we're adding support in Ghost - we're also bumping the minimum Node 14 version to 14.17.0 so we can merge dependencies who have higher Node 14 requirements than current - this commit adds Node 16 to the `package.json` engines and to CI - also bumps all dependencies that needed new versions to add Node 16 support
2021-10-26 22:12:37 +03:00
node-version: '14.17.0'
Added `yarn` cache to CI workflows (#13716)
2021-11-30 11:01:22 +03:00
cache: yarn
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 19:04:16 +03:00
- 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
Fixed canary build after `yarn` command changes refs https://github.com/TryGhost/Ghost/commit/7e6800b2b88d20942b0a3058a3d16cbab5f9bca7 - referenced commit deprecated `grunt main` in favor of `yarn main` but this wasn't updated so we never installed dependencies for Admin, which caused the build to break - this commit switches to the new command
2021-07-06 12:22:07 +03:00
- run: yarn main
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 19:04:16 +03:00
- 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
Update actions/upload-artifact action to v3
2022-03-03 23:04:30 +03:00
- uses: actions/upload-artifact@v3
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 19:04:16 +03:00
with:
name: ghost-canary
path: .dist/release/*
retention-days: 7
Reference in New Issue Copy Permalink