Skip to content

retry wrapper LDAP #7896

retry wrapper LDAP

retry wrapper LDAP #7896

Triggered via push December 18, 2024 15:39
Status Failure
Total duration 12m 15s
Artifacts
branch_meta  /  branch_meta
0s
branch_meta / branch_meta
Publish image and scan with trivy  /  Publish image
50s
Publish image and scan with trivy / Publish image
create_branch_identifier_for_deletion  /  convert_branch_name
create_branch_identifier_for_deletion / convert_branch_name
select_helm_version_generation_and_image_tag_generation
0s
select_helm_version_generation_and_image_tag_generation
CodeQL  /  Analyze CodeQL
1m 53s
CodeQL / Analyze CodeQL
Linting  /  Nest Lint
1m 22s
Linting / Nest Lint
Tests and Sonarcloud  /  Tests and Sonarcloud
12m 6s
Tests and Sonarcloud / Tests and Sonarcloud
scan_helm  /  Kics Helm Chart Scan
29s
scan_helm / Kics Helm Chart Scan
Scheduled trivy scan of latest image  /  Trivy Scan
Scheduled trivy scan of latest image / Trivy Scan
create_branch_identifier  /  convert_branch_name
0s
create_branch_identifier / convert_branch_name
Publish image and scan with trivy  /  pre_scan
0s
Publish image and scan with trivy / pre_scan
delete_namespace  /  create_dbildungs_iam_keycloak_db_name
delete_namespace / create_dbildungs_iam_keycloak_db_name
delete_namespace  /  create_dbildungs_iam_server_db_name
delete_namespace / create_dbildungs_iam_server_db_name
delete_namespace  /  create_ticket_nr_variable
delete_namespace / create_ticket_nr_variable
release_helm  /  release
49s
release_helm / release
Publish image and scan with trivy  /  ...  /  Trivy Scan
Publish image and scan with trivy / Trivy scan for uploaded image / Trivy Scan
delete_namespace  /  delete_databases_and_namespace
delete_namespace / delete_databases_and_namespace
wait_for_helm_chart_to_get_published
1m 1s
wait_for_helm_chart_to_get_published
delete_successful
0s
delete_successful
deploy  /  ...  /  branch_meta
deploy / create_ingress_prefix / branch_meta
deploy  /  create_dbildungs_iam_keycloak_db_name
deploy / create_dbildungs_iam_keycloak_db_name
deploy  /  create_dbildungs_iam_server_db_name
deploy / create_dbildungs_iam_server_db_name
deploy  /  ...  /  search_for_helm_tagname
deploy / find_dbildungs_iam_keycloak_helm_chart_tag / search_for_helm_tagname
deploy  /  ...  /  search_for_helm_tagname
deploy / find_dbildungs_iam_ldap_helm_chart_tag / search_for_helm_tagname
deploy  /  ...  /  search_for_helm_tagname
deploy / find_dbildungs_iam_server_helm_chart_tag / search_for_helm_tagname
deploy  /  ...  /  search_for_helm_tagname
deploy / find_schulportal_client_helm_chart_tag / search_for_helm_tagname
deploy  /  determine_playwright_branch
deploy / determine_playwright_branch
deploy  /  ...  /  convert_branch_name
deploy / create_lowercase_ingress_prefix / convert_branch_name
deploy  /  deployment
deploy / deployment
deploy  /  ...  /  run_playwright_end2end_tests
deploy / run_playwright_tests / run_playwright_end2end_tests
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 20 warnings
Publish image and scan with trivy / Publish image
buildx failed with: ERROR: failed to solve: process "/bin/sh -c npm run build" did not complete successfully: exit code: 1
Linting / Nest Lint: src/core/ldap/domain/ldap-event-handler.ts#L213
This assertion is unnecessary since the receiver accepts the original type of the expression
Linting / Nest Lint
Process completed with exit code 1.
Tests and Sonarcloud / Tests and Sonarcloud
Process completed with exit code 1.
select_helm_version_generation_and_image_tag_generation
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
branch_meta / branch_meta
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
create_branch_identifier / convert_branch_name
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
scan_helm / Kics Helm Chart Scan
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
[MEDIUM] Container Running With Low UID: charts/dbildungs-iam-server/templates/backend-deployment.yaml#L24
Check if containers are running with low UID, which might cause conflicts with the host's user table.
[MEDIUM] Container Running With Low UID: charts/dbildungs-iam-server/templates/cronjob.yaml#L22
Check if containers are running with low UID, which might cause conflicts with the host's user table.
[MEDIUM] Container Running With Low UID: charts/dbildungs-iam-server/templates/backend-deployment.yaml#L71
Check if containers are running with low UID, which might cause conflicts with the host's user table.
[MEDIUM] Container Running With Low UID: charts/dbildungs-iam-server/templates/cronjob.yaml#L22
Check if containers are running with low UID, which might cause conflicts with the host's user table.
[MEDIUM] Container Running With Low UID: charts/dbildungs-iam-server/templates/cronjob.yaml#L22
Check if containers are running with low UID, which might cause conflicts with the host's user table.
[MEDIUM] Container Running With Low UID: charts/dbildungs-iam-server/templates/backend-deployment.yaml#L24
Check if containers are running with low UID, which might cause conflicts with the host's user table.
[MEDIUM] Container Running With Low UID: charts/dbildungs-iam-server/templates/backend-deployment.yaml#L24
Check if containers are running with low UID, which might cause conflicts with the host's user table.
[MEDIUM] Container Running With Low UID: charts/dbildungs-iam-server/templates/cronjob.yaml#L22
Check if containers are running with low UID, which might cause conflicts with the host's user table.
[LOW] Container Requests Not Equal To It's Limits: charts/dbildungs-iam-server/templates/cronjob.yaml#L47
Containers must have the same resource requests set as limits. This is recommended to avoid resource DDoS of the node during spikes and means that 'requests.memory' and 'requests.cpu' must equal 'limits.memory' and 'limits.cpu', respectively
[LOW] Container Requests Not Equal To It's Limits: charts/dbildungs-iam-server/templates/backend-deployment.yaml#L24
Containers must have the same resource requests set as limits. This is recommended to avoid resource DDoS of the node during spikes and means that 'requests.memory' and 'requests.cpu' must equal 'limits.memory' and 'limits.cpu', respectively
Publish image and scan with trivy / Publish image
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
release_helm / release
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Linting / Nest Lint
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
CodeQL / Analyze CodeQL
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
wait_for_helm_chart_to_get_published
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Tests and Sonarcloud / Tests and Sonarcloud
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636