From: "Jan-Simon Möller" <dl9pf@gmx.de>
To: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
Cc: "'Bird, Timothy'" <Tim.Bird@sony.com>, fuego@lists.linuxfoundation.org
Subject: Re: [Fuego] Fuego's version up and other changes
Date: Thu, 02 Feb 2017 10:50:13 +0100 [thread overview]
Message-ID: <4156365.Fcv9M2rRMI@elrond> (raw)
In-Reply-To: <000301d27d18$1255b6a0$370123e0$@toshiba.co.jp>
Am Donnerstag, 2. Februar 2017, 14:49:08 schrieb Daniel Sangorrin:
> >
> > If the complexity of the above can be hidden from
> > the 'casual' user, who has a board, and just wants to
> > run an existing test on it, then that would be good.
> > For me, this includes the whole issue of plans and
> > specs as well. I'd like to make awareness of those
> > optional for Fuego users who don't need them.
> >
> > Daniel's scripts take a minimum of arguments, and
> > do a pretty good job in this regards. If they can
> > use jjb behind the scenes, making it so that end users
> > don't have to fiddle with YAML files full of weird,
> > Jenkins parameters, that would be good, IMHO.
>
> Yeah, I agree with that. The simpler for the users the better.
> Also for the poor developers.
>
I fully agree, it should be simpler to users and the developer.
I think this can be done and it will open-up cycles as we have to deal less
with jenkins itself and more with the tests.
Best,
JS
next prev parent reply other threads:[~2017-02-02 9:50 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 0:28 [Fuego] RFC: Fuego's version up and other changes Daniel Sangorrin
2017-01-12 5:51 ` Ibe.Kengo
2017-01-12 6:44 ` Daniel Sangorrin
2017-01-12 8:15 ` Ibe.Kengo
2017-01-12 8:45 ` Daniel Sangorrin
2017-01-12 9:04 ` Ibe.Kengo
2017-01-12 9:18 ` Daniel Sangorrin
2017-01-13 1:02 ` Bird, Timothy
2017-01-13 1:29 ` Daniel Sangorrin
2017-01-13 1:37 ` Bird, Timothy
2017-01-13 1:45 ` Daniel Sangorrin
2017-01-13 1:57 ` Bird, Timothy
2017-01-13 2:05 ` Daniel Sangorrin
2017-01-13 3:34 ` Bird, Timothy
2017-01-13 4:36 ` Daniel Sangorrin
2017-01-20 0:53 ` [Fuego] " Bird, Timothy
2017-01-20 7:09 ` Daniel Sangorrin
2017-01-28 2:14 ` Bird, Timothy
2017-01-31 1:56 ` Daniel Sangorrin
2017-01-31 20:54 ` Jan-Simon Möller
2017-02-02 1:25 ` Bird, Timothy
2017-02-02 5:49 ` Daniel Sangorrin
2017-02-02 9:50 ` Jan-Simon Möller [this message]
2017-01-31 23:15 ` Jan-Simon Möller
2017-02-01 0:56 ` Daniel Sangorrin
2017-02-01 10:46 ` Jan-Simon Möller
2017-02-02 1:57 ` Bird, Timothy
2017-02-02 6:06 ` Daniel Sangorrin
2017-02-03 1:04 ` Daniel Sangorrin
2017-02-13 3:51 ` Daniel Sangorrin
2017-02-14 19:55 ` Bird, Timothy
2017-02-15 18:39 ` Kevin Hilman
2017-02-02 9:57 ` Jan-Simon Möller
2017-02-02 5:45 ` Daniel Sangorrin
2017-02-02 1:35 ` Bird, Timothy
2017-02-02 5:52 ` Daniel Sangorrin
2017-02-02 10:04 ` Jan-Simon Möller
2017-02-02 20:51 ` Kevin Hilman
2017-02-02 22:16 ` Bird, Timothy
2017-02-02 23:37 ` Kevin Hilman
2017-02-04 0:07 ` Jan-Simon Möller
2017-02-07 1:56 ` Daniel Sangorrin
2017-02-02 1:17 ` Bird, Timothy
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=4156365.Fcv9M2rRMI@elrond \
--to=dl9pf@gmx.de \
--cc=Tim.Bird@sony.com \
--cc=daniel.sangorrin@toshiba.co.jp \
--cc=fuego@lists.linuxfoundation.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.