Avoiding multiple triggering after "git rebase"

Hello,

Currently, when someone does "git rebase", each rebased commit is considered as a separate one for some reason and causes lots of junk stuff in our TC build queue.

Is it possible to tell teamcity to treat "git rebase" commits as a one commit?

3 comments
Comment actions Permalink

Hello,

We still having this problem. It looks like, that TC groups builds by commiter (?), so that's why it creates long queue for the same branch. If I cancel all builds from the queue, exept last one, then last build contains changes by all commiters. Is it possible to set some setting in TC to do that automatically?

0
Comment actions Permalink

Andrew, do you use a per-checking VCS trigger option?


0
Comment actions Permalink

Dmitry,

I think that was the case. "Trigger a build on each check-in" and "Include several check-ins in a build if they are from the same committer" options were checked. I've unchecked them now.

Thank you!

0

Please sign in to leave a comment.