-
Notifications
You must be signed in to change notification settings - Fork 32
Extend CI tests to include 2.10 and master + add EE #339
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
Comments
Regarding EE: we investigated this topic in golang connector and you can consider results in tarantool/go-tarantool#183. Regarding 2.10: the best option is to add support for the new tarantool versions into setup-tarantool action. I'm working on it. Precisely, I'm working on ability to set exact versions (like 1.10.8) and then plan to work on 2.10 support. However you can consider tricks implemented in CI for the smtp module: it directly installs necessary tarantool versions. |
Update: I resolved tarantool/setup-tarantool#19, so Beware: Don't forget quotes around |
Duplicate of #331? |
Not exactly, I also want to include tarantool master here. |
You can copy-paste tarantool/expirationd#117 for example. |
This patch inroduce CI testing on the latest git version of Tarantool, which is built as `Debug`. By default master branch is used. However, any other one can be used too: just change everything after `debug-` to another name. Part of tarantool#339
This patch inroduce CI testing on the latest git version of Tarantool, which is built as `Debug`. By default master branch is used. However, any other one can be used too: just change everything after `debug-` to another name. Part of #339
I have no idea how to do it, so here is the ticket.
Update: only EE support is left. Preferably of multiple versions of EE.
The text was updated successfully, but these errors were encountered: