Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Bitbucket Pipeline breaks with long command

I have this bug in my pipeline that started yesterday when I added a second environment variable that changes the `docker build` command.

this command does not work (real values were replaced)

docker build -f mydir/Dockerfile -t my/corp/tag --build-arg VAR1=$VAR1 --build-arg VAR2=$VAR2 . 

With error `"docker build" requires exactly 1 argument.`

The build args list is dynamically generated. If I write the command as is and execute, the same error happens. It took me a while to find out that this works:

docker build -f mydir/Dockerfile -t my/corp/tag --build-arg VAR1=$VAR1 . 

At first I thought that the problem was the amount of arguments and that a special character was breaking the interpreter. 

Then it came to my mind that the LENGTH of the command was too long. With the two arguments, 278 characters.and with only one, it's 189. It breaks somewhere between 190 and 278 characters long.

Is that an known issue? Is there a workaround? Could someone help me please



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events