public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <claudius.heine.ext@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>,
	isar-users <isar-users@googlegroups.com>
Subject: Re: [DISCUSSIONS] CI build
Date: Thu, 23 May 2019 15:43:24 +0200	[thread overview]
Message-ID: <5dae12a5-f0c2-b8ee-eea7-15eb2791ba4f@siemens.com> (raw)
In-Reply-To: <d789f914-b58b-83fe-94b9-6c675309a9c5@siemens.com>

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?

Cheers,
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

  reply	other threads:[~2019-05-23 13:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-22  7:26 Claudius Heine
2019-05-22  8:20 ` Maxim Yu. Osipov
2019-05-22  9:10   ` Claudius Heine
2019-05-22  9:50     ` Maxim Yu. Osipov
2019-05-22 11:28       ` Claudius Heine
2019-05-23  8:10         ` Claudius Heine
2019-05-23 13:43           ` Claudius Heine [this message]
2019-05-23 13:56             ` Maxim Yu. Osipov
2019-05-23 14:36               ` Claudius Heine
2019-05-22 19:44 ` Baurzhan Ismagulov
2019-05-23  4:44   ` Jan Kiszka
2019-05-23  8:32     ` Claudius Heine
2019-05-23  8:39       ` Jan Kiszka
2019-05-23 10:58       ` Maxim Yu. Osipov
2019-05-23 11:35 ` Henning Schild
2019-05-23 12:11   ` Baurzhan Ismagulov
2019-05-30  8:29 ` Jenkins project configuration by user Maxim Yu. Osipov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5dae12a5-f0c2-b8ee-eea7-15eb2791ba4f@siemens.com \
    --to=claudius.heine.ext@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=mosipov@ilbers.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox