[
https://issues.apache.org/jira/browse/METAMODEL-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326631#comment-15326631
]
Dennis Du Krøger commented on METAMODEL-1096:
---------------------------------------------
In the case of Sakila, it seems so simple that there's not really a reason to
remove it unless the download location isn't stable, something like this should
do the trick:
{noformat}
before_script:
- curl -O http://downloads.mysql.com/docs/sakila-db.tar.gz && tar -xzf
sakila-db.tar.gz
- mysql -u root < sakila-db/sakila-schema.sql
- mysql -u root < sakila-db/sakila-data.sql
{noformat}
(No guarantees for correctness :))
That might of course not be the case for other example databases used.
> Add some databases to Travis, so integration tests can run
> ----------------------------------------------------------
>
> Key: METAMODEL-1096
> URL: https://issues.apache.org/jira/browse/METAMODEL-1096
> Project: Apache MetaModel
> Issue Type: Bug
> Reporter: Dennis Du Krøger
> Priority: Minor
>
> It seems like our integration tests are bitrotting a little, which is not
> only a problems in itself, but also proves that they are _never run_, which
> is pretty bad.
> It would be wonderful if we could get Travis to start at least a few database
> servers, so we at least can run those.
> There's a few here: https://docs.travis-ci.com/user/database-setup/
> Only problem is getting the required test databases imported. I looked a bit
> at the Sakila database we use for the MySQL integration tests, and that
> should just be a quick curl download, uncompression and import. I guess it's
> probably the same for the others.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
