3 ms·

I've read the description, but I fail to understand how this is different from just merging current master into the PR and running integration on that before me

I've read the description, but I fail to understand how this is different from just merging current master into the PR and running integration on that before merging in back into master? This can be done with 10 lines of groovy in Jenkins. Also the exact workflow described with staging branch and batch merge is probably another 20-30 lines.

ljm 7y ago
This is what Travis CI did/does and I have not seen another CI platform offer the same. Travis runs your test suite on the merge commit, not the head of the branch.
- clintonb 7y ago
  Travis tests both the development branch and the merge/integration branch. https://docs.travis-ci.com/user/pull-requests/#double-builds-on-pull-requests https://docs.travis-ci.com/user/pull-requests/#double-builds...
DougBTX 7y ago
That process assumes nothing gets merged during the integration test run. The script could check to see if the target branch has changed in the mean time, and fail the merge if it has, then I think it would be the same.