Setuptools consuming excessive CI resources
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 1.4k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
@jaraco I think the large # of jobs this introduces to setuptools' GitHub workflows is slowing down builds for other PyPA projects. There is a limit of 20 concurrent jobs org-wide for our plan, and setuptools has gone from 36 jobs in #3078 to 119 jobs here. I've noticed a significant backlog over at https://github.com/pypa/warehouse/actions over the last few days and suspect this might be why.
Any thoughts on how we could get this down to a more reasonable number of concurrent jobs per workflow run?
(cc @ewdurbin)
Originally posted by @di in https://github.com/pypa/setuptools/issues/2923#issuecomment-1035840098
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reviewing the current GitHub workflow definitions and comparing their job counts with the change referenced in #3078. Identify the workflow fan-out causing the resource increase and confirm the desired concurrency target with maintainers; done means an agreed reduction is implemented without losing required CI coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100