13 Commits

Author	SHA1	Message	Date
Reece	23da810b19	Fixes bug ... JS formatting Updated README.md SS4 Compliance & Updated Tests Namespaced templates Update .travis.yml, .scrutinizer.yml Update composer.json	2017-06-05 09:41:56 -03:00
UndefinedOffset	5f9610046e	Changed travis config to test against 3.5 for PGSQL, SQLITE and MYSQL, and additionally MYSQL for 3.1	2017-04-13 10:19:52 -03:00
Ingo Schommer	372819a57a	Test against 3.3 core and PHP 5.6 (#93) ... * Removed builds for unsupported 3.0 release line * Added 3.3 release testing Note that we're trying to make this smarter going forward, just testing against `3@stable` (see https://github.com/silverstripe-labs/silverstripe-travis-support/issues/33) * Testing on PHP 5.6, reduced variations Testing every release line against every DB driver and every PHP version tends to increase the complexity of maintaining the builds (more chance of a false negative). It also strains the free resources provided by Travis CI	2016-05-16 21:22:10 -03:00
Ed Chipman	2f5cee4e36	Fixed query error causing crash on postgres (fixes #87)	2016-02-13 13:43:39 -04:00
Ed Chipman	1eb946a8a5	Fixed travis config	2016-02-06 17:36:00 -04:00
Ed Chipman	9863a71380	Attempt to fix travis ignore of 3.1 and 3.2 PGSQL failures	2016-02-06 17:21:58 -04:00
Ed Chipman	7bd56c578d	Allow PGSQL to fail for 3.1-3.2	2016-02-06 17:14:21 -04:00
UndefinedOffset	51302bb0aa	3.2 is no longer allowed to fail	2015-10-13 12:08:42 -03:00
Daniel Hensby	32cb8d67be	Move to new travis containerised infrastructure	2015-08-05 13:56:56 -03:00
Ed Chipman	fe9b45bd3b	Updated travis tests to check 3.2 but allow failures until 3.2 is stable #73	2015-07-22 19:49:23 -03:00
Ed Chipman	3f1f5dbdb4	Changed travis to not allow any failures	2014-05-03 17:07:22 -03:00
UndefinedOffset	399dc0ab89	Allow PGSQL and SQLLITE to fail on 3.1	2013-04-09 13:44:47 -03:00
UndefinedOffset	efdaed9899	Setup travis support	2013-04-09 12:09:06 -03:00