Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.1-2, 10.1.17-1
Description
I simplified and refactored the original suggestion from Daniel Black regarding a .travis.yml file that enables the usage of the continous integration service by Travis, which is free for open source projects and easily available to anybody who wants to developd and work with the MariaDB server sources.
This Travis-CI file is not intended to replace the buildbots currently used by MariaDB core developers, but rather to provide an extra facility for occasional contributors who don't have their own buildbot trees.
Currently Travis-CI has a 50 minute limit on the build duration, so the tests are limited to the 'main' suite. Parallel Travis-CI jobs would be a way around that restriction, but it wastes resources, so I am working with Travis-CI dev to figure out another more effective solution.
The Travis build also includes building the Debian packages, which will help spot packaging breakages early on.
The code in this PR branch passes the test. Log visible at https://travis-ci.org/MariaDB/server/builds/92879843
Yes, please look into the build log if you can fix the failure?
The point of Travis-CI is to spot regerssions and point out the exact commit (in any branch, anywhere) where the regression occured. That function is not fulfilled if the test is already broken. The page https://travis-ci.org/MariaDB/server should be all green when contributors start branching off the 10.2 branch to do their new feature/fix.
Checkout https://travis-ci.org/MariaDB/mariadb-connector-j how it is all green. (Good work diego dupin!)