Re: [DISCUSSIONS] CI build

["Maxim Yu. Osipov" <mosipov@ilbers.de>]

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?

Regards,
Maxim.

> 
> Cheers,
> Claudius
> 


-- 
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov