View more than 50 commits on the commit page Edited

I'm using Bitbucket Server and would like to view more than the 50 most recent commits on the specific branch I view when I go to the "Commits" page on a repository. 

I've done a little bit of research, and according to this article about the Bitbucket Server config properties the default for page.max.commits is actually 100. Weirdly enough, each repo on my Bitbucket instance (which has hundreds and hundreds of commits over the years) I can only see the 50 most recent commits.

I realize this can be done with git in the command line, but is there any way to show it in the Bitbucket GUI?

2 answers

This widget could not be displayed.

 

Scroll to the bottom of the page.  The page should then load the next 50 commits, and so on.

You may also like the "All Branches Graph" that the Bit-Booster - Rebase Squash Amend paid add-on makes available.  It loads 166 commits per page.  The page auto-scrolls as well (e.g., loads the next 166 commits if you scroll to the bottom).

Full disclosure: my company maintains Bit-Booster - Rebase Squash Amend.

Ah, so when I scroll to the bottom of the page nothing happens! I suppose I didn't realize that functionality existed.

I'll keep your plugin in mind, but I'm going to start investigating server logs and front-end browser exceptions to see why this AJAX call might be failing. Thanks!

In my experience things like this sometimes happen when you run a reverse-proxy in front of Bitbucket Server to achieve https (e.g., Apache 2), but without everything quite correctly configured.

In particular my "bitbucket.properties" required these lines:

server.secure=true
server.scheme=https
server.proxy-port=443
server.proxy-name=bitbucket.mycompany.com

 And my Bitbucket Settings (in the Bitbucket Web UI) required a baseUrl set to "https://bitbucket.mycompany.com".

What version of Bitbucket Server are you running?  These settings go in a different file if you're on 3.x or 4.x versions.  For 5.0 or newer, what I've posted here might help resolve this.

This widget could not be displayed.
Kelly Wong Atlassian Team Feb 11, 2018

Try increase page.max.index.results parameter in Bitbucket Server config properties -- bitbucket.properties file and restart Bitbucket server after the updates.

 
page.max.index.results -- Maximum number of commits which may be returned from the index when querying by an indexed attribute. For example, this limits the number of commits which may be returned when looking up commits against a Jira issue.

 

[Reference: Bitbucket Server config properties - https://confluence.atlassian.com/bitbucketserver/bitbucket-server-config-properties-776640155.html]

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Aug 10, 2018 in Bitbucket

What is your #1 piece of advice to new users getting started using Bitbucket?

Hello Community! My name is Claire Maynard, and I’m a Product Marketing Manager on the Bitbucket team. I’m interested in hearing what advice or tips you have for new users getting started on ...

282 views 15 2
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you