Integrate Drone CI #11

New Issue

GiteaMirror · 2025-11-02T03:03:25-06:00

GiteaMirror commented

2025-11-02 03:03:25 -06:00

Originally created by @tboerger on GitHub (Nov 3, 2016).

Originally assigned to: @metalmatze on GitHub.

To keep the CI system as fast as possible we should replace TravisCI with Drone CI, we can use my hosted version or we can also run our own Drone CI instance, however we prefer.

Originally created by @tboerger on GitHub (Nov 3, 2016). Originally assigned to: @metalmatze on GitHub. To keep the CI system as fast as possible we should replace TravisCI with Drone CI, we can use my hosted version or we can also run our own Drone CI instance, however we prefer.

GiteaMirror added the type/enhancement label 2025-11-02 03:03:25 -06:00

GiteaMirror closed this issue

2025-11-02 03:03:25 -06:00

GiteaMirror commented

2025-11-02 03:03:26 -06:00

@lunny commented on GitHub (Nov 3, 2016):

So which work should we do?

@lunny commented on GitHub (Nov 3, 2016): So which work should we do?

GiteaMirror commented

2025-11-02 03:03:26 -06:00

@strk commented on GitHub (Nov 3, 2016):

@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.

@strk commented on GitHub (Nov 3, 2016): @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.

GiteaMirror commented

2025-11-02 03:03:26 -06:00

@tboerger commented on GitHub (Nov 3, 2016):

@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

@tboerger commented on GitHub (Nov 3, 2016): @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

GiteaMirror commented

2025-11-02 03:03:27 -06:00

@tboerger commented on GitHub (Nov 3, 2016):

@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.

@tboerger commented on GitHub (Nov 3, 2016): > @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.

GiteaMirror commented

2025-11-02 03:03:27 -06:00

@lunny commented on GitHub (Nov 4, 2016):

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

@lunny commented on GitHub (Nov 4, 2016): At the beginning, we will use the public service of drone. I think. @tboerger

GiteaMirror commented

2025-11-02 03:03:27 -06:00

@strk commented on GitHub (Nov 4, 2016):

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

@strk commented on GitHub (Nov 4, 2016): @bradrydzewski access to beta.drone.io would be great. I guess actual speed would depend on availability of agents.

GiteaMirror commented

2025-11-02 03:03:27 -06:00

@makhov commented on GitHub (Nov 6, 2016):

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.

@makhov commented on GitHub (Nov 6, 2016): 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.

GiteaMirror commented

2025-11-02 03:03:27 -06:00

@xinity commented on GitHub (Nov 6, 2016):

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.

@xinity commented on GitHub (Nov 6, 2016): 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.

GiteaMirror commented

2025-11-02 03:03:28 -06:00

@tboerger commented on GitHub (Nov 7, 2016):

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.

@tboerger commented on GitHub (Nov 7, 2016): 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.

GiteaMirror commented

2025-11-02 03:03:28 -06:00

@lunny commented on GitHub (Nov 9, 2016):

Is this work now?

@lunny commented on GitHub (Nov 9, 2016): Is this work now?

GiteaMirror commented

2025-11-02 03:03:28 -06:00

@lunny commented on GitHub (Nov 9, 2016):

Or we can put it on v1.1

@lunny commented on GitHub (Nov 9, 2016): Or we can put it on v1.1

GiteaMirror commented

2025-11-02 03:03:28 -06:00