Skip to content

[Tech] Bump org.springframework.boot:spring-boot-starter-security #7068

[Tech] Bump org.springframework.boot:spring-boot-starter-security

[Tech] Bump org.springframework.boot:spring-boot-starter-security #7068

Status Failure
Total duration 12h 2m 55s
Artifacts 1

cicd.yml

on: push
Set application version and env profile
4s
Set application version and env profile
Build and package
6m 17s
Build and package
Run backend unit tests
3m 33s
Run backend unit tests
Run frontend unit tests
2m 47s
Run frontend unit tests
Matrix: Run E2E tests
Run E2E multi windows tests
6h 1m
Run E2E multi windows tests
Push to registry
0s
Push to registry
Fit to window
Zoom out
Zoom in

Annotations

35 errors and 12 warnings
Run backend unit tests
Process completed with exit code 2.
Run E2E tests (1)
The job running on runner GitHub Actions 7 has exceeded the maximum execution time of 360 minutes.
Run E2E tests (1)
The operation was canceled.
Run E2E tests (11)
The job running on runner GitHub Actions 1 has exceeded the maximum execution time of 360 minutes.
Run E2E tests (11)
The operation was canceled.
Run E2E multi windows tests
The job running on runner GitHub Actions 16 has exceeded the maximum execution time of 360 minutes.
Run E2E multi windows tests
The operation was canceled.
Run E2E tests (13)
The job running on runner GitHub Actions 13 has exceeded the maximum execution time of 360 minutes.
Run E2E tests (13)
The operation was canceled.
Run E2E tests (12)
The job running on runner GitHub Actions 10 has exceeded the maximum execution time of 360 minutes.
Run E2E tests (12)
The operation was canceled.
Run E2E tests (15)
The job running on runner GitHub Actions 8 has exceeded the maximum execution time of 360 minutes.
Run E2E tests (15)
The operation was canceled.
Run E2E tests (16)
The job running on runner GitHub Actions 9 has exceeded the maximum execution time of 360 minutes.
Run E2E tests (16)
The operation was canceled.
Run E2E tests (14)
The job running on runner GitHub Actions 6 has exceeded the maximum execution time of 360 minutes.
Run E2E tests (14)
The operation was canceled.
Run E2E tests (10)
The job running on runner GitHub Actions 11 has exceeded the maximum execution time of 360 minutes.
Run E2E tests (10)
The operation was canceled.
Run E2E tests (3)
The job running on runner GitHub Actions 4 has exceeded the maximum execution time of 360 minutes.
Run E2E tests (3)
The operation was canceled.
Run E2E tests (4)
The job running on runner GitHub Actions 20 has exceeded the maximum execution time of 360 minutes.
Run E2E tests (4)
The operation was canceled.
Run E2E tests (2)
The job running on runner GitHub Actions 3 has exceeded the maximum execution time of 360 minutes.
Run E2E tests (2)
The operation was canceled.
Run E2E tests (8)
The job running on runner GitHub Actions 19 has exceeded the maximum execution time of 360 minutes.
Run E2E tests (8)
The operation was canceled.
Run E2E tests (5)
The job running on runner GitHub Actions 5 has exceeded the maximum execution time of 360 minutes.
Run E2E tests (5)
The operation was canceled.
Run E2E tests (6)
The job running on runner GitHub Actions 18 has exceeded the maximum execution time of 360 minutes.
Run E2E tests (6)
The operation was canceled.
Run E2E tests (7)
The job running on runner GitHub Actions 15 has exceeded the maximum execution time of 360 minutes.
Run E2E tests (7)
The operation was canceled.
Run E2E tests (9)
The job running on runner GitHub Actions 12 has exceeded the maximum execution time of 360 minutes.
Run E2E tests (9)
The operation was canceled.
Set application version and env profile
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: pozetroninc/github-action-get-latest-release@master. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Build and package
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: ishworkh/docker-image-artifact-upload@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Run frontend unit tests: frontend/cypress/e2e/sidebars/custom_zones.spec.ts#L29
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/cypress/e2e/sidebars/regulatory_layers.spec.ts#L383
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/cypress/e2e/sidebars/regulatory_layers.spec.ts#L393
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/cypress/e2e/sidebars/regulatory_layers.spec.ts#L419
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/cypress/e2e/utils/getUtcizedDayjs.ts#L15
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/src/api/alert.ts#L89
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/src/api/alert.ts#L90
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/src/api/faoAreas.ts#L18
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/src/api/faoAreas.ts#L19
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Run frontend unit tests: frontend/src/api/faoAreas.ts#L19
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator

Artifacts

Produced during runtime
Name Size
action_image_artifact_monitorfish-app_v1.48.0_snapshot Expired
371 MB