Reputation: 195
I'm having problems running my cloud build triggers reliably because of what appears to be a credentials timeout.
I have set up my Google Cloud devops project within Google Cloud Build and authenticated the triggers with my private GitHub repository. My private GitHub repository has the Cloud Build GitHub App integration.
My Cloud Build triggers work for a while, running fine whether run automatically or manually.
Then after a few hours I started to get errors in my trigger execution:
...
FETCHSOURCE
Initialized empty Git repository in /workspace/.git/
remote: Invalid username or password.
fatal: Authentication failed for 'https://github.com...
To try to resolve this I have used the Cloud Build triggers page to disconnect and then re-connect and re-authenticate with my private GitHub repository. The repository management page shows a successful re-authentication, but I still get a "Invalid username or password" error when I run my triggers.
Is there something I'm missing about the way private repository authentication works? Is there another setting I'm missing that auto-refreshes Cloud Build authentication?
Upvotes: 5
Views: 2230
Reputation: 3768
This issue is the same to this public tracker issue:
Unable to fetch repository from Github
Google Cloud Engineering Team is working on solving the issue. You can star the public issue tracker feature requests and add comment in the thread that you are also affected to ensure that you will receive the updates about it.
Upvotes: 4