jlab-cluster/helm-charts
3
0 Fork 0
Code Issues 15 Pull Requests 3 Actions Packages Wiki Activity

probe: does the install-test run on the rebuilt Gitea docker runner
Validate Helm Charts / Detect changed charts (pull_request) Successful in 10s
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 6s
Details
Validate Helm Charts / Trivy config ${{ fromJSON(needs.detect-changed-charts.outputs.scan-charts) }} (pull_request) Successful in 24s
Details
Validate Helm Charts / Install-test ${{ fromJSON(needs.detect-changed-charts.outputs.install-charts) }} (pull_request) Successful in 17m31s
Details

Browse Source 
Throwaway. Bumps cyberchef (fast baseline, comparable with GitHub) and
freesailarr (nine containers, real Wireguard tunnel - the hardest case in
the repo) so both enter the install-test matrix, and prints the runner's
cgroup facts plus the k3s node log if it still fails.
This commit is contained in:
jklein committed 2026-09-16 16:08:47 +02:00
1 parent b9917505cd
commit 0f04899877
3 files changed
+24 -3
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

freesailarr/Chart.yaml
+1 -1
View File
@@ -8,7 +8,7 @@ description: A Helm chart to deploy a Wireguard-tunneled media automation stack
type: application
version: 3.0.5+up1.0.0
version: 3.0.6+up1.0.0
# The chart's own version marker, freely chosen and tied to no upstream. The
# stack bundles nine independently versioned projects, so there is no single
# "app version" to track here.