Simplify the complete Infection CI workflow and preserve reports
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github-actions, php
- Domain
- ci-cd, devops, testing-qa
Research direction
Start by reviewing infection.json5, the existing complete Infection workflow, and the normal PHPUnit workflows to compare compatibility coverage and identify the canonical runtime. Check the related pull-request workflow in #8901 and verify safe parallelism, report formats, and available metadata. Done means a manually runnable workflow preserves logs and machine-readable reports, exposes runtime details, and visibly fails on operational errors without an arbitrary score threshold.
Written by the indexing model from the issue text.
Description
Goal
Simplify the complete Infection GitHub Actions workflow so LibreSign has one reliable CI execution path for full mutation runs and preserves enough evidence for baseline analysis.
This workflow is for complete mutation runs. It is separate from the normal pull-request change-aware mutation workflow.
Current problem
The current Infection workflow combines mutation testing with a PHP/Nextcloud compatibility matrix.
Mutation testing and compatibility testing answer different questions.
LibreSign already has normal PHPUnit/CI coverage for supported runtime combinations. Repeating the complete mutation suite across a compatibility matrix can multiply an already expensive workload without evidence that each combination provides distinct mutation-testing signal.
Investigation
Before removing the current matrix, verify:
- what compatibility coverage is already provided by normal PHPUnit workflows;
- whether Infection has produced mutation-specific failures on different supported PHP/Nextcloud combinations;
- which PHP and Nextcloud versions should define the canonical full-mutation environment;
- whether more than one full-run combination has a measured reason to remain.
Do not remove compatibility coverage merely to reduce runtime.
Do not retain duplicate mutation runs merely because the matrix already exists.
Required outcome
Provide a complete-run Infection workflow that:
- can be started from GitHub Actions;
- uses the agreed canonical runtime configuration;
- keeps workflow YAML focused on orchestration;
- exposes the effective Infection command/configuration;
- preserves useful logs and machine-readable reports;
- records runtime and environment metadata;
- fails visibly for operational Infection/PHPUnit failures.
The workflow must not introduce an arbitrary blocking mutation-score threshold.
Reporting
Preserve enough information to diagnose:
- generated mutants;
- killed mutants;
- escaped mutants;
- uncovered mutants;
- timeout mutants;
- execution errors;
- MSI and Covered Code MSI;
- total runtime.
When Infection supports a suitable machine-readable report, preserve it as a GitHub Actions artifact.
Parallelism
Use only a worker/thread configuration shown to be safe for LibreSign test isolation.
Do not force --threads=1 permanently only to hide shared-state races.
Done when
- The complete Infection workflow has a documented runtime/Nextcloud environment.
- Compatibility testing is not duplicated without a measured reason.
- A complete Infection run can be launched from GitHub Actions.
- Useful reports and logs survive the CI run.
- Runtime and environment metadata are visible.
- Operational failures cannot silently pass.
- No arbitrary merge-blocking score is introduced.
- The workflow is suitable for producing the new authoritative baseline.
Related
- Parent epic: #8897
- Current Infection configuration:
infection.json5 - Pull-request mutation workflow: #8901
- Dominant language
- PHP
- Stars
- 828
- Forks
- 159
- Avg merge
- 7h 43m
- Merged PRs (30d)
- 537
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from LibreSign/libresign
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
LibreSign/libresign#9007 · 1 reaction ·
Maintainers usually reply within 1 day
-
backend enhancement php
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Validation page says "This document is valid" for a document with no signaturePossibly taken @maia-andre claimed this 8 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
LibreSign/libresign#8284 · 5 comments ·
Maintainers usually reply within 1 day
-
backend php
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
All issues in LibreSign/libresign
Similar issues
-
needs-triage Platform(Default)
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Feature-Request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
RSS-Bridge/rss-bridge#5123 ·
Maintainers usually reply within 1 day
-
[Store] RstLoader detects headings inside indented code blocksPossibly taken @lazerg claimed this today. OpenBug Status: Needs Review Store
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug repo:ckeditor
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
No Code Attached Yet
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
joomla/joomla-cms#48611 ·
Maintainers usually reply within 1 day