If one build is to @CHANGE and the next run is to @STATIC_LABEL, the p4 plugin calculates the changes by running:
p4 changes -m20 <path>@CHANGES,@STATIC_LABEL
This can be a performance hog especially when the number of tagged files in the label is large. This affects other uses as it takes massive read locks on db.rev.
Request a way to avoid the p4 changes or fix the performance on the p4d server.
[JENKINS-68516] Changelog calculation after syncing to label can lock up server
Assignee | New: Joel Brown [ joel_brown ] |
Summary | Original: Changelog calculation after building to label can lock up server | New: Changelog calculation after syncing to label can lock up server |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Resolved in 1.13.0