You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I had troubles setting up a git repository against Gitlab.
The connection test failed with "Cannot decode connection params" while a test checkout provided the following error in the stack trace:
at java.lang.Thread.run(Thread.java:748) Caused by: java.io.IOException: unrecognised object: OPENSSH PRIVATE KEY
I found out that i needed to convert my key file to an older format that contains "BEGIN RSA PRIVATE KEY" instead of the "BEGIN OPENSSH PRIVATE KEY" my key file originally contained.
Since the original key file was created as per Gitlab instruction, and worked in many other scenarios (including a local shell git test with the bamboo user), I wonder if my setup is broken somehow? Please note that I use the official Bamboo docker container.
Hi!
as workaround you can mount the authentication parameters into docker container :)
https://community.atlassian.com/t5/Bamboo-questions/Bamboo-Git-authentication-fails/qaq-p/329703
Hence you key will work
Cheers,
Gonchik Tsymzhitov
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.