Skip to content

Commit

Permalink
Introduce github action to build release tarball.
Browse files Browse the repository at this point in the history
  • Loading branch information
morrone committed Jan 24, 2022
1 parent 204cdef commit 6fba32f
Showing 1 changed file with 49 additions and 0 deletions.
49 changes: 49 additions & 0 deletions .github/workflows/create-release.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,49 @@
name: Create Release

on:
push:
tags:
- '*'

jobs:
build:
name: Create Release
runs-on: ubuntu-20.04

steps:
- uses: actions/checkout@v2
# actions/checkout@v2 breaks annotated tags by converting them into
# lightweight tags, so we need to force fetch the tag again
# See: https://github.com/actions/checkout/issues/290
- name: Repair tag
run: git fetch -f origin ${{ github.ref }}:${{ github.ref }}
#- name: Verify tag is annotated
# run: if test x$(git for-each-ref ${{ github.ref }} | awk '{print $2}') = xtag; then /bin/true; else echo "\"${{ github.ref }}\" does not look like an annotated tag!"; /bin/false; fi
- name: bootstrap
run: sh bootstrap
- name: configure
run: ./configure
- name: make dist
run: |
make dist
echo TARBALL_NAME=$(ls *.tar.gz | head -1) >> $GITHUB_ENV
- name: Create Release
id: create_release
uses: actions/create-release@v1
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
tag_name: ${{ github.ref }}
release_name: Release ${{ github.ref }}
draft: false
prerelease: false
- name: Upload Release Asset
id: upload-release-asset
uses: actions/upload-release-asset@v1
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
upload_url: ${{ steps.create_release.outputs.upload_url }} # This pulls from the CREATE RELEASE step above, referencing it's ID to get its outputs object, which include a pload_url See this blog post for more info: https://jasonet.co/posts/new-features-of-github-actions/#passing-data-to-future-steps
asset_path: ./${{ env.TARBALL_NAME }}
asset_name: ${{ env.TARBALL_NAME }}
asset_content_type: application/gzip

0 comments on commit 6fba32f

Please sign in to comment.