Commit status publisher Error

Answered

Publish status error in build #24 {build id=575, buildTypeId…details »


Publish status error in build #24 {build id=575, buildTypeId=****Digital_WebApp}: Cannot publish status to Bitbucket Cloud for VCS root RAC Digital Web: response code: 400, reason: BAD REQUEST, message: 'Bad request. Field 'url': Enter a valid URL.'

 

 

6 comments

How do I debug this feature I guess its not in the build log.

0

Hi Rob,

Commit Status publisher prints logs in teamcity-server.log file, please check it. What URL is used?

1

thanks I ended up just installing the new version of team city witch has this feature installed already and it worked :)

0

Thank you for the update! Glad that issue was resolved.

0

Using 2017.2.4 I never get status back to out enterprise github when PR is pulled.  In the logs I see the events...

 

 

[2018-10-17 08:55:46,479]   INFO - her.github.ChangeStatusUpdater - Scheduling GitHub status update for hash: 7b782e13f7005a0c79652a556b1358ed9ce5f9b4, branch: refs/heads/development, buildId: 6735, status: Pending 
[2018-10-17 08:55:46,707]   INFO - her.github.ChangeStatusUpdater - Updated GitHub status for hash: 7b782e13f7005a0c79652a556b1358ed9ce5f9b4, buildId: 6735, status: Pending 
[2018-10-17 08:56:25,094]   INFO -   jetbrains.buildServer.SERVER - Build finished received for build: #1.0.0-dev-71 {build id=6735, buildTypeId=Freight_AngularJS_Version5_PrBuilds_DocViewBuild} 
[2018-10-17 08:56:25,102]   INFO - ndexer.EventBasedBuildsIndexer - Indexing finishing build: #1.0.0-dev-71 {build id=6735, buildTypeId=Freight_AngularJS_Version5_PrBuilds_DocViewBuild} 
[2018-10-17 08:56:25,121]   INFO - de.impl.history.DBBuildHistory - Created build history entry; build id: 6735, finish date: 2018-10-17 08:56:25.079 
[2018-10-17 08:56:25,126]   INFO - her.github.ChangeStatusUpdater - Scheduling GitHub status update for hash: 7b782e13f7005a0c79652a556b1358ed9ce5f9b4, branch: refs/heads/development, buildId: 6735, status: Success 
[2018-10-17 08:56:25,128]   INFO - tbrains.buildServer.ACTIVITIES - Finished build Freight :: Angular :: Version 5+ :: PR Builds :: doc-view-build {id=Freight_AngularJS_Version5_PrBuilds_DocViewBuild, internal id=bt1528} #1.0.0-dev-71 {build id=6735, promotion id=6735, branch=refs/heads/bapfingsten-patch-1, history=false, agent="angular-node10-2" {id=69}, triggered by "'bapfingsten' (Pfingsten, Bob A) {id=10}" (##type='user' userId='10' origin='rest'). Started 2018-10-17 08:55:46.508, finished <null>. Status "NORMAL 'Running'"} 
[2018-10-17 08:56:25,340]   INFO - her.github.ChangeStatusUpdater - Updated GitHub status for hash: 7b782e13f7005a0c79652a556b1358ed9ce5f9b4, buildId: 6735, status: Success 

 

0

Hi Robert,

Would you mind to describe your configuration in more details please?
Here is what we are interested in:
- Have I got it right, that you are experiencing problems after merging PRs into their target branch? 
- What is the target branch in this example and where the pull request came from? (branch name in the same repo, or in forker repo?)
- Do you have a single VCS root attached to the configuration or a number of them?
- What is the default branch and branch specs of this (or these) VCS root(s)?
- It seems the build is triggered on the refs/heads/bapfingsten-patch-1 branch, while the status is published for refs/heads/development. In which branch does actually that change with SHA 7b782e... reside and for which branch the build is triggered?
- How have you triggered the build?
- What is the configuration of Commit Status Publisher?
- What version of Teamcity are you using?

Thanks, and excuse me for so many questions!

0

Please sign in to leave a comment.