pnoltes opened a new pull request, #822:
URL: https://github.com/apache/celix/pull/822
This PR introduces storage for the **fuzz testing corpus** using GitHub
build artifacts.
## Proposed Workflow
* **Upload:** The fuzz testing corpus artifact is uploaded only when
building on the `master` branch.
* **Usage:** All other branches pull and use the latest corpus artifact from
the `master` branch during their runs.
## Feedback Requested
I’m looking for input on whether this is the optimal approach, specifically
regarding:
1. **GitHub Artifacts:** Is using build artifacts the right storage
mechanism for this, or should we look into alternatives?
2. **Branch Strategy:** Is using the `master` branch corpus for all other
branches the correct way to handle seed data?
* **The Logic:** The idea behind using the `master` corpora as a seed is
to ensure branches have a more **deterministic build**. By doing this, the
corpora only changes when the `master` branch itself is updated, preventing
noise from fluctuating seeds on feature branches.
Any thoughts or suggestions on this setup are welcome!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
