I would like finer control over what Fisheye puts into repository. In Perforce terms, this is usually done via a client specification (instead of just a simple path). For instance, I have a repository path that has numerous sub directories, however, a few of the sub directories have different security requirements. I would like do define a single Fisheye repository that selects all the sub-directories that are unrestricted and another one for the security restricted sub directories
[FE-699] Allow Perforce respository definition via a client spec
Workflow | Original: JAC Suggestion Workflow [ 3022658 ] | New: JAC Suggestion Workflow 3 [ 3642315 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Component/s | New: Indexing [ 41890 ] | |
Component/s | Original: vcs-Perforce [ 12291 ] | |
Labels | New: p4 perforce |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2949211 ] | New: JAC Suggestion Workflow [ 3022658 ] |
Workflow | Original: FECRU Development Workflow - Triage [ 943742 ] | New: Confluence Workflow - Public Facing v4 [ 2949211 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Backlog Order (Obsolete) | Original: 9420000000 | |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Workflow | Original: FECRU Development Workflow (Triage) [ 309186 ] | New: FECRU Development Workflow - Triage [ 943742 ] |
Workflow | Original: Simple review flow with triage [ 155903 ] | New: FECRU Development Workflow (Triage) [ 309186 ] |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Needs Triage [ 10030 ] | New: Closed [ 6 ] |
Status | Original: Open [ 1 ] | New: Needs Triage [ 10030 ] |
Workflow | Original: Copy of review flow with triage [ 154170 ] | New: Simple review flow with triage [ 155903 ] |