stack-orchestrator/.gitea/workflows/publish.yml

49 lines
1.5 KiB
YAML
Raw Normal View History

2023-04-07 01:04:00 +00:00
name: Publish
on:
pull_request:
branches: '*'
push:
branches: '*'
jobs:
2023-04-10 04:41:01 +00:00
publish:
name: "Build and publish"
2023-04-07 01:04:00 +00:00
runs-on: ubuntu-latest
steps:
- name: "Clone project repository"
uses: actions/checkout@v3
- name: "Install Python"
uses: cerc-io/setup-python@v4
with:
python-version: '3.8'
- name: "Print Python version"
run: python3 --version
- name: "Install shiv"
run: pip install shiv
- name: "Create release"
2023-04-10 04:41:01 +00:00
uses: cerc-io/action-gh-release@gitea-v1
2023-04-07 01:04:00 +00:00
# We haven't decided how to trigger this release job.
# It might be done on creation of a git tag
# Or it might be done on merge to a release branch
# Somehow by this point however we need to know the release version
2023-04-07 01:33:27 +00:00
with:
2023-04-10 04:41:01 +00:00
tag_name: "v1.2.5"
2023-04-07 01:04:00 +00:00
- name: "Build local shiv package"
2023-04-10 04:41:01 +00:00
id: build
2023-04-07 01:04:00 +00:00
# Build has to be done after deciding on the version because
# we bundle the version into the build
2023-04-10 04:41:01 +00:00
run: |
./scripts/build_shiv_package.sh
result_code=$?
echo "::set-output name=package-file::$(ls ./package/*)"
exit $result_code
- name "Stage artifact file"
run: |
cp ${{ steps.build.outputs.package-file }} ./laconic-so
2023-04-07 01:04:00 +00:00
- name: "Upload release artifact"
2023-04-10 04:41:01 +00:00
uses: cerc-io/action-gh-release@gitea-v1
2023-04-07 01:33:27 +00:00
with:
2023-04-10 04:41:01 +00:00
tag_name: "v1.2.5"
files: ./laconic-so