Support for bundling Chromium unittests into a tarball.

blimp/BUILD.gn

Index: blimp/BUILD.gn
diff --git a/blimp/BUILD.gn b/blimp/BUILD.gn
index 14408f934809126833c08aa239b194013a9995a5..4ac99d598103dcffddf24b0dcd216a67a2e4b158 100644
--- a/blimp/BUILD.gn
+++ b/blimp/BUILD.gn
@@ -138,3 +138,41 @@ if (is_linux) {
     ]
   }
 }
+
+# Builds and bundles the tests into a tarball that can be used to build a
+# Docker image.
+action("blimp_engine_env_tests_bundle") {
+  testonly = true
+  script = "//blimp/tools/bundle.py"
+
+  # These form the arguments to the script.
+  _rebased_out_dir = rebase_path(root_out_dir)
+  _rebased_dockerfile = rebase_path("//blimp/Dockerfile")
+  _bundle = "$root_out_dir/blimp_engine_env_tests_bundle.tar.gz"
+
+  # Depending on this ensures that both the manifest is generated
+  # and everything in the manifest has been built.
+  deps = [
+    ":generate_blimp_engine_env_tests_manifest",
+  ]
+
+  sources = [
+    _blimp_engine_env_tests_manifest,

[Sriram, 2016/06/02 19:55:05]

Should this be _rebased_blimp_engine_env_tests_manifest? It is not clear as when
one would use rebased version vs not.

[Jess, 2016/06/02 23:02:14]

Nope. That will fail to build.

The issue is that rebasing is being used to set arguments to both the root and
gen dir. The naming convention I copied from engine bundling tracks if a rebase
occurred rather than which root directory a file is part of. That code should
probably be refactored too, but it might be best to tackle that in a stand alone
codereview.

https://chromium.googlesource.com/chromium/src/+/master/tools/gn/docs/languag...

+    _rebased_dockerfile,
+  ]
+  outputs = [
+    _bundle,
+  ]
+
+  # Manually specify the actual arguments to the script.
+  args = [
+    "--build-dir",
+    _rebased_out_dir,
+    "--dockerfile",
+    _rebased_dockerfile,
+    "--manifest",
+    _rebased_blimp_engine_env_tests_manifest,
+    "--output",
+    rebase_path(_bundle),
+  ]
+}