Multiple builds triggered

[chasepeeler]

Stash is setup to send a notification to jenkins after a commit to the develop branch. However, after we merge a pull request, it will trigger two builds.

The first build (in hipchat) says something like "Started by changes from John Doe (x files(s) changed)

The second build will just say "Started by an SCM change"

The second build is triggered pretty soon after the first build (it doesn't run until the first build is finished, however).

[chasepeeler]

This is the hook setup:

[dhumeniuk]

I have something similar happen, see issue #63

[chasepeeler]

I've been adding comments related to this issue under issue #63

[loa]

@chasepeeler Can you check something for me?

For me it seems like I get multiple triggers only if there is an open pull-request for the branch. Can you verify?

[chasepeeler]

If I merge a pull request (whether others are open or not) it does this. If I merge locally then push, it doesn't (even if there is an open pull request).

I've actually "solved" the issue by setting a quiet time of 30 seconds.

[dhumeniuk]

Where is the quiet time set? I couldn't seem to find this as an option in Jenkins.

On Mon, Jun 30, 2014 at 11:18 AM, Chase Peeler notifications@github.com wrote:

If I merge a pull request (whether others are open or not) it does this. If I merge locally then push, it doesn't (even if there is an open pull request).

I've actually "solved" the issue by setting a quiet time of 30 seconds.

— Reply to this email directly or view it on GitHub https://github.com/Nerdwin15/stash-jenkins-postreceive-webhook/issues/66#issuecomment-47544548 .

[chasepeeler]

It's under "Advanced Project Options"

[dhumeniuk]

I tried setting the quiet time, but it doesn't always seem to work, might not be long enough I guess, eagerly awaiting this linked pull request.