Hi Uze and Madan, I have enabled the 'Build Current Patchsets Only' option for Gerrit, and will look into plugins for prioritizing the 1.0.0-dev branch.
Regards, Trevor Bramwell On Thu, Oct 01, 2015 at 10:14:51AM +0000, Madan Kanth Lanka wrote: > Hi Trevor, > > > > Additional request on top of Mr. Choi's request. > > When a new patch is submitted, is it possible to cancel the build for the > previous patch which was already triggered. This will help save lot of > time. > > > > Thanks, > > Madan > > ------- Original Message ------- > > Sender : Uze Choi<uzchoi at samsung.com> S6/Principal Engineer/IoT Solution > Lab./Samsung Electronics > > Date : Oct 01, 2015 13:14 (GMT+09:00) > > Title : [dev] Prioritization for build job on release branch > > > > Hi Trevor, > > > > After cherry-picking from master into release branch to create the release > candidate, Jenkins build verification will take more than 4~5 hours. > > After few hours has been passed from commit, some of the build job has not > been allocated yet. > > > > Could you set high priority for release(1.0.0-dev) branch during release > period (maybe until next week), that is very Urgent time to generate the > release candidate ASAP > > I!-m not sure this is possible or otherwise can you do this by manually? > > > > BR, Uze Choi -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: Digital signature URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20151001/a9089549/attachment.sig>
