[
https://issues.apache.org/jira/browse/LUCENE-9321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17101604#comment-17101604
]
Uwe Schindler commented on LUCENE-9321:
---------------------------------------
In my opinion, only the Smoke Tester on Jenkins should run the full
documentation analysis. The liklyhood that a single commit breaks this is not
large. If we check that the links inside a single module are fine, I think t's
OK for a precommit check. The global link checking mainly only fails when you
do structural changes to the build (like adding new modules). And in that case
you would run the whole build anyways.
For everyday use, I would make the precommit checks as fast as possible and let
Jenkins + Smoketester do the rest. But that's just my opinion.
Sorry for not proceeding, very busy at moment. Tro to get on that later. I need
lunch first.
> Port documentation task to gradle
> ---------------------------------
>
> Key: LUCENE-9321
> URL: https://issues.apache.org/jira/browse/LUCENE-9321
> Project: Lucene - Core
> Issue Type: Sub-task
> Components: general/build
> Reporter: Tomoko Uchida
> Assignee: Uwe Schindler
> Priority: Major
> Fix For: master (9.0)
>
> Attachments: screenshot-1.png
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> This is a placeholder issue for porting ant "documentation" task to gradle.
> The generated documents should be able to be published on lucene.apache.org
> web site on "as-is" basis.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
