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
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 have a super project which has 4 sub modules. It is a known fact that using ssh + auth tokens for jenkins is a good practice rather than using https + password combo. As a result, I configured .gitmodules with ssh and configured jenkins/git repository with ssh public/private keys. Now, jenkins build environment is setup and it works clean.
But for users who are using SourceTree and rely on https login method, it no longer performs https authentication instead tries ssh and fails as public/private tokens weren't present on their system. I know there is a workaround to let users create tokens and avoid this failure.
But on the contrary, is it also possible for SourceTree to try https if ssh login fails? Since SourceTree is used by users and not by machines, giving more priority to HTTPS login makes sense right?