Skip to content

If a project B use project A as a junction, B should not try to use the bst remote cache of A (at least by default) #401

Description

See original issue on GitLab
In GitLab by [Gitlab user @jjardon] on May 18, 2018, 16:58

If project A is popular, this will littery kill the cache server

More if you take the timeout problems in account: #276

Metadata

Metadata

Assignees

No one assigned

    Labels

    cache serverIssue related to cache server interactions

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions