Hmm, there is a stable URL for the javadoc plugin output: <https://builds.apache.org/job/Solr-reference-guide-master/javadoc/> (at least after the first build anyway). Seems okay, though the URL sucks (HTML format ref guide is not “javadoc”; I checked and there is no configuration option for the URL). Also, with this change we now have to provide two separate URLs for each branch, one for each format. On balance, I guess I'm okay with leaving it this way.
-- Steve www.lucidworks.com > On May 12, 2017, at 12:15 PM, Steve Rowe <[email protected]> wrote: > > Uwe, > >> On May 12, 2017, at 12:00 PM, Uwe Schindler <[email protected]> wrote: >> >> Ah by the way: I changed the master job a bit. Instead of "archiving" the >> HTML docs as "artifact", I used the "publish javadocs" post-build step to >> publish it as conventional Javadocs. This makes it show as "Documentation" >> link on the Jenkins base page. Also browsing is faster, as it does not need >> to do additional stuff on jenkins, its just a simple static HTML view. > > Unfortunately, this causes the HTML format not to be accessible from the > “last successful build artifacts” view, e.g. > <https://builds.apache.org/job/Solr-reference-guide-master/lastSuccessfulBuild/artifact/>, > which AFAICT means we can’t have a stable URL for the HTML format. I think > this is bad. > > -- > Steve > www.lucidworks.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
