From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Jan-Simon =?ISO-8859-1?Q?M=F6ller?= Date: Tue, 31 Jan 2017 21:54:32 +0100 Message-ID: <2089327.AE25eAEzJN@elrond> In-Reply-To: <003001d27b65$2d0c2650$872472f0$@toshiba.co.jp> References: <000d01d26ba1$94c8a5d0$be59f170$@toshiba.co.jp> <003001d27b65$2d0c2650$872472f0$@toshiba.co.jp> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="nextPart2493848.4cV4qvzlu3" Content-Transfer-Encoding: 7Bit Subject: Re: [Fuego] Fuego's version up and other changes List-Id: Mailing list for the Fuego test framework List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: fuego@lists.linuxfoundation.org Cc: "'Bird, Timothy'" This is a multi-part message in MIME format. --nextPart2493848.4cV4qvzlu3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Hi Daniel, Tim, * ! I've setup an instance of the -next branch and I'm using and working on= it right now. Let me add a few notes and observations: * I like the create-job / delete-job and the node scripts. They simplif= y=20 things a lot. * A extension to this approach IMHO would be the use of jenkins-job-bui= lder. The beauty of this is that we do not have to deal with the xml oursel= ves. Instead we define yaml files and let jjb create the necessary xml. Another plus is that such an approach would also allow ppl to add the testcases to an *existing* jenkins using the jjb templates.=20 Let me illustrate this with a jump-start example: Installation of jjb (in fuego container): $ cd ~/ $ sudo apt-get install python-pip $ sudo pip install jenkins-job-builder # should be 1.6.x $ cat < jjb-conf.ini [job_builder] ignore_cache=3DTrue keep_descriptions=3DFalse include_path=3D.:scripts:~/git/ recursive=3DTrue [jenkins] user=3DAnonymous password=3D url=3Dhttps://localhost/ ##### This is deprecated, use job_builder section instead #ignore_cache=3DTrue query_plugins_info=3DFalse EOF $ mkdir jjb $ cd jjb/ $ mkdir testjob $ cat < testjob/testjob.yaml - project: name: fuego-tests-smoke machine: - raspberrypi3 testname: -=20 -=20 -=20 -=20 -=20 jobs: - {machine}.smoke.batch - {machine}.smoke.{testname} - job-template: name: '{machine}.smoke.batch' project-type: freestyle concurrent: false node: master builders: - orchestrator-script ON - trigger '{machine}.smoke.*' BLOCKING - orchestrator-script OFF ALWAYS - job-template: name: '{machine}.smoke.{testname} project-type: freestyle concurrent: false node: {machine} =20 --=20 -- Jan-Simon M=F6ller dl9pf@gmx.de --nextPart2493848.4cV4qvzlu3 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="iso-8859-1"

Hi = Daniel, Tim, * !

 

I've setup an instanc= e of the -next branch and I'm using and working on it right now.

 

Let me add a few note= s and observations:

* I like the create-j= ob / delete-job and the node scripts. They simplify

things a lot.

* A extension to this= approach IMHO would be the use of jenkins-job-builder.

The beauty of this = is that we do not have to deal with the xml ourselves.

Instead we define y= aml files and let jjb create the necessary xml.

Another plus is tha= t such an approach would also allow ppl to add

the testcases to an= *existing* jenkins using the jjb templates.

 

Let me illustrate thi= s with a jump-start example:

 

Installation of jjb (= in fuego container):

$ cd ~/

$ sudo apt-get instal= l python-pip

$ sudo pip install je= nkins-job-builder

#= should be 1.6.x

 

$ cat <<EOF >= ; jjb-conf.ini

[job_builder]

ignore_cache=3DTrue

keep_descriptions=3DF= alse

include_path=3D.:scri= pts:~/git/

recursive=3DTrue

[jenkins]

user=3DAnonymous

password=3D

url=3Dhttps://localho= st/

##### This is depreca= ted, use job_builder section instead

#ignore_cache=3DTrue<= /p>

query_plugins_info=3D= False

EOF

 

$ mkdir jjb

$ cd jjb/

 

$ mkdir testjob

$ cat <<EOF >= ; testjob/testjob.yaml

- project:

name: fuego-tests= -smoke

machine:

- raspberrypi= 3

testname:

-

-

-

-

-

jobs:

- {machine}.s= moke.batch

- {machine}.s= moke.{testname}

 

- job-template:

name: '{machine}.= smoke.batch'

project-type: fre= estyle

concurrent: false=

node: master

 

builders:

- orchestrator-sc= ript ON

- trigger '{machi= ne}.smoke.*' BLOCKING

- orchestrator-sc= ript OFF ALWAYS

 

- job-template:

name: '{machine}.= smoke.{testname}

project-type: fre= estyle

concurrent: false=

node: {machine}

 

 

 

-- =

--<= /p>

Jan= -Simon M=F6ller

dl9= pf@gmx.de

--nextPart2493848.4cV4qvzlu3--