Publishing snapshot Javadoc is broken
cpovirk opened this issue · 3 comments
(I manually pushed it in the meantime.)
$ bash util/generate-latest-docs.sh
...
[gh-pages 1f012fd5] Latest javadoc on successful travis build 948 auto-pushed to gh-pages.
211 files changed, 3142 insertions(+), 1956 deletions(-)
delete mode 100644 api/latest/allclasses.html
rewrite api/latest/index.html (94%)
create mode 100644 api/latest/jquery/images/ui-bg_flat_0_aaaaaa_40x100.png
create mode 100644 api/latest/jquery/images/ui-bg_flat_75_ffffff_40x100.png
delete mode 100644 api/latest/jquery/images/ui-bg_glass_65_dadada_1x400.png
create mode 100644 api/latest/jquery/images/ui-bg_glass_65_ffffff_1x400.png
rewrite api/latest/jquery/jquery-ui.min.css (95%)
rewrite api/latest/jquery/jquery-ui.min.js (98%)
rewrite api/latest/jquery/jquery-ui.structure.min.css (77%)
copy api/latest/{index.html => overview-summary.html} (92%)
delete mode 100644 api/latest/package-list
delete mode 100644 api/latest/packages
remote: Permission to google/truth.git denied to [secure].
fatal: unable to access 'https://github.com/google/truth/': The requested URL returned error: 403
Contrast to the output from the latest Guava push:
$ util/update_snapshot_docs.sh
...
Committing changes... Done.
Update succeeded.
Javadoc and JDiff published to gh-pages.
That update went through: google/guava@8bd5686
The two projects use similar scripts: Truth, Guava.
And similar Travis configs: Truth, Guava.
Here's a report of a similar problem from years ago. The link there talks about github_token
, which we don't set in either config. So that might not be relevant here.
I wonder if the "secure" tokens in our config has expired, then?
I don't see any "Secrets" set up in either project's settings. I do see "Integrations & services" entries for "Travis CI" for both. (That page also reminds me that "Services" are deprecated in favor of "Apps" and "webhooks.") And there's a way to edit the secret "Token" there. However, neither project has the "Active" checkbox checked. So I still might not be in the right place.
OK, here's some evidence that the "secure" tokens in the Travis config are relevant:
google/guava@a6ce7b5 (but note that some may be for Sonatype: google/guava@d675f3c)
Hmm, now I'm wondering if I remember something about this long ago from when cgruber switched companies. Presumably the token is tied to him.
I found some instructions on generating a new token:
- https://badel2.github.io/2018/09/15/github-token-from-travis.html
- https://voorhoede.github.io/front-end-tooling-recipes/travis-deploy-to-gh-pages/#set-encrypted-access-token
I'll try those.
Following some internal docs, I've enabled "Require pull request reviews before merging" for the master
branch in our branch settings.
Victory:
Published Javadoc to gh-pages.