Drone

[yusf]

Drone is a Container-Native, Continuous Delivery Platform

https://drone.io/ | https://github.com/drone/drone

Would be interesting to combine it with Gitea enabling a pretty serious code lifecycle platform.

[murgero]

@yusf Ah so a system like Jenkins but can be over a distributed network? That sounds AMAZING. Sign me tf up!

[marcusquinn]

@yusf Does look good.

Looking at as an alternative to GitLab Runners.

Could be the perfect pairing for Gitea too. Dockerised:

• https://docs.drone.io/
• https://docs.drone.io/server/provider/gitea/
• https://docs.drone.io/runner/overview/
• http://plugins.drone.io/

[fbartels]

@marcusquinn I am using both Gitea and Drone on Cloudron. I have posted about it in https://forum.cloudron.io/topic/3350/offered-drone-ci-on-cloudron

[marcusquinn]

@fbartels Nice, only just discovered Drone from your post and that combo does look tasty, I'm having a crazy few weeks/year but it's certainly on my radar.

[fbartels]

I have meanwhile made the app public so anybody can now install it from my git repo. It can be found at https://github.com/fbartels/cloudron-drone-app

[A Former User]

I've updated the repo here to automate pulling down the latest version of Drone. Open to feedback, of course.

Repo: https://git.atridad.dev/atridad/cloudron-drone-ci

[A Former User]

@girish I can get around to some test for this one of these days. Do you think this is a good fit for the store? Of course, drone runners would need to be run elsewhere. I tried to package that out of curiosity but no dice so far. Best run on another VM anyways. But always good to have the CI server run on the same cloudron as a gitea instance.

[girish]

@atridad yes, that will be great. I think having runners separate is fine, that's how the GitLab CI is as well (we have runners in a separate VM). From what I remember, the app needed configuration on first run itself, is that still the case?

[A Former User]

@girish it does, yeah. I can change the default to something more sensible like git.domain.tld.

The post install can be found here: https://git.atridad.dev/atridad/cloudron-drone-ci/src/branch/master/POSTINSTALL.md

I can also put it on the cloudron Git to make it easier.

[fbartels]

@girish said in Drone:

I think having runners separate is fine

Separate does not have to mean off Cloudron however. One of the systems I am running my Drone runners is also the Cloudron system where I am running the app/dashboard. Simply not started as a Cloudron app, but through docker-compose (I have scripting for that in my Drone app). The Runner only cleans up containers it has created itself, so its safe to use in my opinion.

[A Former User]

@fbartels same here. It seems to be safe to run.

[girish]

@atridad said in Drone:

I can also put it on the cloudron Git to make it easier.

Yes, please. We can then move this package forward.

[A Former User]

@girish Oh could you give me access to make repos on there again? Username is atridad. I made a new account.

[girish]

@atridad Yes, of course. Done.

[A Former User]

@girish Thanks! Its here: https://git.cloudron.io/atridad/cloudron-drone-ci

[girish]

@atridad I got it going here - https://git.cloudron.io/cloudron/drone-app/ . It seems the .env file is missing in the git repo, you should have permissions to add it.

[A Former User]

@girish oh whoops, I’ll add that right away

[A Former User]

@girish I work with macOS and because I cant import into your gitlab I copied and pasted the files into a new repo I made. Unfortunately the .env file is considered a hidden file and didn't show up in finder...

Good catch. Its in there now.

[robi]

@atridad That's a preference you can set in finder to show all hidden files or use the CLI.