-
- Downloads
refactor remaining code to manifest
Now it's fully manifest approach with the naming, thinking and everything. Makes a lot of things clearer and should help getting multiarch done. In theory this is sufficient going forward, since manifests can also be used for single-arch. In order to be backwards compatible and still support the simple tagging approach we can re-introduce the tagging part and split it by using different CI templates, while the build-ah-engine uses the multiarch templates. For compatibility reasons I'd use a new template name for multiarch in that case.
Showing
- .gitlab-ci.yml 1 addition, 1 deletion.gitlab-ci.yml
- gitlab-ci-template.yml 2 additions, 4 deletionsgitlab-ci-template.yml
- resources/shell-tools/bin/manifest-push.sh 14 additions, 4 deletionsresources/shell-tools/bin/manifest-push.sh
- resources/shell-tools/bin/manifest.sh 25 additions, 20 deletionsresources/shell-tools/bin/manifest.sh
- resources/shell-tools/bin/pull.sh 0 additions, 89 deletionsresources/shell-tools/bin/pull.sh
- resources/shell-tools/install.sh 6 additions, 9 deletionsresources/shell-tools/install.sh
- resources/shell-tools/test/multiarch.sh 0 additions, 40 deletionsresources/shell-tools/test/multiarch.sh
Loading