Drone

[msbt]

@girish oh nice, it seems the woodpecker agents come with single binary files, this could make it easier to set up, right?

[girish]

@msbt yes, quite nice that it has release binaries which IIRC drone didn't have.

[fbartels]

@msbt said in Drone:

this could make it easier to set up, right?

In the end drone and woodpecker are meant to run workloads in containers. So it does not make much difference if the agent comes as a binary or a container that is configured to interact with the docker socket.

[msbt]

@fbartels ah good point, thanks for the clarification! Do you think we can get it to work with the docker addon we have?

[fbartels]

@msbt yes, I would imagine that one could wrap the agent into a Cloudron app, but I honestly do not see that much of a value to it.

Reasons:

• the agent does not have a webinterface by default (but one can be enabled with https://docs.drone.io/runner/docker/configuration/reference/drone-ui-disable/)
• the agent does not store anything, so needs no backups
• needs manual configuration for address of drone server and shared secret anyways

I just have a small docker-compose.yml on any system that I want to act as a runner (my laptop, desktop, ..., even on my cloudron instance).

[msbt]

@fbartels I get most of the reasons and I'm using it the same way you suggested, but I once crashed one of my Cloudrons because I installed a wrong docker-compose thing to launch the runners, which either updated or removed Docker, thus killing Cloudron. It was a quick fix to reinstall Docker, but would be nice to have the runners as an app so people don't have to tinker and install things outside the Cloudron ecosystem.

Would be also easier to migrate and such, or launch/start additional runners on different Cloudrons with one click if more are needed without sshing into each box.

[marcusquinn]

@girish Any plans to add this to the App Store?

[marcusquinn]

This is working very well for us, paired with Gitea. Highly recommend making this an official app store install.

[msbt]

@marcusquinn same here, but the Drone runners are still not part of the equation, would be nice if they could work together with the docker addon to have it 100% "portable"

[girish]

@marcusquinn Which package are you using ? Or are you running this outside Cloudron ?

[vladimir.d]

@girish said in Drone:

@marcusquinn Which package are you using ? Or are you running this outside Cloudron ?

We are running Docker runner and SSH runner as docker containers and Exec runner as a service on the Cloudron host, basically exactly as described in the Drone documentation.
https://docs.drone.io/runner/overview/

@msbt said in Drone:

@marcusquinn same here, but the Drone runners are still not part of the equation, would be nice if they could work together with the docker addon to have it 100% "portable"

Maybe we'll package runners as cloudron apps later that could build & deploy an app on Cloudron.

[girish]

@vladimir-d I meant the drone server. How are you running it - https://docs.drone.io/server/overview/ ? Is it a Cloudron package or something else?

[msbt]

@girish our own @fbartels already created a nice package: https://github.com/fbartels/cloudron-drone-app which require a few manual steps, but is still good to go.

Back then I used a mashup of this one and the one atridad (?) created (which is no longer online it seems).

[girish]

Ah, I didn't realize @fbartels opened it up for all.

[vladimir.d]

@girish we are using drone app packaged by @fbartels.

[girish]

We published Woodpecker now, which is a fork of Drone. If needed, we can also publish a Drone package later.

[fbartels]

Drone is transitioning away from a simple CI runner to a full platform incl. git repository hosting.

https://github.com/harness/gitness#what-is-gitness-and-where-is-drone

Seems a risky move with so many well established other market players (free and paid).

Edit: they just had their first beta release.

[robi]

With vendor and pipeline agnosticism this will be useful to many.

Might even be a good idea for the Cloudron team to consider using it internally since it supports so many languages well and builds faster.