[Show/Hide Right Column]

Continuous Integration


Tiki releases every 6 months. However, the next release should ideally be "releasable at any time". Also, actual releases should be very easy (goal: 30 minutes for the technical part).

To get closer to these goals, we are working on setting up a community Continuous Integration server.

Wishlist for Tiki community

Pre-Dogfood Server

For humans to be able to see yesterday's data with tomorrow's code

Profiles demo server

  • Having a test server with main profiles applied regularly, for testing/demo.

Continuous build

For the daily pre-release zip file to be as close as possible to the final one

Continuous Testing Server

Machines testing code, according to a series of tests

  • Run all tests
    • Check PHP & Smarty Syntax, etc.
    • Check that all JavaScript can be safely minified with JSLint
    • Detect closing ?> tags from DevTips
  • Run the security tests regularly (monthly?) and report to Security Team about new potentially risky files
  • Ideas from How to improve the release process
  • etc

Please see Continuous Testing Server

Related links

Contributors to this page: Marc Laporte .
Page last modified on Wednesday 04 December, 2013 05:57:24 CET by Marc Laporte.

Spaces [toggle]

Search Wishes (subject only) [toggle]

Keywords [toggle]

The following is a list of keywords that should serve as hubs for navigation within the Tiki development and should correspond to documentation keywords.

Each feature in Tiki has a wiki page which regroups all the bugs, requests for enhancements, etc. It is somewhat a form of wiki-based project management. You can also express your interest in a feature by adding it to your profile. You can also try out the Dynamic filter.

TogetherButton [toggle]

Documentation: PluginTogether