Build triggers stopped working - bitbucket cloud

Drone Support
1

Setup:
Drone 0.8
Bitbucket Cloud

bitbucket hook state (user hook)

Name	Description	Last accessed	Actions
DroneIO_Dev		2017-10-17T16:23:31.837528+00:00	Revoke

So this was accessed yesterday when I built the server. Today I come in and push a build, and nothing happens.

There are 3 builds from yesterday, on 3 different pushes.

2 active steps in the pipeline, the second one has a branch filter [master, ci/*]. However the first step wasn’t polled.

I’m going to delete the OAuth key, and redeploy the drone server. These are the logs and config I pulled out before I try to fix this.

docker-compose:

cat /docker-compose.yml
version: ‘2’
services:
drone-server:
image: drone/drone:0.8
ports:
- 80:8000
- 9000:9000
volumes:
- /var/lib/drone:/var/lib/drone/
- /etc/drone/key.pem:/etc/drone/key.pem
restart: always
environment:
- DRONE_OPEN=true
- DRONE_HOST=${DRONE_HOST}
- DRONE_BITBUCKET=true
- DRONE_BITBUCKET_CLIENT=${DRONE_BITBUCKET_CLIENT}
- DRONE_BITBUCKET_SECRET=${DRONE_BITBUCKET_SECRET}
- DRONE_DATABASE_DRIVER=mysql
- DRONE_DATABASE_DATASOURCE=${DRONE_DATABASE_DATASOURCE}
- DRONE_SECRET=${DRONE_SECRET}

And I didn’t look at the logs before when it was working, but I see the hook calling github api’s. I’m hoping this is just a naming thing, where the bitbucket integration is leveraging github code…

docker logs

[GIN-debug] POST   /hook                     --> github.com/drone/drone/server.PostHook (12 handlers)
[GIN-debug] POST   /api/hook                 --> github.com/drone/drone/server.PostHook (12 handlers)
[GIN-debug] GET    /stream/events            --> github.com/drone/drone/server.EventStreamSSE (12 handlers)
[GIN-debug] GET    /stream/logs/:owner/:name/:build/:number --> github.com/drone/drone/server.LogStreamSSE (15 handlers)
[GIN-debug] GET    /api/info/queue           --> github.com/drone/drone/server.GetQueueInfo (13 handlers)

I don’t see a timestamp on the log entries…

2

Yes, these represent the Go package names, which by convention include the version control location in the path. I should point out that this code has been in place for a little over 2 years with minimal change, and is therefore considered quite stable and well tested in production.

These log entries show the registered endpoints (created when the application first starts). These logs do not show any traffic. Based on these logs, I would be left to assume that no traffic from bitbucket is reaching drone, otherwise you would see something in the logs like this:

time="2017-10-17T17:47:17Z" level=info latency=505.695µs method=POST path="/hook"

Lastly I can confirm Bitbucket hooks are working with 0.8

3

ok thanks.

The timestamp log is helpful. I’ll reconfigure and redeploy and look for that timestamp entry in the logs.

Thanks!