Hi Alex, Like the Beam project, the HTML edition of the Solr Reference Guide is regularly built from Jenkins with Jekyll via a script[1], which uses RVM[2] to enable Jekyll+gems, then invokes the relevant targets from the Solr Ant build. The result is then served from Jenkins’s “Document”/javadoc view, e.g. <https://builds.apache.org/view/L/view/Lucene/job/Solr-reference-guide-master/javadoc/>.
[1] https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;a=blob;f=dev-tools/scripts/jenkins.build.ref.guide.sh [2] Ruby Version Manager (RVM): https://rvm.io -- Steve www.lucidworks.com > On Jan 20, 2018, at 2:37 AM, Alex Harui <aha...@adobe.com.INVALID> wrote: > > I'm just learning about Jekyll and GH Pages. We will be using GH Pages > but I don't see a way to have the equivalent of a staging server like we > do in Apache CMS. So I thought about using Jenkins to call Jekyll to > build (but not serve) the site. Then the last successful artifacts would > act as a staging server? > > Or if there is a better way that's fine too. > > Thanks, > -Alex > >
