-
Notifications
You must be signed in to change notification settings - Fork 2
Update tarantool if there is more fresh version #14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
As I see, the 'Setup from cache' step in CI has more or less same timing as before. It was 2-4 seconds and here we see 2-4 seconds. That's nice! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The logic looks good. (I didn't test it, just glanced over the changed code.)
No objections from me.
732abb6
to
b9fa7f1
Compare
I've reorganized the code. It was necessary for adding a test. Re-approve please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No objections from my side.
b9fa7f1
to
b7589b7
Compare
Once a version is installed it's cached. A user could drop the cache manually (by updating cache-key), but it should be automated. This patch changes the caching logics. The 'cache-key' input is deprecated. Instead, it includes precise deb package version which is obtained by parsing repo content manually: ```js http_get("https://download.tarantool.org/tarantool/release/2.6" + "/ubuntu/dists/focal/main/binary-amd64/Packages" ) ``` It doesn't waste too much time and allows us to reinstall tarantool from apt-get when the new verison is out. Resulting key looks like ```txt tarantool-setup-focal-2.8.0.0.gefc30ccf8-1 ```
b7589b7
to
3defc67
Compare
The patch resolves the problem described in #9 (comment).
Once a version is installed it's cached. A user could drop the cache manually (by updating the
cache-key
), but it should be automated.This patch changes the caching logic. The
cache-key
input is deprecated. Instead, it's generated and includes a precise deb package version which is obtained by parsing repo content manually:It doesn't waste too much time and allows us to reinstall tarantool from apt-get when the new version is out.
The resulting
cache-key
looks liketarantool-setup-focal-2.8.0.0.gefc30ccf8-1
.