From 67e1938190091a7a300b573bc19253c0cf48f31e Mon Sep 17 00:00:00 2001 From: Levi Schoen Date: Tue, 20 Dec 2022 12:48:15 -0800 Subject: [PATCH] metric workflow status based on overall result --- .github/workflows/metric-pipeline.yml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/.github/workflows/metric-pipeline.yml b/.github/workflows/metric-pipeline.yml index 92eb6822..0cd059dc 100644 --- a/.github/workflows/metric-pipeline.yml +++ b/.github/workflows/metric-pipeline.yml @@ -21,6 +21,7 @@ on: jobs: metric-pipeline-result: runs-on: ubuntu-latest + if: always() # always run to capture workflow success or failure steps: # Make sure the secrets are stored in you repo settings - name: Configure AWS Credentials @@ -29,11 +30,16 @@ jobs: aws-access-key-id: ${{ secrets.CI_AWS_KEY_ID }} aws-secret-access-key: ${{ secrets.CI_AWS_KEY_SECRET }} aws-region: ${{ inputs.aws-region }} - if: always() # Setup credentials even if the workflow failed + - name: Calculate Pipleline Success + # run this action to get the workflow conclusion + # You can get the conclusion via env (env.WORKFLOW_CONCLUSION) + # values: neutral, success, skipped, cancelled, timed_out, + # action_required, failure + uses: technote-space/workflow-conclusion-action@v3 - name: Metric Pipleline Success # replace TAG by the latest tag in the repository uses: ros-tooling/action-cloudwatch-metrics@0.0.5 - if: always() # Need to run to log the workflow failure with: + metric-value: ${{ env.WORKFLOW_CONCLUSION == 'success' }} metric-name: ${{ inputs.metric-name }} namespace: ${{ inputs.namespace }}