Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🤖 Automatically create GH release after cnspec bump #271

Merged
merged 1 commit into from
Jul 16, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .github/workflows/cnspec-update.yml
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,7 @@ jobs:
MAJOR=$(echo "${{ steps.version.outputs.version }}" | cut -d. -f1)
go get go.mondoo.com/cnspec/${MAJOR}@${{ steps.version.outputs.version }}
go mod tidy
echo "${{ steps.version.outputs.version }}" > VERSION

- name: Prepare title and branch name
id: branch
Expand Down
62 changes: 62 additions & 0 deletions .github/workflows/gh-release.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,62 @@
name: Create GitHub Release

## Only trigger release when the VERSION file changed on main branch
on:
push:
paths:
- "VERSION"
branches:
- main

jobs:
create-gh-release:
name: GH Release
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Set release version
run: echo "RELEASE_VERSION=$(cat VERSION)" >> $GITHUB_ENV
- name: Release
uses: softprops/action-gh-release@v2
with:
tag_name: ${{ env.RELEASE_VERSION }}
generate_release_notes: true
make_latest: true
token: ${{ secrets.PACKER_PLUGIN_DEPLOY_KEY_PRIV }}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need a specific token to bypass GH limitations on the GITHUB_TOKEN to trigger subsequent workflow runs.


check-release:
name: Check whether the release actually started
runs-on: ubuntu-latest
needs: create-gh-release
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Set release version
run: echo "RELEASE_VERSION=$(cat VERSION)" >> $GITHUB_ENV
- name: Release file present?
id: check_release_file
uses: nick-fields/retry@v3
with:
retry_wait_seconds: 10
timeout_seconds: 5
max_attempts: 60
retry_on: error
# error on HTTP code different to 302
command: curl -o /dev/null -s -w "%{http_code}\n" "https://github.com/mondoohq/packer-plugin-cnspec/releases/download/${{ env.RELEASE_VERSION }}/packer-plugin-cnspec_${{ env.RELEASE_VERSION }}_SHA256SUMS" | grep 302
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I couldn't find an easy way to query the workflow itself. When the workflow is done, we should have this file.

- uses: sarisia/actions-status-discord@v1
if : ${{ always() && steps.check_release_file.outputs.status == 'failure' }}
with:
webhook: ${{ secrets.DISCORD_WEBHOOK }}
benr marked this conversation as resolved.
Show resolved Hide resolved
status: ${{ steps.check_release_file.outputs.status }}
url: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
description: Workflow ${{ github.workflow }} for ${{ env.RELEASE_VERSION }} failed
color: 0xff4d4d
- uses: sarisia/actions-status-discord@v1
if : ${{ always() && steps.check_release_file.outputs.status == 'success' }}
with:
webhook: ${{ secrets.DISCORD_WEBHOOK }}
status: ${{ steps.check_release_file.outputs.status }}
url: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
description: Workflow ${{ github.workflow }} for ${{ env.RELEASE_VERSION }} succeeded
color: 0x5dea20
Loading