Build Status does not reflect on Bitbucket for the MASTER Branch
Hi ,
I am trying to trigger a build whenever Pull Request is created against the Development or Master branch.
I have created a Pull Request Build Feature and this works as expected.
Also I have a created another Build Feature - Commit Status Publisher . This helps me view the status of the build in Bitbucket..
This works when i create Pull Request from
- A feature branch to Development
- A feature branch to Master
In both the above cases , the build gets triggered in TeamCity and i am able to view the Status on Bitbucket.
However , when i create a Pull Request from - Development to Master , the build triggers in TeamCity ,but the status does not reflect in Bitbucket.
I am not sure why it works for a feature branch and not for the Development branch
Any help would be much appreciated.
Thanks
Please sign in to leave a comment.
Hello!
Apologies for the delayed response; could I ask you to enable debug-general logging preset (see the instruction on how to do that here: https://www.jetbrains.com/help/teamcity/teamcity-server-logs.html#Changing+Logging+Configuration) next time you would process a PR from development to master branch, and then send over teamcity-server.log.* files from your <TeamCity Server>/logs folder via our upload resource: https://uploads.jetbrains.com? I will check if we do the call to BitBucket in the first place, and if there are any communication errors for these PRs.
debug-general preset will significantly increase the verbosity so I suggest to rollback to default preset once you have the data captured.
Hi ,
Thanks for your reply.
I have enabled the logging preset and uploaded the Logs
Upload id: 2020_09_07_YbuQTQDWeeUTDWqR (file: Logs.txt)
Please let me know if you would need any other information.
Thanks
Hello!
Unfortunately, logs do not specify any attempts to publish build status except for four times when the attempt failed, with ProductAzureApiProd_BuildProductApiPr configuration (due to the fact the changes were not collected in the first place). It appears that the logging preset was not enabled (in fact, there are no lines at all with the DEBUG level) - could you please make sure it is enabled while development - > master PR is being processed?