Skip to content

fix: user config in auto merge #9197

fix: user config in auto merge

fix: user config in auto merge #9197

Re-run triggered September 27, 2024 20:31
Status Failure
Total duration 5m 46s
Artifacts

main.yaml

on: pull_request
Matrix: build / build-and-push-image
install-env  /  install-test-env
1m 14s
install-env / install-test-env
is-tagged-release
22s
is-tagged-release
test-checks  /  trivy-scan-code
25s
test-checks / trivy-scan-code
test-checks  /  cocogitto
22s
test-checks / cocogitto
test-checks  /  gitleaks
31s
test-checks / gitleaks
test-checks  /  check_immutable_sqitch_files
22s
test-checks / check_immutable_sqitch_files
test-checks  /  check_deleted_sqitch_tags
24s
test-checks / check_deleted_sqitch_tags
rebase-feature-pr
0s
rebase-feature-pr
Matrix: test-checks / codeql-scan
setup-s3-backup  /  deploy-s3-secret-to-dev
17s
setup-s3-backup / deploy-s3-secret-to-dev
setup-s3-backup  /  deploy-s3-secret-to-test
28s
setup-s3-backup / deploy-s3-secret-to-test
setup-s3-backup  /  deploy-s3-secret-to-prod
35s
setup-s3-backup / deploy-s3-secret-to-prod
cleanup_feature  /  clean-feature-env
cleanup_feature / clean-feature-env
test-checks  /  lint-chart
46s
test-checks / lint-chart
deploy-feature  /  setup-feature-database
deploy-feature / setup-feature-database
test-containers  /  trivy-scan-app
test-containers / trivy-scan-app
test-containers  /  trivy-scan-db
test-containers / trivy-scan-db
test-e2e  /  yarn-test-e2e-admin
test-e2e / yarn-test-e2e-admin
test-e2e  /  yarn-test-e2e-analyst
test-e2e / yarn-test-e2e-analyst
test-e2e  /  yarn-test-e2e-applicant
test-e2e / yarn-test-e2e-applicant
test-zap  /  zap-owasp-full
test-zap / zap-owasp-full
ensure-sqitch-plan-ends-with-tag
3s
ensure-sqitch-plan-ends-with-tag
deploy-feature  /  deploy-feature-to-openshift-development
deploy-feature / deploy-feature-to-openshift-development
test-containers  /  renovate
test-containers / renovate
test-e2e  /  yarn-test-e2e-finalize
test-e2e / yarn-test-e2e-finalize
deploy-feature  /  update-jira-issue
deploy-feature / update-jira-issue
deploy  /  is-tagged-release
deploy / is-tagged-release
deploy  /  deploy-to-openshift-development
deploy / deploy-to-openshift-development
deploy  /  ensure-sqitch-plan-ends-with-tag
deploy / ensure-sqitch-plan-ends-with-tag
deploy  /  ...  /  export-secrets
deploy / backup-secrets-dev / export-secrets
deploy  /  deploy-to-openshift-test
deploy / deploy-to-openshift-test
deploy  /  deploy-to-openshift-production
deploy / deploy-to-openshift-production
deploy  /  ...  /  export-secrets
deploy / backup-secrets-test / export-secrets
deploy  /  ...  /  export-secrets
deploy / backup-secrets-prod / export-secrets
deploy  /  create-release
deploy / create-release
deploy  /  ...  /  create_hotfix_branch
deploy / create_hotfix_branch / create_hotfix_branch
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 10 warnings
build / cron-sp
ERROR: Error response from daemon: Head "https://registry-1.docker.io/v2/moby/buildkit/manifests/buildx-stable-1": unauthorized: incorrect username or password
build / db
The job was canceled because "ghcr_io_bcgov_conn-ccbc_3" failed.
build / db
ERROR: Error response from daemon: Head "https://registry-1.docker.io/v2/moby/buildkit/manifests/buildx-stable-1": unauthorized: incorrect username or password
build / app
The job was canceled because "ghcr_io_bcgov_conn-ccbc_3" failed.
build / app
ERROR: Error response from daemon: Head "https://registry-1.docker.io/v2/moby/buildkit/manifests/buildx-stable-1": unauthorized: incorrect username or password
test-code / jest
Docker build failed with exit code 1
setup-s3-backup / deploy-s3-secret-to-dev
The following actions use a deprecated Node.js version and will be forced to run on node20: aws-actions/configure-aws-credentials@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
setup-s3-backup / deploy-s3-secret-to-test
The following actions use a deprecated Node.js version and will be forced to run on node20: aws-actions/configure-aws-credentials@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
setup-s3-backup / deploy-s3-secret-to-prod
The following actions use a deprecated Node.js version and will be forced to run on node20: aws-actions/configure-aws-credentials@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
install-env / install-test-env
The following actions use a deprecated Node.js version and will be forced to run on node20: asdf-vm/actions/setup@v2, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-code / jest
Docker build failed with exit code 1, back off 3.715 seconds before retry.
test-code / jest
Docker build failed with exit code 1, back off 3.486 seconds before retry.
test-code / eslint
The following actions use a deprecated Node.js version and will be forced to run on node20: asdf-vm/actions/setup@v2, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-code / schema
The following actions use a deprecated Node.js version and will be forced to run on node20: asdf-vm/actions/setup@v2, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-code / pgtap
The following actions use a deprecated Node.js version and will be forced to run on node20: asdf-vm/actions/setup@v2, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-code / reverts
The following actions use a deprecated Node.js version and will be forced to run on node20: asdf-vm/actions/setup@v2, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/