I don’t know if this is related to this ticket Payload URL generation of webhooks ignores DRONE_HOST
But that hasn’t been updated in a while.
When I go to bitbucket there is a link to the actual build instance.
IE: should be:
http://<dns_name>/<account>/<repository_name>/85
But what I get is:
https://bitbucket.org/ip-172-17-130-168.domain.ad/<account>/<repo_name>/86
docker-compose.yml file:
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}
DRONE_HOST is part of the problem - as I’m setting it to the ec2 (ip-172-17-130-168.domain.ad).
However it’s also injecting bitbucket.org.
I know Bitbucket Cloud may not fully support this feature, but it seems as if I were to change DRONE_HOST I’d still have an issue.