It would be nice to see support for seeing the result of the TeamCity build on the GitLab's Merge Request page. (For reference, plugin for TC & GitHub integration: https://github.com/jonnyzzz/TeamCity.GitHub)
Designs
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related or that one is blocking others.
Learn more.
I developed something like it, but using new concepts like: BuildId (from Teamcity Server) after a POST REQUEST on BuildQueue (using Teamcity Rest API).
I had to persist this ID on database (used properties field) and than loaded info on commit_status method, based on commit hash.
This way, every commit on source branch from a MR is re-builded and generated a new BuildId and I can see all the fail/success history for every commit hash.
What is necessary to push this to any gitlab-ce branch? Also I set my Teamcity config to use PROPERTIES and Gitlab fills them. So I hardcoded them (tests purpose) but I thought put them into MR properties page.
PS.: I develop this feature within teamcity_service.rb on branch 8-0-stable
First of all, thank you for raising an issue to help improve the GitLab product. We're sorry about this, but this particular issue has gone unnoticed for quite some time. To establish order in the GitLab-CE Issue Tracker, we must ensure that every issue is correctly labelled and triaged, to get the proper attention.
This issue will be closed, as it meets the following criteria:
No activity in the past 4 months
Unlabelled
Unassigned
It's not associated with a particular milestone
We'd like to ask you to help us out and determine whether this issue should be reopened.
If this issue is reporting a bug, please can you attempt to reproduce on the latest version of GitLab or GitLab.com, to help us to understand whether the bug still needs our attention.
If this issue is proposing a new feature, please can you verify whether the feature proposal is still relevant.