It's a little incontinent, but the setting to skip tests if the .travis.yml file is missing is off by default.
To enable this setting, if you have admin rights to the repos, Log into https://travis-ci.org using your github credentials. Go to https://travis-ci.org/profile/OCA and click on the wrench of a repo Enable the "Build only if .travis.yml is present" option As for the documentation, I started from http://docs.travis-ci.com/user/languages/python/ and built from there. For postgis which is system package, install it using apt-get in pre-isntall: http://docs.travis-ci.com/user/installing-dependencies/ geojson, being a python package, can be installed in the install section with pip -- Sandy ----- Mail original ----- De: "Nicolas Bessi" <[email protected]> À: "Joël Grand-Guillaume" <[email protected]> Cc: [email protected], "Guewen Baconnier" <[email protected]> Envoyé: Mercredi 25 Juin 2014 14:25:06 Objet: Re: [Openerp-community] OCA: transition from Launchpad to Github Hello Sandy, What would you think about changing travis setup for OCA repoitories during transition period in order not to be run if travis.yml is missing. This will prevent failed build mail to be sent. I would also really appreciate if you can give us again pointer to your travis setup documentation. I want to add required dependencies to be able to run test on geospatial-addons that have special requierment like postgis and geojson. Thanks for the job Regards Nicolas 2014-06-25 20:00 GMT+02:00 Joël Grand-Guillaume < [email protected] > : Hi Daniel, We though about using the LP synchro against github to periodically pull github branches. No need of special script here, so legacy deployments should be fine. Regards, Joël On Wed, Jun 25, 2014 at 4:48 PM, Daniel Reis < [email protected] > wrote: Can you 'git push' back to the bzr remote? Yes, git-remote-bzr supports that. Note that we shouldn't need that here. Stéphane Bidoul proposed a migration strategy on this thread, on 21/06/2014, based on git-bzr-ng. For short you: * Use "git bzr clone" from Launchpad, and then "git bzr import" to fetch other branches (6.1, 7.0, ...) * Afterwards you can both "git push" to git/github remotes and "git bzr push" to LP. The main advantage of his solution was that it makes easy to keep LP in sync with the changes made on GitHub. Even if we do all maintenance on GitHub, some people would like to be able to keep using LP for legacy deployments, and it's important for them to have a way to sync GitHub commit to the LP repos. But from your answer, probably "git-remote-bz" can also achieve that. DR ______________________________ _________________ Mailing list: https://launchpad.net/~ openerp-community Post to : openerp-community@lists. launchpad.net Unsubscribe : https://launchpad.net/~ openerp-community More help : https://help.launchpad.net/ ListHelp -- camp to camp INNOVATIVE SOLUTIONS BY OPEN SOURCE EXPERTS Joël Grand-Guillaume Division Manager Business Solutions +41 21 61 9 10 28 www.camptocamp.com _______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp -- Nicolas Bessi Senior ERP consultant Business Solution technical manager Camptocamp SA PSE A CH-1015 Lausanne http://openerp.camptocamp.com Direct: +41 21 619 10 26 Office: +41 21 619 10 10 _______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
