Skip to content

Commit 60fa1dc

Browse files
committed
docs on crontab usage
1 parent f0bc481 commit 60fa1dc

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

src/BenchmarksApps/TLS/crank/agent/README.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,21 @@
44

55
### Crontab configuration
66

7+
Machines are configured to perform a git pull, get latest changes, rebuild crank and restart it once in a while. On linux machines it is happening via `cron`.
8+
In order to be able to use Dockerfile from this folder (`/crank/agent`), one should change the crontab.
9+
710
To lookup crontab configured:
811
```
912
sudo crontab -l
1013
```
1114

15+
You can use crontab like this:
16+
```
17+
0 0 * * * cd /home/dotnetperfuser/src/crank/docker/agent; ./stop.sh; docker rm -f $(docker ps -a -q --filter "label=benchmarks"); docker system prune --all --force --volumes; git checkout -f main; git reset --hard; git pull; cd /home/dotnetperfuser/src/Benchmarks; git checkout -f main; git reset --hard; git pull; cp -rf /home/dotnetperfuser/src/Benchmarks/src/BenchmarksApps/TLS/crank/agent/* /home/dotnetperfuser/src/crank/docker/agent/; cd /home/dotnetperfuser/src/crank/docker/agent; ./build.sh <arguments>; ./run.sh <arguments>
18+
```
19+
20+
Cron tab does the following:
21+
1) fetches the latest dotnet/crank
22+
2) fetches latest aspnetcore/Benchmarks
23+
3) copies dockerfile from aspnetcore/Benchmarks into dotnet/crank
24+
4) builds and runs the crank agent using custom Dockerfile

0 commit comments

Comments
 (0)