kris
November 30, 2018, 7:58pm
1
I updated my pull request during this build: https://travis-ci.org/jbardin/scp.py/builds/439188626
While a new build was started with the updated branch, some jobs of the running build picked up the UPDATED branch, while others used the old one (the ones that succeeded).
1 Like
Travis gets the source from a special Github’s ref linked to the PR , there’s no way to detect if Github “pulled the rug from underneath us” and changed its contents midway.
So the expected behavior would probably be to cancel the build if the PR branch is force-pushed (not sure if regular pushing also applies).
The pull request synchronize event contains a ‘merge_commit_sha’, you should use that instead of the ‘refs/pull/?/merge’ ref.
1 Like
I’m still having this issue . Is there any news about it?
Going to be (and just started) looking into this personally. Will get back to you as soon as I’ve found an end result.
1 Like