| commit | 38079f8979e71f62235c518b880413e82196ca1e | [log] [tgz] |
|---|---|---|
| author | Dave Fisher <dave@davefisher.tech> | Tue Apr 02 12:14:24 2019 -0700 |
| committer | GitHub <noreply@github.com> | Tue Apr 02 12:14:24 2019 -0700 |
| tree | e059201fd667af1913dce4b4e43b63763504c278 | |
| parent | e9cce6e37e67c999f3ab54b299951cd42f7cc88f [diff] |
Take the git push out of the script ... Try in Jenkins
The website is built using JBake and a Groovy template. The builds for the website do require internet access.
JBAKE_HOME pointing to your JBake installation.export JBAKE_HOME=/home/jenkins/tools/jbake/jbake-2.6.3export JBAKE_HOME=/usr/local/Cellar/jbake/2.6.4You can fork from github https://github.com/apache/incubator and raise a pull request.
There is a custom bake.sh file that is used to build the website. You can call it with any of the arguments you would pass to jbake. The easiest way to use it is to run ./bake.sh -b -s. This will start up JBake in a watching mode as you make changes it will refresh after a short period of time.
While working with it locally, you'll notice that the site URLs redirect to incubator.apache.org; to change this edit jbake.properties and uncomment the line referencing localhost. Alternatively you can rename jbake-local.properties
If you want to run the full site build locally including the clutch analysis and any other other content remaining in SVN then you can use ./build_local.sh. Instead of publishing the site it finishes with JBake in watching mode.
Commits to the master branch are automatically checked out and built using build_site.sh.
The corresponding jenkins job can be found at https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20Site/
The result of the website build are pushed to the asf-site branch which are then published automatically using gitwcsub
Most of the pages in the site are written using Asciidoctor. While it is a form of asciidoc it does have some syntax differences that are worth reviewing
The site templates are written in groovy scripts. Even though the files end with .gsp they are not GSP files and do not have access to tag libraries. You can run custom code in them, similar to what is done in homepage.gsp and projectspage.gsp.