Skip to content

Dev Pipeline

Dev Pipeline #4370

Triggered via delete November 29, 2024 10:06
Status Success
Total duration 1m 44s
Artifacts
branch_meta  /  branch_meta
branch_meta / branch_meta
Publish image and scan with trivy  /  Publish image
Publish image and scan with trivy / Publish image
create_branch_identifier_for_deletion  /  convert_branch_name
0s
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
scan_helm  /  Kics Helm Chart Scan
29s
scan_helm / Kics Helm Chart Scan
CodeQL  /  Analyze CodeQL
CodeQL / Analyze CodeQL
Linting  /  Nest Lint
Linting / Nest Lint
Scheduled trivy scan of latest image  /  Trivy Scan
Scheduled trivy scan of latest image / Trivy Scan
Tests and Sonarcloud  /  Tests and Sonarcloud
Tests and Sonarcloud / Tests and Sonarcloud
create_branch_identifier  /  convert_branch_name
create_branch_identifier / convert_branch_name
Publish image and scan with trivy  /  pre_scan
Publish image and scan with trivy / pre_scan
delete_namespace  /  create_dbildungs_iam_keycloak_db_name
0s
delete_namespace / create_dbildungs_iam_keycloak_db_name
delete_namespace  /  create_dbildungs_iam_server_db_name
0s
delete_namespace / create_dbildungs_iam_server_db_name
delete_namespace  /  create_ticket_nr_variable
0s
delete_namespace / create_ticket_nr_variable
release_helm  /  release
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
1m 6s
delete_namespace / delete_databases_and_namespace
wait_for_helm_chart_to_get_published
0s
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

10 warnings
[MEDIUM] Container Running With Low UID: charts/schulportal-client/templates/deployment.yaml#L30
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/schulportal-client/templates/deployment.yaml#L25
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/schulportal-client/templates/deployment.yaml#L25
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] Image Without Digest: charts/schulportal-client/templates/deployment.yaml#L27
Images should be specified together with their digests to ensure integrity
[LOW] Liveness Probe Is Not Defined: charts/schulportal-client/templates/deployment.yaml#L25
In case of an unresponsive container, a Liveness Probe can help your application become more available since it restarts the container. However, it can lead to cascading failures. Define one if you really need it
[LOW] Missing AppArmor Profile: charts/schulportal-client/templates/deployment.yaml#L18
Containers should be configured with an AppArmor profile to enforce fine-grained access control over low-level system resources
[LOW] Pod or Container Without LimitRange: charts/schulportal-client/templates/deployment.yaml#L5
Each namespace should have a LimitRange policy associated to ensure that resource allocations of Pods, Containers and PersistentVolumeClaims do not exceed the defined boundaries
[LOW] Pod or Container Without ResourceQuota: charts/schulportal-client/templates/deployment.yaml#L5
Each namespace should have a ResourceQuota policy associated to limit the total amount of resources Pods, Containers and PersistentVolumeClaims can consume
[LOW] Root Container Not Mounted Read-only: charts/schulportal-client/templates/deployment.yaml#L30
Check if the root container filesystem is not being mounted read-only.