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

"Get-ChildItem env:" error in deployment script: duplicate key?

My organisation is migrating from Bamboo 6.0.1 to Bamboo 6.8.0 (don't ask why not 6.10). My task is to migrate the build- and deployment projects from the old to the new environment.

In the old environment, we have a powershell script that loops through the environment variables. In order to get the variables, it calls "Get-ChildItem env:". Works like a charm, so I copied the script to the new environment. Unfortunately the script ends up in an error:

Get-ChildItem : An item with the same key has already been added.

When I try to call "Get-ChildItem env:" in the powershell console, the command executes successfully.

The error leads me to this page:
which tells me that this error is caused by a duplicate key in the environment variables.

In the deployment output, Bamboo outputs "using extra environment variables:" but there are no duplicates in there.

My conclusion: Bamboo is somehow adding a duplicate (differently cased?) environment variable, which is causing me this problem.

I also looked through the release notes after Bamboo 6.8.0 to see if there is some fix relating environment variables, but nothing seems to point me in the right direction.

Does anyone recognise this behaviour? Any ideas on how to investigate further which key is duplicated and how to solve this or prevent this from happening?

1 answer

Hi @Berry de Groot 

Were you able to find any solution/workaround for this issue?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events