1 Answer
- Newest
- Most votes
- Most comments
2
We have seen issues in the past where the casing of the repository as configured in CodePipeline does not match the casing of the repository in GitHub or Bitbucket, and as a result, pipelines were not being properly triggered - even though using "Release Changes" would work.
One suggestion would be to edit the Source action in the AWS Console and use the name of the repository as it appears in the dropdown that appears when configuring the source action - for other customers this has resolved the issue.
answered 3 years ago
Relevant content
- asked 2 years ago
- Accepted Answerasked 4 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago
Try revoking the AWS Connector for Github and resetting up the connection. But it sounds like you can manually start the pipeline.
I just went through this creating a workshop for this setup a couple weeks ago... I can try it again. You are using v2.8.0. Which region are your in? Anything special with your github account?