Not sure if it's related but in jenkins logs for one of the latest builds [1] I've noticed following:
Documentation error (missing docs): <command id='show asciidoc counters'> <param name='asciidoc' doc='(null)' /> <param name='counters' doc='(null)' />
Documentation error (missing docs): <command id='show asciidoc counters'> <param name='asciidoc' doc='(null)' /> <param name='counters' doc='(null)' />
In general, gerrit have link to jenkins for particular build failure. As for 2nd question - the patch is identified by "Change-Id" in the commit message so all you've got to do is to re-send the patch with the same id. Personally I use gerrit extension for magit in emacs to obtain the patch and git-review for submission. In general - please refer to http://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit.
On 06/15/2016 11:02 AM, Aravind Sirsikar wrote:
Hi, Can you guide us to address issues we are currently facing about Gerrit process as listed below
- Jenkins Build reports failure. Can you suggest the reason for this. Because in our local branch the Unit test and build is successful.
- Is there any specific process to resubmit patch after addressing the review comments.
Thanks, Aravind Sirsikar
[1] http://jenkins.osmocom.org/jenkins/job/osmo-pcu-gerrit/label=linux_amd64_ubu...