ubuntu-touch-coreapps team mailing list archive

[Frank Mertens <frank@xxxxxxxxxxx>]

On 03/14/2013 08:32 AM, Martin Mrazik wrote:
> Hi,
> 
> On 03/14/2013 08:23 AM, David Planella wrote:
>> -------- Missatge original -------- Assumpte: [Ubuntu-touch-coreapps]  [Calendar] daily build is not daily Data: Wed, 13 Mar 2013 22:05:35 +0100 De: Frank Mertens <frank@xxxxxxxxxxx> A: ubuntu-touch-coreapps@xxxxxxxxxxxxxxxxxxx
> 
>> Does anybody around here know how to tell this Jenkins bot to rebuild a package? For the calendar app it is nearly a week behind:
> 
>> https://launchpad.net/~ubuntu-touch-coreapps-drivers/+archive/daily/+sourcepub/3016240/+listing-archive-extra
> 
> Our
> 
> jenkins is hooked on the following "events":
> 
> 1. a new merge proposal with state "Needs Review" is created or a bzr revision is pushed to such a merge proposal/branch.
> 
> In this case jenkins builds the branch+trunk and votes Needs Fixing/Approve on the merge proposal based on the result.
> 
> 2. Merge proposal's global state is changed to "Approved".
> 
> In this case jenkins builds the branch+trunk (to make sure it still works) and does the following things in addition: * if the build/test fails the MP state is changed to "Needs Review" * Otherwise it merges the code (the commit message from the merge proposal is used to commit this merge) and pushes the result to the target branch/trunk _and_ * uploads the new version to the PPA
> 
> 
> In other words -- if you push to trunk yourself, jenkins will not notice the change (as it expects _every_ change will go through merge proposal and will be merged automatically). The easiest way to get a newest package in the PPA is therefore to let jenkins do the auto-merging via an approved merge proposal.
> 
> HTH.
> 
> Thanks,
> 
> Martin
> 
> 

Wow! The bot is doing the merge?
(Cool, I was already wondering why it went so smooth the last time...;)

Thx for the info,
helps a lot.

-- 
gplus.to/frankencode
frankencode@freenode