Investigate and fix Consent behat test break

[phavekes]

This issue is imported from pivotal - Originaly created at Sep 23, 2019 by Michiel Kodde

In #166206956 a couple of Consent tests where marked as WIP. They where marked that way because they started breaking on Travis, but not on local test builds. The problem was not debugged as this would be rather time consuming. We want to have more control over the builds and shoud investigate how we can make our CI more robust. 

• Would a docker image of EB Deploy be a good alternative?
• What would it cost to maintain that?
• What other test features would be opened up with that?
• Can we keep using our current Travis setup, but make it more robust, and less prone to break?

[phavekes]

Personally I would create at first only the test setup in docker. Travis has docker support so it won\'t be hard to get it working. When we have this container we could then decide if it could work for OC-deploy and we could decide if additional changes are needed. Also the PO could then decide if the setup deliveres what is expected and has a base container to possibly use in OC-Deploy. I think it would be a too big step to implement it directly in OC-deploy as a lot of additional services should be configured in order to let the whole stack work.

We have the added benefit that we:

• could debug the CI tests locally whit the same state which currently is very hard
• could move our codebase for example to gitlab if we want to (not that we have to)
• could automate a release build
• loose the dependency on possible broken base images in Travis
• need less time to maintain the tests because we have full control and can reproduce the same state

https://docs.travis-ci.com/user/docker/ (bstrooband - Sep 25, 2019)