AdamNowotny / BuildReactor

Developer notifications and dashboard (Google Chrome extension)
Other
137 stars 43 forks source link

Feature request: Add support for team city feature branches #57

Open blowsie opened 8 years ago

blowsie commented 8 years ago

Each team city configuration has a default branch, but it can also have feature branches.

An example of this (using git flow) looks something like this.

To my knowledge, Build reactor only shows activity for the default branch. What is the best way to display information for the dynamic feature branches? If it is not possible currently, is it possible to add such a feature into build reactor?

p.s. great extension, thanks!


TeamCity feature branches : https://confluence.jetbrains.com/display/TCD8/Working+with+Feature+Branches Go GD Feature branches: https://www.go.cd/2015/04/27/Feature-Branch-Support/

AdamNowotny commented 8 years ago

You can define what branch should be monitored (for TeamCity at least) in service configuration screenshot from 2016-10-22 19-18-24

blowsie commented 8 years ago

Thanks @AdamNowotny, whilst i did see this option, it really doesn't fit a dynamic use case, where feature and release branches are coming and going on a regular basis.

Teamcity Piaza does offer this functionality, but overall I think Build Reactor is a better tool right now. https://github.com/timomeinen/team-piazza

blowsie commented 8 years ago

Perhaps being able to specify a branch specification is one way to go

eg

refs/heads/develop
refs/heads/feature/*
bmja62 commented 7 years ago

I also have this problem and I think it is nice to use wildcards on branch filter. I use BuildReactor and I love that but this is the only thing that I need more.

brettswift commented 3 years ago

4 years later, I'm trying BuildReactor again, and was hoping this feature would be here. Just a +1 from me :)

AdamNowotny commented 3 years ago

I haven't used TeamCity in years so that's why no progress here. But PRs are welcome! The "branch" field would need to be changed to accept multiple specifications with wildcards. The logic to get latest builds is here https://github.com/AdamNowotny/BuildReactor/blob/master/src/services/teamcity/teamcity.js#L31, the request being sent to CI is here https://github.com/AdamNowotny/BuildReactor/blob/master/src/services/teamcity/teamcityRequests.js#L24.

brettswift commented 3 years ago

Appreciate all the info to get started.

I don't have time to work on this for a long while at least but would appreciate anyone that does. :)

On Thu., Jun. 24, 2021, 2:15 p.m. Adam Nowotny, @.***> wrote:

I haven't used TeamCity in years so that's why no progress here. But PRs are welcome! The "branch" field would need to be changed to accept multiple specifications with wildcards. The logic to get latest builds is here https://github.com/AdamNowotny/BuildReactor/blob/master/src/services/teamcity/teamcity.js#L31, the request being sent to CI is here https://github.com/AdamNowotny/BuildReactor/blob/master/src/services/teamcity/teamcityRequests.js#L24 .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/AdamNowotny/BuildReactor/issues/57#issuecomment-867922800, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFQYFJBUDYJCLKREF6SLCTTUOG53ANCNFSM4CTG6MDQ .