Build ext separately in nightly
Open
Nobody has claimed this yet.
Category: CI
Feature
- Dominant language
- C
- Stars
- 40.4k
- Forks
- 8.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 96
Description
Description
Currently, the build is tested in CI for building all ext together with the main php.
This is fine for testing the functionality, but basically any ext build can be broken due configure/linking issues.
This is a feature request to build all ext separately in one extra nightly job to prevent issues like #12565, #13745, #13764 to happen again.
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 inspecting the existing CI configuration that builds all extensions with PHP and the nightly jobs around it. The work is complete when an additional nightly job builds each extension separately, catching configure or linking failures without changing the existing functionality tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100