ops(ci): configure LLM API keys in Forgejo CI for integration test execution #710

Merged

freemo merged 1 commit from ops/m3-ci-llm-keys into master 2026-03-14 22:40:58 +00:00

Conversation 3 Commits 1 Files changed 2 +32

freemo commented 2026-03-12 01:36:06 +00:00

Owner

Copy link

Summary

Configures the Forgejo CI pipeline to inject LLM API keys as environment variables during Robot Framework integration test execution, enabling real LLM endpoint calls after mock removal (#698, #699, #700).

Closes #701

Changes

CI pipeline

• .forgejo/workflows/ci.yml — Updated the integration test job to inject ANTHROPIC_API_KEY and OPENAI_API_KEY from Forgejo repository secrets as environment variables, with masking enabled to prevent exposure in CI logs

Documentation

• docs/development/ci-cd.md — New documentation describing:
  • Required secret names (ANTHROPIC_API_KEY, OPENAI_API_KEY)
  • How to add secrets via Forgejo repository settings
  • How secrets are injected and masked in CI
  • Verification steps to confirm integration tests pass with real LLM endpoints

Design decisions

• Secrets are scoped to the integration test job only (not available to unit test or lint jobs)
• Unit tests (Behave BDD) continue to run without requiring API keys
• Secret names follow the convention used by the LLM provider SDKs (ANTHROPIC_API_KEY, OPENAI_API_KEY)

Quality Checks

• nox -e typecheck — 0 Pyright errors
• nox -e lint — all checks passed
• nox -e format — all files unchanged
• No secrets committed to source code

## Summary Configures the Forgejo CI pipeline to inject LLM API keys as environment variables during Robot Framework integration test execution, enabling real LLM endpoint calls after mock removal (#698, #699, #700). Closes #701 ## Changes ### CI pipeline - **`.forgejo/workflows/ci.yml`** — Updated the integration test job to inject `ANTHROPIC_API_KEY` and `OPENAI_API_KEY` from Forgejo repository secrets as environment variables, with masking enabled to prevent exposure in CI logs ### Documentation - **`docs/development/ci-cd.md`** — New documentation describing: - Required secret names (`ANTHROPIC_API_KEY`, `OPENAI_API_KEY`) - How to add secrets via Forgejo repository settings - How secrets are injected and masked in CI - Verification steps to confirm integration tests pass with real LLM endpoints ### Design decisions - Secrets are scoped to the integration test job only (not available to unit test or lint jobs) - Unit tests (Behave BDD) continue to run without requiring API keys - Secret names follow the convention used by the LLM provider SDKs (`ANTHROPIC_API_KEY`, `OPENAI_API_KEY`) ## Quality Checks - `nox -e typecheck` — 0 Pyright errors - `nox -e lint` — all checks passed - `nox -e format` — all files unchanged - No secrets committed to source code

freemo added this to the v3.2.0 milestone 2026-03-12 01:36:10 +00:00

freemo added the

Type

Task

label 2026-03-12 01:36:11 +00:00

freemo added a new dependency 2026-03-12 02:15:18 +00:00

#701 ops(ci): Configure LLM API keys in Forgejo CI for integration test execution

freemo self-assigned this 2026-03-12 20:33:28 +00:00

freemo reviewed 2026-03-12 20:36:41 +00:00

freemo left a comment

Copy link

Review — PR #710: ops(ci): configure LLM API keys in Forgejo CI

Diff Summary

• Files changed: 2 (ci.yml, docs/development/ci-cd.md)
• Lines: +26 / −0

Commit Message Compliance

• Issue #701 metadata: ops(ci): configure LLM API keys in Forgejo CI for integration test execution
• PR commit first line: ops(ci): configure LLM API keys in Forgejo CI for integration test execution
• Match: ✅ Exact match

Closes Keyword

• PR body contains Closes #701 ✅

Label Compliance

Required Label	Status
Type label	✅ Type/Task
Priority label	❌ Missing (issue has Priority/Critical)
MoSCoW label	❌ Missing (issue has MoSCoW/Must have)

Code Quality

• CI change is correctly scoped to the integration_tests job only — unit tests and lint jobs are unaffected.
• Secrets use ${{ secrets.* }} syntax with automatic masking — no risk of log exposure.
• Documentation in ci-cd.md is comprehensive: includes a full secrets table covering both LLM keys and existing AWS/ASV secrets, and clearly distinguishes unit vs. integration test requirements.
• No secrets committed to source.

Verdict: COMMENT

Code and documentation quality are good. The only compliance gap is that the PR itself is missing Priority/Critical and MoSCoW/Must have labels — please add them to match issue #701 before merge.

## Review — PR #710: ops(ci): configure LLM API keys in Forgejo CI ### Diff Summary - **Files changed:** 2 (`ci.yml`, `docs/development/ci-cd.md`) - **Lines:** +26 / −0 ### Commit Message Compliance - **Issue #701 metadata:** `ops(ci): configure LLM API keys in Forgejo CI for integration test execution` - **PR commit first line:** `ops(ci): configure LLM API keys in Forgejo CI for integration test execution` - **Match:** ✅ Exact match ### Closes Keyword - PR body contains `Closes #701` ✅ ### Label Compliance | Required Label | Status | |---|---| | Type label | ✅ `Type/Task` | | Priority label | ❌ Missing (issue has `Priority/Critical`) | | MoSCoW label | ❌ Missing (issue has `MoSCoW/Must have`) | ### Code Quality - CI change is correctly scoped to the `integration_tests` job only — unit tests and lint jobs are unaffected. - Secrets use `${{ secrets.* }}` syntax with automatic masking — no risk of log exposure. - Documentation in `ci-cd.md` is comprehensive: includes a full secrets table covering both LLM keys and existing AWS/ASV secrets, and clearly distinguishes unit vs. integration test requirements. - No secrets committed to source. ### Verdict: COMMENT Code and documentation quality are good. The only compliance gap is that the PR itself is missing `Priority/Critical` and `MoSCoW/Must have` labels — please add them to match issue #701 before merge.

freemo added the

MoSCoW

Must have

Points

3

Priority

Critical

State

In Progress

labels 2026-03-12 20:57:07 +00:00

freemo commented 2026-03-14 04:43:27 +00:00

Author

Owner

Copy link

PM Review — Day 34

Status: Mergeable, 0 reviews, Priority/Critical, M3 (v3.2.0), Points/3
Author: @freemo

Review Summary

Clean, well-scoped 2-file PR:

• .forgejo/workflows/ci.yml — adds ANTHROPIC_API_KEY and OPENAI_API_KEY secret refs to integration_tests job only (correctly not leaking to lint/unit test jobs)
• docs/development/ci-cd.md — thorough documentation of CI secrets

No credentials in source code — only ${{ secrets.* }} references. This is a prerequisite for E2E tests to pass in CI.

Assessment

• No issues found. Clean, minimal, correct.
• Merge priority: HIGH — this blocks CI execution of all E2E/integration tests that require LLM API keys (PRs #786-#820, #799-#802, etc.)
• Label note: State is In Progress but this looks complete — should be In Review

Action Items

Who	Action	Deadline
@brent.edwards	Peer review — CI/QA domain, quick approval expected	Day 35
@freemo	Confirm secrets are configured in Forgejo admin UI	Day 35

## PM Review — Day 34 **Status**: Mergeable, 0 reviews, Priority/Critical, M3 (v3.2.0), Points/3 **Author**: @freemo ### Review Summary Clean, well-scoped 2-file PR: - `.forgejo/workflows/ci.yml` — adds `ANTHROPIC_API_KEY` and `OPENAI_API_KEY` secret refs to `integration_tests` job only (correctly not leaking to lint/unit test jobs) - `docs/development/ci-cd.md` — thorough documentation of CI secrets No credentials in source code — only `${{ secrets.* }}` references. This is a prerequisite for E2E tests to pass in CI. ### Assessment - **No issues found.** Clean, minimal, correct. - **Merge priority: HIGH** — this blocks CI execution of all E2E/integration tests that require LLM API keys (PRs #786-#820, #799-#802, etc.) - **Label note**: State is `In Progress` but this looks complete — should be `In Review` ### Action Items | Who | Action | Deadline | |-----|--------|----------| | @brent.edwards | **Peer review** — CI/QA domain, quick approval expected | Day 35 | | @freemo | Confirm secrets are configured in Forgejo admin UI | Day 35 |

freemo referenced this pull request 2026-03-14 04:43:34 +00:00

test(e2e): E2E acceptance criteria for M3 (v3.2.0) — decisions, validations, and invariants #799

freemo referenced this pull request 2026-03-14 04:43:45 +00:00

test(e2e): E2E acceptance criteria for M4 (v3.3.0) — corrections, subplans, and checkpoints #814

freemo reviewed 2026-03-14 22:07:13 +00:00

freemo left a comment

Copy link

PM Status — Day 34

@freemo — CI LLM API keys (#701). Mergeable with 2 comments. This is Priority/Critical + Must Have.

Status: In Progress. This is a DevOps prerequisite for real LLM integration tests in CI. Blocks full mock removal completion (#699).

Dependency chain: PR #710 → #701 (CI keys configured) → #699 (unittest.mock removal) → M3 mock removal complete.

Priority: Critical path for M3 closure. Please prioritize after bug #620 regression investigation.

---

PM status — Day 34

## PM Status — Day 34 @freemo — CI LLM API keys (#701). Mergeable with 2 comments. This is **Priority/Critical + Must Have**. **Status**: In Progress. This is a DevOps prerequisite for real LLM integration tests in CI. Blocks full mock removal completion (#699). **Dependency chain**: PR #710 → #701 (CI keys configured) → #699 (unittest.mock removal) → M3 mock removal complete. **Priority**: Critical path for M3 closure. Please prioritize after bug #620 regression investigation. --- *PM status — Day 34*

freemo force-pushed ops/m3-ci-llm-keys from c5ad6ab7ea to 8720400cf7 2026-03-14 22:22:31 +00:00 Compare

freemo scheduled this pull request to auto merge when all checks succeed 2026-03-14 22:22:50 +00:00

freemo scheduled this pull request to auto merge when all checks succeed 2026-03-14 22:34:09 +00:00

freemo force-pushed ops/m3-ci-llm-keys from 8720400cf7 to ce722ed0ea 2026-03-14 22:34:19 +00:00 Compare

freemo merged commit ce722ed0ea into master 2026-03-14 22:40:58 +00:00

freemo deleted branch ops/m3-ci-llm-keys 2026-03-14 22:40:59 +00:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

auto/needs-reevaluation

Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.

  

controller-managed

Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.

  

auto/blocked-by-deps

PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.

  

auto/ci-timeout

Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.

  

auto/claimed-implementer

Currently being processed by an implementer worker.

  

auto/claimed-merge

Currently being processed by the merge driver.

  

auto/claimed-reviewer

Currently being processed by a reviewer worker.

  

auto/driver-down

Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.

  

auto/invariant-violation

Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.

  

auto/last-attempt-tier-0

In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.

  

auto/last-attempt-tier-1

In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.

  

auto/last-attempt-tier-2

In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.

  

auto/last-attempt-tier-min

In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.

  

Automation Tracking

Tracking issues used by the AI Automation system for agents to communicate and report.

  

auto/needs-conflict-resolution

Rebase conflict needs LLM conflict-resolver.

  

auto/needs-implementer

Failing CI needs implementer attention.

  

auto/postmortem

Documenting a driver incident or rollback.

  

auto/ready-to-merge

Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.

  

auto/restart-throttled

Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.

  

auto/revert

Revert PR backing out an invariant violation. Fast-tracked through the merge driver.

  

auto/sentinel

Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.

  

auto/stale-inactivity

No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.

  

auto/unstable

Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.

  

Blocked

A ticket in a blocked state and unable to complete until some other task is completed first.

  

Bounty

$100

A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$1000

A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$10000

A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$20

A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$2000

A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$250

A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$50

A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$500

A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$5000

A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$750

A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  

MoSCoW

Could have

Could have feature in order to satisfy the epic/legendary.

  

MoSCoW

Must have

Must have feature in order to satisfy the epic/legendary.

  

MoSCoW

Should have

Should have feature in order to satisfy the epic/legendary.

  

Needs Feedback

There are questions in the ticket that can not be completed until the project owner provides clarity.

  

Points

1

1 man-hours worth of work for an expert with no learning curve.

  

Points

13

13 man-hours worth of work for an expert with no learning curve.

  

Points

2

2 man-hours worth of work for an expert with no learning curve.

  

Points

21

21 man-hours worth of work for an expert with no learning curve.

  

Points

3

3 man-hours worth of work for an expert with no learning curve.

  

Points

34

34 man-hours worth of work for an expert with no learning curve.

  

Points

5

5 man-hours worth of work for an expert with no learning curve.

  

Points

55

55 man-hours worth of work for an expert with no learning curve.

  

Points

8

8 man-hours worth of work for an expert with no learning curve.

  

Points

88

88 man-hours worth of work for an expert with no learning curve.

  

Priority

Backlog

This ticket has backlogged priority and is not to be worked on yet

  

Priority

CI Blocker

Critical priority issue that blocks CI/CD pipeline and prevents PR merges

  

Priority

Critical

The priority is critical

  

Priority

High

The priority is high

  

Priority

Low

The priority is low

  

Priority

Medium

The priority is medium

  

Signed-off: Owner

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  

Signed-off: Scrum Master

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  

Signed-off: Tech Lead

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  

Spike

A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  

State

Completed

The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  

State

Duplicate

A ticket that represents the same content as an existing ticket.

  

State

In Progress

A ticket that is actively being developed.

  

State

In Review

A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  

State

Paused

This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  

State

Unverified

All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  

State

Verified

The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  

State

Wont Do

This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  

Type

Automation

Any edits or discussion about the AI automated coding system.

  

Type

Bug

Something that doesnt work as intended.

  

Type

Discussion

Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  

Type

Documentation

An error or improvement needed in the documentation.

  

Type

Epic

Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  

Type

Feature

Some new functionality not present.

  

Type

Legendary

A type of Epic which will contain other Epics.

  

Type

Refactor

A code change that restructures existing code without changing its external behavior.

  

Type

Support

Someone needs help using the project.

  

Type

Task

A generic task that doesnt fit into the other type categories.

  

Type

Testing

Work exclusively focusing on fixing or expanding testing.

No labels

auto/needs-reevaluation

controller-managed

auto/blocked-by-deps

auto/ci-timeout

auto/claimed-implementer

auto/claimed-merge

auto/claimed-reviewer

auto/driver-down

auto/invariant-violation

auto/last-attempt-tier-0

auto/last-attempt-tier-1

auto/last-attempt-tier-2

auto/last-attempt-tier-min

Automation Tracking

auto/needs-conflict-resolution

auto/needs-implementer

auto/postmortem

auto/ready-to-merge

auto/restart-throttled

auto/revert

auto/sentinel

auto/stale-inactivity

auto/unstable

Blocked

Bounty

$100

Bounty

$1000

Bounty

$10000

Bounty

$20

Bounty

$2000

Bounty

$250

Bounty

$50

Bounty

$500

Bounty

$5000

Bounty

$750

MoSCoW

Could have

MoSCoW

Must have

MoSCoW

Should have

Needs Feedback

Points

1

Points

13

Points

2

Points

21

Points

3

Points

34

Points

5

Points

55

Points

8

Points

88

Priority

Backlog

Priority

CI Blocker

Priority

Critical

Priority

High

Priority

Low

Priority

Medium

Signed-off: Owner

Signed-off: Scrum Master

Signed-off: Tech Lead

Spike

State

Completed

State

Duplicate

State

In Progress

State

In Review

State

Paused

State

Unverified

State

Verified

State

Wont Do

Type

Automation

Type

Bug

Type

Discussion

Type

Documentation

Type

Epic

Type

Feature

Type

Legendary

Type

Refactor

Type

Support

Type

Task

Type

Testing

Milestone

Clear milestone

No items

No milestone

v3.2.0

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

freemo

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks

#701 ops(ci): Configure LLM API keys in Forgejo CI for integration test execution

cleveragents/cleveragents-core

Reference

cleveragents/cleveragents-core!710

No description provided.