Drone

[fbartels]

@msbt the webinterface on the runners is only for debugging as far as I know. So they do not really need to be reachable from the public internet. The only important thing is that the runners can reach the "dashboard" to get job information.

I have runners deployed on a few machines, even had it running on my laptop.

And one of the Drone jobs indeed builds a hugo blog and then deploys it via surfer.

[msbt]

@fbartels thanks, it does work indeed, I even used your cloudron-surfer image to deploy a demo Hugo to a surfer instance.

Although I would still find it a lot more practical if the runner was an actual part of cloudron, so we go full circle and have all the benefits, like when you migrate everything on a new machine

[A Former User]

@msbt True. The best part about runners though is that they need barely any config and don't need to store much at all. It is very scalable. As for my image, I do need to fix that. I've been slammed with projects and life lately but I'm trying to get to everything I've said I would do lol

[robi]

@atridad If you detail out some steps of what needs doing, perhaps someone can chip in at the repo you specify.

Many hands make short work.

[fbartels]

@robi from my perspective that is all already part of https://github.com/fbartels/cloudron-drone-app/. Atridad just decided that he wanted to do his own app.

[robi]

@fbartels ah, thanks for the clarification!

[A Former User]

@robi Just added that. Thing about this repo is hopefully making it more viable as an official app. One thing that I think would help is support for required environment variables when installing specific apps. Similar to how the ports are defined. That would let us specify the gitea URL and the OAuth info.

[robi]

@atridad said in Drone:

@robi ... One thing that I think would help is support for required environment variables when installing specific apps. Similar to how the ports are defined. That would let us specify the gitea URL and the OAuth info.

Sounds like a good feature request.

[A Former User]

@robi Submitted.

[A Former User]

@atridad Replying to your post in my feature request here to keep it in the drone thread. It might be able to make the runner work too?????
https://docs.cloudron.io/packaging/addons/#docker

[msbt]

@atridad uh nice catch, that would be awesome!

[girish]

Is anyone aware of the licensing changes to Drone? There are some notes here - https://laszlo.cloud/drone-community-edition-what-is-included

There is a fork of drone now called woodpecker ci. I opened a request for that here https://forum.cloudron.io/topic/7186/woodpecker-ci . From https://woodpecker-ci.org/faq#why-is-woodpecker-a-fork-of-drone-version-08, "The Drone CI license was changed after the 0.8 release from Apache 2 to a proprietary license. Woodpecker is based on this latest freely available version."

[fbartels]

@girish yes, I've been following the woodpecker project also already for a while. it seems quite active. On the other hand I have not noticed any limitations in my usage of Drone so far. Also the "agent less single node" limitation is something I cannot confirm, multiple runners here without any problems.

[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?