[Fuego] [PATCH] Allow ftc script to properly use Jenkins configured port
Tim.Bird at sony.com
Thu Feb 8 20:02:43 UTC 2018
> hi tim, so could you consider moving to Python's ConfigParser? Saves
> code, uniform file format... just misses the "source conf" in bash,
> but I wonder if that will be needed. In any case you can provide a
> tool such as others do (docker-machine env, etc), which would convert
> to plain shell variables (basically read and print as "%s=%r" % (key,
Actually, thinking about this more...
Maybe we should add an 'ftc config' command, similar to 'git config',
that would allow reading one variable. Then we could do something like:
jenkins_port="$(ftc config jenkins_port)"
in entrypoint.sh (and similar code in other places in fuego).
Then we could switch to some standard parser like Python's.
More information about the Fuego