When running the "swupd verify" command to install the base OS and the
selected bundles, the progress of the command execution was just being
shown as a progress bar that was looping until the swupd command
finished. This approach was not ideal since this process can take
several minutes to complete, and since the progress bar was just
spinning it didn't provide a real feedback for the user to know in what
part the process was. This can trigger some anxiety in users.
This commit solves this problem by using the machine readable output
from swupd to determine the exact part of the process where the install is
and report this to the user using a series of steps along with a progress
bar (or percentage value in not TUI installer) that shows how far the
step has gotten.
Signed-off-by: Castulo Martinez <castulo.martinez@intel.com>
Now users may defined environment variables to be used in the image
generation. Also, these variables are passed down to the pre and post
install hook scripts.
Signed-off-by: Leandro Dorileo <leandro.maciel.dorileo@intel.com>
Command run through PipeRunAndLog would hang waiting for standard input.
We were overwriting the defined stdin input stream.
Signed-off-by: Mark D Horn <mark.d.horn@intel.com>
Introduce the initial support to post-install hooks. The code also
expands a set of pre-defined variables, for now the only exposed
variable is the chrootDir (the directory where the target system is
mounted).
Signed-off-by: Leandro Dorileo <leandro.maciel.dorileo@intel.com>
This patch introduces the local-travis, an small util program locally
emulate the remote travis execution. The program will read the travis
yaml file and execute the tasks.
The program is not intended to be manually executed but wrapped by
"make check-coverage". The program uses the env var TRAVIS_CONF to
know where to find the travis yaml file (the makefile will have it all
set for you).
We also use the http_proxy, https_proxy and no_proxy if they are set.
If we're executing a docker command that supports -e flag then these
variables are also handled.
The check-coverage.sh script will also auto update the coverage database
and commit the changes if it detects a coverage increase. In order to
do that check-coverage will only update the database if there's no
unstaged changes in the tree and if it's being executed with
make check-coverage.
Signed-off-by: Leandro Dorileo <leandro.maciel.dorileo@intel.com>
This is code is still alpha. The Text-based User Interface is
undergoing a resign of the layout before beta.
Signed-off-by: Mark D Horn <mark.d.horn@intel.com>
Castulo Martinez