7903: Use local repo for version and upgrade cli - #7904
Conversation
…into 7899-retrieve-cli-script-locally-when-available
67e9c94 to
f0e5dc7
Compare
762288c to
661eb33
Compare
f0e5dc7 to
6081942
Compare
661eb33 to
c1dd12a
Compare
6081942 to
95edad2
Compare
c1dd12a to
b7a61ac
Compare
95edad2 to
fb38637
Compare
b7a61ac to
62bfd93
Compare
fb38637 to
1c03b92
Compare
62bfd93 to
fbdc1c5
Compare
|
|
||
| If you have the CLI installed already it will be replaced with the version that is built. If the `runInDocker.sh` script | ||
| is different in the version you installed before, it will not be replaced. You can find it | ||
| at `$HOME/.local/bin/sleeper`, and manually overwrite it with the contents of `./scripts/cli/runInDocker.sh`. |
There was a problem hiding this comment.
It looks like the explanation in this paragraph is missing now?
There was a problem hiding this comment.
Will add something back in
| ./scripts/cli/install.sh | ||
| ``` | ||
|
|
||
| If you want to use a custom container registry with locally built images, pass the `--registry` flag: |
There was a problem hiding this comment.
I don't understand what this means, you can't use a container registry and locally built images at the same time?
| and put it on the system path. Then `sleeper ...` commands will work as though you'd installed it normally. | ||
| To install the CLI from the local repository, run the install script directly. It will detect `runInDocker.sh` | ||
| alongside it and use that instead of downloading from GitHub, and will record the local repository path so that | ||
| `sleeper cli upgrade` and `sleeper cli pull-images` continue to use the local version: |
There was a problem hiding this comment.
Is this correct? The build scripts tag with the local image tags. The install script pulls the remote images, and then re-tags them with the local image tags.
There was a problem hiding this comment.
I'm not sure I understand, this paragraph doesn't mention tagging at all?
|
This needs testing. #7614 is done now so it looks like it can be tested against that. |
1c03b92 to
7a4c41a
Compare
fbdc1c5 to
38297fa
Compare
61ba51c to
7e50919
Compare
d188bca to
8bbd5a5
Compare
7e50919 to
c525e60
Compare
8bbd5a5 to
7967a7c
Compare
c525e60 to
7a0f903
Compare
7967a7c to
cb8d6b0
Compare
…hub.com:gchq/sleeper into 7899-retrieve-cli-script-locally-when-available
…com:gchq/sleeper into 7903-use-local-repo-for-version-and-upgrade
…903-use-local-repo-for-version-and-upgrade
…custom registries
|
Can be re reviewed. I've tested with a custom registry but haven't been able to test with a version other that latest That testing will need to wait for the other registry to publish versions |
Make sure you have checked all steps below.
Issue
Feature". Note that before an issue is finished, you can still make a pull request by raising a separate issue
for your progress.
Tests
Documentation
separate issue for that below.