Getting Started

1. When does Awesome Graphs index repository data?

After Awesome Graphs is installed on Bitbucket Server it starts indexing all repositories associated with it right away. Commit data is indexed in batches to decrease the load on the machine memory.

2. Does Awesome Graphs use the throttling approach to indexing data?

Yes. Indexing repositories is a resource-intensive process. With adaptive throttling, Bitbucket examines the total physical memory on the machine and determines a maximum ticket number that the machine can safely support. This approach improves the system performance during indexing.

3. Where does Awesome Graphs store indexed data?

The indexed data is stored in the Bitbucket Server database. Storing persistent data helps to avoid reindexing each time the app is reinstalled or updated.

4. Are commits from forks included in graphs?

Commits from fork repositories are shown in People, Contributions in a user profile and project graphs and reports. Only unique commits are counted. If the same commit exists both in a fork and an original repository, it is counted only once.


Performance

1. I have an instance of Bitbucket Server with a lot of heavily branched repositories. Shall I install Awesome Graphs on it right away?

For large Bitbucket Server instances, it's highly recommended to try Awesome Graphs on a staging environment first. If it runs smoothly, install it on a production instance. If you run into problems, contact us.

2. How will the size of my database grow after installing Awesome Graphs?

The amount of space Awesome Graphs tables and their indexes consume in the database depends on the number of commits and pull requests in all repositories. See this page to estimate the growth of your database size.

3. Awesome Graphs is indexing data and completely loads one CPU core. Is it normal?

Yes. On large Bitbucket Server instances, Awesome Graphs can load one core completely. We recommend installing it on a server with at least a dual-core CPU for better performance.

4. It takes too long to index my repositories. What is the problem?

On large Bitbucket Server instances, Awesome Graphs may need some time to index all data. In this case, we recommend running Awesome Graphs on a staging environment first.

Delays in indexing may also happen when a repository is corrupted and Awesome Graphs waits until the repository indexing timeout is over. For Bitbucket Server and Bitbucket Data Center, the timeout is 16 hours.

5. We are experiencing Bitbucket Server performance issues after installing Awesome Graphs. Why?

  • Awesome Graphs 4.0 and above. Issues with a lack of RAM are not expected in Awesome Graphs 4.0 or above. However, on large Bitbucket Server instances, Awesome Graphs can load one CPU core completely. Learn more about this. If you experience performance issues after installing the app, contact us.
  • Awesome Graphs 3.8.3 and below. Most likely you don't have enough RAM to index all data in your repositories. This can happen on large Bitbucket Server instances (with over 400 000 commits). Please, add more RAM for your JVM, we recommend installing at least 1.5 GB of RAM for a stable performance. If this doesn't help, please, contact us. Also, see It takes too long to index my repository. What is the problem?

Licensing

1. Does Awesome Graphs support Bitbucket Data Center?

Yes, if you're using the paid version of Awesome Graphs 2.1.0 or higher.

2. My Bitbucket Server instance is used under a Community/OpenSource/Classroom license. Can I get Awesome Graphs for free?

Yes, in this case, you can request a free Community/OpenSource/Classroom license for Awesome Graphs directly from Atlassian. To do that, please, follow this link.

Your free Awesome Graphs license is valid only if your organization is approved by Atlassian for a Community/OpenSource/Classroom license type. To learn more about Atlassian Community, OpenSource, Classroom licenses, see this page.

3. What happens when my commercial license expires?

Commercial licenses are perpetual, meaning the product will continue to operate the same way as it does before and after the maintenance period expires. When your software maintenance expires, you will no longer be able to receive technical support or software updates. 


Other Questions

1. How can I merge two users with different emails who in fact are one person?

You can use .mailmap file in the repository to do this. Please, note this affects only commits made after the mailmap file was added. Changing a global .mailmap file in Git won't help (see details here). Also, please see the documentation for e-mail management in Awesome Graphs.

2. What time zone is used for displaying statistics?

Awesome Graphs uses user timezones set in Bitbucket Server. If a user doesn't set their individual timezone in their account settings, their timezone is defined by the default time zone set for all users. Learn more about timezones

3. Are merge commits counted in the Contributors and Contributions graphs?

No. Only regular commits and pull requests are taken into account.

4. Why there's no link to Contributions from the Contributors graph?

The Contributors graph displays a link to Contribution only if a contributor is a Bitbucket Server user and:

  • either their email is the same as in the Git settings,
  • or their Git username is the same as their Bitbucket Server display name.

See How can I merge two users with different emails who in fact are one person? to learn how to merge different user names and emails for one person.

5. How to view Contributions of disabled users when using Crowd?

The Contributions page in the user profile is available only if a user exists in Bitbucket Server. When disabling Bitbucket Server users in Crowd by making them inactive, they disappear from the list of users in Bitbucket Server.

As a workaround, you can leave a user active in Crowd and not disable that user, but delete that user's the Bitbucket User permission by removing that user from the group that defines Bitbucket Users. Refer to Removing Users from a Group to learn how to do that. This user will be considered unlicensed and will not count towards your Bitbucket Server license limit.

6. Do you have VPAT?

VPAT® - Voluntary Product Accessibility Template is a document describing a product's conformance with accessibility standards. You can see VPAT for Awesome Graphs for Bitbucket Server here.

7. Do you have ECCN?

Awesome Graphs for Bitbucket Server does not have an ECCN - Export Control Classification NumberIt is not a dual-use software and is not specially designed for the production of dual-use technologies. It should not be licensed according to the Commerce Control List (CCL).

8. What should I do if I'm having problems with Awesome Graphs?

Contact us providing as much information about your problem as possible.