diff options
| author | Alberto Sartori <alberto.sartori@huawei.com> | 2023-11-16 10:06:14 +0100 |
|---|---|---|
| committer | Alberto Sartori <alberto.sartori@huawei.com> | 2023-11-16 10:54:03 +0100 |
| commit | a22da1c7831b389809d085ff6867febba4dc95bc (patch) | |
| tree | 77184aaca5231e02334f37349403e3d3d17d882a /test/end-to-end/serve-service | |
| parent | a170c330955206e7df9d5ce7da1d196f24e283d8 (diff) | |
| download | justbuild-a22da1c7831b389809d085ff6867febba4dc95bc.tar.gz | |
remote-execution-endpoint: fall back to remote-serve-endpoint
If only the `--remote-serve-endpoint` option is specified on the
command line, the `--remote-execution-endpoint` is also set to the
given value.
This makes the spawning and usage of just-execute consistent. When
just-serve is started, if no remote execution endpoint is provided,
the same process will also act as a just-execute instance. With the
current patch, the client can thus only write, on command line, the
remote serve address, avoiding the repetition of the same address for
two different options.
Diffstat (limited to 'test/end-to-end/serve-service')
| -rw-r--r-- | test/end-to-end/serve-service/serve_start_execute.sh | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/test/end-to-end/serve-service/serve_start_execute.sh b/test/end-to-end/serve-service/serve_start_execute.sh index 6cc0448f..5cad0400 100644 --- a/test/end-to-end/serve-service/serve_start_execute.sh +++ b/test/end-to-end/serve-service/serve_start_execute.sh @@ -77,3 +77,10 @@ ENDTARGETS "${JUST}" install --local-build-root "${LBR}" -r localhost:${PORT} -o . grep 'just-serve-just-execute' out.txt + +# test that if we only pass --remote-serve-address it is also used as remote +# execution endpoint + +rm -rf "${LBR}" +"${JUST}" install --local-build-root "${LBR}" --remote-serve-address localhost:${PORT} -o . +grep 'just-serve-just-execute' out.txt |