lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Rowe (JIRA)" <>
Subject [jira] [Commented] (SOLR-10568) Automate HTML builds via Jenkins to occur with each commit
Date Wed, 26 Apr 2017 19:26:04 GMT


Steve Rowe commented on SOLR-10568:

Assuming we have a jenkins job(s) building the ref guide for "unreleased" versions/branches
(based on a git change trigger), and we want developers to be able to review the output, can't
we just use the "lastStable" artifacts URLs to serve them?
 ...we could serve the *unreleased* HTML or PDF versions of the ref guide from similar URLs,
which owuld always update anytime there is a successful build)


I'll explore creating a Jenkins job (hosted on the ASF Jenkins nodes dedicated to website
building) to build all forms of the unreleased guide.  We can then decide about triggering
separately, but initially a periodic trigger, at least once a day I think, should be fine.

> Automate HTML builds via Jenkins to occur with each commit
> ----------------------------------------------------------
>                 Key: SOLR-10568
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message