[ 
https://issues.apache.org/jira/browse/SOLR-10568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985420#comment-15985420
 ] 

Uwe Schindler edited comment on SOLR-10568 at 4/26/17 7:27 PM:
---------------------------------------------------------------

I agree with Hoss here. It is quite easy to instruct ASF Jenkins to run on 
every commit in a branch of SVN or GIT. No need for svbpubsub or anything. The 
results of a Jenkins run can be declared as "release artifacts" (a PDF file) 
and Jenkins copies them away and also archives them. So we have an archive of 
PDF files. If HTML is created it can be handled like "Javadocs". E.g. the 
Release documents of Lucene and Solr are a whole Website structure including 
custom HTML pages, but it is just marked as "Javadocs" in Jenkins builds - so 
published automatically.


was (Author: thetaphi):
I agree with Hoss here. It is quite easy to instruct ASF Jenkins to run on 
every commit in a branch of SVN or GIT. No need for svbpubsub or anything. The 
results of a Jenkins run can be declared as "release artifacts" (a PDF file) 
and Jnekins copies them away and also archives them. So we have an archive of 
PDF files. If HTML is created it can be handled like "Javadocs". E.g. the 
Release documents of Lucene and Solr are a whole Website structure including 
custom HTML pages, but it is just marked as "Javadocs" in Jenkins builds - so 
published automatically.

> Automate HTML builds via Jenkins to occur with each commit
> ----------------------------------------------------------
>
>                 Key: SOLR-10568
>                 URL: https://issues.apache.org/jira/browse/SOLR-10568
>             Project: Solr
>          Issue Type: Sub-task
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: documentation
>            Reporter: Cassandra Targett
>            Priority: Minor
>
> Spin-off from SOLR-10295.
> The idea is to use a mechanism (possibly gitpubsub and/or svnpubsub?) so 
> Jenkins builds of HTML format of the Ref Guide occur as soon as commits are 
> made to any non-released branch.
> This would allow any committer to see doc changes ASAP after a commit to 
> verify the presentation of the information is as expected.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to