You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jackrabbit.apache.org by sv...@apache.org on 2025/04/11 21:49:49 UTC

svn commit: r1925024 - /jackrabbit/site/live/jcr/continuous-integration.html

Author: svn-site-role
Date: Fri Apr 11 21:49:49 2025
New Revision: 1925024

URL: http://svn.apache.org/viewvc?rev=1925024&view=rev
Log:
@trivial: Site checkin for project Apache Jackrabbit Site-1.0-SNAPSHOT

Modified:
    jackrabbit/site/live/jcr/continuous-integration.html

Modified: jackrabbit/site/live/jcr/continuous-integration.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/jcr/continuous-integration.html?rev=1925024&r1=1925023&r2=1925024&view=diff
==============================================================================
--- jackrabbit/site/live/jcr/continuous-integration.html (original)
+++ jackrabbit/site/live/jcr/continuous-integration.html Fri Apr 11 21:49:49 2025
@@ -186,11 +186,12 @@
    limitations under the License.
 -->
 <h1>Continuous Integration</h1>
-<p>Apache Jackrabbit uses <a class="externalLink" href="https://www.jenkins.io/">Jenkins</a> for continuous integration builds.</p><section>
+<p>Apache Jackrabbit 2 uses <a class="externalLink" href="https://www.jenkins.io/">Jenkins</a> for continuous integration builds while
+Apache Jackrabbit Oak uses <a class="externalLink" href="https://github.com/features/actions">GitHub Actions</a>.</p><section>
 <h2><a name="Build_targets_and_schedule"></a>Build targets and schedule</h2>
-<p>See the <a class="externalLink" href="https://ci-builds.apache.org/job/Jackrabbit/">Jackrabbit page</a>
+<p>See the <a class="externalLink" href="https://ci-builds.apache.org/job/Jackrabbit/">Jenkins Jackrabbit page</a>
 on the Jenkins server for the list of configured Jackrabbit builds and
-their current status.</p>
+their current status. For Jackrabbit Oak, refer to the <a class="externalLink" href="https://github.com/apache/jackrabbit-oak/actions/workflows/build.yml">GitHub Actions page</a>.</p>
 <p>The builds are configured to daily check the Git repository for updates
 and to run builds whenever there are changes (in the relevant branches). Build and test errors are
 reported on the dev@ mailing list.</p></section>