dashorst commented on PR #1772:
URL: https://github.com/apache/maven-site/pull/1772#issuecomment-6790121545

   @elharo Nothing outside this repository can make CI fail.
   
   - The check reads only the rendered `target/site` and the `.htaccess` files 
in it. It makes no network requests.
   - It only knows the addresses this repository has published, listed in 
`src/published-addresses.txt`. Pages of the component sites (the plugins, 
`/ref/`, `/resolver/`, and so on) are not on that list.
   - A redirect into a part of the server that another build writes is not 
followed further: the paths in the `components.links` files, `/components/`, 
and the `download.cgi` scripts. The summary counts it as "to sites outside this 
build", never as broken. If a plugin site moves or drops a page, this build 
doesn't notice.
   
   What does fail CI is a change in this repository that leaves a published 
address or anchor leading nowhere: deleting or renaming a page, or dropping the 
id of a heading, without a redirect or a `Redirect gone`. The check runs in the 
`site` phase, so it fails both the PR workflow (`verify site`) and the Jenkins 
`site`/`site-deploy` job, and it prints the `Redirect` line or anchor to add. A 
new page never fails it; it is only reported as not on the list yet. If the 
check is ever in the way, `-Dexec.skip` skips it; it is the only exec execution 
in a normal site build.
   


-- 
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]

Reply via email to