Uze, Madan, and All, To ensure 1.0.0-dev is given priority, I have installed the following plugins:
- Accelerated Build Now Plugin: Allows for manually pushing jobs to the top of the queue. This should be used with discretion and only in cases where changes need to be pushed through. [1] - Purge Build Queue Plugin: Allows for removing all current jobs from the queue. This is required for worst case scenarios where all jobs may need to be retriggerd. [2] - Priority Sorter Plugin: Lets us define priorities for jobs and different queuing strategies. This will allow for giving Integration jobs priority. [3] The queue has been purged and Jenkins will need to be restarted in order for the plugins to be installed. After Jenkins is back up, I will requeue Integration builds, following by 1.0.0-dev patches, followed by patchsets that were previously in the queue. I expect this to cause no more than 30 minutes disruption to the builds. Regards, Trevor Bramwell [1] https://wiki.jenkins-ci.org/display/JENKINS/Accelerated+Build+Now+Plugin [2] https://wiki.jenkins-ci.org/display/JENKINS/Purge+Build+Queue+Plugin [3] https://wiki.jenkins-ci.org/display/JENKINS/Priority+Sorter+Plugin On Thu, Oct 01, 2015 at 09:04:31AM -0700, Trevor Bramwell wrote: > 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/78ad13e9/attachment.sig>
