You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by an...@apache.org on 2020/07/28 20:26:23 UTC

[jena-site] branch master updated: Jenkins build job instructions

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

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


The following commit(s) were added to refs/heads/master by this push:
     new 814d469  Jenkins build job instructions
814d469 is described below

commit 814d46970888372e1a6733af351ea86e50b237c3
Author: Andy Seaborne <an...@apache.org>
AuthorDate: Tue Jul 28 21:25:52 2020 +0100

    Jenkins build job instructions
---
 README.md | 26 +++++++++++++++++++++++++-
 1 file changed, 25 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 4b4286d..8397067 100644
--- a/README.md
+++ b/README.md
@@ -44,7 +44,7 @@ work, execute `hugo server -D` to continuously generate and serve the website on
 
 ## Building and publishing the website
 
-The ASF Jenkins [Jena_Site job](https://builds.apache.org/job/Jena_Site/) is
+The ASF Jenkins [Jena_Site job](https://ci-builds.apache.org/job/Jena_Site/) is
 used for generating the website and committing the generated site to the
 `asf-site` branch.
 
@@ -53,3 +53,27 @@ the release process.
 
 [gitpubsub](https://www.apache.org/dev/gitpubsub.html) is used to publish the
 site, using the content from the `asf-site` and `javadoc` branches.
+
+## ASF Jenkins job
+
+The `Jenkinsfile` was contributed in https://github.com/apache/jena-site/pull/17
+(July 2020).
+
+Steps to do to setup the Jenkins job:
+
+* Create a new multibranch pipeline (e.g. 'Jena_Site').
+
+* Branch source -> git
+
+* Set the gitbox url -> `https://gitbox.apache.org/repos/asf/jena-site.git` and use
+the jenkins (master pub key) credentials.
+
+* In the 'Scan Multibranch Pipeline Triggers' check the 'Periodically if not
+otherwise run' checkbox and enter a sane value (e.g. 15 minutes). This is needed
+because webhooks are not delivered to ci-builds (yet - 2020-07-28).
+
+* Save the job and click the 'Scan Multibranch Pipeline Now' button to trigger an
+initial scan. A first run may also happen as the SCM polls.
+
+It is at this point that it gets the label `git-websites` so the first job may
+have run on the wrong node.