Built-in Buildkite connector for CI logs
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
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
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
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from piotrekno1/second-shift
-
code-review secondshift
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
piotrekno1/second-shift#419 ·
Maintainers usually reply within 1 day
-
area: deployment
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
piotrekno1/second-shift#310 ·
Maintainers usually reply within 1 day
-
code-review secondshift
Difficulty 4/5 3-5 days Newbie friendliness 46/100
piotrekno1/second-shift#421 ·
Maintainers usually reply within 1 day
-
code-review secondshift
Difficulty 4/5 3-5 days Newbie friendliness 56/100
piotrekno1/second-shift#420 ·
Maintainers usually reply within 1 day
-
Fix failed-delivery retries on PostgreSQLPossibly taken @piotrekno1 claimed this today. Opencode-review fix-approved secondshift
Difficulty 3/5 1-2 days Newbie friendliness 35/100
piotrekno1/second-shift#418 ·
Maintainers usually reply within 1 day
All issues in piotrekno1/second-shift
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
area:cli area:security enhancement priority:medium size:small
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
RonaldHensbergen/composable-data-stack#1338 ·
Maintainers usually reply within 1 day
-
area:stdlib effort:S impact:med platform:linux type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
automated endpoint-dead needs-curation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
almanac-data/climate-almanac#139 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
UKGovernmentBEIS/inspect_ai#6695 · 1 comment ·
Maintainers usually reply within 1 day