mirror of
https://github.com/fleetdm/fleet
synced 2026-04-21 13:37:30 +00:00
Update vulnerability dashboard to deploy from a parentless commit (#31887)
Changes: - Updated the `deploy-vulnerability-dashboard` workflow to deploy the app from a parentless commit.
This commit is contained in:
parent
2ba5a5e208
commit
53bb51e49f
2 changed files with 22 additions and 2 deletions
|
|
@ -37,6 +37,8 @@ jobs:
|
|||
heroku_email: ${{secrets.HEROKU_EMAIL_FOR_BOT_USER}}
|
||||
justlogin: true
|
||||
- run: heroku auth:whoami
|
||||
# Install the heroku-repo plugin in the Heroku CLI
|
||||
- run: heroku plugins:install heroku-repo
|
||||
|
||||
# Set the Node.js version
|
||||
- name: Use Node.js ${{ matrix.node-version }}
|
||||
|
|
@ -69,11 +71,13 @@ jobs:
|
|||
# Compile assets
|
||||
- run: cd ee/vulnerability-dashboard/ && npm run build-for-prod
|
||||
|
||||
# Reset the Heroku app's git repo to prevent errors when pushing to the repo. (See https://github.com/fleetdm/fleet/issues/14162 for more details)
|
||||
- run: heroku repo:reset -a vulnerability-dashboard
|
||||
|
||||
# Commit newly-built assets locally so we can push them to Heroku below.
|
||||
# (This commit will never be pushed to GitHub- only to Heroku.)
|
||||
# > The local config flags make this work in GitHub's environment.
|
||||
- run: git add ee/vulnerability-dashboard/.www
|
||||
- run: git -c "user.name=GitHub" -c "user.email=github@example.com" commit -am 'AUTOMATED COMMIT - Deployed the latest, including modified HTML layouts and .sailsrc file that reference minified assets.'
|
||||
|
||||
# Configure the Heroku app we'll be deploying to
|
||||
- run: heroku git:remote -a vulnerability-dashboard
|
||||
|
|
@ -83,7 +87,22 @@ jobs:
|
|||
# > Since a shallow clone was grabbed, we have to "unshallow" it before forcepushing.
|
||||
- run: echo "Unshallowing local repository…"
|
||||
- run: git fetch --prune --unshallow
|
||||
|
||||
# Deploy to Heroku
|
||||
- run: echo "Deploying branch '${GITHUB_REF##*/}' to Heroku…"
|
||||
- run: git push heroku +${GITHUB_REF##*/}:master
|
||||
- name: Deploy to Heroku
|
||||
run: |
|
||||
set -euo pipefail
|
||||
git add -A
|
||||
# Create a git tree object that contains only the changes in the /website folder.
|
||||
TREE=$(git write-tree)
|
||||
# Create a parentless commit from the tree object.
|
||||
COMMIT=$(git -c "user.name=Fleetwood" -c "user.email=github@example.com" \
|
||||
commit-tree "$TREE" \
|
||||
-m 'AUTOMATED COMMIT - Deployed the latest, including generated collateral such as compiled documentation, modified HTML layouts, and a .sailsrc file that references minified client-side code assets.')
|
||||
# Push the parentless commit to Heroku
|
||||
# Note: The commit pushed to Heroku will not contain the full git history.
|
||||
# This lets up deploy this app from the Fleet monorepo while working around Heroku's pack size limits.
|
||||
git push heroku "$COMMIT":refs/heads/master --force
|
||||
- name: 🌐 The dashboard has been deployed
|
||||
run: echo '' && echo '--' && echo 'OK, done. It should be live momentarily.' && echo '(if you get impatient, check the Heroku dashboard for status)'
|
||||
|
|
|
|||
|
|
@ -50,6 +50,7 @@ To run a local vulnerability dashboard with docker, you can follow these instruc
|
|||
>
|
||||
>- Password: `abc123`
|
||||
|
||||
|
||||
## How it's made
|
||||
|
||||
This is a [Sails v1](https://sailsjs.com) application:
|
||||
|
|
|
|||
Loading…
Reference in a new issue