Stream: cds hooks/committers
Topic: Travis deployment
Josh Mandel (Jul 18 2019 at 18:05):
The changes I merged led to...
38 files changed, 4376 insertions(+) Couldn't push the build to github.com/cds-hooks/sandbox.git:gh-pages failed to deploy
in the Travis build. Anybody know how this is supposed to work, and whether there are known/pre-existing issues with the continuous deployment process? (FYI @Dennis Patterson)
Josh Mandel (Jul 18 2019 at 18:07):
https://github.com/cds-hooks/sandbox/blob/master/.travis.yml#L20 indicates that Travis should have a GITHUB_TOKEN variable (presumably injected as a secret via Travis env vars), but I can't see it in https://travis-ci.org/cds-hooks/sandbox/settings. Might just be a permission issue.
Josh Mandel (Jul 18 2019 at 18:08):
(Or rather I do see that it exists in Travis, but not its value and can't verify whether it's still a valid token with push rights to this rep:
pasted image
Josh Mandel (Jul 18 2019 at 18:14):
I'm going to create a new bot user for github (cds-hooks-sandbox-bot) to manage access tokens for deployment to the sandbox, unless something like this already exists? (@Kevin Shekleton may recall.)
Josh Mandel (Jul 18 2019 at 18:22):
Done -- https://github.com/cds-hooks/sandbox/settings/collaboration now shows
and this user has a personal token available in Travis (good only for pushing to the https://github.com/cds-hooks/sandbox repo).
Dennis Patterson (Jul 18 2019 at 18:34):
cool... yeah I was starting to look into that, too... i don't have admin access to the travis-ci build to see/modify the variable and don't have admin access to the CDS Sandbox repo
Josh Mandel (Jul 18 2019 at 19:16):
Let me add you to the admin list for the sandbox...
Josh Mandel (Jul 18 2019 at 19:17):
done.
Last updated: Apr 12 2022 at 19:14 UTC
