retry wrapper LDAP #7896
branch_meta
/
branch_meta
0s
Publish image and scan with trivy
/
Publish image
50s
create_branch_identifier_for_deletion
/
convert_branch_name
select_helm_version_generation_and_image_tag_generation
0s
CodeQL
/
Analyze CodeQL
1m 53s
Linting
/
Nest Lint
1m 22s
Tests and Sonarcloud
/
Tests and Sonarcloud
12m 6s
scan_helm
/
Kics Helm Chart Scan
29s
Scheduled trivy scan of latest image
/
Trivy Scan
delete_namespace
/
create_dbildungs_iam_keycloak_db_name
delete_namespace
/
create_dbildungs_iam_server_db_name
delete_namespace
/
create_ticket_nr_variable
Publish image and scan with trivy
/
...
/
Trivy Scan
delete_successful
0s
deploy
/
create_dbildungs_iam_keycloak_db_name
deploy
/
create_dbildungs_iam_server_db_name
deploy
/
...
/
search_for_helm_tagname
deploy
/
...
/
search_for_helm_tagname
deploy
/
...
/
search_for_helm_tagname
deploy
/
...
/
search_for_helm_tagname
deploy
/
...
/
run_playwright_end2end_tests
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
|