Lewis John McGibbney created NUTCH-3163:
-------------------------------------------
Summary: Integrate Apache Yetus' pre-commit patch testing into
Nutch GitHub Continuous Integration
Key: NUTCH-3163
URL: https://issues.apache.org/jira/browse/NUTCH-3163
Project: Nutch
Issue Type: New Feature
Components: ci/cd
Reporter: Lewis John McGibbney
Assignee: Lewis John McGibbney
Fix For: 1.23
I recently dedicated some time to Hadoop and Tez patches and liked the Apache
Yetus pre-commit patch CI as it is another step to helping reviewers.
My goal is to add Yetus' pre-commit patch testing to Nutch’s CI so every pull
request is checked automatically before review. This gives contributors fast,
consistent feedback and helps reviewers focus on design and behaviour instead
of style and basic checks.
Benefits
* Faster feedback: Contributors see Yetus results (compile, tests, style,
license) on each PR without running everything locally. Problems are caught in
CI instead of in review.
* Consistent checks: The same set of checks runs on every PR (e.g. Ant build,
javac/javadoc, optional RAT, XML/YAML lint). Reduces “works on my machine” and
keeps the bar for contributions clear.
* Better use of review time: Reviewers can rely on Yetus for formatting,
license headers, and basic build/test, and spend more time on logic, APIs, and
Nutch-specific behaviour.
* Unified reporting: Yetus produces a single report (HTML in the artifact,
Markdown in the PR comment) so both contributors and reviewers see one place
for pass/fail and details.
* Alignment with the ASF: Yetus is widely used in Apache projects; using it in
Nutch matches common ASF contribution workflows and makes it easier for
contributors from other Yetus-using projects.
* Optional local use: Contributors can run {{test-patch}} locally (e.g. with
{{{}--build-tool=ant{}}}) before opening a PR, which can shorten the review
cycle.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
