Optimize CI pipeline: Harbor base image + reliable registry URL #23
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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-slimwithapt-getandgem installon 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
mainvia PRs #70, #76, #78. Superseded by closed issues #69 and #73.Shipped in PR #70 (base image + parallel steps) and PR #76 (build-arg registry fix). Closing as completed.
Closing — all acceptance criteria are met on
main:harbor.tail5b443a.ts.net/library/ruby-rails-build:latest✓harbor.harbor.svc.cluster.localwithinsecure: true✓docs/infrastructure-and-pipeline.md✓Work was completed across PRs #70, #76, #78. Superseded by closed issues #69 and #73.