Reputation: 61
When I push new changes to my work branch, two executions are created for that push.
I've tried to reproduce this on other branches, but only happens on some branches of my repository. And I looked for this issue, but this seems to happens to no one.
Upvotes: 2
Views: 1381
Reputation: 1
In my case, I simply switch my codepipeline source from GitHub Version 1 to GitHub Version 2 and added the inline policy to the appropriate codepipeline role:
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "",
"Effect": "Allow",
"Resource": "*",
"Action": [
"codestar-connections:UseConnection",
"appconfig:StartDeployment",
"appconfig:GetDeployment",
"appconfig:StopDeployment",
"codecommit:GetRepository"
]
}
]
}
The double execution immediately suspended. Version 1 uses OAuth-based tokens to connect to your GitHub repository. By contrast, the GitHub action (version 2) uses a connection resource to associate AWS resources to your GitHub repository.
Upvotes: 0
Reputation: 1
Depending on how you configured the integration, Github can create multiple webhooks. In my case two webhooks were created off the same branch. One that triggers on Push and Pull Requests and another that triggers just on push. Hence push would trigger both webhooks. You can edit the webhooks in Github.
Upvotes: 0
Reputation: 61
I've found that my pipeline has 2 webhooks associated. I'm generating the pipeline and the Github webhook through AWS CLI, did this happen to someone? Is it possible that when I create the pipeline the creation is automatically generating the webhook and the association?
Upvotes: 4
Reputation: 1605
Do you possibly have source polling enabled and a CloudWatch rule configured?
Upvotes: 0