On the Beam project, we've got a Jenkins job that stages the site: https://github.com/apache/beam/blob/master/.test-infra/jenkins/job_beam_PreCommit_Website_Stage.groovy
You can see Jenkins making a comment about where the staged contents are, as here: https://github.com/apache/beam-site/pull/273. Lately, Jenkins has stopped making these convenient comments (IIUC inherited configs change under us - sad face) but the staged URL is still available in the logs, or by guesswork. TBH it is just a shell script with no magic or infra needs. Kenn On Sun, Jan 21, 2018 at 6:42 AM, Lukasz Lenart <lukaszlen...@apache.org> wrote: > ASF doesn't support GH Pages, instead you can use a "asf-site" branch > which can be automatically deployed into a web server (fill a ticket > for INFRA)[1]. We use Docker to test changes locally as there is no a > staging option when using Jekyll [2]. > > [1] https://builds.apache.org/view/S-Z/view/Struts/job/Struts-site/ > [2] https://github.com/apache/struts-site > > > Regards > -- > Łukasz > + 48 606 323 122 http://www.lenart.org.pl/ > > 2018-01-20 8:37 GMT+01:00 Alex Harui <aha...@adobe.com.invalid>: > > 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 > > > > >
