Skip to content

ci(.github/workflows): move engine install to databricks/databricks-bot-engine@76a6e590#538

Merged
eric-wang-1990 merged 2 commits into
mainfrom
bump-engine-ref-reviewer-turns-cap
Jun 21, 2026
Merged

ci(.github/workflows): move engine install to databricks/databricks-bot-engine@76a6e590#538
eric-wang-1990 merged 2 commits into
mainfrom
bump-engine-ref-reviewer-turns-cap

Conversation

@eric-wang-1990

@eric-wang-1990 eric-wang-1990 commented Jun 21, 2026

Copy link
Copy Markdown
Collaborator

What

Two related changes to all four bot workflows:

  1. Install the engine from the org repo. Repoint from the personal eric-wang-1990/databricks-bot-engine to databricks/databricks-bot-engine, pinned to ENGINE_REF: 76a6e5902b217606b72a9476636df0d761260846 (initial org import, extracted from databricks/databricks-driver-test@898d020e).
  2. Run on the peco-driver self-hosted runner. runs-on: [self-hosted, Linux, X64, peco-driver] (was ubuntu-latest). The install pulls from a private org repo and the tests hit the live endpoint, so the job must run on a runner with access to the internal databricks network/org — the same runner adbc's reyden nightly uses. Resolves the "VERIFY: pick a protected/self-hosted runner" placeholders.

Why

The canonical published engine moved from a personal repo to the org repo. 76a6e590 includes the reviewer fix this PR originally carried (review-phase max_turns 20→100 + explicit out-of-turns failure, fixing the reviewer death on #536) plus current hub main.

Secret

The existing BOT_ENGINE_PAT reads the org repo (confirmed) — no secret change needed. It just has to be reachable from the peco-driver runner.

Verify

After merge, re-run the reviewer on #536 — it should complete with max_turns=100 (or fail with the explicit cap message).

This pull request and its description were written by Isaac.

…e590

Repoints all four bot workflows from the personal install repo
(eric-wang-1990/databricks-bot-engine) to the org repo
(databricks/databricks-bot-engine), and pins ENGINE_REF to 76a6e590 — the
initial engine import there, extracted from databricks-driver-test@898d020e.

That engine state includes the reviewer fix this PR originally carried
(review-phase max_turns 20→100 + explicit out-of-turns failure message),
plus the rest of current hub main. The existing BOT_ENGINE_PAT has read
access to the org repo, so no secret change is needed.

Co-authored-by: Isaac
@eric-wang-1990
eric-wang-1990 force-pushed the bump-engine-ref-reviewer-turns-cap branch from 2c91281 to df246d7 Compare June 21, 2026 06:58
@eric-wang-1990 eric-wang-1990 changed the title ci(bot): bump ENGINE_REF to f37c5250 (reviewer turn-cap fix) ci(bot): move engine install to databricks/databricks-bot-engine@76a6e590 Jun 21, 2026
The four bot workflows now pip-install the engine from the PRIVATE org repo
databricks/databricks-bot-engine. That install (and the live-endpoint tests)
needs a runner with access to the internal databricks network/org, so move
them off ubuntu-latest to the peco-driver self-hosted runner
([self-hosted, Linux, X64, peco-driver]) — the same runner adbc's reyden
nightly uses. Resolves the "VERIFY: pick a protected/self-hosted runner"
placeholders.

Co-authored-by: Isaac
@eric-wang-1990 eric-wang-1990 changed the title ci(bot): move engine install to databricks/databricks-bot-engine@76a6e590 ci(.github/workflows): move engine install to databricks/databricks-bot-engine@76a6e590 Jun 21, 2026
@eric-wang-1990
eric-wang-1990 merged commit 2e3e239 into main Jun 21, 2026
1 of 3 checks passed
@eric-wang-1990
eric-wang-1990 deleted the bump-engine-ref-reviewer-turns-cap branch June 21, 2026 07:18
eric-wang-1990 added a commit that referenced this pull request Jun 21, 2026
…er) (#539)

## Problem

After moving the bot workflows to the self-hosted **peco-driver** runner
(#538), `actions/setup-python` fails there:

> Version 3.11 was not found in the local cache … not found for this
operating system.

Self-hosted runners have no GitHub tool-cache (that's why setup-python
"just worked" on `ubuntu-latest`), and this one can't reach the version
manifest.

## Fix

The runner is provisioned with system **python3.11** + **Node**. All
four bot workflows drop `actions/setup-python` and instead build a venv
from the runner's `python3.11`, put on `$GITHUB_PATH` so later `pip` /
`python -m …` steps resolve to 3.11 unchanged. Node (for
`@anthropic-ai/claude-code`, which the Python SDK shells out to) comes
from the runner.

Followup workflows keep their `if: skip != 'true'` guard. YAML
validated; title checked against adbc's checker.

## Requires (runner provisioning, one-time)

`python3.11` + `python3.11-venv` and Node/npm installed on the
peco-driver runner and on the runner service's PATH.

This pull request and its description were written by Isaac.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant