[
https://issues.apache.org/jira/browse/SOLR-10568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007298#comment-16007298
]
Steve Rowe commented on SOLR-10568:
-----------------------------------
bq. I'll clone that one into a new job "Solr-reference-guide-master" and change
the branch accordingly in the job config, then remove the original job (I seem
to recall that renaming Jenkins jobs is problematic).
Done: https://builds.apache.org/job/Solr-reference-guide-master/ . I deleted
the {{jira/solr-10290}} branch job.
bq. 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)
I changed the git repo from
{{https://git-wip-us.apache.org/repos/asf/lucene-solr.git}} to
{{git://git.apache.org/lucene-solr.git}}, the latter of which is used by some
(all?) of the other Lucene/Solr ASF Jenkins jobs. I *think* these are usable
interchangeably, but maybe not?
Also, in the Advanced section for the git repository, the {{Refspec}} was
configured as {{+refs/heads/master:refs/remotes/origin/master}} (I cloned the
original job from one of the existing ones on the {{git-websites}} label, and I
must have forgotten to unfurl the Advanced section, so didn't notice this).
<== I'm guessing this was the problem, but I'm not sure.
Anyway, I manually built the new job, and it succeeded after pulling the most
recent master commit (2f6700972).
> 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]
