[
https://issues.apache.org/jira/browse/SOLR-10568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007230#comment-16007230
]
Cassandra Targett edited comment on SOLR-10568 at 5/11/17 9:31 PM:
-------------------------------------------------------------------
[~steve_rowe] - Now that the ref guide is on master, we should change up the
job https://builds.apache.org/job/Solr-reference-guide-jira-SOLR-10290/ to run
from master?
Did we decide what to do about the branches? Do we need a job for each branch?
*edit*: also, it seems that build isn't pulling from the repo properly...the
last good build is from today, but the console output shows build errors that
Hoss and I have definitely fixed, and the sha is from 27 April (49c92bf0)
was (Author: ctargett):
[~steve_rowe] - Now that the ref guide is on master, we should change up the
job https://builds.apache.org/job/Solr-reference-guide-jira-SOLR-10290/ to run
from master?
Did we decide what to do about the branches? Do we need a job for each branch?
> 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: [email protected]
For additional commands, e-mail: [email protected]
