Tipi documentation
- π Welcome to the Tipi Documentation
- π Getting started C++
- π¦ Getting started Rust (alpha)
- Key Principles and Goals
- Build by Convention
- Environments
- Compile options
- Authentication
- Dependencies and project configuration
- Ignore and exclude
- Running tests
- Build cache
- Share build cache across my team
- Downloading remote build results
- Data Security and Privacy
- Continuous integration
- Environment variables
- IDE Integration VSCode
Downloading remote build results
Starting with tipi v0.0.51
you can download build results directly onto your machine without downloading the full build directory.
Assuming we have a structure like this:
.
βββ src
β βββ string_to_json.cpp
β βββ stringstream_mayham.cpp
We can now build for linux-cxx17
the sources remotely like this:
tipi -t linux-cxx17 build .
Download a single file
Finally we can download the complete binary like this:
tipi -t linux-cxx17 download "./build/linux-cxx17/bin/src/string_to_json"
Download multiple files with a wildcard
Finally we can download the complete binaries like this:
tipi -t linux-cxx17 download "./build/linux-cxx17/bin/src/string*"
Note that you have to take care of shell expansion. If your local shell is able to find files that match the *
pattern it will pass just these paths to tipi.
Adding quotes solves this problem.
This will create a structure like this on your machine:
./build
βββ 24ba3b7
β βββ bin
β βββ src
β βββ string_to_json
β βββ stringstream_mayham
βββ linux-cxx17 -> /usr/local/share/.tipi/vC.w/1da57b4-stringstream_mayham.b/24ba3b7
Downloading the full build tree
To always synchronize the full build tree it's possible to build the application by appending --sync-build
to the command line :
tipi -t linux-cxx17 build . --sync-build
This can be a very big download following the build folder size.
Found an error or want to add more info? Write an issue or contribute changes to this documentation at tipi-build/docs on