CI is too slow

Open
#2,460 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Domain
ci-cd

Research direction

Start by reviewing recent CI runs and comparing the durations of each job. Investigate the slowest jobs and the reported flakiness, then verify that proposed fixes reduce total CI time and prevent items from dropping out of the merge queue.

Written by the indexing model from the issue text.

Description

CI used to take ~5 mins total, but is now commonly taking over 30 mins. This is extremely limiting, especially now we have enabled merge queue. Items often spend an hour or more in the queue, and can then drop out due to flakiness.

Investigate which CI jobs are the slowest and why, and find fixes.

Dominant language
Java
Stars
10.5k
Forks
1.5k
Avg merge
1d 12h
Merged PRs (30d)
133

Contributor guide

Open the contributing guide

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 github/copilot-sdk

All issues in github/copilot-sdk

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.