Implement deploy status checks for github integration #15451
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This introduces a new state for pull requests called
'deployed'
.A cron job checks the deploy status of every pull request regularly and updates the state accordingly once deployed.
It will also add a comment to each relevant work package to let users know where the pull request was deployed to.
To make this work an
introspection
permission is introduced and the APIv3 root endpoint amended with the deployed core SHA that is running.Lastly, next to the
deploy_targets
table another tablegithub_deploy_status_checks
is created used to make sure the deploy status is only checked as often as necessary and not more.To do
deployed
state in frontend