Skip to content

chore: bump @aws-sdk/node-http-handler from 3.296.0 to 3.374.0 in /app #9967

chore: bump @aws-sdk/node-http-handler from 3.296.0 to 3.374.0 in /app

chore: bump @aws-sdk/node-http-handler from 3.296.0 to 3.374.0 in /app #9967

Triggered via pull request November 20, 2024 19:35
Status Failure
Total duration 16m 6s
Artifacts 5

main.yaml

on: pull_request
Matrix: build / build-and-push-image
install-env  /  install-test-env
4m 54s
install-env / install-test-env
is-tagged-release
22s
is-tagged-release
test-checks  /  trivy-scan-code
24s
test-checks / trivy-scan-code
test-checks  /  cocogitto
24s
test-checks / cocogitto
test-checks  /  gitleaks
27s
test-checks / gitleaks
test-checks  /  check_immutable_sqitch_files
21s
test-checks / check_immutable_sqitch_files
test-checks  /  check_deleted_sqitch_tags
26s
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
6s
setup-s3-backup / deploy-s3-secret-to-dev
setup-s3-backup  /  deploy-s3-secret-to-test
6s
setup-s3-backup / deploy-s3-secret-to-test
setup-s3-backup  /  deploy-s3-secret-to-prod
6s
setup-s3-backup / deploy-s3-secret-to-prod
has-merge-conflict  /  check_merge_conflicts
0s
has-merge-conflict / check_merge_conflicts
cleanup_feature  /  clean-feature-env
cleanup_feature / clean-feature-env
test-checks  /  lint-chart
28s
test-checks / lint-chart
deploy-feature  /  setup-feature-database
6s
deploy-feature / setup-feature-database
test-containers  /  trivy-scan-app
2m 0s
test-containers / trivy-scan-app
test-containers  /  trivy-scan-db
32s
test-containers / trivy-scan-db
test-e2e  /  yarn-test-e2e-applicant
5m 12s
test-e2e / yarn-test-e2e-applicant
test-e2e  /  yarn-test-e2e-admin
3m 26s
test-e2e / yarn-test-e2e-admin
test-e2e  /  yarn-test-e2e-analyst
5m 48s
test-e2e / yarn-test-e2e-analyst
test-zap  /  zap-owasp-full
4m 22s
test-zap / zap-owasp-full
ensure-sqitch-plan-ends-with-tag
0s
ensure-sqitch-plan-ends-with-tag
deploy-feature  /  deploy-feature-to-openshift-development
0s
deploy-feature / deploy-feature-to-openshift-development
test-containers  /  renovate
44s
test-containers / renovate
test-e2e  /  yarn-test-e2e-finalize
55s
test-e2e / yarn-test-e2e-finalize
deploy-feature  /  update-jira-issue
0s
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

5 errors and 3 warnings
setup-s3-backup / deploy-s3-secret-to-test
Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
has-merge-conflict / check_merge_conflicts
Secret JIRA_AUTH is required, but not provided while calling.
setup-s3-backup / deploy-s3-secret-to-dev
Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
setup-s3-backup / deploy-s3-secret-to-prod
Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
deploy-feature / setup-feature-database
Error: Failed to login: Required action inputs are missing. Either "openshift_token", or both "openshift_username" and "openshift_password" must be set.
Sensitive data should not be used in the ARG or ENV commands: app/Dockerfile#L20
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "SENTRY_AUTH_TOKEN") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Sensitive data should not be used in the ARG or ENV commands: app/Dockerfile#L21
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "SENTRY_AUTH_TOKEN") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "zap_scan". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

Artifacts

Produced during runtime
Name Size
bcgov~CONN-CCBC-portal~4LX4VI.dockerbuild
79.7 KB
bcgov~CONN-CCBC-portal~H50O9B.dockerbuild
47.7 KB
bcgov~CONN-CCBC-portal~IF9JGV.dockerbuild
82.4 KB
bcgov~CONN-CCBC-portal~R12SBZ.dockerbuild
121 KB
zap_scan
979 KB