[Fuego] [PATCH] Fuego Release Test Repository
guicc at profusion.mobi
Tue Feb 20 02:31:53 UTC 2018
On Mon, Feb 19, 2018 at 10:12 PM, <Tim.Bird at sony.com> wrote:
> > -----Original Message-----
> > From: Tim.Bird
> > > -----Original Message-----
> > > From: Guilherme Campos Camargo
> > > Hello, everyone
> > >
> > > This repository
> > What repository? https://bitbucket.org/profusionmobi/fuego?
> > I see a repository on bitbucket, under profusionmobi, called
> > 'fuego-release-test'? Is that the one? I can find no mention
> > of the repository below...
> > I presume I clone something, then run build_and_run.sh?
> > Do I need to have any fuego materials pre-installed?
> > (the 'driving' fuego?)
> I have several instances of Fuego available on my machine, but I wasn't
> sure if one of these was supposed to be running when I ran
You shouldn't need to have any of them running. fuego-release-test should
> I did this:
> $ git clone https://bitbucket.org/profusionmobi/fuego-release-test
> $ cd fuego-release-test
> $ ./build_and_run.sh -p 8080 up
> Error: no such container: fuego-rt-container
> Am I supposed to have a container named 'fuego-rt-container'?
> I see other command line options:
> -c to start from scratch
> -d to run in detached mode
> Should I be using these?
Sorry, Tim. As I explained in my last e-mail, just use
$./build_and_run.sh -c -p 8080 up
There's a bug that's requiring -c on the first time - to create the
> What is the meaning of 'up' and 'down'. Sorry, but I'm confused
> about how this works.
'up' would create the container (if not already present), then start it.
'down' would just 'stop' the container.
A user would then be able to restart by running './build_and_run.sh up'
or 'start from scratch' (erasing all saved data/logs/test results) by using
'./build_and_run -c up'.
> Please help.
> -- Tim
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Fuego