|
|
|
Previously QB may queue a lot of build requests if there are a lot of open pull requests there even if there are updates in these pull requests, and QB can only realize that there are no changes at change detection phase. With this flag, we can bypass the change detection phase if there are no updates to these pull requests.
This is actually an improvement requested by several other customers using GitHub integration heavily. Oh wow. Why do you have both the build condition and this other flag? That's confusing. :-( Thank you for the explanation Robin.
While keep that flag turned off, you can also manually build any pull requests by specifying pull request id on GitHub repo definition.
To avoid queueing many build requests (even if there are no changes), QB has a flag "Queue Changed Branches Only" in advanced setting of configuration. You may turn off it to have QB queue pull request builds so that it goes through normal change detection and build firing process, and then you can run the build manually to force build of your open pull requests.
I believe this same bug is keeping me from running builds manually against pull requests one at a time (I'd like to test some manually before setting it loose on 6+ hours of builds).
I should add that my concern is being able to re-run failed builds because I've screwed up (the steps aren't correct) or something else has failed (reaching quota limit against GitHub, etc.).
|
Thanks for the explanation!