svn commit: r1880188 - /jackrabbit/site/trunk/src/site/markdown/continuous-integration.md

[re...@apache.org]

Author: reschke
Date: Thu Jul 23 08:03:17 2020
New Revision: 1880188

URL: http://svn.apache.org/viewvc?rev=1880188&view=rev
Log:
update CI page

Modified:
    jackrabbit/site/trunk/src/site/markdown/continuous-integration.md

Modified: jackrabbit/site/trunk/src/site/markdown/continuous-integration.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/continuous-integration.md?rev=1880188&r1=1880187&r2=1880188&view=diff
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/continuous-integration.md (original)
+++ jackrabbit/site/trunk/src/site/markdown/continuous-integration.md Thu Jul 23 08:03:17 2020
@@ -17,21 +17,14 @@
 
 Continuous Integration
 ======================
-Apache Jackrabbit uses [Hudson](https://hudson.dev.java.net/)
-for continuous integration builds. The Jackrabbit builds are a part of the [Hudson zone|http://hudson.zones.apache.org/hudson/]
-in the Apache infrastructure. See the [Hudson wiki page](http://wiki.apache.org/general/Hudson)
-for more information about the Hudson installation at Apache. The wiki
-page also contains instructions on how to get an account if you're a member
-of the [Jackrabbit Team](jackrabbit-team.html)
-and want to modify the continuous integration settings.
-
+Apache Jackrabbit uses [Jenkins](https://www.jenkins.io/) for continuous integration builds.
 
 Build targets and schedule
 --------------------------
-See the [Jackrabbit page](http://hudson.zones.apache.org/hudson/view/Jackrabbit/)
-on the Hudson server for the list of configured Jackrabbit builds and
+See the [Jackrabbit page](https://ci-builds.apache.org/job/Jackrabbit/)
+on the Jenkins server for the list of configured Jackrabbit builds and
 their current status.
 
-The builds are configured to hourly check the Subversion server for updates
+The builds are configured to daily check the Subversion server for updates
 and to run builds whenever there are changes. Build and test errors are
 reported on the dev@ mailing list.