I recently installed and configured drone and gitea, following the guide and installing docker runners.
Everything seems to work fine, except when drone tries to find the .drone.yml as it reports having no tasks despite a pipeline existing in the config.
When ^C is pressed it prints {"error":"context canceled","msg":"runner: cannot get queue item","os":"linux", ...} so I’m unsure if I configured something wrong.
Drone does not detect .drone.yml in gitea repository
can you provide more details as to why you think Drone cannot find a .drone.yml? If Drone cannot fetch the yaml it usually writes an error message to the logs, which I do not see in your post.
you might also consider describing this issue in terms of a) what behavior am I experiencing and b) what do I expect to happen and c) provide a full dump of your server logs and your configuration so that we have a more complete picture of what is going on.
but first, please see the following threads which may help you to resolve any issues:
There is no logged build or anything of the sort. When setting it to debug log mode, I only see
{"arch":"amd64","kernel":"","kind":"pipeline","level":"debug","msg":"manager: request queue item","os":"linux","time":"2019-10-19T14:02:56Z","type":"docker","variant":""}
{"arch":"amd64","kernel":"","kind":"pipeline","level":"debug","msg":"manager: request queue item","os":"linux","time":"2019-10-19T14:02:56Z","type":"docker","variant":""}
I did not see anything relating to webhooks or anything of the sort.
UPDATE: The runner gives the following errors:
2019/10/19 14:11:22 [DEBUG] POST https://drone.dilaton.martmists.com/rpc/v1/request
2019/10/19 14:11:22 [DEBUG] POST https://drone.dilaton.martmists.com/rpc/v1/request
2019/10/19 14:11:52 [DEBUG] POST https://drone.dilaton.martmists.com/rpc/v1/request (status: 524): retrying in 1s (30 left)
2019/10/19 14:11:52 [DEBUG] POST https://drone.dilaton.martmists.com/rpc/v1/request (status: 524): retrying in 1s (30 left)
2019/10/19 14:12:22 [ERR] POST https://drone.dilaton.martmists.com/rpc/v1/request request failed: Post https://drone.dilaton.martmists.com/rpc/v1/request: context deadline exceeded
{"arch":"amd64","level":"debug","machine":"Drone-Runner-Dilaton","msg":"runner: polling queue","os":"linux","time":"2019-10-19T14:12:22Z"}
2019/10/19 14:12:22 [DEBUG] POST https://drone.dilaton.martmists.com/rpc/v1/request
2019/10/19 14:12:22 [ERR] POST https://drone.dilaton.martmists.com/rpc/v1/request request failed: Post https://drone.dilaton.martmists.com/rpc/v1/request: context deadline exceeded
{"arch":"amd64","level":"debug","machine":"Drone-Runner-Dilaton","msg":"runner: polling queue","os":"linux","time":"2019-10-19T14:12:22Z"}
2019/10/19 14:12:22 [DEBUG] POST https://drone.dilaton.martmists.com/rpc/v1/request
2019/10/19 14:12:52 [DEBUG] POST https://drone.dilaton.martmists.com/rpc/v1/request (status: 524): retrying in 1s (30 left)
2019/10/19 14:12:52 [DEBUG] POST https://drone.dilaton.martmists.com/rpc/v1/request (status: 524): retrying in 1s (30 left)
2019/10/19 14:13:22 [ERR] POST https://drone.dilaton.martmists.com/rpc/v1/request request failed: Post https://drone.dilaton.martmists.com/rpc/v1/request: context deadline exceeded
{"arch":"amd64","level":"debug","machine":"Drone-Runner-Dilaton","msg":"runner: polling queue","os":"linux","time":"2019-10-19T14:13:22Z"}
2019/10/19 14:13:22 [ERR] POST https://drone.dilaton.martmists.com/rpc/v1/request request failed: Post https://drone.dilaton.martmists.com/rpc/v1/request: context deadline exceeded
2019/10/19 14:13:22 [DEBUG] POST https://drone.dilaton.martmists.com/rpc/v1/request
{"arch":"amd64","level":"debug","machine":"Drone-Runner-Dilaton","msg":"runner: polling queue","os":"linux","time":"2019-10-19T14:13:22Z"}
2019/10/19 14:13:22 [DEBUG] POST https://drone.dilaton.martmists.com/rpc/v1/request
This issue claims drone is failing to detect the Yaml file. The Yaml file is fetched by the server, not the runner. I therefore need to see the server logs, not the runner logs.
However, it is unclear to me why you think Drone is failing to detect the yaml. This issue does a poor job of describing the actual problem you are experiencing, which is making this difficult for us to help you.
The issue is that Drone is not outputting any errors by default, and there are no builds triggered on the drone server instance. The server logs consist only of
{"arch":"amd64","kernel":"","kind":"pipeline","level":"debug","msg":"manager: context canceled","os":"linux","time":"2019-10-19T14:28:52Z","type":"docker","variant":""}
{"arch":"amd64","kernel":"","kind":"pipeline","level":"debug","msg":"manager: request queue item","os":"linux","time":"2019-10-19T14:28:53Z","type":"docker","variant":""}
repeating indefinitely
the below threads discuss all known root causes for when no build is triggered:
Those posts both suggest that this would be a false positive, yet still no builds are triggered.
The config file (.drone.yml in project root) exists, and the Drone page states “Your Build List is Empty.”
This thread describes every possible root cause. You are still not providing me with very much information, or telling me which potential root causes in that thread you tested for and ruled out. For example:
Did your version control system trigger the webhook?
did you check gitea to see if the webhook exists?
does the webhook url match your Drone url?
did you verify gitea can access your Drone url (with curl, for example)?
Did Drone receive the webhook?
You have said that you see nothing in the server logs. The thread suggests that if you see nothing in the server logs, no webhook was received. This indicates a problem with webhook delivery. Did you check your gitea logs to see why no webhook delivery was sent?
All of this is discussed in Nothing happens when I push code, no builds, or builds stuck in pending
I have the same problem and i fix it
i use gogs
first click setting -> webhooks
maybe you use https but drone add webhook to http
my english is not very well
change webhook
This is discussed in Nothing happens when I push code, no builds, or builds stuck in pending. If the webhook is not using the correct scheme you need to ensure the server proto is correctly defined.
You did not configure the correct DRONE_SERVER_HOST or DRONE_SERVER_PROTO which caused Drone to set an incorrect webhook address.