Wolfgang Walther
fd1efa4635
The reason why those workflows were split in the first place was just to obtain loadtest results quicker, because the in the separated workflow, only the single loadtest job needs to finish before the artifacts can be downloaded. However, the disadvantage of this approach was, that the results were not as easily accessible as they could be in a single workflow. Additionally, it's possible to depend on the "prepopulate nix" job for efficiency if the loadtest runs in the main workflow.
33 lines
841 B
YAML
33 lines
841 B
YAML
name: Upload Reports
|
|
|
|
on:
|
|
workflow_run:
|
|
workflows: ["CI"]
|
|
types:
|
|
- completed
|
|
|
|
jobs:
|
|
upload:
|
|
name: Loadtest
|
|
permissions:
|
|
checks: write
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- name: Download from Artifacts
|
|
uses: dawidd6/action-download-artifact@v3
|
|
with:
|
|
workflow: ${{ github.event.workflow.name }}
|
|
run_id: ${{github.event.workflow_run.id }}
|
|
name: loadtest.md
|
|
path: artifacts
|
|
- name: Upload to GitHub Checks
|
|
uses: LouisBrunner/checks-action@v2.0.0
|
|
with:
|
|
token: ${{ secrets.GITHUB_TOKEN }}
|
|
sha: ${{ github.event.workflow_run.head_sha }}
|
|
name: Loadtest Results
|
|
conclusion: neutral
|
|
output: |
|
|
{"summary":""}
|
|
output_text_description_file: artifacts/loadtest.md
|