[tahoe-lafs-trac-stream] [Tahoe-LAFS] #4098: CircleCI is Broken

[Tahoe-LAFS]

#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 btlogy):

 As discussed in the last N&B: it seems like meejah has shaken CircleCI
 enough with his `meejahcircleci` user the fix the "ghost key" issue.

 The solution was perceived as simple as removing the existing key.
 However, as we have verified, CircleCI has automatically re-created an new
 read-only deploy key!

 This process can be explicitly done via the project settings/key or
 silently triggered if an admin un-follow, then follow the project on the
 CircleCI web app.

 Bottom line:

 - the Tahoe-LAFS project has now a new deployed key which is used to
 checkout the code,
 - unless we customize the checkout, CircleCI requires and SSH and will try
 to automatically provision one (when not stuck in a partial config),
 - this automatic provisioning is likely the main reason why CircleCI
 requires so much power via Github OAuth,
 - avoiding this is tricky (re-configure an orgs w/o Github Oauth) and
 require a lot of work (e.g.: manual webhook).


 While it might give us some thoughts about the future of our CI, I think
 we can close this issue.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/4098#comment:20>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage