[
https://issues.apache.org/jira/browse/SOLR-10568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985170#comment-15985170
]
Hoss Man commented on SOLR-10568:
---------------------------------
bq. 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.
Do we really need any special publishing "mechanism" here?
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?
Example: here's the Changes.html file served from jenkins for the last stable
build of the 6.x artifacts jenkins job...
https://builds.apache.org/job/Lucene-Artifacts-6.x/lastStableBuild/artifact/lucene/dist/changes/Changes.html
...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)
(this isn't a general purpose solution for publishing content/code, but for the
purpose of developers reviewing the generated output of recently committed
changes -- that's pretty much exactly what jenkins "artifacts" hosting is for)
> 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]
