How to freeze changeID on Gerrit?

I have a repository on my Gerrit server where the changeID needs to be tested within a few hours of being viewed and ready to ship.

When testing the changed ID to be sent, I would like to freeze / hook the changeID so that no one pushes new patch sets or permutations.

When the testing phase is complete, it should be possible to send this changeID file, but for this it would be desirable that the corresponding changeID does not have any new patches after starting the testing phase.


Currently, when someone creates a new patchset in ChangeID that I have already started testing, I have 2 options:

1) Start testing again with a new set of patches, which is delaying my work. 2) Ignore the new patchset and cherry-pick directly from the patchset I started testing, and when finished testing, push it for refs / heads / master.

+3


source to share


1 answer


The Gerrit administrator for your Gerrit server needs to set up an additional custom shortcut that uses the "PatchSetLock" function. This will look like a different code view, and when installed, will prevent new patches from being added to that change ID.

The administrator will also need to install the project's ACLS so that developers have permission to edit the tag. Similar to what is probably already configured for the code tag.



Details here: https://gerrit-review.googlesource.com/Documentation/config-labels.html

+2


source







All Articles