Drone

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

[A Former User]

@robi ahhh I'll check that out. I was being lazy tbh and didn't just use the command-line.

[fbartels]

@atridad said in Drone:

I cant import into your gitlab I copied and pasted the files into a new repo I made

the next time you could also add an additional remote to your local repo and then push to this new remote. This has also the upside of preserving history.

[girish]

@atridad thanks!

Trying to understand how this app works. If I configure this for gitea, then it will use the gitea provider to sign in - https://docs.drone.io/server/provider/gitea/ ?

If that's the case, what is https://docs.drone.io/server/user/registration/ ? Or is the OAuth stuff separate from the users?

[A Former User]

@girish The OAuth is seperate I believe. So far I haven't been able to see an issue with open registration. But yeah it uses gitea as a login provider.

[A Former User]

@fbartels Good point. I'll do that next time.

[fbartels]

@girish my drone app has some install instructions and further usage in its readme (including the gitea setup). you can find them at https://github.com/fbartels/cloudron-drone-app#installation.

[msbt]

@atridad I had to add RUN chmod +x /app/code/start.sh to your Dockerfile in order to install it properly, it was throwing a 400 error.

Is there any chance to add the runners/agents as cloudron apps as well? I was just playing around with the exec runner and couldn't get it to work, but I would think it could be the same as the cloudron-build-service, no?

[fbartels]

@msbt you don't really need an app for that, you can just run the docker runner on your cloudron host. I am using https://github.com/fbartels/cloudron-drone-app/blob/master/runner/docker-compose.yml along with a .env file with my server specific values.