You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The migration of the new "meta" jobs out of "work-in-progress" (docker-library/meta-scripts#94docker-library/meta-scripts#95) has reminded me that we need to finally delete the multiarch jobs on Jenkins. And once we do that, then the badges will stop working. They are currently not providing value since the multiarch jobs are unused. We do not have a 1 for 1 replacement since the new jobs are not per-repo, but strictly per-arch only. I guess the put-shared badge will still be correct for now.
So, this issue is to make a choice with the code in generate-repo-stub-readme.sh and then apply it to all of our image-specific repos:
IMO we should just remove all of these -- the GitHub ones give a false sense of "status" (they're only useful to maintainers/contributors), and the rest don't have a direct analog in the new system. 😅
The migration of the new "meta" jobs out of "work-in-progress" (docker-library/meta-scripts#94 docker-library/meta-scripts#95) has reminded me that we need to finally delete the
multiarch
jobs on Jenkins. And once we do that, then the badges will stop working. They are currently not providing value since themultiarch
jobs are unused. We do not have a 1 for 1 replacement since the new jobs are not per-repo, but strictly per-arch only. I guess theput-shared
badge will still be correct for now.So, this issue is to make a choice with the code in
generate-repo-stub-readme.sh
and then apply it to all of our image-specific repos:docs/generate-repo-stub-readme.sh
Lines 66 to 140 in 53e5d3b
The text was updated successfully, but these errors were encountered: