[scm] source code management - lock of perforce branch

 

perforce Locking of branches （Perforce branch locking）

Usually in some milestone Of build When or some branch The life cycle of , We all need to lock branch To prohibit yes branch Modification of .

 

There are two ways to lock perforce branch：

 

1） Permissions on the table （protection table）

Usually we use a group To manage a branch Authority . For example, the default is as follows ：

write group envision * //dev/envision/esi/...

When We need to lock in branch //dev/envision/esi/... when , Can be in p4admin Of ＧＵＩ Modify in the management tool protection table Or add a new line at the end lock branch, for example read group envision * //dev/envision/esi/...

 

It can also be used in scripts p4 protect To modify the permission table , To lock or unlock a ｂｒａｎｃｈ.

 

2）triggers

also You can use one trigger To achieve locking branch Purpose . this trigger The execution process is ： When there is changelist when , Check whether the included files belong to designated branch, If it belongs to the one to be locked branch Then refuse to submit , So as to achieve lock branch Purpose . All to lock Of branches It can be put in a txt file , then trigger By checking this txt To get those branches want lock, When you need to lock new branch, Just add it here txt Medium will do .

Use trigger The shortcomings of the method add all submit Time for .

End ！

author ：iTech

WeChat official account : cicdops

github：​ ​https://github.com/cicdops/cicdops​​