CODEWITHSUNDEEP
.netcontinuous-integrationazure-devopsazure-pipelines
Renato Fontes
Renato Fontes

Reputation: 68

VSTS Build are getting queued twice on git commit

I'm configuring VSTS builds for various projects and setting up continuous integration so they are triggered automatically whenever a commit is made to the bitbucket git repository. For some reason every time I make a commit two builds get queued instead of one.

I tried using the built it bitbucket cloud endpoint and also using an external git and polling it every 60 seconds. I also tried disabling the continuous integrations trigger since I though maybe there was another built in mechanism triggering the builds, but then I got no builds queued.

Upvotes: 0

Views: 331

Answers (2)

alexr
alexr

Reputation: 96

Have you checked on the Bitbucket site, how many Webhooks are set up for the repository? It looks like either multiple build definition and/or triggers are/were created for the same repository.

Upvotes: 1

Yang Cao
Yang Cao

Reputation: 11

I am not able to repro this with Bitbucket cloud endpoint (let's focus on getting this work since it offers better integration). How did you configure your triggers? Could you please post a screenshot? Also with the two builds, are they building the same commit?

My config looks like this: my Bitbucket build CI trigger

Upvotes: 0

Related Questions