Skip to content

[Tech] Bump org.flywaydb:flyway-database-postgresql in /backend #5542

[Tech] Bump org.flywaydb:flyway-database-postgresql in /backend

[Tech] Bump org.flywaydb:flyway-database-postgresql in /backend #5542

Triggered via push February 6, 2025 13:40
Status Success
Total duration 10m 46s
Artifacts 2

cicd-app.yml

on: push
Set application version and env profile
8s
Set application version and env profile
Build and package
4m 9s
Build and package
Run backend unit tests
3m 55s
Run backend unit tests
Run frontend unit tests
2m 7s
Run frontend unit tests
Matrix: Run E2E tests
Run E2E multi windows tests
0s
Run E2E multi windows tests
Generate and upload source maps to Sentry
26s
Generate and upload source maps to Sentry
Push to registry
30s
Push to registry
Fit to window
Zoom out
Zoom in

Annotations

15 warnings
Run frontend unit tests: frontend/src/features/Dashboard/components/DashboardForm/Toolbar/Filters/FiltersTags.tsx#L49
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/src/features/Dashboard/components/DashboardForm/Toolbar/Filters/FiltersTags.tsx#L50
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/src/features/Mission/components/Filters/Table/FilterTags.tsx#L47
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/src/features/Mission/components/Filters/Table/FilterTags.tsx#L48
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/src/features/Mission/components/Filters/Table/FilterTags.tsx#L49
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/src/features/Mission/components/Filters/Table/FilterTags.tsx#L50
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/src/features/Mission/components/Filters/Table/FilterTags.tsx#L51
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/src/features/Mission/components/Filters/Table/FilterTags.tsx#L52
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/src/features/Mission/components/MissionForm/ActionForm/ControlForm/InfractionForm/NatinfSelector.tsx#L29
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/src/features/Mission/components/MissionForm/MissionForm.tsx#L182
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/
The 'as' keyword should match the case of the 'from' keyword: infra/docker/app/Dockerfile#L11
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-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/
The 'as' keyword should match the case of the 'from' keyword: infra/docker/app/Dockerfile#L32
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: infra/docker/app/Dockerfile#L128
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/

Artifacts

Produced during runtime
Name Size
MTES-MCT~monitorenv~697HRS.dockerbuild
204 KB
action_image_artifact_monitorenv-app_v1.54.1_snapshot
188 MB