Spurious extra builds
We're doing something screwy...every time we push a change to a working branch on github, Appveyor properly creates a build. But as you can see from the link, it also creates a second duplicate build that suggests that the change has also been pushed to our mainline "dev" branch.
http://screencast.com/t/eFmq2dXQX1t
That's not the case here. Our normal process is, after it builds clean on Appveyor, we will use github pull requests to merge the working branch into dev, which should in turn cause an Appveyor build. But we don't want, and don't understand how we're causing, these duplicates of the working branches to generate builds.
Can you advise?
(One other thing. my main email address is [email blocked]. it looks like this support forum needs updating to learn that that's a legitimate email address now.)
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Feodor Fitsner on 06 Sep, 2015 05:19 PM
Hi Alex,
You can disable building pull requests. Open webhook settings on GitHub and disable "pull request" event.
2 Posted by Alex Edelstein on 09 Sep, 2015 01:06 AM
Perhaps we're confused. We don't want to disable all pull requests. We want
to build pull requests. But Appveyor is queueing up extra pull requests
that don't seem to exist and don't make sense to us. Can you give a little
more insight as to why that is?
Support Staff 3 Posted by Feodor Fitsner on 09 Sep, 2015 01:19 AM
What do you mean by "don't exist"? Have you checked "Recent deliveries" on GitHub webhook to see what was sent to AppVeyor?
- Feodor
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:59 AM.