[delete-cloud]

Summary

• set explicit pip index and timeout for Woodpecker lint/smoke steps
• pass pip/uv index build args into the Kaniko app image build
• keep Dockerfile defaults on official PyPI for non-CI builds

Verification

• woodpecker-cli lint .woodpecker/ci.yml
• uv run ruff check src/coding_agent/observability/ src/coding_agent/ui/http_server.py src/coding_agent/ui/session_manager.py tests/ui/test_server_compat_imports.py tests/coding_agent/test_agent_observability.py tests/coding_agent/test_bee_template_pack_smoke.py
• git diff --check

Context

Woodpecker #145/#146 failed before image build because CI could not resolve hatchling from PyPI. A rerun with PIP_INDEX_URL passed lint/smoke, then Kaniko failed inside Dockerfile RUN pip install uv because the index setting was not passed into the Docker build environment.

Summary by CodeRabbit

• Bug Fixes
  • Improved build and test reliability by standardizing package download settings across CI and image builds.
  • Reduced the chance of timeouts or inconsistent dependency fetching during linting, smoke tests, and image creation.

[coderabbitai]

Warning

Review limit reached

@delete-cloud, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 55 minutes and 43 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 8b0519bd-59e9-4d18-b6bb-319974914725

📥 Commits

Reviewing files that changed from the base of the PR and between 122f521 and 53f1bb2.

📒 Files selected for processing (1)

• coding-agent/Dockerfile

📝 Walkthrough

Walkthrough

The CI workflow and builder image now carry pip and uv index settings through job environment variables, build arguments, and Dockerfile environment configuration.

Changes

Package index settings propagation

Layer / File(s)	Summary
Builder env contract coding-agent/Dockerfile	The builder stage declares pip and uv build arguments and exposes them as environment variables in the image.
CI job wiring .woodpecker/ci.yml	The lint, smoke-test, and image-build jobs define pip and uv environment values, and the image build passes them to Kaniko as build arguments.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 I hop through builds with nimble feet,
Pip and uv now share one treat.
From CI to image, values glide,
A tidy trail from side to side.
Ears up, the package path is neat!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the main change: passing Python package index settings into the image build.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/woodpecker-pip-index

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@coding-agent/Dockerfile`:
- Around line 27-31: The Dockerfile’s ENV block is persisting package-index URLs
into the final image, which should not happen. Remove PIP_INDEX_URL and
UV_DEFAULT_INDEX from the image-wide ENV settings and keep them build-scoped
instead, passing them only into the specific RUN steps that need package
installation. Use the existing Dockerfile ENV/RUN sections to locate the change
and preserve PYTHONDONTWRITEBYTECODE, PYTHONUNBUFFERED, and PIP_DEFAULT_TIMEOUT
as image environment values.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 08e0609d-7c2f-4d69-aafb-79c5d6cdaba9

📥 Commits

Reviewing files that changed from the base of the PR and between 7a3cf30 and 122f521.

📒 Files selected for processing (2)

• .woodpecker/ci.yml
• coding-agent/Dockerfile