CI: add per-module testsuites
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 40
- Forks
- 30
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 8
Description
Feature Overview
Currently, we have no way to know if a module that is shipped in pkg-oss actually works. During the PR CI phase we only check that the package builds.
The proposal is to:
- Check if the module package is installable and loadable
- Run module own tests (if possible) to determine if it actually works with the given nginx version
It's not yet clear if those additional checks should be blocking PRs or rather inform us about the possible issues. What do we do if the module is broken with the current version of nginx? We don't own that specific code, even if we provide a way to build it.
Alternatives Considered
No response
Additional Context
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 by reviewing the PR CI packaging flow and how module packages are built for each nginx version. Define checks for package installability, loadability, and module-owned tests, then resolve whether failures should block PRs or only report compatibility issues. Done means the CI behavior and failure policy are documented and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100