[EGPRS] Gerrit guidance to address Jenkins Build failure and resubmission of patch.

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/osmocom-net-gprs@lists.osmocom.org/.

Neels Hofmeyr nhofmeyr at sysmocom.de
Wed Jun 15 13:53:59 UTC 2016


On Wed, Jun 15, 2016 at 01:24:02PM +0200, Max wrote:
> If you have access to jenkins you can manually retrigger corresponding
> build but since re-sending the patch series is just single command (git
> review) which takes less than 1 minute to execute I think it would be
> quicker that way.

Gerrit will refuse resending identical patches.

We can click 'rebase' on the gerrit website to retrigger a build, once some
other patch (i.e. max's fix) has been pushed to master.

Alternatively radisys can rebase locally onto the updated master and then
re-submit to gerrit.

~Neels


-- 
- Neels Hofmeyr <nhofmeyr at sysmocom.de>          http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschäftsführer / Managing Directors: Harald Welte
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.osmocom.org/pipermail/osmocom-net-gprs/attachments/20160615/316a746c/attachment.bin>


More information about the osmocom-net-gprs mailing list