[aerogear-dev] [digger-build-cli] thoughts around the CLI usage

Leonardo Rossetti lrossett at redhat.com
Tue Oct 18 05:04:18 EDT 2016


Hello,

I was thinking on some enhancements around the CLI usage:

*Log files*
Right now it automatically saves the command output into a text file, but
it wouldn't need to since you can always use a pipe to to that like "abcd
buid > build.log" or "abcd build | tee build.log".

*Setup command*
A setup command to set default configurations "abcd setup" such as default
android debug keystore config, android home path, cordova path, etc.

*Build config file*
An optional hidden yaml/json file ".digger" or ".abcd" that would have some
information for the CLI such as the build type and platform ("andoid" and
"gradle" for example) in the future this could also specify a different
build version or path to use.

*Debug flag*
Commands that start another process (such as "build' or "sign") could use a
flag "--debug" which if set to true would output everything into stdout,
otherwise would just print the actual command response (for example the
build command would output a list of generated APKs). Default value for
debug would be true.

WDYT?
-- 
Leonardo Rossetti
lrossett at redhat.com
+55 11 99703 0621
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20161018/e218f1a4/attachment.html 


More information about the aerogear-dev mailing list