From f723b8b878a3c4a4687b9e337a875500bebb39b1 Mon Sep 17 00:00:00 2001 From: Vincent Ambo Date: Thu, 4 Jul 2019 11:18:12 +0100 Subject: feat(third_party/bazel): Check in rules_haskell from Tweag --- .../bazel/rules_haskell/tests/run-start-script.sh | 30 ++++++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100755 third_party/bazel/rules_haskell/tests/run-start-script.sh (limited to 'third_party/bazel/rules_haskell/tests/run-start-script.sh') diff --git a/third_party/bazel/rules_haskell/tests/run-start-script.sh b/third_party/bazel/rules_haskell/tests/run-start-script.sh new file mode 100755 index 000000000000..6803581f0010 --- /dev/null +++ b/third_party/bazel/rules_haskell/tests/run-start-script.sh @@ -0,0 +1,30 @@ +#!/bin/sh + +# Run the start script in its own workspace +# and build the example binary target. + +set -e + +pwd=$(pwd) +cd $(mktemp -d) +$pwd/start + +# Copy the bazel configuration, this is only useful for CI +mkdir tools +cp $pwd/.bazelrc .bazelrc + +# Set Nixpkgs in environment variable to avoid hardcoding it in +# start script itself. + +# overrides the used rules_haskell, because +# when we're testing the start on a feature branch (CI), +# the latest rules_haskell version doesn't always work. +# If on the branch we update Bazel to a version with breaking +# changes, then we need to adapt to those changes in the branch. +# Which in turn means the start script should pull in those changes too. + +NIX_PATH=nixpkgs=$pwd/nixpkgs/default.nix \ + bazel build \ + --config=ci \ + --override_repository=io_tweag_rules_haskell=$pwd \ + //:example -- cgit 1.4.1