helm-charts

0 Fork 0

Author	SHA1	Message	Date
jklein	2775e5d850	probe: single chart, to isolate whether k3s boots at all Validate Helm Charts / Detect changed charts (pull_request) Successful in 3s Details Validate Helm Charts / Resource quantities (pull_request) Successful in 8s Details Validate Helm Charts / Build ${{ fromJSON(needs.detect-changed-charts.outputs.charts) }} (pull_request) Successful in 4s Details Validate Helm Charts / Install-test ${{ fromJSON(needs.detect-changed-charts.outputs.install-charts) }} (pull_request) Failing after 22s Details Validate Helm Charts / Trivy config ${{ fromJSON(needs.detect-changed-charts.outputs.scan-charts) }} (pull_request) Successful in 9s Details Both charts in the matrix collide: Gitea runs the legs CONCURRENTLY in one job on one Docker daemon, and both create a cluster named install-test. One leg logs 'Re-using existing network', the other 'container name /k3d-install-test-server-0 is already in use', and the first rollback deletes the shared network under the second. The workflow is still byte-identical to PR #253 - only cyberchef is bumped now, which is the single-leg case most PRs actually produce, and the only way to see whether k3s itself comes up.	2026-09-17 00:14:03 +02:00
jklein	9a676c1700	probe: unmodified PR #253 workflow, cyberchef + freesailarr in the matrix Validate Helm Charts / Detect changed charts (pull_request) Successful in 3s Details Validate Helm Charts / Resource quantities (pull_request) Successful in 7s Details Validate Helm Charts / Build ${{ fromJSON(needs.detect-changed-charts.outputs.charts) }} (pull_request) Successful in 5s Details Validate Helm Charts / Trivy config ${{ fromJSON(needs.detect-changed-charts.outputs.scan-charts) }} (pull_request) Successful in 14s Details Validate Helm Charts / Install-test ${{ fromJSON(needs.detect-changed-charts.outputs.install-charts) }} (pull_request) Failing after 1m10s Details Throwaway. The workflow file is byte-identical to PR #253 - the curl -4 Helm step and the shortened matrix of the earlier rounds were diagnostic crutches and are gone, so this measures what will actually run. Only the two Chart.yaml versions differ, to pull both charts into the install-test matrix.	2026-09-17 00:10:32 +02:00

1 changed files with 1 additions and 1 deletions

									
										cyberchef/Chart.yaml
									
		+1
		-1
	
												View File
												
				@@ -5,7 +5,7 @@ icon: https://raw.githubusercontent.com/gchq/CyberChef/master/src/web/static/ima

				type: application

				version: 9.0.1+up11.4.0

				version: 9.0.2+up11.4.0

				appVersion: "11.4.0"

				maintainers:

Compare commits