Skip to content

Tech - Correction du healthcheck pour l'intégration (#3945) #8976

Tech - Correction du healthcheck pour l'intégration (#3945)

Tech - Correction du healthcheck pour l'intégration (#3945) #8976

Triggered via push December 3, 2024 12:03
Status Success
Total duration 13m 48s
Artifacts 2

cicd.yml

on: push
Set application version and env profile
5s
Set application version and env profile
Build and package
4m 57s
Build and package
Run backend unit tests
3m 52s
Run backend unit tests
Run frontend unit tests
3m 37s
Run frontend unit tests
Matrix: Run E2E tests
Run E2E multi windows tests
3m 29s
Run E2E multi windows tests
Generate and upload source maps to Sentry
30s
Generate and upload source maps to Sentry
Push to registry
28s
Push to registry
Fit to window
Zoom out
Zoom in

Annotations

14 warnings
Run frontend unit tests: frontend/src/coordinates.ts#L61
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/src/features/AdministrativeZone/useCases/getAdministrativeZones.ts#L46
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/src/features/BackOffice/edit_regulation/identification/RegulationLayerZoneLine.tsx#L34
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/src/features/BackOffice/slice.ts#L54
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/src/features/ControlUnit/components/ControlUnitListDialog/FilterBar.tsx#L39
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/src/features/CustomZone/useCases/editName.ts#L33
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/src/features/CustomZone/useCases/fitToView.ts#L25
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/src/features/CustomZone/useCases/remove.ts#L29
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/src/features/CustomZone/useCases/showOrHide.ts#L38
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/src/features/Draw/layer.tsx#L35
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Stage names should be lowercase: infra/docker/app/Dockerfile#L11
StageNameCasing: Stage name 'buildBack' should be lowercase More info: https://docs.docker.com/go/dockerfile/rule/stage-name-casing/
Stage names should be lowercase: infra/docker/app/Dockerfile#L32
StageNameCasing: Stage name 'buildFront' should be lowercase More info: https://docs.docker.com/go/dockerfile/rule/stage-name-casing/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: infra/docker/app/Dockerfile#L126
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
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: "action_image_artifact_monitorfish-app_v1.72.0_snapshot". 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
MTES-MCT~monitorfish~N7KE03.dockerbuild
72.1 KB
action_image_artifact_monitorfish-app_v1.72.0_snapshot
403 MB