I use SourceTree exclusively with our corporate Stash servers; everything is served up in our intranet. Why does SourceTree now require me to have an Attlassian Account in order to use SourceTree with our internal-only servers?
Agreed. I run a developer environment for a University and automation is key for running a tight devops environment. This isn't just an Ops thing it's also impactful to our developers and not to mention possibly an issue for compliance by requiring students to give them protected information in order to use the service.
Regardless, until they drop this they will not get their product in the hands of future developers. Something to think about if you want to increase brand awareness.
I can see the benefit for those that are indepent devs that don't use a corporate SSO environment but that's not a huge portion of the market. At least create a standalone enterprise installer or add installer options that allow admins to integrate the app with their own cloud or on-prem solutions.
Our department is migrating from different legacy source control systems to Stash + JIRA, and we were hoping to use SourceTree for our devs. However, we're on a very restrictive network so we can't even see the login page, which makes it impossible to install without jumping through hoops.
New team members who weren't on before 2.0 will now be on-boarded with SmartGit instead and everyone else will switch as they change their PCs. I miss the nice ST commit graphs, and really don't understand the decision to force a logon at install time, especially for clients who are paying a lot for the rest of the Atlassian suite. Yes, we could make a re-jigged ST part of our default image. No, I don't want to have to do that when there are easier alternatives.
Maybe Atlassian steals a glance at github - and wants to push the usage of their Bitbucket cloud server. As github offers a a gitclient with tight integration to github.com, Atlassian targets to a similar combination of git-client (SourceTree) and git-server (Bitbucket cloud) as github does.
Atlassian is trying to move towards a one-account-across-all-services model. Obviously Stash isn't included in those services, but apparently they think the SourceTree registration should be. As far as I can tell, that's all they used the account for when I put in the information - they didn't try to immediately link up Bitbucket Cloud or anything like that.
I'd like to say coming into a new company and convincing the dev's to even look at JIRA and Stash/Bitbucket server, only to have the awkward "sign up" process for each and every team member for sourcetree has kind of screwed adoption of JIRA. Which sucks considering what that means for my projects and teams.
We have a new product released using SourceTree for the version control interface. I go out to create another repository for a new project and I am forced to sign up for an Atlassian account. Absurd, I'll go elsewhere, I do not like companies that play 'profit games'. It's like a 'bait and switch' sales tactic.
Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs