tree 6d9b6435ed817ca05b50f3cfa00c0fd0d228f381
parent d78d291b2ba2bae1ad5e370672bcd66decda80f6
author Nicolas Lopez <nlopezgi@gmail.com> 1540839780 -0400
committer GitHub <noreply@github.com> 1540839780 -0400
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJb11lkCRBK7hj4Ov3rIwAAdHIIAHeNqJsXd6knHr1y1d9ph7aL
 LkM/dCPUBv0cRbz8Krh76YlDroWXJ4dfscvYJ/j8mull53O97/9c3fxgoy2w+/rQ
 NuTSBu5DW55cmO+c84cqv4X1JRZwkpCxsvYJ/KSavMwe6eZr2yM0yfRkvkyBQN4A
 yca12d6M7p+H6QA6WXN95QMnJzS7YgPSR725u45eX1HJ7BKMm24es049bxX53nuT
 xzzqyUtX+b2NgAvc9XhCVMxeRlv5aIgGW6qRWrYY/l9j4WU9dHEZe5xzs9etzVzR
 eq2G409lHDQq8jD3tKdknicYp6Dpb0v3NtYzRVxrOQOU5XC24tT11DqsY+xMMNU=
 =MMVB
 -----END PGP SIGNATURE-----
 

Produce docker autoconfig logs (#1) (#223)

* Produce docker autoconfig logs (#1)

Docker autoconfig is not printing out anywhere the results of executing commands inside the container. This PR adds a new output to the rule that produces the log.
Example outputs produced by an autoconfig rule:
Target //tests/config:ubuntu-xenial-autoconfig up-to-date:
bazel-bin/tests/config/ubuntu-xenial-autoconfig-layer.tar
bazel-bin/tests/config/ubuntu-xenial-autoconfig.tar
bazel-bin/tests/config/ubuntu-xenial-autoconfig.digest
bazel-bin/tests/config/ubuntu-xenial-autoconfig_log.log
bazel-bin/tests/config/ubuntu-xenial-autoconfig_outputs.tar

* produce message to debug errors

* resolved review comments
* added print message in rule that shows instructions for reproducing
execution of docker container. Rule prints out (example):

== Docker autoconfig will run. ==
To debug any errors run:
> docker run -d <image_id> bash
Where <image_id> is the image id printed out by the ubuntu-xenial-autoconfig_extract.tar rule.
Then run:
>/ubuntu-xenial-autoconfig_install.sh
from inside the container.