Commit Status Publisher Badly Broken in 2025.07 197242
Had to roll back our upgrade, the commit status publisher to Azure Devops was totally broken in the 2025.07 it was always coming up with errors. Don't really have any time to debug this, other than grab a few logs, as it's a breaking issue for us, as this is used as a pull request workflow, so everything stops if this breaks…
Log Snippets:
[2025-07-24 16:46:42,492] WARN - ains.buildServer.COMMIT_STATUS - Failed to publish status for the build #45512 {build id=190304, buildTypeId=BranchBuildsMainApplicationUiTfs} to tfs: Commit Status Publisher has failed to publish publishBuildStatus.buildFinished status: jetbrains.buildServer.commitPublisher.PublisherException: Azure DevOps publisher has failed to get parent commits in repository https://myserver/tfs/DefaultCollection/TPA/_git/printer-rome-MainApplication (enable debug to see stacktrace)
[2025-07-24 16:47:21,634] WARN - ains.buildServer.COMMIT_STATUS - Cannot determine if event "QUEUED" can be published for current revision state in VCS. : jetbrains.buildServer.commitPublisher.PublisherException: Commit Status Publisher HTTP request has failed (enable debug to see stacktrace)
[2025-07-24 16:47:21,761] INFO - ains.buildServer.COMMIT_STATUS - Publishing status to Azure DevOps: build id 190307, revision 3eded705915ac4656968448cd477a8798a03369b, event publishBuildStatus.buildStarted
[2025-07-24 16:47:21,947] WARN - ains.buildServer.COMMIT_STATUS - Failed to publish status for the build #45513 {build id=190307, buildTypeId=BranchBuildsMainApplicationUiTfs} to tfs: Commit Status Publisher has failed to publish publishBuildStatus.buildStarted status: jetbrains.buildServer.commitPublisher.PublisherException: Azure DevOps publisher has failed to get parent commits in repository https://myserver/tfs/DefaultCollection/TPA/_git/printer-rome-MainApplication (enable debug to see stacktrace)
[2025-07-24 16:54:40,756] INFO - ains.buildServer.COMMIT_STATUS - Publishing status to Azure DevOps: build id 190306, revision fc86ac49560486cc01536a359e8654810c7e6f6a, event publishBuildStatus.buildFinished
Please sign in to leave a comment.
Hi Mark,
Sorry for any inconvenience caused.
It seems that your issue is related to the following known issue: TW-94893: Commit status publishing to Azure DevOps fails after upgrade to 2025.07.
Our development team is already involved in this ticket. You can subscribe to the issue and add your comments directly on the YouTrack page to stay informed about progress.
However, I am unable to reproduce the issue on my side. Alternatively, you can help us investigate further by providing logs:
Go to Administration | Diagnostics in the TeamCity web UI.
1. Switch to the Troubleshooting tab and choose the logging preset: debug-commit-status.
2. Reproduce the issue.
3. Download and attach the following logs:
- teamcity-server.log
- teamcity-commit-status.log
Please upload them via: https://uploads.jetbrains.com/. Once uploaded, let us know the exact upload ID so we can retrieve them.
> Had to roll back our upgrade,
However, TeamCity does not support downgrading between major versions (i.e., changes in the first two version digits).
For details, refer to our documentation: Upgrading TeamCity Server and Agents
TeamCity server stores its data in the database and in TeamCity Data Directory on the file system. Different TeamCity versions use different data structure of the database and Data Directory. Upon starting a newer version of TeamCity, the data is kept in the old format until you confirm the upgrade and data conversion on the Maintenance page in the web UI. Until you do so, you can back up the old data; however, once the upgrade is complete, the data is converted to the new format.
Once the data is converted, downgrade to the previous TeamCity versions which uses different data format is not possible!
If you created a backup before upgrading, you may be able to restore TeamCity from that backup:
Restoring TeamCity Data from Backup.
Thanks for your understanding and cooperation.
Best Regards,
Tom
We run a VM, and the database is on the same VM. We shapshot the VM before upgrade, and in the event it fails, we can rollback everything to exactly the same as it was before upgrade.
As this caused us such a problem, and it was obvious very quickly it wasn't working, we didn't stay on this version very long before reverting. I managed to grab the logs, and that's it.
We are sorry for the inconvenience.
I am glad to know that you can rollback everything.
Please follow the TW-94893 (https://youtrack.jetbrains.com/issue/TW-94893/Commit-status-publishing-to-Azure-DevOps-fails-after-upgrade-to-2025.07) for any progress.
Thanks for your understanding and cooperation.
Best Regards,
Tom
We are seeing the same thing with BitBucket Cloud.
We apologize for the inconvenience.
As a temporary workaround, please specify the tokens directly in the feature settings instead of using secure parameters.
https://youtrack.jetbrains.com/issue/TW-94893/Commit-status-publisher-with-parameter-references-fails-after-upgrade-to-2025.07#focus=Comments-27-12434295.0-0
Thanks for your understanding
Best Regards,
Tom