[
https://issues.apache.org/jira/browse/SOLR-10568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16008620#comment-16008620
]
Steve Rowe commented on SOLR-10568:
-----------------------------------
Chris Lambertus offered to help troubleshoot the 6.6 job issue on INFRA-14143,
but declined to provide me access to those general (non-project-specific) build
slaves. I manually kicked off the 6.6 job and it succeeded! Maybe there was
something weird about the squash merge commit or something?
FYI because of changes Uwe instigated, the HTML format is no longer under
latest successful build artifacts, but are instead available from the
"Document" link from the job's landing page, pointing to a ".../javadocs/"
page, e.g. for the 6.6 job:
[https://builds.apache.org/job/Solr-reference-guide-6.6/javadoc/].
> 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]
