Re: [DISCUSSIONS] CI build

[Claudius Heine <claudius.heine.ext@siemens.com>]

On 23/05/2019 15.56, Maxim Yu. Osipov wrote:
> On 5/23/19 3:43 PM, Claudius Heine wrote:
>> Hi,
>>
>> On 23/05/2019 10.10, [ext] Claudius Heine wrote:
>>> Hi,
>>>
>>> On 22/05/2019 13.28, [ext] Claudius Heine wrote:
>>> [...]
>>>>>
>>>>>>
>>>>>>>
>>>>>>>>   - Manually triggering of build jobs
>>>>>>>>     -> After pushing of CI branch, build has to be triggered via 
>>>>>>>> button
>>>>>>>
>>>>>>> One may enable such build trigger (I believe that such trigger is 
>>>>>>> enabled for Henning's project). but from my user's experience I 
>>>>>>> prefer to start the build manually.
>>>>>>
>>>>>> I normally just push to the ci branch when I want to start tests.
>>>>>
>>>>> I've enabled the corresponding options for your projects - please try.
>>>>
>>>> Thanks. But I think I should now have two branches for each 
>>>> different build parameter set. So that I don't trigger both builds 
>>>> just for one push.
>>>
>>> I pushed a ch/ilbers-ci-fast branch for the fast build.
>>
>> I have to say the this polling option that jenkins does is suboptimal.
>> Is there a way to add a git hook that triggers the build exactly when 
>> the commit arrives on github?
> 
> There is an option GitHub hook trigger for GITScm polling:
> 
> If Jenkins will receive PUSH GitHub hook from repo defined in Git SCM 
> section it will trigger Git SCM polling logic. So polling logic in fact 
> belongs to Git SCM.
> 
> Should I enable it for you?

Yes, if you can tell me how to use it.

 From what I read, there should be a curl command that I can add to the 
github repo hook settings. But I don't know the address I should use and 
if I needs some login information etc.

Thanks,
Claudius

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de