Use Docker images as build environments

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?

1 comment

  • 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'.

  • 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.

Comment

Log in or Sign up to comment
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 ...

261 views 3 8
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