Built-in Buildkite connector for CI logs

Open
#112 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
ci-cd, devtools

Research direction

Read the GitHub Actions connection and tools from issue #69, then inspect the ci-failure-review entry point and the existing output limits. Implementing the proposed Buildkite connection spans scoped read-only authentication, build and job retrieval, log handling, and compatible tool shapes. Done means running ci-failure-review on a Buildkite pipeline with a known flaky test and confirming the report cites the failing step from its log.

Written by the indexing model from the issue text.

Description

area: connectors help wanted idea

Idea

Add Buildkite as a built-in connection, so ci-failure-review can read Buildkite builds and job logs.

Problem

ci-failure-review can read GitHub Actions runs and logs (#69). Teams that run CI on Buildkite get nothing built in and need a custom connection.

Proposed initial scope

  • A Buildkite connection with a read-only API access token, limited to one organization and the chosen pipelines.
  • Read tools only, as an allowlist: list builds for a pipeline, get a build with its jobs, get a job's log.
  • Job logs come back as text, capped like GitHub Actions logs (the last 300 lines).
  • Logs pass through the existing output limits and are never stored in plaintext beyond the run's artifacts.
  • Same tool shapes as the GitHub Actions tools where possible, so one skill can work with either.

Validation

Run ci-failure-review against a Buildkite pipeline with a known flaky test and confirm the report cites the failing step from the log.

Split out from #54.

Dominant language
Python
Stars
1
Forks
1
Avg merge
1h 9m
Merged PRs (30d)
322

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from piotrekno1/second-shift

All issues in piotrekno1/second-shift

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.