toxcore/.travis/bazel-linux

#!/bin/sh

ACTION="$1"

set -eu

travis_install() {
  # Get bazel.
  wget https://github.com/bazelbuild/bazel/releases/download/0.16.0/bazel-0.16.0-installer-linux-x86_64.sh
  chmod +x bazel-0.16.0-installer-linux-x86_64.sh
  ./bazel-0.16.0-installer-linux-x86_64.sh --user
  echo 'build --jobs=4 --curses=no --verbose_failures' >> $HOME/.bazelrc
  echo 'build --config=linux' >> $HOME/.bazelrc
  echo "build --config=$CC" >> $HOME/.bazelrc
  pip install --user yamllint
}

travis_script() {
  bazel test \
    //c-toxcore:license_test \
    //c-toxcore:readme_test \
    //c-toxcore:yamllint_test

  # TODO(iphydf): Make tests have a chance to succeed.
  # Run the tests, but if they fail, at least we should be able to build.
  # bazel test //c-toxcore/... || bazel build //c-toxcore/...
  bazel build //c-toxcore/...
}

if [ "-z" "$ACTION" ]; then
  "travis_script"
else
  "travis_$ACTION"
fi
Add the bazel build as one of the PR-blocking builds. 2018-07-11 00:12:10 +08:00			`#!/bin/sh`

			`ACTION="$1"`

			`set -eu`

			`travis_install() {`
			`# Get bazel.`
Run project tests like yamllint_test. We check that: * The license is GPLv3. * .travis.yml conforms with the toktok style specification. * There exists a README.md file. 2018-08-19 07:32:04 +08:00			`wget https://github.com/bazelbuild/bazel/releases/download/0.16.0/bazel-0.16.0-installer-linux-x86_64.sh`
			`chmod +x bazel-0.16.0-installer-linux-x86_64.sh`
			`./bazel-0.16.0-installer-linux-x86_64.sh --user`
Add the bazel build as one of the PR-blocking builds. 2018-07-11 00:12:10 +08:00			`echo 'build --jobs=4 --curses=no --verbose_failures' >> $HOME/.bazelrc`
Use `--config` to tell bazel about the environment. Instead of importing a well-known file. This gives toktok-stack more freedom in where and how it wants to define its interface, as long as it provides the configurations requested ("linux" and "clang"). 2018-08-15 04:34:24 +08:00			`echo 'build --config=linux' >> $HOME/.bazelrc`
			`echo "build --config=$CC" >> $HOME/.bazelrc`
Run project tests like yamllint_test. We check that: * The license is GPLv3. * .travis.yml conforms with the toktok style specification. * There exists a README.md file. 2018-08-19 07:32:04 +08:00			`pip install --user yamllint`
Add the bazel build as one of the PR-blocking builds. 2018-07-11 00:12:10 +08:00			`}`

			`travis_script() {`
Add tool to find directly recursive calls in toxcore. We should avoid recursion, as it makes reasoning about stack growth harder. This tool shows (currently) 4 (non-tail) recursive functions, at least 2 of which are easy to fix. 2018-08-27 23:51:41 +08:00			`bazel test \`
			`//c-toxcore:license_test \`
			`//c-toxcore:readme_test \`
			`//c-toxcore:yamllint_test`
Run project tests like yamllint_test. We check that: * The license is GPLv3. * .travis.yml conforms with the toktok style specification. * There exists a README.md file. 2018-08-19 07:32:04 +08:00
Stop running tests in the bazel build. These always fail at present. We'll need to look into making them not always fail so we can enable them and get some useful signal from them. 2018-08-12 22:24:38 +08:00			`# TODO(iphydf): Make tests have a chance to succeed.`
Add the bazel build as one of the PR-blocking builds. 2018-07-11 00:12:10 +08:00			`# Run the tests, but if they fail, at least we should be able to build.`
Stop running tests in the bazel build. These always fail at present. We'll need to look into making them not always fail so we can enable them and get some useful signal from them. 2018-08-12 22:24:38 +08:00			`# bazel test //c-toxcore/... \|\| bazel build //c-toxcore/...`
			`bazel build //c-toxcore/...`
Add the bazel build as one of the PR-blocking builds. 2018-07-11 00:12:10 +08:00			`}`

			`if [ "-z" "$ACTION" ]; then`
			`"travis_script"`
			`else`
			`"travis_$ACTION"`
			`fi`