Optimize CI pipeline: Harbor base image + reliable registry URL #23

Closed
opened 2026-05-25 03:09:01 +00:00 by ldraney · 2 comments
Owner

Type

Feature

Lineage

Project: landscaping-assistant
Board: board-landscaping-assistant

Repo

ldraney/landscaping-assistant

User Story

As a developer, I want the CI pipeline to use the pre-built Harbor base image and a reliable registry path so that builds are faster and don't fail due to transient network issues.

Context

CI pipeline uses ruby:3.4.9-slim with apt-get and gem install on every run instead of the pre-built Harbor base image (ruby-rails-build). The kaniko build-and-push step uses the external Harbor URL which routes through Tailscale DERP and is unreliable from inside the cluster. Multiple consecutive pipeline failures (53-56) due to Harbor connectivity.

Resolution

All criteria met on main via PRs #70, #76, #78. Superseded by closed issues #69 and #73.

### Type Feature ### Lineage Project: landscaping-assistant Board: board-landscaping-assistant ### Repo ldraney/landscaping-assistant ### User Story As a developer, I want the CI pipeline to use the pre-built Harbor base image and a reliable registry path so that builds are faster and don't fail due to transient network issues. ### Context CI pipeline uses `ruby:3.4.9-slim` with `apt-get` and `gem install` on every run instead of the pre-built Harbor base image (`ruby-rails-build`). The kaniko build-and-push step uses the external Harbor URL which routes through Tailscale DERP and is unreliable from inside the cluster. Multiple consecutive pipeline failures (53-56) due to Harbor connectivity. ### Resolution All criteria met on `main` via PRs #70, #76, #78. Superseded by closed issues #69 and #73.
Author
Owner

Shipped in PR #70 (base image + parallel steps) and PR #76 (build-arg registry fix). Closing as completed.

Shipped in PR #70 (base image + parallel steps) and PR #76 (build-arg registry fix). Closing as completed.
Author
Owner

Closing — all acceptance criteria are met on main:

  • Lint/test steps use harbor.tail5b443a.ts.net/library/ruby-rails-build:latest
  • Kaniko pushes via harbor.harbor.svc.cluster.local with insecure: true
  • Pipeline runs green end-to-end ✓
  • NetworkPolicy investigation resolved (external URL for pulls, internal for push) ✓
  • CI image convention documented in docs/infrastructure-and-pipeline.md

Work was completed across PRs #70, #76, #78. Superseded by closed issues #69 and #73.

Closing — all acceptance criteria are met on `main`: - Lint/test steps use `harbor.tail5b443a.ts.net/library/ruby-rails-build:latest` ✓ - Kaniko pushes via `harbor.harbor.svc.cluster.local` with `insecure: true` ✓ - Pipeline runs green end-to-end ✓ - NetworkPolicy investigation resolved (external URL for pulls, internal for push) ✓ - CI image convention documented in `docs/infrastructure-and-pipeline.md` ✓ Work was completed across PRs #70, #76, #78. Superseded by closed issues #69 and #73.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ldraney/landscaping-assistant#23
No description provided.