All of lore.kernel.org
 help / color / mirror / Atom feed
From: <daniel.sangorrin@toshiba.co.jp>
To: gpi@mailbox.org, fuego@lists.linuxfoundation.org, Tim.Bird@sony.com
Subject: Re: [Fuego] Dockerfile vs install-debian.sh
Date: Mon, 27 Jul 2020 11:52:57 +0000	[thread overview]
Message-ID: <OSBPR01MB205378E7D07CDFA9369E9FCCD0720@OSBPR01MB2053.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <eba92086-a36d-2085-ca7a-3186ed733a1c@mailbox.org>

Hi Georg
Tim: I have a question of your at the end.

> -----Original Message-----
> From: Fuego <fuego-bounces@lists.linuxfoundation.org> On Behalf Of Georg Piewald
> Sent: Monday, July 27, 2020 8:14 PM
> To: fuego@lists.linuxfoundation.org
> Subject: [Fuego] Dockerfile vs install-debian.sh
> 
> Hi guys,
> 
> I was just looking into how to install Fuego without a Docker container (since the CHANGELOG says it's possible). Apparently, that's what
> install-debian.sh is good for (or is there something else, that I missed?).

Yes, I created it in 2019 and it worked at that time. I run it together with LAVA.
Unfortunately, I haven't been able to maintain it since then for private reasons. Now I am back but I can't spend as much time as I'd like.
https://bkk19.sched.com/event/Li6u/bkk19-tr08-how-to-integrate-fuego-automated-testing-tool-in-your-ci-loop
You have the slides there (and the presentation is on youtube)

> But honestly, this script seems like a halfhearted attempt to me and strongly violates the DRY principle. It is clearly descendant from
> Dockerfile, but did not evolve with it. Several later modifications in Dockerfile did not make it to install-debian.sh. How do you plan to keep
> these files in sync?

You are right. This was just a fast prototype to prove a point (that Fuego can work with LAVA, Ktest, Linaro test definitions, and other test frameworks) on that conference.
It is waiting for proper integration and maintenance.
 
> I propose to only let install-debian.sh have all the code that sets up the OS and installs all requirements. The Dockerfile instead should do
> (almost) nothing but execute install-debian.sh.

Yes, that was my plan as well.
 
> An additional benefit of that method is that it will be much easier to also keep Dockerfile.nojenkins in sync with the standard Dockerfile.
> Because here we have the same problem of lots of copied code, that is slowly drifting apart. We might even not need Dockerfile.nojenkins
> anymore at all.

Exactly.

> I can offer to implement this, unless there are strong objections by anyone.

That would super awesome. It would be good if you see my video on Youtube or at least read the slides to get a bit of background of what I wanted to do with it.
Also if you have any question about why i did that, or if there is a missing piece of code please let me know.

Tim: do you agree?

Best regards,
Daniel

  reply	other threads:[~2020-07-27 11:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27 11:14 [Fuego] Dockerfile vs install-debian.sh Georg Piewald
2020-07-27 11:52 ` daniel.sangorrin [this message]
2020-07-27 11:54   ` daniel.sangorrin
2020-07-27 17:41   ` Bird, Tim
2020-07-28  8:25   ` Georg Piewald
2020-07-28  9:25     ` daniel.sangorrin
2020-07-27 17:33 ` Bird, Tim
2020-07-30 21:38   ` Georg Piewald
2020-09-30 23:57     ` daniel.sangorrin

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=OSBPR01MB205378E7D07CDFA9369E9FCCD0720@OSBPR01MB2053.jpnprd01.prod.outlook.com \
    --to=daniel.sangorrin@toshiba.co.jp \
    --cc=Tim.Bird@sony.com \
    --cc=fuego@lists.linuxfoundation.org \
    --cc=gpi@mailbox.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.