View more than 50 commits on the commit page

Question

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?

KellyW · Answer

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]

Julius Davies _GitBoost_com_ · Answer

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.

John Marciniak · Answer

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!