From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dl9pf@gmx.de>
From: Jan-Simon =?ISO-8859-1?Q?M=F6ller?= <dl9pf@gmx.de>
Date: Thu, 02 Feb 2017 10:50:13 +0100
Message-ID: <4156365.Fcv9M2rRMI@elrond>
In-Reply-To: <000301d27d18$1255b6a0$370123e0$@toshiba.co.jp>
References: <000d01d26ba1$94c8a5d0$be59f170$@toshiba.co.jp>
	<ECADFF3FD767C149AD96A924E7EA6EAF1049DF17@USCULXMSG01.am.sony.com>
	<000301d27d18$1255b6a0$370123e0$@toshiba.co.jp>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [Fuego] Fuego's version up and other changes
List-Id: Mailing list for the Fuego test framework
	<fuego.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/fuego>,
	<mailto:fuego-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/fuego/>
List-Post: <mailto:fuego@lists.linuxfoundation.org>
List-Help: <mailto:fuego-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/fuego>,
	<mailto:fuego-request@lists.linuxfoundation.org?subject=subscribe>
To: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
Cc: "'Bird, Timothy'" <Tim.Bird@sony.com>, fuego@lists.linuxfoundation.org

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