{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 等我变得足够好 的问题《Show in GitLab TeamCity builds status》','https://www.manongdao.com/q-656524.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I've managed to configure TeamCity to automatically pull the new checked-in changes from GitLab and build it.
Next step I would like that the build status icon in GitLab reflects the build status from TeamCity.
At the moment each build TeamCity builds, GitLab continues to show "build:skipped". As I understand this is because it's not run with Gitlab CI and that my repo misses gitlab-ci.yml. I did setup the TeamCity CI service for the project but it didn't help with anything. Maybe I'm misunderstanding the purpose of this service.
Is there a way to change the default build tracker from GitLab-CI to TeamCity so that I can see the build status from TeamCity in GitLab as well?
With TeamCity 10 the Commit Status Publisher build feature is deployed with the default installation. Also GitLab is supported now out of the box. Enter the URL of your server and your private token and it will work like a charm.
To view your build status on GitLab, you need to setup a commit status publisher feature for your build configuration. The commit status publisher plugin is open source and located on GitHub
Currently, it does not have GitLab support out-of-the-box, but we have received a pull request that implements it. We have not yet merged it to the plugin, so you can either wait for the pr to be merged (watch the request in the tracker here), or you can build the plugin from the branch with the pr included and install it on your server.