Skip to content

Commit 538ac05

Browse files
committed
Update admin/code_hosts/perforce.schema.json schema for v6.5.1211
1 parent f7a1303 commit 538ac05

File tree

1 file changed

+25
-12
lines changed

1 file changed

+25
-12
lines changed

docs/admin/repo/perforce.mdx

Lines changed: 25 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -221,53 +221,66 @@ With this setting, Sourcegraph will ignore any rules with a host other than `*`,
221221

222222
{/* SCHEMA_SYNC_START: admin/code_hosts/perforce.schema.json */}
223223
{/* WARNING: This section is auto-generated during releases. Do not edit manually. */}
224-
{/* Last updated: Manual setup - will be automated via sourcegraph/sourcegraph releases */}
224+
{/* Last updated: 2025-07-01T23:25:40Z via sourcegraph/sourcegraph@v6.5.1211 */}
225225
```json
226226
{
227227
// If non-null, enforces Perforce depot permissions.
228-
"authorization": null,
228+
"authorization": {
229+
"ignoreRulesWithHost": false,
230+
"subRepoPermissions": false
231+
},
229232

230233
// Depots can have arbitrary paths, e.g. a path to depot root or a subdirectory.
231-
"depots": null,
232234
// Other example values:
233235
// - [
234236
// "//Sourcegraph/",
235237
// "//Engineering/Cloud/"
236238
// ]
239+
"depots": null,
237240

238241
// Configuration for the experimental p4-fusion client
239-
"fusionClient": null,
240-
241-
// Only import at most n changes when possible (git p4 clone --max-changes).
242-
"maxChanges": 1000,
242+
"fusionClient": {
243+
"cacheLabels": false,
244+
"enabled": false,
245+
"fsyncEnable": false,
246+
"includeBinaries": false,
247+
"lookAhead": 2000,
248+
"maxChanges": -1,
249+
"networkThreads": 12,
250+
"networkThreadsFetch": 12,
251+
"noConvertLabels": false,
252+
"printBatch": 100,
253+
"refresh": 1000,
254+
"retries": 10
255+
},
243256

244257
// Client specified as an option for p4 CLI (P4CLIENT, also enables '--use-client-spec')
245258
"p4.client": null,
246259

260+
// REQUIRED:
247261
// The ticket value for the user (P4PASSWD). You can get this by running `p4 login -p` or `p4 login -pa`. It should look like `6211C5E719EDE6925855039E8F5CC3D2`.
248262
"p4.passwd": null,
249263

264+
// REQUIRED:
250265
// The Perforce Server address to be used for p4 CLI (P4PORT). It's recommended to specify the protocol prefix (e.g. tcp: or ssl:) as part of the address.
251-
"p4.port": null,
252266
// Other example values:
253267
// - "ssl:111.222.333.444:1666"
254268
// - "tcp:111.222.333.444:1666"
269+
"p4.port": null,
255270

271+
// REQUIRED:
256272
// The user to be authenticated for p4 CLI (P4USER).
257-
"p4.user": null,
258273
// Other example values:
259274
// - "admin"
275+
"p4.user": null,
260276

261277
// The pattern used to generate the corresponding Sourcegraph repository name for a Perforce depot. In the pattern, the variable "{depot}" is replaced with the Perforce depot's path.
262-
//
263278
// For example, if your Perforce depot path is "//Sourcegraph/" and your Sourcegraph URL is https://src.example.com, then a repositoryPathPattern of "perforce/{depot}" would mean that the Perforce depot is available on Sourcegraph at https://src.example.com/perforce/Sourcegraph.
264-
//
265279
// It is important that the Sourcegraph repository name generated with this pattern be unique to this Perforce Server. If different Perforce Servers generate repository names that collide, Sourcegraph's behavior is undefined.
266280
"repositoryPathPattern": "{depot}"
267281
}
268282
```
269283
{/* SCHEMA_SYNC_END: admin/code_hosts/perforce.schema.json */}
270-
271284
## Known issues and limitations
272285

273286
We are actively working to significantly improve Sourcegraph's Perforce support. Please [contact us](https://help.sourcegraph.com/hc/en-us/requests/new) to help us prioritize any specific improvements you'd like to see.

0 commit comments

Comments
 (0)