From my limited experience, the bitbucket pipelines are extremely lacking compared to drone. They allow only a single build image, and don't allow service containers. For these reason if one were to describe bitbucket pipelines as a drone clone, it would have to be described as a really half assed drone clone , because without these features I'm not sure how it can be used for any real world builds.
but I digress ...
As a company, we have decided to go for Drone, but we still find many gaps in the product.
we would recommend discussing these gaps in the gitter room (you won't get good responses in these forums). In some cases you might find it is possible to use drone out-of-the-box by just changing your approach. But until we know the gaps, it is tough to say.
The best way we have thought of covering those gaps is contributing to Drone development
Contributions are welcome but should align with the project vision. For these reasons I recommend discussing changes in the gitter room prior to starting to code so that nobody's time is wasted.
We are mainly Java devs and will need to undergo some training on Go and its ecosystem
If your team has limited Go experience it might be best to sponsor feature requests. We are working to partner with consulting firm &yet for sponsored development work. They are experienced in Docker, Go, Node and they have contributed to Drone in the past.