All of lore.kernel.org
 help / color / mirror / Atom feed
From: <Tim.Bird@sony.com>
To: dhinakar.k@samsung.com
Cc: fuego@lists.linuxfoundation.org
Subject: Re: [Fuego] ANNOUNCE: Fuego Release v1.5.0 (Flame)
Date: Fri, 23 Aug 2019 17:56:17 +0000	[thread overview]
Message-ID: <ECADFF3FD767C149AD96A924E7EA6EAF977A4CC1@USCULXMSG01.am.sony.com> (raw)
In-Reply-To: <20190822122703epcms5p820209c77bb679e8a99b5292b3cdbf62a@epcms5p8>

Dhinakar,

Thanks for the suggestion.  The QuickStart guide does not have the full description
of options to install.sh.  The page http://fuegotest.org/wiki/Installing_Fuego is intended
to have complete information, and it mentions --priv.

However, I think some of the material you have would be good
to add to the page.  I'll try to work on this next week when I'm back in the office.

Thanks for the suggestions.
 -- Tim


> -----Original Message-----
> From: Dhinakar Kalyanasundaram 
> 
> Hi Tim,
> 
> 
> 
> Thanks for the Fuego Release v1.5.0 (Flame).
> 
> I have some suggestions on the quick steps provided in
> http://fuegotest.org/wiki/Fuego_Quickstart_Guide to download, build, start
> and access fuego.
> 
> It is better to mention about '--priv' option and providing your own name for
> the docker image to the 'install.sh' script.
> 
> I have provided the details below. If you feel it is good to have these
> information, please update the 'Fuego_Quickstart_Guide'.
> 
> 
> 
> $ git clone https://bitbucket.org/fuegotest/fuego.git
> 
> $ cd fuego
> 
> ~/fuego$ ./install.sh
> 
> 
> 
> To run the container in a special privileged mode that allows access to host
> USB devices (needed for accessing Android targets and USB-SERIAL devices),
> create it using the "--priv" command line option
> 
> ~/fuego$ ./install.sh --priv
> 
> 
> 
> By default, install.sh creates a docker image called 'fuego' and a docker
> container called 'fuego-container'.
> 
> To provide a customized name for the docker image provide additional
> parameter to ./install.sh as given below.
> 
> ~/fuego$ ./install.sh --priv fuego-base-image-20thaug2019
> 
> 
> 
> Cloning of fuego-core gets started, and by default port 8090 will be used as
> shown below.
> 
> ……..
> 
> Cloning into 'fuego-core'...
> remote: Counting objects: 11269, done.
> remote: Compressing objects: 100% (613/613), done.
> remote: Total 11269 (delta 334), reused 0 (delta 0)
> Receiving objects: 100% (11269/11269), 272.61 MiB | 795.00 KiB/s, done.
> Resolving deltas: 100% (7259/7259), done.
> Checking out files: 100% (1197/1197), done.
> Using Port 8090
> Sending build context to Docker daemon  559.3MB
> …….
> 
> The following console messages will appear at the end of a successful
> installation.
> 
> …….
> 
> Successfully built 6392cddfcb05
> Successfully tagged fuego-base-image-20thaug2019:latest
> 5812e109f4e085e737ae487361bd5c7414db6e9a8c30f93a8af68f74ebaf4dd0
> Docker container 'fuego-base-image-20thaug2019-container' is ready with
> Fuego installation.
> To start, run: ./start.sh fuego-base-image-20thaug2019-container
> …….
> 
> 
> To start the default container use 'start.sh' as shown below:
> 
> ~/fuego$ ./start.sh
> 
> 
> 
> To start your custom container provide additional parameter to ./start.sh as
> given below.
> 
> ~/fuego$ ./start.sh fuego-base-image-20thaug2019-container
> 
> …….
> 
> The following console messages gets displayed if the container is successfully
> started.
> 
> -------
> Starting Fuego container (fuego-base-image-20thaug2019-container)
> Correct java version found
> [ ok ] Starting Jenkins Automation Server: jenkins.
> [ ok ] Starting network benchmark server.
> …….
> 
> 
> 
> Fuego interface can be accessed using the below url.
> 
> $ firefox http://107.108.73.106:8090/fuego/
> 
> 
> 
> Regards,
> 
> Dhinakar
> 
> 
> 
> 
> 
> --------- Original Message ---------
> 
> Sender : Tim.Bird@sony.com <Tim.Bird@sony.com>
> 
> Date : 2019-08-15 08:57 (GMT+5:30)
> 
> Title : [Fuego] ANNOUNCE: Fuego Release v1.5.0 (Flame)
> 
> 
> 
> Hello everyone,
> 
> I am pleased to announce the release of Fuego version 1.5.0, nicknamed
> "Flame".
> Below are the release notes for this version.  There are a few outstanding
> bugs
> that didn't get fixed in this release (that's always true), but overall the system
> is
> a big improvement from the 1.4 release.
> 
> Thank you to everyone who has contributed to this release.
> 
> REQUEST:  Please test the release and let me know if anything in your Fuego
> workflow has broken.
> 
> The release can be found in the master branches on the repositories on
> bitbucket,
> for the fuegotest account.  The v1.5.0 release is available with:
>  $ git clone https://bitbucket.org/fuegotest/fuego.git
> 
> See  http://fuegotest.org/wiki/Fuego_Quickstart_Guide for the instructions
> to install
> this release.  Note that some instructions have changed.  Hopefully they
> have been
> simplified from previous releases.
> 
> I did a pass over the wiki to update the documentation to reflect changes
> in directory paths, default TCP/IP ports, and repository URLs.  However,
> I may have missed something.  If you see something wrong in the Fuego
> documentation please let me know.
> 
> Below is the CHANGELOG for this release.  A full set of release notes, with
> detailed descriptions of new features and a list of new tests is available on
> the fuegotest wiki.  Please see http://fuegotest.org/wiki/Release_1.5_Notes
> 
> Regards,
>  -- Tim
> 
> -- CHANGELOG --
> == [1.5.0] - 2019-08-14 ==
>  * Added a new "batch test" feature
>    * Added ability to manually group tests by batch-id, from the command line
>  * Added some new functions to core, for use by test programs:
>    * run_test
>    * allocate_next_batch_id
>  * Simplified directory layout for the Fuego system
>  * Changed the default port to 8090, from 8080
>  * New options to install.sh
>    * Ability to specify the TCP port for the Jenkins server
>    * Ability to build a docker container that does not include a Jenkins server
>    * Ability to build a docker container without using the docker image cache
>  * Ability to install Fuego directly to a host machine
>     (not inside a docker container)
>  * Upgraded Fuego base Linux distro to Debian stretch
>  * Upgraded Jenkins version to 2.164.1
>  * Added many new tests
>  * Added prototype support for sending results to a Squad and fserver back
> ends
>  * Added new transport: ssh2serial - for ssh to a control board to
>     which the target board is connected by serial port
>  * Added prototype support for board power management via ftc
>  * Fixed output from serio, to support live update of the console log during
>     a command
> _______________________________________________
> Fuego mailing list
> Fuego@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/fuego
> 
> 
> 
> <http://ext.samsung.net/mail/ext/v1/external/status/update?userid=dhina
> kar.k&do=bWFpbElEPTIwMTkwODIyMTIyNzAzZXBjbXM1cDgyMDIwOWM3N
> 2JiNjc5ZThhOTliNTI5MmIzY2RiZjYyYSZyZWNpcGllbnRBZGRyZXNzPVRpbS5CaX
> JkQHNvbnkuY29t>

  reply	other threads:[~2019-08-23 17:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-15  3:27 [Fuego] ANNOUNCE: Fuego Release v1.5.0 (Flame) Tim.Bird
     [not found] ` <CGME20190815032727epcas3p36e1d1a2aa7471fa5ac20c14399c83a8d@epcms5p8>
2019-08-22 12:27   ` Dhinakar Kalyanasundaram
2019-08-23 17:56     ` Tim.Bird [this message]
     [not found]     ` <CGME20190815032727epcas3p36e1d1a2aa7471fa5ac20c14399c83a8d@epcms5p7>
2019-08-26  8:00       ` Dhinakar Kalyanasundaram

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=ECADFF3FD767C149AD96A924E7EA6EAF977A4CC1@USCULXMSG01.am.sony.com \
    --to=tim.bird@sony.com \
    --cc=dhinakar.k@samsung.com \
    --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.