workflow - How to avoid hasted gerrit review submits? -




over last year of using ~5 different gerrit servers encountered common issue: while performing review, did +2 , submitted change, entire review effort become useless.

how can avoid issue?

you implement special strategy "lock" approval , "unlock" after timeout. example:

1) create custom label on gerrit (ex: timeout)

2) set gerrit-trigger on jenkins trigger job every patchset pushed gerrit. every patchset following:

2.1) set label timeout = -1 (lock).

2.2) save in file change number time when unlocked.

3) set on jenkins periodical job timeout changes in lock file. set label timeout = +1 (unlock) when it's needed.

some people +1 permission on label timeout can bypass timeout period if needed.





wiki

Comments

Popular posts from this blog

Asterisk AGI Python Script to Dialplan does not work -

python - Read npy file directly from S3 StreamingBody -

kotlin - Out-projected type in generic interface prohibits the use of metod with generic parameter -