nextcloud / nextcloud/cookbook
Speed up CI testing
Open
Nobody has claimed this yet.
maintenance
meta and development
- Dominant language
- HTML
- Stars
- 641
- Forks
- 113
- Avg merge
- 21h 31m
- Merged PRs (30d)
- 26
Description
The CI testing could be faster. Here, some ideas can be collected
- Separate migration tests from main tests and run the migration tests only three times (once per DB system)
- Install NC core only once and reuse it using artifacts/caches
- Use one PHP version for installation and do not install for each version
- Cache Docker container images
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 reviewing the repository's CI configuration and measuring the current testing workflow. Work through the listed ideas around migration-test separation, NC core reuse, PHP installation, and Docker image caching; done means the CI checks still pass with reduced runtime.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, php
- Domain
- ci-cd, devops, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100