Skip to content

[ca] Document hourly-ci-cleaner tool access issue#7297

Merged
pelikhan merged 2 commits intomainfrom
ci-cleaner-workflow-fix-20251222-170956-8501429fb2999733
Dec 22, 2025
Merged

[ca] Document hourly-ci-cleaner tool access issue#7297
pelikhan merged 2 commits intomainfrom
ci-cleaner-workflow-fix-20251222-170956-8501429fb2999733

Conversation

@github-actions
Copy link
Contributor

Problem

The hourly-ci-cleaner workflow (run #281 and all subsequent runs) fails to execute CI cleanup tasks because development tools are not available in the agent execution environment.

Root Cause

Agentic workflows with engine: copilot run in two separate jobs:

  1. Activation job - Runs setup steps (Install Make, Setup Go, Setup Node.js)
  2. Agent job - Runs agent instructions in a separate Docker container

Tools installed in the activation job are not available in the agent job container. The agent only has access to tools specified in the tools: configuration (currently bash and edit).

Evidence

When the agent tries to run CI cleanup commands:

$ make fmt
bash: make: command not found

$ go fmt ./...
bash: go: command not found

Environment check confirms:

  • Running as awfuser (uid=1001) without sudo access
  • Cannot install packages with apt-get
  • Tools not found in PATH

Impact

This PR

Adds documentation to docs/issues/hourly-ci-cleaner-tool-access.md explaining:

  • The issue and root cause
  • Current impact on the repository
  • Proposed solutions (convert to regular GitHub Actions or fix tool access)
  • Temporary workaround

Proposed Solutions

Option 1: Regular GitHub Actions (Recommended)

Convert to standard GitHub Actions workflow since CI cleanup is deterministic and doesn't require AI decision-making.

Option 2: Fix Tool Access

Investigate how to persist tools from activation job to agent job, or configure agent container with development tools.

Option 3: Hybrid Approach

Use GitHub Actions for tool-dependent commands, agentic workflow only for PR creation.

Next Steps

  1. Review this documentation
  2. Decide on preferred solution approach
  3. Implement fix in separate PR
  4. Test with actual CI failure scenario
  5. Monitor for reliability

Related

AI generated by Hourly CI Cleaner

The hourly-ci-cleaner workflow cannot execute CI cleanup commands
because development tools (Go, make, Node.js) are not available in
the agent execution environment.

Agentic workflows run in separate containers where tools installed
in the activation job are not available to the agent job.

This documents the issue and proposes solutions including converting
to a regular GitHub Actions workflow.

Ref: Workflow run #281
@pelikhan
Copy link
Contributor

@copilot copy the steps from the activation job into the agent job so that the build tools are also available

Copy link
Contributor

Copilot AI commented Dec 22, 2025

@pelikhan I've opened a new pull request, #7299, to work on those changes. Once the pull request is ready, I'll request review from you.

@pelikhan pelikhan marked this pull request as ready for review December 22, 2025 17:41
@pelikhan pelikhan merged commit d61d525 into main Dec 22, 2025
5 of 6 checks passed
@pelikhan pelikhan deleted the ci-cleaner-workflow-fix-20251222-170956-8501429fb2999733 branch December 22, 2025 17:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants