Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

"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: https://github.com/PowerShell/PowerShell/issues/6305
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?

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

190 views 4 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you