tk/Ocelot
1
0
Fork 0
mirror of https://github.com/nsnail/Ocelot.git synced 2025-06-19 15:28:16 +08:00
Code Issues Packages Projects Releases Wiki Activity

updated to remove develop

Browse Source
This commit is contained in:
TomPallister
2020-01-16 22:15:16 +00:00
parent 47efd86661
commit 0e6f44b342
11 changed files with 25 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/building/building.rst
View File

@ -1,10 +1,10 @@
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.
* The best way to build Ocelot is using the Dockerfile.build file which can be found in the docker folder in Ocelot root. Use the following command `docker build -f ./docker/Dockerfile.build .`.
* The other `./*.ps1` scripts perform subsets of the build process, if you don't want to run the full build.
* You'll can run the `./build.ps1` or `./build.sh` script depending on your OS. This will compile, run unit and acceptance tests and build the output packages locally. Output will got to the `./artifacts` directory.
* 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.
* There is a Makefile to make it easier to call the various targers in `build.cake`. The scripts are called with .sh but can be easily changed to ps1 if you are using Windows.
* Alternatively you can build the project in VS2017 with the latest .NET Core SDK.
* Alternatively you can build the project in VS2019 with the latest .NET Core SDK.