[sling-site] branch master updated: Mention Jenkins git-websites trick for publishing

[bd...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

bdelacretaz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 7284a9e  Mention Jenkins git-websites trick for publishing
7284a9e is described below

commit 7284a9e883c411a5957601481be37e54eada393e
Author: Bertrand Delacretaz <bd...@apache.org>
AuthorDate: Wed Jan 24 11:52:44 2018 +0100

    Mention Jenkins git-websites trick for publishing
---
 README.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/README.md b/README.md
index 88f13ff..218f220 100644
--- a/README.md
+++ b/README.md
@@ -20,6 +20,8 @@ Clone this repository and run the below commands or equivalent:
 
 The [ASF's gitpubsub mechanism](https://blogs.apache.org/infra/entry/git_based_websites_available) then synchronizes that content to [http://sling.apache.org](http://sling.apache.org), usually within a few seconds. More details about the publication process can be found in the [ASF Documentation about Project sites](https://www.apache.org/dev/project-site.html).
 
+We could automate this using a Jenkins job that's restricted to run on build nodes having the `git-websites` label, as done by [Apache PLC4X](http://plc4x.incubator.apache.org/developers/website.html).
+
 ## Variables in page content
 Adding `expandVariables=true` to a page's front matter enables simple variables replacement, see the `pageVariables` map in
 templates code for which variables are supported or to add more variables. A pattern like `${sling_tagline}` in page content

-- 
To stop receiving notification emails like this one, please contact
bdelacretaz@apache.org.