public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Baurzhan Ismagulov <ibr@radix50.net>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v4 00/15] Add developers test
Date: Fri, 10 Feb 2023 21:04:19 +0100	[thread overview]
Message-ID: <20230210210419.2f23034a@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20230210205414.0c687aca@md1za8fc.ad001.siemens.net>

Am Fri, 10 Feb 2023 20:54:14 +0100
schrieb Henning Schild <henning.schild@siemens.com>:

> Am Fri, 10 Feb 2023 18:13:40 +0100
> schrieb Baurzhan Ismagulov <ibr@radix50.net>:
> 
> > On Fri, Feb 10, 2023 at 11:19:57AM +0100, Henning Schild wrote:
> > > > > Too much to read. Give me a branch on github. I trigger a
> > > > > pipeline and give you the result. I just push buttons and need
> > > > > to know/understand nothing ... that is my offer.    
> > > > 
> > > > ubely/devel_runtest (948af8e7) - includes both "(v4) Add
> > > > developers tests" and "(v2) Support running custom commands in
> > > > VM" patchsets  
> > > 
> > > Your pipeline is running.  
> > 
> > This patchset drops ccache and sstate testcases from "fast". The
> > next step is to add the necessary coverage to "dev" and switch to
> > it by default. You also suggested to drop sdk, containerbuild,
> > containersdk -- we will consider it in this next step.
> 
> I did not even look. I just triggered and delivered the result.
> 
> We will have to see how we get our both CI results public where
> triggers probably have to stay manual.
> 
> I think ilbers is much better at the triggers for "trusted
> contributors" at the moment and maybe ilbers will also be faster on
> the public view.
> 
> Getting this done in Siemens might be a longer story. But we will keep
> an eye on "gitlab-ci" doing what "ilbers"/"jenkins" does to get the
> same output even if we can not publish or allow external triggers.
> 
> This is all going in the right direction, now at least we have the
> same results and the duration in a shape that Siemens infra allows.

The infra we currently run on in Siemens might never allow "external
triggers" or "sharing reports" unfortunately. And getting/maintaining
infra for public use might be complicated as well.

So i think the "ilbers" does it in public and Siemens does it
internally as well ... might just be what we get.

But that does not seem too bad, because others might also have a hard
time to "publish" and we can learn from that limitation to help
"others".

Henning

> Henning
> 
> > With kind regards,
> > Baurzhan
> 


  reply	other threads:[~2023-02-10 20:04 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06 12:33 Uladzimir Bely
2023-02-06 12:33 ` [PATCH v4 01/15] CI: Enable downloads dir sharing Uladzimir Bely
2023-02-06 12:33 ` [PATCH v4 02/15] CI: Add IMAGE_INSTALL override Uladzimir Bely
2023-02-06 12:33 ` [PATCH v4 03/15] CI: Add developers test Uladzimir Bely
2023-02-06 12:33 ` [PATCH v4 04/15] CI: Remove duplicated targets Uladzimir Bely
2023-02-06 12:33 ` [PATCH v4 05/15] CI: move to avocado to 99.0 Uladzimir Bely
2023-02-06 12:33 ` [PATCH v4 06/15] CI: fix shell coding style Uladzimir Bely
2023-02-06 12:33 ` [PATCH v4 07/15] CI: install qemu-system when qemu testing is requested Uladzimir Bely
2023-02-06 12:33 ` [PATCH v4 08/15] testsuite: remove tests from "fast" set Uladzimir Bely
2023-02-06 12:33 ` [PATCH v4 09/15] CI: Get rid of setting cross from outside Uladzimir Bely
2023-02-06 12:33 ` [PATCH v4 10/15] CI: Make cross compile to be default Uladzimir Bely
2023-02-06 12:33 ` [PATCH v4 11/15] CI: Get rid of setting repro from outside Uladzimir Bely
2023-02-06 12:33 ` [PATCH v4 12/15] CI: Allow example module checking disabling Uladzimir Bely
2023-02-06 12:34 ` [PATCH v4 13/15] testsuite: Fix terminal broken after run test executed Uladzimir Bely
2023-02-06 12:34 ` [PATCH v4 14/15] CI: Update testsuite documentation Uladzimir Bely
2023-02-06 12:34 ` [PATCH v4 15/15] CI: Add single target test case Uladzimir Bely
2023-02-09  8:39 ` [PATCH v4 00/15] Add developers test Uladzimir Bely
2023-02-09 15:46   ` Henning Schild
2023-02-10  2:42     ` Uladzimir Bely
2023-02-10  9:44       ` Henning Schild
2023-02-10  9:51         ` Uladzimir Bely
2023-02-10 10:19           ` Henning Schild
2023-02-10 17:13             ` Baurzhan Ismagulov
2023-02-10 19:54               ` Henning Schild
2023-02-10 20:04                 ` Henning Schild [this message]
2023-02-12 17:16                 ` Baurzhan Ismagulov
2023-02-10 17:36             ` Henning Schild
2023-02-14  5:43 ` Uladzimir Bely

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=20230210210419.2f23034a@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=ibr@radix50.net \
    --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