-
Notifications
You must be signed in to change notification settings - Fork 652
Make sure that we're not evaluating excluded branches #680
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make sure that we're not evaluating excluded branches #680
Conversation
In #673 I noticed that
This my first attempt to address this performance bottleneck and all feedback is welcome. |
Did you see my comment on the cause in the other thread? Sent from my Windows Phone From: Örjan Sjöholmmailto:[email protected] In #673#673 I noticed that track-merge-target must be set to track develop is develop is merged into master but then, getting the base configuration got really slow on the build server e.g. feature[/-]: [20:31:40][Step 1/1] INFO [10/08/15 20:30:56:35] Project root is: D:\BuildAgent\work\607b08944775ee0f This my first attempt to address this performance bottleneck and all feedback is welcome. [image]https://cloud.githubusercontent.com/assets/124032/10406566/4575f040-6ee1-11e5-8394-61b78108b9b9.png — |
If you are referring to removing the commit message strategy, so yes? I think this pr addresses something else, e.g the last yellow line in the trace here: #677 (comment) I think it's 2 different execution paths, both suffering performance problems? |
6a4d975
to
0eb9eb5
Compare
This commit removes the excluded branches before we're trying to find branches containing the commit. This will also exclude branches we it's not possible to find a configuration. Fixes GitTools#684
0eb9eb5
to
33f8921
Compare
Make sure that we're not evaluating excluded branches
This pull request addresses issue #684