[tahoe-lafs-trac-stream] [Tahoe-LAFS] #4098: CircleCI is Broken
Tahoe-LAFS
trac at tahoe-lafs.org
Tue Aug 20 22:08:27 UTC 2024
#4098: CircleCI is Broken
-------------------------+-----------------------
Reporter: meejah | Owner:
Type: task | Status: new
Priority: normal | Milestone: undecided
Component: unknown | Version: n/a
Resolution: | Keywords:
Launchpad Bug: |
-------------------------+-----------------------
Comment (by sajith):
The docs on both CircleCI and !GitHub are confusing and my head hurts from
trying to figure them out, but my current reading is that we'll need to
install a "CircleCI !GitHub App" in the tahoe-lafs !GitHub organization.
https://circleci.com/docs/github-apps-integration/
It seems that tahoe-lafs was originally configured with an old-fashioned
"!GitHub OAuth app". That is what the URL
`https://app.circleci.com/pipelines/github/tahoe-lafs/<blah-blah-blah>`
suggests. If we were using the "CircleCI !GitHub App", that would have
been `https://app.circleci.com/tahoe-lafs/circleci/<blah-blah-blah>`. With
that, CircleCI should be able to generate checkout keys, and presumably
share the public part of those keys with !GitHub.
I could complain about the useless error message from CircleCI, but that
would produce nothing useful...
I have not been keeping up, but it is possible that either !GitHub or
CircleCI stopped working with the old-fashioned OAuth app. I do not have
admin permissions on tahoe-lafs GitHub project, so I can't install the
"CircleCI !GitHub App" there.
--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/4098#comment:6>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list