What we do for the OpenWhisk website is the following: We use jekyll [1] to generate the site out of markdown files
We use github repo [2] with two branches master and asf-site We follow normal flow of using PRs, when they get merged to master a Jenkins job that is configure with "Poll SCM" on gitbox mirror repo then kicks to run a build The jenkins is configure [3] to use the jenkins file from the repo [4] it run jekyll to generate the html website and then push to the asf-site The job is restricted to jenkins node git-websites and then push to the asf-site branch on on gitbox mirror repo. And that's the end of the process in a few minutes changes are live on the web site [5] Feel free to checkout what we do and re-use any parts [1] https://jekyllrb.com [2] https://github.com/apache/incubator-openwhisk-website [3] https://builds.apache.org/view/O/view/OpenWhisk/job/OpenWhisk-website/configure [4] https://github.com/apache/incubator-openwhisk-website/blob/master/tools/jenkins/website_build.groovy [5] https://openwhisk.apache.org -- Carlos On Sat, Feb 10, 2018 at 7:42 PM sebb <seb...@gmail.com> wrote: > On 10 February 2018 at 21:46, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > > Hi, > > > > Is is possible to add notes on publishing to svnpubsub from Jenkins, > please? > > > > Gitpubsub is perfect for sites that are build from only one Git repo. > > But when a site mixes content from many repositories (like a main site + > one > > site per component release), svnpubsub is more suited > > I'm curious - why is that? > > > This is for example the case for Maven site > > http://maven.apache.org/developers/website/index.html > > > > And once Jenkins will have the ability to commit to svnpubsub like it > can do > > to gitpubsub, we'll be able to stop using CMS to publish (then we'll be > able > > to switch to Git for the site source, keeping generated html in > svnpubsub) > > > > Regards, > > > > Hervé > > > > Le samedi 3 février 2018, 17:40:35 CET Chris Lambertus a écrit : > >> Hi folks, > >> > >> There has been a lot of interest lately in creating and deploying > project > >> sites with gitpubsub and markdown builders like Pelican, Jekyll, etc. To > >> date, we have very little documentation or guidance on this approach. > I’d > >> like to fix that by developing some documentation as a starting point > for > >> projects wishing to use this system. > >> > >> Some current gaps I’m aware of: > >> > >> - no “staging” URLs similar to CMS (a fix is in the works) > >> - few examples for Jenkins/Buildbot jobs > >> - no documentation on migrating from CMS markdown/templating > >> > >> I’ve started a cwiki page > >> > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=75964385 > >> < > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=75964385> > >> in the hopes of addressing this. > >> > >> I’d like to ask folks to take a look at this and let me know what other > >> information projects would find useful in this documentation. If anyone > has > >> created internal documentation for their own work with > markdown+gitpubsub, > >> I’d love to have a link. > >> > >> Thanks, > >> Chris > >> ASF Infra > > > > >
