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
I'm currently using sourceTree in an offline environment, but the initial splashscreen requires connecting to the Atlassian webserver to start. Is there a way to bypass this and use the current license file I already have for sourceTree?
It is possible to install SourceTree 1.8.2 on an offline Windows environment. This can be done by first installing it on an online computer and registering there. Next, copy the folder %USERPROFILE%\AppData\Local\Atlassian (or a subset, perhaps only \SourceTree\sourcetree.license) over to the offline computer. Then SourceTree runs.
I have not yet verified that this solution is in line with the license agreement. Any idea?
Confirmed this on Windows 7 x64 with 18.104.22.168. The sourcetree.license file is no longer used. It appears to be a combination of the following:
Seems that this is a bug so anyone affected should report it as such.
I couldn't find out how to do this the first time round because it was hidden away on the support site. Here's a direct link to report a SourceTree bug: https://support.atlassian.com/servicedesk/customer/portal/1/create/4
Hey Everyone - Unfortunately, we don't support offline installations. That said, it is a one-time registration and once you authenticate with a valid Atlassian account, you'll be able to use SourceTree entirely offline. In February, we updated our Terms and Conditions to align with Atlassian's Customer Agreement. The registration requires everyone to acknowledge those new terms and also ensure that SourceTree is distributed in accordance with Export Control laws. Sorry for the inconvenience this change has caused.
Thank you for your support.
SourceTree Product Manager
Hi Rahul, this is very inconvenient and unacceptable for enterprises. How do you deploy/maintain sourcetree at atlassian? How do you force your users to use the latest sourcetree given the the amount of security advisories you send out for git and sourcetree?
I really think Atlassian should think about a way to enable unattended/silent installation for sourcetree, make it managable through sccm. You could validate, while silently installing, if there is a BitBucket Server instance on the local network or something. You are promoting this product and we are paying good money for BitBucket Server each year. We have over 1100 sourcetree installations in our company and they range from version 1.1 to 2.1.10. It's undoable and a great security risk. Please think about this and about your enterprise customers!
Same problem at my company, which recently adopted Atlassian in a big way. Enterprise customers are all going to have the same issue. The need for this is perplexing, and the explanation above doesn't scan. No one else does this.
Very recently there was an offline-installable version released, which I found by hunting through the boards. It worked great in our hardened server network, and it seemed that Atlassian was going to fix this once and for all. Now we're back to this same unnecessary problem with 2.3.5. Not impressed with the support so far.
So, basically the "answer" is to tell companies who are trying to protect their software is that they doing something wrong. As for the comment about "Export Control Laws", if companies are hiding their own software away from the outside world then it would be awfully hard to export a tool they are using for their software.
You are aware that Atlassian made some steps since this discussion and Sourcetree for Enterprises is available from the sourctreeapp.com website:
Though it still flaws at some points, it makes lives a lot easier for enterprises trying to manage their installed base ;)
@Rick van Twillert _TMC_ But that still doesn't allow you to install without having to register each time!
We are wanting to use it in an environment with mandatory profiles, so every time it gets launched you're having to essentially go through the registration process each time...It's nuts.
I have to agree with @Craig.
The "Enterprise Solution" forces every user to go through the final setup after installation (Registration/Login).
This is an unacceptable solution in mid-size or larger companies because it unnecessarily increases the support effort for the software (Keyword: Unattended Deployment).
I could share the information, how we handle this in our company at the moment (from a "technial view"), if you are interested?
I did a diff on the contents of %USERPROFILE%\AppData\Local\Atlassian from a clean installation before and after registering online.
%USERPROFILE%\AppData\Local\Atlassian\SourceTree\accounts.json is created.
%USERPROFILE%\AppData\Local\Atlassian\SourceTree.exe_Url_<hash>\22.214.171.124\Startup.Profile is modified.
%USERPROFILE%\AppData\Local\Atlassian\SourceTree.exe_Url_<hash>\126.96.36.199\user.config is modified.
After some cursory analysis, my guess is the registration is getting baked into one of the binary objects stored in user.config
Likewise. Updated to 1.8.2 today hoping the licensing system might have been simplified (educational environment, trying to get SourceTree to work well in my classroom, where computers re-image when rebooted). Appears that the opposite has happened, and our offline license file no longer works – getting splash screen / requirement to connect after updating from 1.6.
All help topics on corporate licensing I could find (e.g. https://confluence.atlassian.com/sourcetreekb/sourcetree-license-for-corporate-usage-388404078.html, https://confluence.atlassian.com/sourcetreekb/sourcetree-silent-installation-windows-732267345.html have the following message:
PAGE NO LONGER VALID WITH THE RELEASE OF SOURCETREE FOR MAC OSX 2.2 AND SOURCETREE FOR WINDOWS 1.8
Is there no longer a corporate license key option?