{"action":"opened","issue":{"url":"https://api.github.com/repos/travis-ci/travis-ci/issues/6395","repository_url":"https://api.github.com/repos/travis-ci/travis-ci","labels_url":"https://api.github.com/repos/travis-ci/travis-ci/issues/6395/labels{/name}","comments_url":"https://api.github.com/repos/travis-ci/travis-ci/issues/6395/comments","events_url":"https://api.github.com/repos/travis-ci/travis-ci/issues/6395/events","html_url":"https://github.com/travis-ci/travis-ci/issues/6395","id":168564496,"number":6395,"title":"Re-build unchanged pull request to a branch that had its .travis.yml updated","user":{"login":"danilobellini","id":2096474,"avatar_url":"https://avatars.githubusercontent.com/u/2096474?v=3","gravatar_id":"","url":"https://api.github.com/users/danilobellini","html_url":"https://github.com/danilobellini","followers_url":"https://api.github.com/users/danilobellini/followers","following_url":"https://api.github.com/users/danilobellini/following{/other_user}","gists_url":"https://api.github.com/users/danilobellini/gists{/gist_id}","starred_url":"https://api.github.com/users/danilobellini/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/danilobellini/subscriptions","organizations_url":"https://api.github.com/users/danilobellini/orgs","repos_url":"https://api.github.com/users/danilobellini/repos","events_url":"https://api.github.com/users/danilobellini/events{/privacy}","received_events_url":"https://api.github.com/users/danilobellini/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-08-01T04:33:06Z","updated_at":"2016-08-01T04:33:06Z","closed_at":null,"body":"Suppose there are 2 pull requests, A and B, both targeted to the same upstream branch. Also, let A include an update to `.travis.yml`, and B be anything else that doesn't change such file. For any reason, A was merged while B was kept untouched. If I re-run the B pull-request jobs (by clicking either \"restart build\" or \"restart job\"), it will test the new branch tip (the last commit, including stuff from A) \"auto-merged\" to the pull request commit (B), but it completely neglects the new `.travis.yml` description.\r\n\r\n[\"Building Pull Requests\" docs](https://docs.travis-ci.com/user/pull-requests) tells us that:\r\n\r\n> Travis CI also currently doesn’t build pull requests when the upstream branch is updated\r\n\r\nActually, that documentation is just about the lack of a build trigger for the GitHub update notification, but this issue is about a manual build (clicking on \"restart build\"). Clearly, the new upstream branch tip commit is used when restarting the build, but not its new `.travis.yml`, which is an inconsistency.\r\n\r\nThere might be some matrix update, leading to a different number of jobs, or even a different matrix structure (where the \"restart job\" wouldn't make much sense, just the \"restart build\" would). That's actually my case: https://travis-ci.org/danilobellini/fractals/builds/146923616\r\n\r\nIn a more general case, both A/upstream and B might update `.travis.yml`. Travis CI is just generating garbage when it runs/restarts a job with a deprecated build script that wasn't generated by the actual `.travis.yml`.\r\n\r\nPerhaps #6031 was about this issue as well."}}
{"actor":{"display_login":"danilobellini"}}