AWS CodePipeline不再起作用-GitHub的令牌权限不足 [英] AWS CodePipeline doesn't work anymore - GitHub's token insufficient permissions

问题描述

我已经创建了以GitHub为源的AWS Code Pipeline.一切正常，我可以从GitHub轻松获取存储库.通过此管道，我已经将我的应用程序部署了上百万次.

I've created AWS Code Pipeline with GitHub as a source. It was working fine and I was able to fetch repository from GitHub without difficulties. I've deployed my app million times through this pipeline.

直到上周日(2015年11月15日)，当我尝试发布对管道的更改时.

Until last Sunday (15-11-2015) when I tried to release changes to my pipeline.

从那时起我就得到

要么GitHub存储库"epub"不存在，要么GitHub 提供的访问令牌没有足够的权限来访问 资料库.验证存储库是否存在，然后将管道编辑为 将操作重新连接到GitHub.

Either the GitHub repository "epub" does not exist, or the GitHub access token provided has insufficient permissions to access the repository. Verify that the repository exists and edit the pipeline to reconnect the action to GitHub.

错误消息.

我删除了管道，撤消了对GitHub上所有AWS服务的访问，从头开始创建了管道，授予了对GitHub上的AWS CodePipeline App的访问权限. 我能够正确设置管道，当我在设置管道时连接到GitHub时，我能够获取所有存储库，然后选择分支.

I've deleted the pipeline, revoked access to all AWS services on GitHub, created the pipeline from scratch granting access to AWS CodePipeline App on GitHub. I'm able to set up pipeline correctly, when I'm connecting to GitHub while setting up the pipeline, I'm able to fetch all the repos, and choose branch.

但是在运行管道之后，我得到了这个烦人的错误.

But then after I'm running the pipeline I'm getting this annoying error.

在我看来，这是一个GitHub-AWS访问问题，但是我无法控制它，因为GitHub的授权应用程序中的AWS CodePipeline对其进行控制.

It seems to me that this is an GitHub - AWS access issue, but I have no control over it, as AWS CodePipeline in GitHub's authorised applications controls it.

我现在想弄清楚几天，但通过不同的教程和潜在的解决方案却没有成功

I'm trying to figure it out for a couple of days now but without success going through different tutorials and potential solutions

有什么建议吗?

推荐答案

我最近也遇到了这种情况；但是，它看起来像是假阴性:当我推送到正在监视的分支时，尽管Pipeline显示错误的阶段，但它将拉动并将源传递到下一个阶段.

I've been experiencing this recently as well; however, it looks like a false-negative: when I push to a branch being watched, despite the Pipeline showing that stage in error, it pulls and delivers source to the next stage.

奇怪的行为，但实际上不是问题.

Strange behavior, but not actually an issue.

这篇关于AWS CodePipeline不再起作用-GitHub的令牌权限不足的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！