Use Docker images as build environments

[Douglas Lovell]

This article about using a Docker image for your build leaves several open questions:

• Where and how best do you populate the secret username and password?
• Where will pipelines expand the source in the image?
• What will be the current directory and user?
• How does pipelines invoke the image, with what parameters?
• How does pipelines get results of the build?

[Douglas Lovell]

• Where will pipelines expand the source in the image?

It expands into ${BITBUCKET_CLONE_DIR}, which is also the current directory from which the build commands run.

I don't think the answers to the last two questions likely matter much.

[Douglas Lovell]

• Where and how best do you populate the secret username and password?  

This is sort of answered.  There's a suggestion to look at an environment variables article "for more information."  There's more than more information there.  It tells you exactly how to use the pipeline setup to securely set username and password.

• What will be the current directory and user?

The same article answers the first half of this question, indirectly.  The predefined environment variables are listed there.  One of them tells the directory that will be current.  The user will be 'root'.