[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3541: CircleCI cannot find context "dockerhub-auth"
Tahoe-LAFS
trac at tahoe-lafs.org
Mon Nov 30 20:42:56 UTC 2020
#3541: CircleCI cannot find context "dockerhub-auth"
--------------------------------+---------------------------
Reporter: sajith | Owner:
Type: defect | Status: new
Priority: normal | Milestone: undecided
Component: dev-infrastructure | Version: n/a
Keywords: | Launchpad Bug:
--------------------------------+---------------------------
In #3483, we added a "dockerhub-auth" context which holds !DockerHub
credentials to tahoe-lafs' CircleCI settings, in order to solve the
problem imposed by !DockerHub's impending rate limits. It turns out that
having an organization-specific context will prevent CircleCI from running
CI tasks for pull requests made by contributors who have chosen to fork
tahoe-lafs repository at !GitHub.
Here is an example CI run:
https://app.circleci.com/pipelines/github/jaraco/tahoe-lafs/23/workflows
/e2869d9c-43c7-4475-9aac-690826136eb7. All of those failed tasks have
failed with the same "could not find context" error message.
This happens because the tahoe-lafs organization's CircleCI account has a
"dockerhub-auth" context, but any other account that forked the repository
won't have such a context, unless they add one at CircleCI. This is the
source of those errors, and it could be pretty confusing.
A solution would be for the account that forked the repository to create a
"dockerhub-auth" context (an empty context will do) under CircleCI's
"organization settings".
An even better solution would be to adapt our CircleCI configuration such
that it will continue to work even when a "dockerhub-auth" context is not
present. In such cases, CI should continue to function, even if
!DockerHub rate-limits image pulls. This way new contributors won't need
to have commit access to the "canonical" tahoe-lafs repository.
--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3541>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list