Skip to content

feat: make gcpe reports descending #9985

feat: make gcpe reports descending

feat: make gcpe reports descending #9985

Triggered via pull request November 21, 2024 19:35
Status Failure
Total duration 14m 47s
Artifacts 5

main.yaml

on: pull_request
Matrix: build / build-and-push-image
install-env  /  install-test-env
1m 8s
install-env / install-test-env
is-tagged-release
25s
is-tagged-release
test-checks  /  trivy-scan-code
31s
test-checks / trivy-scan-code
test-checks  /  cocogitto
25s
test-checks / cocogitto
test-checks  /  gitleaks
28s
test-checks / gitleaks
test-checks  /  check_immutable_sqitch_files
24s
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
42s
setup-s3-backup / deploy-s3-secret-to-dev
setup-s3-backup  /  deploy-s3-secret-to-test
22s
setup-s3-backup / deploy-s3-secret-to-test
setup-s3-backup  /  deploy-s3-secret-to-prod
33s
setup-s3-backup / deploy-s3-secret-to-prod
has-merge-conflict  /  check_merge_conflicts
26s
has-merge-conflict / check_merge_conflicts
cleanup_feature  /  clean-feature-env
cleanup_feature / clean-feature-env
test-checks  /  lint-chart
25s
test-checks / lint-chart
deploy-feature  /  setup-feature-database
22s
deploy-feature / setup-feature-database
test-containers  /  trivy-scan-app
2m 4s
test-containers / trivy-scan-app
test-containers  /  trivy-scan-db
21s
test-containers / trivy-scan-db
test-e2e  /  yarn-test-e2e-applicant
4m 57s
test-e2e / yarn-test-e2e-applicant
test-e2e  /  yarn-test-e2e-admin
3m 23s
test-e2e / yarn-test-e2e-admin
test-e2e  /  yarn-test-e2e-analyst
5m 22s
test-e2e / yarn-test-e2e-analyst
test-zap  /  zap-owasp-full
4m 51s
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
2m 5s
deploy-feature / deploy-feature-to-openshift-development
test-containers  /  renovate
43s
test-containers / renovate
test-e2e  /  yarn-test-e2e-finalize
47s
test-e2e / yarn-test-e2e-finalize
deploy-feature  /  update-jira-issue
7s
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

2 errors and 6 warnings
is-tagged-release
Unable to process file command 'output' successfully.
is-tagged-release
Invalid format 'v1.211.3'
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/
deploy-feature / deploy-feature-to-openshift-development
Unexpected input(s) 'openshift_app_namespace', 'openshift_metabase_namespace', 'openshift_metabase_prod_namespace', 'next_public_growthbook_api_key', 'aws_s3_bucket', 'aws_s3_region', 'aws_s3_key', 'aws_s3_secret_key', 'aws_role_arn', 'aws_clam_s3_bucket', 'metabase_site_url', 'metabase_embed_secret', 'feature_name', valid inputs are ['openshift_server_url', 'openshift_token', 'openshift_username', 'openshift_password', 'insecure_skip_tls_verify', 'certificate_authority_data', 'namespace', 'reveal_cluster_name']
deploy-feature / deploy-feature-to-openshift-development
Unexpected input(s) 'keycloak_host', 'sa_client_secret', 'sa_client_id', valid inputs are ['openshift_server_url', 'openshift_token', 'openshift_app_namespace', 'openshift_metabase_namespace', 'openshift_metabase_prod_namespace', 'tag', 'client_secret', 'secure_route', 'next_public_growthbook_api_key', 'aws_s3_bucket', 'aws_clam_s3_bucket', 'aws_s3_region', 'aws_s3_key', 'aws_s3_secret_key', 'aws_role_arn', 'certbot_email', 'certbot_server', 'environment', 'enable_load_test', 'metabase_site_url', 'metabase_embed_secret', 'sp_sa_user', 'sp_sa_password', 'sp_site', 'sp_doc_library', 'sp_ms_file_name', 'sp_list_name', 'ches_url', 'ches_client', 'ches_client_secret', 'ches_to', 'ches_keycloak_host', 'feature_name', 'test_pg_password']
deploy-feature / update-jira-issue
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
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~BZKMOH.dockerbuild
121 KB
bcgov~CONN-CCBC-portal~MNMQCM.dockerbuild
80.1 KB
bcgov~CONN-CCBC-portal~Q4YE19.dockerbuild
48.3 KB
bcgov~CONN-CCBC-portal~WAVRX3.dockerbuild
82.7 KB
zap_scan
981 KB