Integrate Drone CI about gitea

[tboerger]

@tboerger how would drone make CI faster ? doesn't travis also support docker ?
That said, I'm ok with using Drone either in addition to or instead of Travis.

Travis is always loaded and pretty slow, drone is not. Beside that is drone much more flexible.

[lunny]

At the beginning, we will use the public service of drone. I think. @tboerger

[makhov]

I know that @tboerger loves Drone and I guess it will be good idea to use it instead of Travis, but I'm sure that we should use public service.

[tboerger]

beta.drone.io will be opened to everybody soon, it's the only public instance of the up2date drone version. Here it's pretty good that we can use whichever plugin we want and in worst case we can simply launch our own instance.

[lunny]

So which work should we do?

[strk]

@tboerger how would drone make CI faster ? doesn't travis also support docker ?
That said, I'm ok with using Drone either in addition to or instead of Travis.

[tboerger]

@lunny the question is if we want to launch our own drone instance or if we should use mine or if we should ask @bradrydzewski for access to beta.drone.io

[strk]

@bradrydzewski access to beta.drone.io would be great. I guess actual speed would depend on availability of agents.

[xinity]

agree @makhov as we are an opensource project, why don't we use public service, i think that would help getting more people on board.
besides build speed is a real matter as the project grows we'll need more builds , more tests and thus more workers.

IMHO we should find a balance between growing needs and public service to attract more people on board.

[lunny]

Is this work now?

[lunny]

Or we can put it on v1.1

[tboerger]

This is a requirement for the build and test pipeline.

[lunny]

But we can use travis-ci on v1.0 if beta.drone.io is not ready.

[strk]

Looks like this is addressed by #96

[strk]

Should this be assigned to @metalmatze as he has an open PR addressing this ?

[tboerger]

Resolved via #96