Skip to content
Merge to Main

on conflict do nothing for config insert (#160) #129

Sign in to view logs

on conflict do nothing for config insert (#160)

on conflict do nothing for config insert (#160) #129

Triggered via push October 16, 2023 21:20
@github-merge-queuegithub-merge-queue[bot]
pushed e31dfa7
main
Status Cancelled
Total duration 1d 19h 31m 22s
Artifacts 1

merge-main.yml

on: push
Semantic Code Analysis
2m 16s
Semantic Code Analysis
Matrix: TEST Deployments
Matrix: PROD Deployments
Matrix: Promote images to PROD
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
@afwilcox
afwilcox
approved Oct 16, 2023
test and
test, test, test, and test

Annotations

4 errors and 2 warnings
PROD Deployments (database)
Canceling since a higher priority waiting request for 'Merge to Main' exists
PROD Deployments (init)
Canceling since a higher priority waiting request for 'Merge to Main' exists
PROD Deployments (backend)
Canceling since a higher priority waiting request for 'Merge to Main' exists
PROD Deployments (frontend)
Canceling since a higher priority waiting request for 'Merge to Main' exists
TEST Deployments (frontend)
The following actions uses node12 which is deprecated and will be forced to run on node16: zaproxy/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
TEST Deployments (backend)
The following actions uses node12 which is deprecated and will be forced to run on node16: zaproxy/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Artifacts

Produced during runtime
Name Size
zap_scan Expired
159 KB