mirror of
https://github.com/nsnail/Ocelot.git
synced 2025-08-07 22:52:25 +08:00
Feat/net6.0 upgrade (#1558)
* +semver: major upgrading from net5.0 to net6.0 * packages upgraded * removed global.json for ocelot sf sample * update build image * test new build * remove make * fix tests * make test fail like in CI * tests passing locally * updated docs Co-authored-by: TGP <thomasgardham-pallister@Thomass-MacBook-Pro-2.local>
This commit is contained in:
@ -1,10 +1,10 @@
|
||||
Building
|
||||
========
|
||||
|
||||
* 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 .`.
|
||||
* You can also just run `dotnet tool restore && dotnet cake` locally!. Output will got to the `./artifacts` directory.
|
||||
|
||||
* 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 best way to replicate the CI process is to build Ocelot locally is using the Dockerfile.build file which can be found in the docker folder in Ocelot root. Use the following command `docker build --platform linux/amd64 -f ./docker/Dockerfile.build .` for example. You will need to change the platform flag depending on your platform.
|
||||
|
||||
* 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 VS2019 with the latest .NET Core SDK.
|
||||
* Alternatively you can build the project in VS2022 with the latest .NET 6.0 SDK.
|
@ -1,24 +1,7 @@
|
||||
Tests
|
||||
=====
|
||||
|
||||
The tests should all just run and work apart from the integration tests which need the following
|
||||
environmental variables setting. This is a manual step at the moment.
|
||||
|
||||
``OCELOT_USERNAME=admin``
|
||||
|
||||
``OCELOT_HASH=kE/mxd1hO9h9Sl2VhGhwJUd9xZEv4NP6qXoN39nIqM4=``
|
||||
|
||||
``OCELOT_SALT=zzWITpnDximUNKYLiUam/w==``
|
||||
|
||||
On windows you can use..
|
||||
|
||||
``SETX OCELOT_USERNAME admin``
|
||||
|
||||
On mac..
|
||||
|
||||
``export OCELOT_USERNAME=admin``
|
||||
|
||||
I need to work out a nicer way of doing this in the future.
|
||||
The tests should all just run and work as part of the build process. You can of course also run them in visual studio.
|
||||
|
||||
|
||||
|
||||
|
Reference in New Issue
Block a user