Travics CI

[Norman0406]

Please provide additional information about TRAVIS CI and how it can be used in this project.

Some questions:

• How do we manage the Travis build process? Is it connected to an individual GitHub profile or can we create a Travis account for LISA, that both of us can access?
• Is it possible to perform additional build events like running python scripts etc., e.g. to create installer packages? How can we configure this?
• When running a build, can Travis automatically increase the build number?

[semaph0r]

https://travis-ci.org/getting_started

And ref 0806aa9

[Norman0406]

Travis CI cannot be used for building on windows. A CI solution that can be used for all builds would be preferable. Investigate alternatives like

• CircleCI
• Jenkins

We could setup a build server on our own (maybe using a RaspberryPi 2?).

[semaph0r]

Nope, raspberry pi does not have enough power. I will provide an Jenkins installation on my root server soon

Am 16. Juni 2015 09:32:20 MESZ, schrieb Norman Link notifications@github.com:

Travis CI cannot be used for building on windows. A CI solution that
can be used for all builds would be preferable. Investigate
alternatives like

• CircleCI
• Jenkins
  Maybe we could setup a build server on our own (maybe using a
  RaspberryPi 2?).

---

Reply to this email directly or view it on GitHub:
#33 (comment)

Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

[Norman0406]

The new RaspberryPi version with a quadcore processor is quite fast compared to previous versions, and parallel builds would be supported. It would be a cheap alternative and it doesn't matter if nightly builds take 2 hours to complete.
I'm still looking for a good application for this thing ;)

[Norman0406]

I guess multi-platform builds must each be done on the platform that it will build for, right? So we need Jenkins to run on a a VM for every supported platform.

[semaph0r]

Shit, I hope you are wrong. Don't know how to deal with multiple plattforms

[Norman0406]

Jenkins can be extended with a VirtualBox plugin. I think this is the way to go:

• Master: Linux system (e.g. Ubuntu) with Jenkins will build Linux versions
• Slave: Windows VM will build for Windows
  • running on the Master
  • configured as a Jenkins slave
• Slave: Mac Mini will build for OS-X
  • configured as a Jenkins slave

We can ignore Mac builds for now. Later we would need a cheap Mac Mini from Ebay.