2025-12-16 19:23:46 -03:00
|
|
|
# harbor-arm-build
|
2025-12-18 01:26:53 -03:00
|
|
|
|
|
|
|
|
Jenkins pipeline for building an arm64 Harbor release straight from upstream and
|
|
|
|
|
pushing the full image set into `registry.bstein.dev/infra`.
|
|
|
|
|
|
|
|
|
|
Key behavior:
|
|
|
|
|
- Parameter `HARBOR_VERSION` (e.g. `v2.14.1`). If left empty, the pipeline
|
|
|
|
|
fetches the latest Harbor GitHub release tag.
|
|
|
|
|
- Runs on an arm64 node with podman/buildah (Docker CLI shim via `podman-docker`);
|
|
|
|
|
no dind is used.
|
|
|
|
|
- Builds all Harbor images with `IMAGENAMESPACE=registry.bstein.dev/infra` and
|
|
|
|
|
tags `${HARBOR_VERSION}-arm64.$BUILD_NUMBER`, then pushes them with the
|
|
|
|
|
`harbor-robot-pipeline` credentials.
|
|
|
|
|
|
|
|
|
|
Trigger manually in Jenkins when a new Harbor version needs to be published to
|
|
|
|
|
the internal registry.
|
2025-12-18 01:36:41 -03:00
|
|
|
|
|
|
|
|
## Running a test build
|
|
|
|
|
- In Jenkins, run the `harbor-arm-build` job (leave `HARBOR_VERSION` blank to
|
|
|
|
|
build the latest upstream release).
|
|
|
|
|
- The agent pulls Harbor sources, builds every component for arm64, and pushes
|
|
|
|
|
the tagged artifacts to `registry.bstein.dev/infra`.
|
|
|
|
|
- Verify the images appear in Harbor under the `infra` project with the
|
|
|
|
|
`${HARBOR_VERSION}-arm64.$BUILD_NUMBER` tag suffix.
|
