Back to pull request #3673

fix: add withdrawn to status external check on history #9845

Sign in to view logs

Triggered via pull request November 15, 2024 18:50

rafasdc

opened #3673

NDT-602-Wrong-Username-in-announcement-history

Status Failure

Total duration 15m 11s

Artifacts 5

main.yaml

on: pull_request

Matrix: build / build-and-push-image

install-env / install-test-env

is-tagged-release

test-checks / trivy-scan-code

test-checks / cocogitto

test-checks / gitleaks

test-checks / check_immutable_sqitch_files

test-checks / check_deleted_sqitch_tags

rebase-feature-pr

Matrix: test-checks / codeql-scan

setup-s3-backup / deploy-s3-secret-to-dev

setup-s3-backup / deploy-s3-secret-to-test

setup-s3-backup / deploy-s3-secret-to-prod

has-merge-conflict / check_merge_conflicts

cleanup_feature / clean-feature-env

test-checks / lint-chart

deploy-feature / setup-feature-database

test-containers / trivy-scan-app

test-containers / trivy-scan-db

test-code / jest

test-code / eslint

test-code / schema

test-code / reverts

test-code / pgtap

test-e2e / yarn-test-e2e-applicant

test-e2e / yarn-test-e2e-admin

test-e2e / yarn-test-e2e-analyst

test-zap / zap-owasp-full

ensure-sqitch-plan-ends-with-tag

deploy-feature / deploy-feature-to-openshift-development

test-containers / renovate

test-e2e / yarn-test-e2e-finalize

deploy-feature / update-jira-issue

deploy / is-tagged-release

deploy / deploy-to-openshift-development

deploy / ensure-sqitch-plan-ends-with-tag

deploy / ... / export-secrets

deploy / deploy-to-openshift-test

deploy / deploy-to-openshift-production

deploy / ... / export-secrets

deploy / ... / export-secrets

deploy / create-release

deploy / ... / create_hotfix_branch

Annotations

2 errors and 3 warnings

test-checks / trivy-scan-code

Process completed with exit code 1.

test-containers / trivy-scan-app

Process completed with exit code 1.

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/

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/

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~4Z1K11.dockerbuild	97.1 KB
bcgov~CONN-CCBC-portal~R8W4UM.dockerbuild	71.2 KB
bcgov~CONN-CCBC-portal~RT5OMF.dockerbuild	39.1 KB
bcgov~CONN-CCBC-portal~W8RN9N.dockerbuild	71.7 KB
zap_scan	980 KB