thanks to antoine, Gem is now using travis-ci for automated test-builds whenever something is pushed to the (github) repository.
https://travis-ci.org/umlaeute/Gem/
todo - enable OSX-builds (antoine, how did you do that?) - upload the built binaries to some webserver (e.g. github) - fix the build-matrix to avoid unnecessary builds
caveats - currently only linux (and osx, see todo) are supported by travis-ci - "linux" is some rather outdated ubuntu (12.04, amd64 only)
fnsdr IOhannes
On 12/02/2014 08:29 PM, IOhannes m zmölnig wrote:
thanks to antoine, Gem is now using travis-ci for automated test-builds whenever something is pushed to the (github) repository.
i forgot: travis-ci also integrates with coverity[1], a static source-code analyser. every now and then² the builds will be sent to coverity to automatically check for bugs. reports will go to the gem-cvs³ mailinglist.
mgfdsr IOhannes
¹ https://scan.coverity.com/projects/1832 ² that is: whenever the `coverity_scan` branch is synched to master manually ³ https://lists.sourceforge.net/lists/listinfo/pd-gem-cvs
thanks you Iohannes for putting everything together and make it work
to enable os x build, i just sent an email to support@travis-ci.com and ask them to enable OS X build for my Gem repo.
and concerning the build upload, I think the easiest is to upload on Github. but one upload per commit would be too much. So I think we can push an automatic Github release every time a tag is set. Travis can do that very kindly (and thanks to Iohannes this is already set).
But daily build could be interesting too. I think we can upload at most one build per day. FTP upload is very easy to setup in Travis, much more than ssh or something else that needs a key identification, but yes more unsecure.
Cheers
Antoine
-- do it yourself http://antoine.villeret.free.fr
2014-12-02 20:29 GMT+01:00 IOhannes m zmölnig zmoelnig@iem.at:
thanks to antoine, Gem is now using travis-ci for automated test-builds whenever something is pushed to the (github) repository.
https://travis-ci.org/umlaeute/Gem/
todo
- enable OSX-builds (antoine, how did you do that?)
- upload the built binaries to some webserver (e.g. github)
- fix the build-matrix to avoid unnecessary builds
caveats
- currently only linux (and osx, see todo) are supported by travis-ci
- "linux" is some rather outdated ubuntu (12.04, amd64 only)
fnsdr IOhannes
GEM-dev mailing list GEM-dev@lists.iem.at http://lists.puredata.info/listinfo/gem-dev
On 12/03/2014 08:38 AM, Antoine Villeret wrote:
thanks you Iohannes for putting everything together and make it work
to enable os x build, i just sent an email to support@travis-ci.com and ask them to enable OS X build for my Gem repo.
thanks. that indeed did the trick. i was slightly confused by their blog-page that a) told me to do this b) told me that i can no longer do this :-(
and concerning the build upload, I think the easiest is to upload on Github. but one upload per commit would be too much. So I think we can push an automatic Github release every time a tag is set. Travis can do that very kindly.
yes. but as it works only for "tagged" (aka "released") versions, it's less useful.
But daily build could be interesting too. I think we can upload at most one build per day. FTP upload is very easy to setup in Travis, much more than ssh or something else that needs a key identification, but yes more unsecure.
probably just upload something like: Gem-travis-osx-20141203.tgz for each build (so multiple builds per day will only keep the last one).
it's a pity we cannot do this via github...
fgarsd IOhannes
-
Antoine Villeret -
IOhannes m zmölnig