use make instead of lots of files

This commit is contained in:
TomPallister 2020-01-13 22:43:16 +00:00
parent fe60a97d27
commit ec7f0de562
13 changed files with 24 additions and 23 deletions

View File

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

View File

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

22
Makefile Normal file
View File

@ -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

View File

@ -1,2 +0,0 @@
./build.ps1 -target BuildAndReleaseUnstable
exit $LASTEXITCODE

View File

@ -1,2 +0,0 @@
./build.ps1 -target RunTests
exit $LASTEXITCODE

View File

@ -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'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 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. * 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.

View File

@ -1,2 +0,0 @@
./build.ps1 -target Release
exit $LASTEXITCODE

View File

@ -1,2 +0,0 @@
./build -target RunAcceptanceTests
exit $LASTEXITCODE

View File

@ -1,3 +0,0 @@
#!/usr/bin/env bash
./build.sh --target RunAcceptanceTests

View File

@ -1,2 +0,0 @@
./build.ps1 -target RunBenchmarkTests
exit $LASTEXITCODE

View File

@ -1,2 +0,0 @@
./build.ps1 -target RunUnitTests
exit $LASTEXITCODE

View File

@ -1,3 +0,0 @@
#!/usr/bin/env bash
./build.sh --target RunUnitTests

View File

@ -1 +0,0 @@
.\tools\GitVersion.CommandLine\tools\GitVersion.exe