From: "Bird, Timothy" <Tim.Bird@sony.com>
To: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>,
'dhinakar k' <dhinakar.k@gmail.com>
Cc: "fuego@lists.linuxfoundation.org" <fuego@lists.linuxfoundation.org>
Subject: Re: [Fuego] Fuego 1.1 version error during install
Date: Wed, 12 Apr 2017 02:50:20 +0000 [thread overview]
Message-ID: <ECADFF3FD767C149AD96A924E7EA6EAF104BF4C3@USCULXMSG01.am.sony.com> (raw)
In-Reply-To: <00ae01d2b31b$dde09ea0$99a1dbe0$@toshiba.co.jp>
> -----Original Message-----
> From: Daniel Sangorrin Tuesday, April 11, 2017 4:32 PM
>
> > -----Original Message-----
> > From: dhinakar k [mailto:dhinakar.k@gmail.com]
> > Sent: Monday, April 10, 2017 9:01 PM
> > Thanks for your response.
> > It seems the problem is due to the Jenkins port & service issue. I was have
> plain vanilla Jenkins running at 8080 port and wanted to
> > setup Fuego at 8081. So temporarily stopped Jenkins service @8080. This
> caused the issue. Now I have swapped the ports so that I can
> > go with defaults to make things easy for Fuego. So that issue is solved now.
>
> Thanks for reporting Dhinakar.
> I will add support for specifying a different port to the Dockerfile.
Daniel,
Note that ftc has the port embedded in it also. Right now the port is hardcoded,
but I plan to read the ftc config parameters from a config file in the future.
I'll let you know when I work on this, where the file will be, and what
values to change in it to have ftc use the right URL or port.
-- Tim
prev parent reply other threads:[~2017-04-12 2:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-08 5:08 [Fuego] Fuego 1.1 version error during install dhinakar k
2017-04-10 1:52 ` Daniel Sangorrin
2017-04-10 12:01 ` dhinakar k
2017-04-11 23:32 ` Daniel Sangorrin
2017-04-12 2:07 ` dhinakar k
2017-04-12 2:50 ` Bird, Timothy [this message]
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=ECADFF3FD767C149AD96A924E7EA6EAF104BF4C3@USCULXMSG01.am.sony.com \
--to=tim.bird@sony.com \
--cc=daniel.sangorrin@toshiba.co.jp \
--cc=dhinakar.k@gmail.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.