Managed by the Infrastructure Team, Testing Team and Wishlist Team, this is to have a daily test upgrade of most of our *.tiki.org sites. So anyone can check anytime how stable trunk (the next version) is with real world data. The name relates to our eat our own dogfood policy.
To check tomorrow's code (trunk) with yesterday's data, you can access the links below. Most of the year, these sites are running trunk, but during the release process, we run the upcoming version. Ex.: branches/9.x is used instead of trunk until dev.tiki.org moves from 8.x to 9.x
http://nextdev.tiki.org/ (updated 4 times per day)
http://nextdoc.tiki.org/ (updated 4 times per day)
http://nextinfo.tiki.org/ (updated 4 times per day)
http://nextthemes.tiki.org/ (updated 4 times per day)
http://nexttv.tiki.org/ (updated 4 times per day)
http://nextprofiles.tiki.org/ (updated 4 times per day)
http://next.tiki.org/ This is for tiki.org The cron job for next.tw.o is executed at noon and midnight my time (-6h to get NY time and -9h to get SF time)
- Dogfooding Tiki on our own sites is great to find bugs, but it makes it difficult to work.
- Say I find a bug on a tiki.org site, is it fixed in the next version, or should I report/try to fix bug?
- This is very time consuming.
- Detecting and fixing bugs is much less efficient without real data. We would like to give developers access to a site where they can test a fix, before committing (or very quickly after)
- The Quality Team is supposed to check that a commit works in trunk, before accepting in the stable branch. How to do this efficiently without data?
Which is why we have set up a continuous Pre-Dogfood Server. Yesterday's data with tomorrow's code (code in trunk). Ideally, this would be part of TRIM so everyone in the community could easily set this up for themselves, but it's not at this stage.
Setup system for permanent testing of trunk with real data
1- Run a new site ex.: nextdev.tiki.org
- On a server we can give trusted devs access to test
- With backup of real data from dev.tiki.org
- Using trunk
2- Daily update of code (from trunk)
3- Daily refresh of data (from live site)
- Use .htaccess password to make sure robots don't index the site
- Upgrade procedure is tested very frequently
- Makes it very easy to compare old & new interfaces (and people can say what they liked/want to keep about the old one)
- Make it easier for Tiki community to make a judgment on when to start dogfooding next version on community site.
- All devs: To test before an upgrade. Ex.: They could load test daily and report any feature or performance regressions.
Ideas to improve
- all pre-dogfood servers should indicate in how many hours is next data refresh
- To make *.tiki.org upgrades easier, to catch regressions sooner, dev.tiki.org could run on monthly updates of trunk code, while nextdev.tiki.org is daily trunk. Before each monthly upgrade, nextdev.tiki.org is checked to catch and fix regressions.
Change the domain name from trunk to next, because it's not always trunk, but always nextdone
- Tracker item: #4200 - - Compare generated HTML for all *.tiki.org sites between versions (to check for regressions/changes of behavior)
- Handle _htaccess
- Use unix file link from .htaccess to _htaccess
Clear all cacheNow part of the shell installer
- Apply a profile or a System Configuration
- To add a header "This is a test site, all modifications will be overriden"
- User_watches = n (Testing changes shouldn't spam people)
- A way to set robots to avoid indexing the site completely
- A way to receive alerts on major breaking
- SQL error, PHP error
- Would need a crawler for early detection of breakage
- To do the same thing, but for various profiles.
- Continuous Integration