Jeff Thomas Atlassian Team

I linked to the Windows instructions, sorry! Try these - https://confluence.atlassian.com/pages/viewpage.action?pageId=270827678

Heather: Since you generated a new ssh key, you'll need to remove your old key from the Bitbucket and add the new one that you just created. These instructions should help.

Our Proxying and securing Stash guide has more information for what changes need to be made. I've provided a sample server.xml that should accomplish this. You'll be adding the secure, scheme, proxyName, and proxyPort parameters. <Connector port="7990" protocol="HTTP/1.1" connectionTimeout="20000"…

Could you turn on debug logging, restart Stash, and then attach your atlassian-stash.log file? I'll see if I can see anything in there that might narrow down the issue. You can turn on debug loggin in the admin menu under Logging and Profiling. The atlassian-stash.log file is located in <Stash installation>/log

Have you tried restarting Stash after turning on SSH?

I believe you're correct, you shouldn't need to setup keys if they repository is public. EDIT: Thanks to John for pointing out that SSH doesn't work for a public repository without keys.

It seems like your public key has not been added to Stash or is not configured properly on your local machine. Check out the documentation at https://confluence.atlassian.com/display/STASH/Using+SSH+keys+to+secure+Git+operationsfor how to setup keys for Stash.

Which version of Git LFS are you using? git lfs version If you're not running the latest, I would suggest trying an upgrade first. One person in https://github.com/github/git-lfs/issues/911 mentioned they did the following which resolved the issue: git config credential.helper managergit lfs pull

I wanted to do this for my stuff, so I whipped up a quick (and dirty) Python script to get these stats. All of my repositories are under by username, so it was easy to find all the commits. If you let me know how yours are setup, I can probably modify the script. It runs slow, but I'll work on improving it. Let me know if…

You're not alone in SourceTree being slow, I've seen posts by other users with similar issues and there are some open issues in the SourceTree JIRA talking about performance. I've experienced it a couple times myself, but restarting SourceTree always seems to fix it.

Hi Charles, Have you checked out the Troubleshooting Performance Problems in SourceTree documentation? There is a checklist of items to verify that could be causing SourceTree to perform slowly. * If you have a lot of untracked files, make sure the filters in SourceTree don't show these as Git/Hg take a long time to…

For Bitbucket Server, it will need to be set up and hosted on your own servers. You can find the getting start guide at https://confluence.atlassian.com/display/BitbucketServer/Getting+started

Hi, This is another one where you've found the Bitbucket Server documentation. Bitbucket Cloud does not currently support the branching model that Bitbucket Server does. Bitbucket Server and Bitbucket Cloud have similar features, but there are differences. When looking for documentation, be sure to note that it…

There are REST API endpoints to manage SSH keys which you should be able to incorporate in your scripts. The documentation is at https://developer.atlassian.com/static/rest/bitbucket-server/4.10.1/bitbucket-ssh-rest.html#idp31840 For example, a POST to /rest/ssh/1.0/keys can be used to add an SSH key to a user.

During the 4th step of installing Fisheye, you setup an admin password. When you go to http://fisheye.company.com/admin/you'll be prompted to enter that admin password. Once you're in there, you can grant the administrator priviledge to a user.

I don't believe there is an administrator account, only a password to access the admin section of Fisheye. After you've logged in to the admin section, you can create users with admin privileges.

@Philip Steinebrunner there is an open feature request for this being tracked at https://jira.atlassian.com/browse/BSERV-4020, feel free to Watch and/or vote for that issue to show your support and stay updated when any progress is made.

If you're wanting to update the username and/or password for the hosted repositories: * Open the Hosted Repositories window by clicking View > Show Hosted Repositories or Command + Shift + H. * Click Edit Accounts * Double-click on the account to update * Make the necessary changes

FishEye stores the dates as the number of milliseconds since January 1, 1970. This query should convert the milliseconds to a date: select to_char(to_date('1970-01-01 00','yyyy-mm-dd hh24') +(cru_create_date)/1000/60/60/24 , 'YYYY-MM-DD HH12:MI:SS am')from cru_review;

To add to Mirko's answer, FishEye and Crucible are two different applications that come bundled together. The features of either FishEye or Crucible are unlocked by the licenses that are used.

In your case, you only had one instance of Stash installed then.

If you had more than one server running Stash. In your case, you just one one server, and will like just have one installation of Stash. I don't think you need to worry about multiple instances.

Hey Sue, Multiple instances in this case would refer to having more than one installation of Stash. You could have Stash installed in different directories and running on separate ports on the same machine or having more than one machine with Stash installed. You'll know if you're running multiple instances if you have two…

Hi Alexander, Could he possibly have some custom window and text coloring? Start > Control Panel > Search for "color" > select Change window color and metrics Below is a screenshot of what mine looks like.

That means the system variable isn't set properly or that you need to refresh your current shell to pick up on the variable. Try opening a new shell and see if the echo command works. If it does not, verify that you've followed the steps for setting up the variable. If you're logged in as the user that will be running…

Could you verify that your system variable is setup correctly by running "echo $FISHEYE_INST" in the terminal?

It sounds like you're pretty much there with the install and data folders. All of my configuration is in my data folder in the config.xml file, which does not get removed during updates and preserves any configuration changes. The Fisheye installation files get extracted to the install folder. You should just need to setup…

Is this a Git or Mercurial repository? If you clone a random repository from GitHub, is the data repeating there as well?

Hi Owen, Yes, the installer will work to perform the upgrade with just the command line. The Bitbucket Server upgrade guide documentation provides a bit more detail (included instructions for how to use console in Linux installations.

I suspect that you may be running into the issue described in detail at Cannot retrieve link and provider entity when creating Application Link. This is caused by changes in the newer version of Tomcat being used by Bitbucket Server and a bug in older versions of JIRA and Bamboo. Give the workaround in the link above a try…