Post

Increased Harbor mirror validation timeout to avoid CI timeouts

Increased Harbor mirror validation timeout to avoid CI timeouts

The Harbor mirror validation step in the CI workflow was timing out, causing spurious failures. I extended the job’s timeout to give it enough time to finish its checks.

Adjusting the CI timeout in harbor-mirror.yml

The workflow file harbor-mirror.yml had the timeout-minutes set to 30. The patch added a minute increment to 45, which is reflected in the diff. This change makes the Harbor mirror validation job wait longer before being marked as failed.

Context for the constraint

The Harbor mirror step validates container images against a registry mirror. In our homelab, pulling and verifying images can take longer than 30 minutes, especially when network conditions are variable. The original timeout caused the job to abort prematurely, resulting in a failed pipeline that required manual re‑run. Extending the timeout lets the job complete its validation without manual intervention.

Verification and operational impact

The next verification step is to confirm that the Harbor mirror job finishes within 45 minutes on a typical run. Once that is observed, the change will reduce false CI failures and keep the pipeline green. For other platform teams, the takeaway is to monitor job durations and adjust timeouts rather than rely on shorter defaults.

This post is licensed under CC BY 4.0 by the author.