Drone
-
@yusf Does look good.
Looking at as an alternative to GitLab Runners.
Could be the perfect pairing for Gitea too. Dockerised:
-
@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
-
I've updated the repo here to automate pulling down the latest version of Drone. Open to feedback, of course.
-
@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.
-
@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?
-
@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.
-
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.
-
@girish Thanks! Its here: https://git.cloudron.io/atridad/cloudron-drone-ci
-
@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.
-
@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.
-
@atridad That's a preference you can set in finder to show all hidden files or use the CLI.