parse-community / parse-community/parse-server
ci: optimize build process
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
New Feature / Enhancement Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
Current Limitation
Currently, the CI runs all builds in parallel. During PR development, that is unnecessary, because if the build fails for, say one version of MongoDB or Node, it is likely to fail for the other ones as well, with the same error. That costs build time and we may hit a GitHub plan limit unnecessarily.
Feature / Enhancement Description
Change the CI process to run builds in batches, for example.
- Run only 1 environment each for MongoDB and Postgres
- If (1) pass, run the rest of the the environments
Example Use Case
n/a
Alternatives / Workarounds
n/a
3rd Party References
n/a
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 by locating the repository's CI workflow definitions and the build matrix for MongoDB, Postgres, and Node environments. Confirm the current parallel behavior, then verify that one environment per database runs first and the remaining environments run only after those checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, mongodb, node.js, postgres
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100