generated from actions/typescript-action
-
Notifications
You must be signed in to change notification settings - Fork 62
Open
Description
I'm not quite sure what is causing this as this configuration has worked before. There's nothing particularly complicated about it and looks similar to the examples given here.
To add to the mystery, the deployment can be seen under Deployments/History but the PR deployment status is stuck in This branch has not been deployed
.
Steps are as follows and job throws no warnings or errors.
Start
- name: Start
uses: bobheadxi/deployments@v1
id: status
with:
step: start
token: ${{ secrets.GITHUB_TOKEN }}
env: staging
Debug output:
targeting ***/***
'start' arguments {
stepArgs: { deploymentID: '', override: false, payload: undefined },
coreArgs: {
environment: 'staging',
description: '',
logsURL: 'https://github.com/***/***/commit/***/checks'
}
}
initializing new deployment for staging @ refs/pull/10/merge
created deployment 783773500 for staging @ refs/pull/10/merge
created deployment status 1627565500 with status "in_progress"
Finish
- name: Finish
uses: bobheadxi/deployments@v1
with:
step: finish
override: false
auto_inactive: false
token: ${{ secrets.GITHUB_TOKEN }}
status: ${{ job.status }}
env: ${{ steps.status.outputs.env }}
deployment_id: ${{ steps.status.outputs.deployment_id }}
env_url: ***
Debug output:
Run bobheadxi/deployments@v1
with:
step: finish
override: false
auto_inactive: false
token: ***
status: success
env: staging
deployment_id: 783773500
env_url: ***
debug: true
env:
AWS_ACCESS_KEY_ID: ***
AWS_SECRET_ACCESS_KEY: ***
BRANCH: testbranch
targeting ***/***
'finish' arguments {
stepArgs: {
status: 'success',
deploymentID: '783773500',
envURL: '***',
override: false,
autoInactive: false
},
finishing deployment for 783773500 with status success
coreArgs: {
environment: 'staging',
description: '',
logsURL: 'https://github.com/***/***/commit/***/checks'
}
}
783773500 status set to success { statusID: 1627565500 }
Metadata
Metadata
Assignees
Labels
No labels