use make instead of lots of files

.circleci/config.yml

@@ -5,4 +5,4 @@ jobs:
       - image: mijitt0m/ocelot-build:0.0.1
     steps:
       - checkout
-      - run: ./build.sh
+      - run: make build

Dockerfile

@@ -6,4 +6,4 @@ COPY ./. .
 
 RUN chmod u+x build.sh
 
-RUN /bin/bash -c "/src/build.sh"
+RUN make build

Makefile

@@ -0,0 +1,22 @@
+NAME ?= ocelot
+
+build:
+	./build.sh
+
+build_and_release_unstable:
+	./build.ps1 -target BuildAndReleaseUnstable && exit $LASTEXITCODE
+
+build_and_run_tests:
+	./build.ps1 -target RunTests && exit $LASTEXITCODE
+
+release:
+	./build.ps1 -target Release && exit $LASTEXITCODE
+
+run_acceptance_tests:
+	./build -target RunAcceptanceTests && exit $LASTEXITCODE
+
+run_benchmarks:
+	./build.ps1 -target RunBenchmarkTests && exit $LASTEXITCODE
+
+run_unit_tests:
+	./build.ps1 -target RunUnitTests && exit $LASTEXITCODE

docs/building/building.rst

@@ -3,8 +3,6 @@ Building
 
 * You'll generally want to run the `./build.ps1` script. This will compile, run unit and acceptance tests and build the output packages locally. Output will got to the `./artifacts` directory.
 
-* You can view the current commit's `SemVer <http://semver.org/>`_ build information by running `./version.ps1`.
-
 * The other `./*.ps1` scripts perform subsets of the build process, if you don't want to run the full build.
 
 * The release process works best with GitFlow branching; this allows us to publish every development commit to an unstable feed with a unique SemVer version, and then choose when to release to a stable feed.