Alan wrote (21 Feb 2015 13:36:41 GMT) :
>> Most of us (including me) do the same as Alan, but IMO that's almost
>> irrelevant to the topic at hand. This same scenario reads:
>>
>> And I need to know if my branch build is broken by something else
>> possibly weeks after my last commit (by e.g Debian changes,
>> changes in branch B, ...)
>> ^^^^^^^^^^^^^^^^^^^
>>
>> ... and we cannot possibly get this without locally merging the topic
>> branch F into B before building.
>>
>> The important point here may be the *locally* word. This merge would
>> only be done in Jenkins own temporary Git checkout, and wouldn't
>> affect how we're handling our branches' Git history.
>>
>> > But I agree this is not the best way to go, so if Alan doesn't come up with
>> > a block on this, I agree to add the clarification.
>>
>> OK. But apparently, either I misunderstood why Alan had trouble with
>> this idea, or Alan has misunderstood the idea, so IMO it would be good
>> to have his opinion now that I've clarified what I think we should do,
>> and why. Alan?
>>
> I do not see any issue with this local merge by our autobuilder. Looks
> to me like the right thing to do.
Thanks for the clarification!
bertagaz: I think it can now be clarified accordingly on the blueprint :)
Cheers,
--
intrigeri
