lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cassandra Targett (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-10568) Automate HTML builds via Jenkins to occur with each commit
Date Thu, 11 May 2017 21:29:04 GMT

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

Cassandra Targett commented on SOLR-10568:
------------------------------------------

[~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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message