Hi
Since yesterday I’m experimenting the same problem with github.
Github webhooks return the same error:
We couldn’t deliver this payload: **timed out**
While drone returns:
{"commit":"dab3e88c6cfbd31e2c6dbd1fd52208c65db3da44","error":"No commit found for the ref dab3e88c6cfbd31e2c6dbd1fd52208c65db3da44","event":"tag","level":"warning","msg":"trigger: cannot find yaml","ref":"refs/tags/v1.0.1-10","repo":"myrepo","time":"2021-03-26T06:47:12Z"}
Screenshot of github webhooks page:
The first valid commit is the git push after tag update, next one (first which failed) is when I push the tag and the next ones are the manual redeliveries.
Here is the trigger section of my .drone.yml file
trigger:
event:
- tag
ref:
- refs/tags/*-*
I think it’s not a problem on github because if I redeliver the same webhook through github webhook page, I got the same error few hours later.
On locally cloned repo I can get the good commit id like drone said:
> git show-ref --tags | grep refs/tags/v1.0.1-10
dab3e88c6cfbd31e2c6dbd1fd52208c65db3da44 refs/tags/v1.0.1-10
When I checkout this commit id it works well and I can find the .drone.yml file.
> master git checkout dab3e88c6cfbd31e2c6dbd1fd52208c65db3da44
Note: switching to 'dab3e88c6cfbd31e2c6dbd1fd52208c65db3da44'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:
git switch -c <new-branch-name>
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
HEAD is now at a9b7d3e 1.0.1-10
> a9b7d3e la
total 624K
drwxr-xr-x 11 root root 4.0K Mar 15 12:29 dist
-rw-r--r-- 1 root root 366 Mar 15 12:26 Dockerfile
-rw-r--r-- 1 root root 2.0K Mar 26 08:48 .drone.yml
-rw-r--r-- 1 root root 1.7K Mar 15 12:26 env-sample
-rw-r--r-- 1 root root 462 Mar 15 12:26 .eslintrc.json
drwxr-xr-x 8 root root 4.0K Mar 26 08:48 .git
-rw-r--r-- 1 root root 55 Mar 15 12:26 .gitignore
-rw-r--r-- 1 root root 35K Mar 15 12:26 LICENSE
-rw-r--r-- 1 root root 60 Mar 15 12:26 .nestcli.json
-rw-r--r-- 1 root root 148 Mar 15 12:26 nodemon.json
-rw-r--r-- 1 root root 3.0K Mar 26 08:48 package.json
-rw-r--r-- 1 root root 486K Mar 26 08:48 package-lock.json
-rw-r--r-- 1 root root 51 Mar 15 12:26 .prettierrc
-rw-r--r-- 1 root root 177 Mar 15 12:26 README.md
drwxr-xr-x 11 root root 4.0K Mar 26 08:48 src
drwxr-xr-x 2 root root 4.0K Mar 15 12:26 test
-rw-r--r-- 1 root root 651 Mar 15 12:26 tsconfig.json
-rw-r--r-- 1 root root 1.3K Mar 15 12:26 webpack.config.js
It was the first time it appears while it was running well for 2 weeks now. Since yesterday all my repos have the same problem.
Can I execute more commands to check something ?
Thank you for your help