Is it possible to do with drone? now each package is separate repo, for monorepo to work only other option I see now is git submodules, which is.. not really fun
can you explain "run recursively .drone files on single machine" ?
Maybe I just wrong with that I implementation idea. I want to support monorepos does not really matter how. I checked how semaphore doing it https://docs.semaphoreci.com/use-cases/building-monorepo-projects/#an-example-monorepo-project-setup. Maybe something similar can be done in drone?
there are a number of community extensions that can be used to extend Drone's functionality to better support monorepos
I recommend https://github.com/meltwater/drone-convert-pathschanged, which takes advantage of some newer features
(both are good, but the one from meltwater uses a v2 endpoint which is more efficient)
@bradrydzewski one more question. Can I use
drone exec with plugins, so I could test configuration locally?
How can I avoid this error?
Ah, fixed using $$TAG
Hi, I'm trying to get drone deployed and running with the latest kubernetes helm chart. Things seem to be running fine until a build is triggered. It get as far as the cloning step but it just hangs there. I've not followed the steps for installation of
drone-kube-runner as it seems to launch a drone-contoller as and when needed (guess the drone-kube-runner is an older method?). Anyone had similar problems?
The one in the official repo is outdated
The controller one has been experimental and have been replaced by the kube runner
That's the one I've used I think. It got updated yesterday (it was 2.5.0 when i installed it and i've updated to 2.5.1 this morning)
Chart
urk, my ex-colleague was disconnected from our github org, and now the github integration is broken :-|
drone-dd8658f9b-48z6t drone time="2020-01-17T14:54:32Z" level=error msg="error: sanity-io/custodian: cannot find .drone.yml in refs/heads/staging: GET https://api.github.com/repos/sanity-io/custodian/contents/.drone.yml?ref=25c1a847c5aba266c3ff88e930ba78220a173937: 401 Bad credentials []"
drone-dd8658f9b-48z6t drone time="2020-01-17T14:54:32Z" level=error msg="error: sanity-io/custodian: cannot find .drone.yml in refs/heads/staging: GET https://api.github.com/repos/sanity-io/custodian/contents/.drone.yml?ref=25c1a847c5aba266c3ff88e930ba78220a173937: 401 Bad credentials []"
Hi @jemaltieri , you should choose the runner based on workload and desired execution environment. We provide some high level overviews at https://docs.drone.io/installation/runners/
For example, if want Drone to execute pipelines directly on the host machine, with no containerization or isolation, choose the exec runner. If you want Drone to execute pipelines inside Docker containers, choose the docker runner. If you want Drone to ssh into existing machines and execute your pipeline as shell commands, choose the ssh runner. If you want to execute pipelines as kubernetes pods, inside a kubernetes environment, choose the kubernetes runner.
And
drone-agent is fully deprecated, correct?
I am sure there are third party tutorials out there somewhere, but we only document how to run Drone using
docker run since this is sort of the "lowest common denominator" across all systems. The docker run command should translate to docker-compose, kubernetes, rancher, ecs, etc since these runtimes are all container-based.
for example, here is a terraform project for running Drone on ECS. It uses the
drone/agent image but these are backward compatible so you should be able to swap with drone/drone-runner-docker https://github.com/appleboy/drone-terraform-in-aws/blob/master/ecs-drone-agent.tf
