I have now moved all scripts for the buildbot to https://github.com/fredowski/pspp-buildbot
Maybe it is even better to keep the scripts there because now all build scripting is in that place. The builds are controlled my master/master.cfg and the scripts in the ci folder. Fritz > Am 17.08.2020 um 18:14 schrieb Friedrich Beckmann <friedrich.beckm...@gmx.de>: > > I would like to avoid any kind of lock-in to some service that > > * will maybe be switched off at some day or > * it turns out that we cannot use it due to legal issues or > * may change their service rendering it unusable > > I agree with you that Travis achieves a high score in this respect. > Thats why I setup the buildbot at Hochschule Augsburg which is based > on buildbot released under GPL 2 (see: http://buildbot.net/about.html) > > The same scripts in the ci folder are used by the debian git builds on > buildbot > > * debian-sid-i386, debian-sid-amd64, debian-buster-amd64 > > and by the Ubuntu bionic build on travis > > * https://travis-ci.org/github/fredowski/pspp > > The file „.travis.yml“ is required for the Ubuntu build on Travis. > If the Ubuntu build would move to buildbot, then the .travis.yml file > could be removed. Then also the pspp repository on github can be removed. > So I reduced the travis specifics to this .travis.yml file - but even > that is not really true because buildbot offers an adaptor that can control > the build from a .travis.yml file: > > https://github.com/buildbot/buildbot_travis (MIT license) > > That is however currently not installed on the buildbot server. The MacOS > builds cannot move to the buildbot because these builds need apple hardware. > But the MacOS builds are currently controlled by other repositories. > > So from my perspective „code … which can only be run using travis“ is not the > code that I would like to merge :-) > > Fritz > >> Am 17.08.2020 um 16:21 schrieb John Darrington >> <j...@darrington.wattle.id.au>: >> >> I'm uneasy with code in the repo which can only be run using travis, >> because >> >> 1) It seems to be SaaSS >> 2) Its terms of use state: >> >> Travis CI offers the use of the Travis CI Software only to entrepreneurs >> within the meaning of section 14 (1) of the German Civil Code. >> >> and section 14(1) defines an entrepeneur to exclude hobbyists. >> (For the benefit of non-germans: >> https://www.gesetze-im-internet.de/englisch_bgb/englisch_bgb.html#p0053 ) >> >> It's effectively not free software if people cannot use it whilst >> exercising their hobby. >> >> J' >> >> On Mon, Aug 17, 2020 at 01:53:37PM +0200, Friedrich Beckmann wrote: >> I have worked on the continuous integration on github/travis and >> on the dedicated pspp build server with buildbot. Up to now I have >> kept the ci scripts in a dedicated branch on github but now >> I would like to merge this into savannah master. The change >> will introduce >> >> * a new directory ???ci??? which contains build scripts >> * a new file .travis.yml (script instructs) >> * a modification of the Makefile.am to ignore the ci >> files in the git-distribution check >> >> The changes are here: >> >> https://github.com/fredowski/pspp/compare/travis >> >> Do you mind the merge? >> >> The current builds are: >> >> a) from the current git >> >> on buildbot http://caeis.etech.fh-augsburg.de:8010/#/builders >> -> debian-sid-i386 >> -> debian-sid-amd64 >> -> debian-buster-amd64 >> on travis >> -> https://travis-ci.org/github/fredowski/osxbundler (MacOS) >> -> https://travis-ci.org/github/fredowski/pspp (Ubuntu bionic) >> >> b) from Bens nightly build distribution package or stable release >> >> on buildbot >> -> opensuse >> on travis >> -> https://travis-ci.org/github/fredowski/homebrew-pspp (MacOS) >> >> All linux builds and probably also a future windows cross build can >> be done on the buildbot server but the MacOS builds can only be >> done on travis. >> >> > >
