Double builds for all merges and PRs


#1

For about a month on one organisation repository, I’ve noticed two builds are being queued for each and every merge to master, and for each PR push. I’ve not seen it on my personal fork of this repo, or any other repo or org.

You can see two builds for each " Merge pull request X from Y" with the same commit ID for these merges to master (https://travis-ci.org/python-pillow/Pillow/builds):

PRs (https://travis-ci.org/python-pillow/Pillow/pull_requests)

Scrolling down, it looks like this started somewhere around build #6713 on 14th January:

Any ideas what is triggering this?


#2

I guess you have two references to Travis with the same purpose in your Github project’s intergration settings because of a recent migration: https://changelog.travis-ci.com/migration-completed-github-services-to-webhooks-88817 .

The simplest way would be to delete all Travis-related integration entries and re-add your project in Travis UI.


#3

That reminds me, we did get ‘This is not an active repository’ around the same time and had to re-enable it:


#4

Yeah, this looks related. If some integration entry stopped working, you added an updated one, then it started working again, you would end up in the current situation.

The integration entries are in https://github.com/python-pillow/Pillow/settings , under “webhooks” and “services”. Only someone with appropriate permissions can see them.


#5

Thanks! There were webhooks, removing the extra one fixed it.