From: Jan Kiszka <jan.kiszka@siemens.com>
To: Claudius Heine <claudius.heine.ext@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [DISCUSSIONS] CI build
Date: Thu, 23 May 2019 10:39:00 +0200 [thread overview]
Message-ID: <0001dca7-4e10-38c4-2b31-9f47faf9cd64@siemens.com> (raw)
In-Reply-To: <a8b0007d-0f98-eef7-52f8-506b1ad16aeb@siemens.com>
On 23.05.19 10:32, Claudius Heine wrote:
>>>> -> Cannot be spread over multiple servers
>>>
>>> Haven't looked at that, ideas welcome. Jan told us he is preparing something,
>>> but load balancing would spread multiple pipelines, not tasks within one
>>> pipeline. Depending on the costs, it might or might not be cheaper for us to
>>> throw more physical servers on the task.
>>>
>>
>> https://lists.cip-project.org/pipermail/cip-dev/2019-May/002371.html
>
> Would have been nice to have this cross-posted to this ML as well.
>
We wanted to do that once a build is public, see also the follow-up in that thread.
> Will Michael write patches for isar to integrate this, or does he needs anything
> to do this?
>
There is currently no need for patches, gitlab-ci.yml already exists in isar and
is being used. But there will likely be the desire to tune that further, add the
qemu-based tests once the infrastructure is running.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-05-23 8:39 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
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 [this message]
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=0001dca7-4e10-38c4-2b31-9f47faf9cd64@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=claudius.heine.ext@siemens.com \
--cc=isar-users@googlegroups.com \
/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