Matrix/element-call-Github
1
0
Fork 0
mirror of https://github.com/vector-im/element-call.git synced 2024-11-15 00:04:59 +08:00
Code Issues Packages Projects Releases Wiki Activity
1d43bd26ed
element-call-Github/.github/workflows/publish.yaml

65 lines
2.1 KiB
YAML
Raw Normal View History

Add CI
2021-12-21 00:58:37 +08:00
name: Build & publish images to the package registry for tags
on:
release:
types: [published]
refactored to reuse the build workflow
2024-04-15 16:53:42 +08:00
workflow_run:
workflows: ["Build"]
add docker builds also for each push to the livekit branch
2023-08-08 17:29:22 +08:00
branches: [livekit]
refactored to reuse the build workflow
2024-04-15 16:53:42 +08:00
types:
- completed
Add CI
2021-12-21 00:58:37 +08:00
env:
REGISTRY: ghcr.io
IMAGE_NAME: ${{ github.repository }}
jobs:
refactored to reuse the build workflow
2024-04-15 16:53:42 +08:00
build_element_call:
if: ${{ github.event.workflow_run.event == 'release' }}
uses: ./.github/workflows/element-call.yaml
secrets:
SENTRY_ORG: ${{ secrets.SENTRY_ORG }}
SENTRY_PROJECT: ${{ secrets.SENTRY_PROJECT }}
SENTRY_URL: ${{ secrets.SENTRY_URL }}
SENTRY_AUTH_TOKEN: ${{ secrets.SENTRY_AUTH_TOKEN }}
vite_app_version: ${{ github.event.release.tag_name || github.sha }}
publish_tarball:
name: Publish tarball
Add CI
2021-12-21 00:58:37 +08:00
runs-on: ubuntu-latest
refactored to reuse the build workflow
2024-04-15 16:53:42 +08:00
outputs:
unix_time: ${{steps.current-time.outputs.unix_time}}
Add CI
2021-12-21 00:58:37 +08:00
permissions:
Upload source maps to sentry (#810) * Pretend to upload source maps to sentry * Build release not in docker so we can upload source maps sensibly and also upload the release as a plain tarball while we're at it * fix yaml * Try specifying version this way * test rebuild * pass secrets through * Too many sentries * It's almost 2023 and we're still having BSD vs GNU tar issues * Maybe get sensible tag name & release identifier * Wrong plugin, and also try the 'release' option which might the right thing * Try a different github action see if github likes that any better * add contents write permission and switch to the asset upload plugin that had the helpful doc * actually put release name in tarball path * copy docker config to right path * Prettify vite config * Only activate sentry plugin if we have secrets * Use env var for tag name * Also spelling env correctly would likely help * Fix variable syntax * Put env var in correct place One day maybe I will not find yaml syntax confusing
2023-01-03 18:48:48 +08:00
contents: write # required to upload release asset
Add CI
2021-12-21 00:58:37 +08:00
packages: write
steps:
Addressing Deprecating save-state and set-output commands
2023-08-09 22:45:56 +08:00
- name: Get current time
id: current-time
run: echo "unix_time=$(date +'%s')" >> $GITHUB_OUTPUT
refactored to reuse the build workflow
2024-04-15 16:53:42 +08:00
- name: 📥 Download artifact
uses: actions/download-artifact@v4
Upload source maps to sentry (#810) * Pretend to upload source maps to sentry * Build release not in docker so we can upload source maps sensibly and also upload the release as a plain tarball while we're at it * fix yaml * Try specifying version this way * test rebuild * pass secrets through * Too many sentries * It's almost 2023 and we're still having BSD vs GNU tar issues * Maybe get sensible tag name & release identifier * Wrong plugin, and also try the 'release' option which might the right thing * Try a different github action see if github likes that any better * add contents write permission and switch to the asset upload plugin that had the helpful doc * actually put release name in tarball path * copy docker config to right path * Prettify vite config * Only activate sentry plugin if we have secrets * Use env var for tag name * Also spelling env correctly would likely help * Fix variable syntax * Put env var in correct place One day maybe I will not find yaml syntax confusing
2023-01-03 18:48:48 +08:00
with:
refactored to reuse the build workflow
2024-04-15 16:53:42 +08:00
github-token: ${{ secrets.GITHUB_TOKEN }}
run-id: ${{ github.event.workflow_run.id }}
name: build-output
path: dist
Upload source maps to sentry (#810) * Pretend to upload source maps to sentry * Build release not in docker so we can upload source maps sensibly and also upload the release as a plain tarball while we're at it * fix yaml * Try specifying version this way * test rebuild * pass secrets through * Too many sentries * It's almost 2023 and we're still having BSD vs GNU tar issues * Maybe get sensible tag name & release identifier * Wrong plugin, and also try the 'release' option which might the right thing * Try a different github action see if github likes that any better * add contents write permission and switch to the asset upload plugin that had the helpful doc * actually put release name in tarball path * copy docker config to right path * Prettify vite config * Only activate sentry plugin if we have secrets * Use env var for tag name * Also spelling env correctly would likely help * Fix variable syntax * Put env var in correct place One day maybe I will not find yaml syntax confusing
2023-01-03 18:48:48 +08:00
- name: Create Tarball
env:
GHA doesn't support ??
2023-08-08 18:59:06 +08:00
TARBALL_VERSION: ${{ github.event.release.tag_name || github.sha }}
Upload source maps to sentry (#810) * Pretend to upload source maps to sentry * Build release not in docker so we can upload source maps sensibly and also upload the release as a plain tarball while we're at it * fix yaml * Try specifying version this way * test rebuild * pass secrets through * Too many sentries * It's almost 2023 and we're still having BSD vs GNU tar issues * Maybe get sensible tag name & release identifier * Wrong plugin, and also try the 'release' option which might the right thing * Try a different github action see if github likes that any better * add contents write permission and switch to the asset upload plugin that had the helpful doc * actually put release name in tarball path * copy docker config to right path * Prettify vite config * Only activate sentry plugin if we have secrets * Use env var for tag name * Also spelling env correctly would likely help * Fix variable syntax * Put env var in correct place One day maybe I will not find yaml syntax confusing
2023-01-03 18:48:48 +08:00
run: |
Fix tarball name for head branch builds
2023-08-08 18:51:21 +08:00
tar --numeric-owner --transform "s/dist/element-call-${TARBALL_VERSION}/" -cvzf element-call-${TARBALL_VERSION}.tar.gz dist
Upload source maps to sentry (#810) * Pretend to upload source maps to sentry * Build release not in docker so we can upload source maps sensibly and also upload the release as a plain tarball while we're at it * fix yaml * Try specifying version this way * test rebuild * pass secrets through * Too many sentries * It's almost 2023 and we're still having BSD vs GNU tar issues * Maybe get sensible tag name & release identifier * Wrong plugin, and also try the 'release' option which might the right thing * Try a different github action see if github likes that any better * add contents write permission and switch to the asset upload plugin that had the helpful doc * actually put release name in tarball path * copy docker config to right path * Prettify vite config * Only activate sentry plugin if we have secrets * Use env var for tag name * Also spelling env correctly would likely help * Fix variable syntax * Put env var in correct place One day maybe I will not find yaml syntax confusing
2023-01-03 18:48:48 +08:00
- name: Upload
Update actions/upload-artifact digest to ef09cda
2024-02-16 03:07:48 +08:00
uses: actions/upload-artifact@ef09cdac3e2d3e60d8ccadda691f4f1cec5035cb
Upload source maps to sentry (#810) * Pretend to upload source maps to sentry * Build release not in docker so we can upload source maps sensibly and also upload the release as a plain tarball while we're at it * fix yaml * Try specifying version this way * test rebuild * pass secrets through * Too many sentries * It's almost 2023 and we're still having BSD vs GNU tar issues * Maybe get sensible tag name & release identifier * Wrong plugin, and also try the 'release' option which might the right thing * Try a different github action see if github likes that any better * add contents write permission and switch to the asset upload plugin that had the helpful doc * actually put release name in tarball path * copy docker config to right path * Prettify vite config * Only activate sentry plugin if we have secrets * Use env var for tag name * Also spelling env correctly would likely help * Fix variable syntax * Put env var in correct place One day maybe I will not find yaml syntax confusing
2023-01-03 18:48:48 +08:00
env:
GITHUB_TOKEN: ${{ github.token }}
with:
Fix main branch image publishing, try 2 * Swap out the 3rd party upload-asset which just seems to be broken for the actual github one which does everything we need here. * Update version of metadata action to one that supports is_default_branch
2023-08-08 21:14:12 +08:00
path: "./element-call-*.tar.gz"
refactored to reuse the build workflow
2024-04-15 16:53:42 +08:00
publish_docker:
needs: publish_tarball
uses: ./.github/workflows/docker.yaml
with:
docker_tags: |
type=sha,format=short,event=branch
type=semver,pattern=v{{version}}
type=raw,value=latest-ci,enable={{is_default_branch}}
type=raw,value=latest-ci_${{needs.publish_tarball.outputs.unix_time}},enable={{is_default_branch}}
Reference in New Issue Copy Permalink