Gitpod resources are wasted by running multiple prebuild processes for same commit
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Bug description
Pushing a commit result in 3 (three!) separate prebuild processes for no apparent reason.
https://gitpod.io/t/phase2/tufts-core/f3835ce4-aa28-4ab6-975a-7dc95d129e83
https://gitpod.io/t/phase2/tufts-core/f5862986-03e7-4268-87ea-fcaac8236931
https://gitpod.io/t/phase2/tufts-core/552b3fc5-c58f-4d23-ac52-af2ea71fd9b6
Steps to reproduce
- Add a repo to team/project, with gitpod.yml setup for Github prebuild.
- Push a commit
- Check the prebuild pages and see that multiple prebuilds are running (usually 2)
https://gitpod.io/t/team/project/prebuilds
Workspace affected
No response
Expected behavior
No response
Example repository
No response
Anything else?
No response
Contributor 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.
Research direction
Start with the listed reproduction steps: configure a repository with GitHub prebuilds, push one commit, and inspect the team's prebuilds page. No file, test, or entry point is named; done means identifying why duplicate prebuilds are launched and verifying that one commit no longer starts multiple processes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, typescript
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100