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:57:29 +0100
Message-ID: <2936516.VbXDTZGgef@elrond>
In-Reply-To: <ECADFF3FD767C149AD96A924E7EA6EAF1049DF46@USCULXMSG01.am.sony.com>
References: <000d01d26ba1$94c8a5d0$be59f170$@toshiba.co.jp>
	<4759757.Uek3Dlbnj3@elrond>
	<ECADFF3FD767C149AD96A924E7EA6EAF1049DF46@USCULXMSG01.am.sony.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
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: "Bird, Timothy" <Tim.Bird@sony.com>
Cc: "fuego@lists.linuxfoundation.org" <fuego@lists.linuxfoundation.org>

Am Donnerstag, 2. Februar 2017, 01:57:34 schrieb Bird, Timothy:
> I'd like to cut down the amount of stuff in the Jenkins job configura=
tion,
> while still allowing some parameters to be managed with the Jenkins
> interface.  Optimally, we could have something as simple as:
> shell: fuego run ${{TESTNAME}}
> with TESTDIR implied and other parameters like the JOB_TIMEOUT
> being auto-calculated from data in the transport, job file, distribut=
ion,
> test itself, and board file.

Yes, if we can reduce this to just the minimum required parameters, it =
would=20
simplify a lot.
The folders are implied and the rest comes out of the conf files.

There are 2 directions as we discussed previously:

- fuego being the central wrapper for a whole series of tests
  shell: fuego run -m {machine} -t {testspec}
  -- in this case we'd likely just have one jenkins job to create
     and the loop + flow-control is all on fuego
  -- downside is that one error will crash the whole series and there
     is no way to restart a single test easily

- fuego starting single tests
  shell: fuego run {testname}
  -- multiple jenkins jobs, flow-control in jenkins
  -- crash limited to one test


Leaning towards "fuego run {testname}" b/c of the finer control imho.

Best,
--
Jan-Simon M=F6ller
dl9pf@gmx.de