Bitbucket Server build status API returning 500 for commits(worked earlier without any Jenkins chang

Question

Hi everyone, We are using the Bitbucket Server REST API to post build statuses to commits from our Jenkins pipelines: Endpoint: POST /rest/api/latest/projects/{projectKey}/repos/{repoSlug}/commits/{commitId}/builds This has been working fine earlier, but recently we started getting 500 Internal Server Error consistently, even though there were no changes on the Jenkins side. Verified: * Authentication (Bearer token) is valid * Request payload is correct (state, key, name, url) * Commit exists and is accessible via GET /commits API * Same issue occurs from Jenkins and manual API calls (PowerShell/Postman) Example: POST https:///rest/api/latest/projects/C/repos/code/commits//builds Body: state=INPROGRESS, key=TEST-123, name=TEST, url=https://test Response: 500 Internal Server Error with message: “An error occurred while processing the request” Additional notes: * Issue is more frequent on feature branch / new commits * Older commits sometimes still work * Retry attempts do not resolve the issue Questions: * Are there known conditions where Bitbucket cannot attach build status to certain commits (e.g., indexing delay or commit reachability)? * Has there been any recent change in this API behavior? * Which server logs should we check to diagnose this? Environment: Bitbucket Server (self-hosted), Jenkins pipelines.

Amulya Kota · Answer

Thanks, I checked the Bitbucket logs and found the following error around the same timestamps as the failed build status API calls:

com.microsoft.sqlserver.jdbc.SQLServerException: Could not allocate space for object 'dbo.AO_C77861_AUDIT_ENTITY'.'pk_AO_C77861_AUDIT_ENTITY_ID' in database 'bitbucket' because the 'PRIMARY' filegroup is full due to lack of storage space or database files reaching the maximum allowed size. Note that UNLIMITED files are still limited to 16TB. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

Other Bitbucket operations such as:

* commits
* pull request creation
* branch creation
* merges

are still working normally. The issue seems to affect only the build status API calls.

Aron Gombas _Midori_ · Answer

A 500 error on the build status API with no changes on the Jenkins side almost always points to something changing on the Bitbucket Server side.

As the very first thing to do, check the Bitbucket Server logs. The most important log is "BITBUCKET_HOME/log/atlassian-bitbucket.log". The 500 response you see is a generic internal server error, but the server log will contain the full stack trace with the actual root cause. Look for entries around the timestamps of your failed requests.