- Apr 08, 2024
-
-
Bogdan Berezovskiy authored
-
- Feb 26, 2024
-
-
EmirVildanov authored
-
- Jan 31, 2024
-
-
Georgy Moshkin authored
-
- Jan 19, 2024
-
-
Dmitry Rodionov authored
New feature `static_build` is added to Cargo.toml. By default dynamic build is being used. build.rs is changed to respect it. Use `cargo build --features static_build` to build static binary. Previous attempt directly modified static-build cmake files which is less convenient and doesnt allow us to support both build types at the same time Replaces https://git.picodata.io/picodata/tarantool/-/merge_requests/143 and https://git.picodata.io/picodata/picodata/picodata/-/merge_requests/817
-
- Dec 26, 2023
-
-
- Aug 18, 2023
-
-
Yaroslav Dynnikov authored
Also fix some fresh clippy warnings
-
- Aug 01, 2023
-
-
Egor Ivkov authored
-
- Apr 14, 2023
-
-
Georgy Moshkin authored
-
- Apr 06, 2023
-
-
Егор Ивков authored
-
- Nov 23, 2022
-
-
These libs installed in Dockerfile aren't used for the build. Instead, tarantool is built with sources from `vendored` directory.
-
- Nov 08, 2022
-
-
Georgy Moshkin authored
-
- Oct 31, 2022
-
-
Yaroslav Dynnikov authored
The whole CI is refactored. The following problems are solved: 1. Couldn't test base image locally without overriding the old one. The testing stage is run in two ways depending on whether some of the docker-related files were changed. If they didn't (most likely), testing stage is run on the `latest` docker image as it used to. Otherwise, the docker image is rebuilt locally and tested. This is done by using `image:pull_policy` option, see [1]. It also makes a problem of using protected credentials irrelevant. 2. Gitlab caching used to be slow Stupid gitlab caching (see [2]) wasted on (un)zipping cache 4 minutes (of 6 total). Now it's replaced with a manual one: an archive (tar) is placed in a docker volume on a self-hosted gitlab runner with no compression. 3. Speed up fetching git. The tarantool-sys submodule requires a tag to be built correctly, but using shallow clones prevented that. We used to work-around it by specifying `GIT_DEPTH: 0`, but that's sub-optimal too. This patch introduces an elegant yet reliable solution: ``` until git describe; do git fetch --deepen 100; done ``` 4. No fine-grained time tracking was available Gitlab only shows the total time of `step_script` without splitting it into particular commands. This problem is solved by incorporating collapsible log sections feature, see [3]. It makes logs fancy too. Refs: - [1] https://docs.gitlab.com/ee/ci/yaml/#imagepull_policy - [2] https://gitlab.com/gitlab-org/gitlab-runner/-/issues/3523 - [3] https://docs.gitlab.com/ee/ci/jobs/#custom-collapsible-sections
-
Move build base on Ubuntu 22.04
-
- Oct 16, 2022
-
-
Valentin Syrovatskiy authored
-
- Aug 29, 2022
-
-
- Aug 23, 2022
-
-
Valentin Syrovatskiy authored
-
- May 30, 2022
-
-
- Apr 28, 2022
-
-
Sergey V authored
-
- Feb 21, 2022
-
-
Yaroslav Dynnikov authored
-
- Feb 18, 2022
-
-
Georgy Moshkin authored
+ tarantool-sys submodule + tarantool-patches directory + build.rs build script to patch and build tarantool + static linking with tarantool + refactoring for cli arguments
-
- Feb 15, 2022
-
- Jan 19, 2022
-
-
Sergey V authored
-
- Dec 20, 2021
-
-
Yaroslav Dynnikov authored
-