Possible solution for bitbucket pipeline docker-run limitation Edited

My integration tests are highly dependent of a elastic search, given that to build my integration tests on bitbucket pipeline I would have to execute the docker-run command to be able to spin up my elastic-search instance during my integration tests.

But as probably some of you know, there's a limitation on the bitbucket pipeline

See the Docker command line reference for information on how to use these commands. Other commands, such as docker run, are currently forbidden for security reasons on our shared build infrastructure.

So given that I don't know how can I spin-up my escluster with all configurations that I need inside, painless scripts, mappings, ports exposed to be available for my integrations tests.

Does someone have any idea how could i achieve this?

1 answer

Actually the limitation is only on docker run --privileged and on volumes sources.

BTW is possible to use docker run with -p and -e and -v so you can setup you enviroment like docker-compose and then do testing :)

We actually use in that way to setup a complete nginx+php+node enviroment and test nginx upstream configuration with curl

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

251 views 3 7
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you