nightly2.sakaiproject.org

Available instances

Status Instance Description Logs Properties
Sakai 12 primary QA test servers
Sakai 12.5

Sakai 12.5 is the latest 12 maintenance release.

Data retention is managed manually for this QA server.

12 QA Tomcat logs 12 QA sakai.properties
Sakai 12 Jira testing (hosted by Marist)

Sakai 12 is the next community supported release of Sakai. This QA server is the main QA instance for verifying Jiras after they have been merged into the 12 branch. This server keeps up with the latest fixes daily. Please note that Jiras which are not yet merged into the 12 branch need to be verified on one of the Trunk/Master servers before the branch manager will merge it back to 12.

Data retention is managed manually for this QA server.

Marist server Tomcat logs Marist server sakai.properties
20.x (Master) Test Instance(s) - Primary servers for QA testing fixed Jiras
Trunk (master) on MySql

Trunk/Master should NOT be used for production installations.

Often used to verify improvements (bugs and features) which have been resolved but not tested. Contains the latest available patches for Sakai, and is constantly changing (i.e. new patches for bug fixes and features every day).

Issues with the 11/12 status field (in Jira) set to Merge will be merged into the 11/12 branch. Merging into the 11/12 branch is a manual process and not real time.

This server and the trunk/master on Oracle are exactly the same, including property settings, except for which database it uses.

mysql master Tomcat logs mysql master sakai.properties
Trunk (master) on Oracle

Trunk/Master should NOT be used for production installations.

Often used to verify improvements (bugs and features) which have been resolved but not tested. Contains the latest available patches for Sakai, and is constantly changing (i.e. new patches for bug fixes and features every day).

Issues with the 11 status field (in Jira) set to Merge will be merged into the 11 branch. Merging into the 11 branch is a manual process and not real time.

This server and the trunk/master on MySQL are exactly the same, including property settings, except for which database it uses.

oracle master Tomcat logs oracle master sakai.properties
Experimental Trunk (master) on MySql

Experimental is the same as trunk/master for Oracle and for MySQL. It uses different properties for QA testing purposes, and sometimes additional Contrib modules or features which are turned off by default.

Experimental build includes the Evaluations Contrib tool.

Please see the properties file.

experimental Tomcat logs experimental sakai.properties
19.x Test Instance(s)
19.x Maintenance Branch on MySql

Contains the latest available patches for Sakai 19 that have been added since the tagged community release.

This branch is currently still unreleased.

The 19 branch is actively supported.

This server and the 19.x Maintenance Branch on Oracle are exactly the same, including property settings, except for which database it uses.

mysql 19.x Tomcat logs mysql 19.x sakai.properties
19.x Maintenance Branch on Oracle

Contains the latest available patches for Sakai 19 that have been added since the tagged community release.

This branch is currently still unreleased.

The 19 branch is actively supported.

This server and the 19.x Maintenance Branch on Oracle are exactly the same, including property settings, except for which database it uses.

oracle 19.x Tomcat logs oracle 19.x sakai.properties
12.x Test Instance(s)
12.x Maintenance Branch on MySql

Contains the latest available patches for Sakai 12 that have been added since the tagged community release.

This branch is currently still unreleased.

The 12 branch is actively supported.

This server and the 12.x Maintenance Branch on Oracle are exactly the same, including property settings, except for which database it uses.

mysql 12.x Tomcat logs mysql 12.x sakai.properties
12.x Maintenance Branch on Oracle

Contains the latest available patches for Sakai 12 that have been added since the tagged community release.

This branch is currently still unreleased.

The 12 branch is actively supported.

This server and the 12.x Maintenance Branch on Oracle are exactly the same, including property settings, except for which database it uses.

oracle 12.x Tomcat logs oracle 12.x sakai.properties
11.x Test Instance(s)
11.x Maintenance Branch on MySql

Contains the latest available patches for Sakai 11 that have been added since the tagged community release.

The latest community release is 11.4, therefore this branch contains fixes that have been applied post-11.4. These improvements will be in 11.5 when it is released (TBD).

The 11 branch is actively supported.

This server and the 11.x Maintenance Branch on Oracle are exactly the same, including property settings, except for which database it uses.

mysql 11.x Tomcat logs mysql 11.x sakai.properties
10.x Test Instance(s)
10.x Maintenance Branch on MySql

Contains the latest available patches for Sakai 10 that have been added since the tagged community release.

The latest community release is 10.7, therefore this branch contains fixes that have been applied post-10.7 .

Sakai 10 will no longer be supported the relase of Sakai 12, anticipated before end of 2017.

Only blocker priority and security patches are considered for the 10.x branch.

10.x Tomcat logs 10.x sakai.properties
Latest Community supported release
Sakai 11.4 on MySql

Sakai 11.4 is the latest community supported release of Sakai.

Data retention is managed manually for this QA server.

11 QA Tomcat logs 11 QA sakai.properties
Other servers
Mail Catcher

Mail Catcher catches all the email notifications sent from a Sakai qa server so that we can safely test email features without worrying about actual emails being sent, or the inconvenience of checking the log file (catalina.out) for messages.

  Jenkins
(Commit access to github project required)
  Sakai API Javadocs

Login information

You can either create an account on each server (which for most will be cleared out nightly) or use the sample users. Sakai's SampleUserDirectoryProvider is also used on every server creates sample users for testing external providers and course rosters.

All passwords are sakai (lowercase)

Additionally any user that starts with "test" can login with the same password as the username no account needed. For example: test123 (password test123) There may exist other accounts for other testing purposes (like datest/datest for testing delegated access)

Restart Schedule:

Notes:


Problems? Contact sakai-core on Google Groups or on Slack at Apereo Slack in #sakaidevs.