Releases: tinybirdco/ci
v4.1.0
v4.0.1
v3.1.1
v4.0.0
Starting from tinybird-cli 4.0.0 the --semver
flag and Releases
are deprecated.
The changes in this Release aim to reflect that deprecation, so in order to deploy changes to the main Workspace you should use the tb deploy
command.
Also we recommend you to create your own CI/CD pipelines. You can use the ones in this repository as a guide.
v3.1.0
What's Changed
Full Changelog: v3.0.0...v3.1.0
- Add new check job in GitHub Actions. It forces format Datafiles so there are no mismatches in the project when working from the UI and git. To activate it create set a tb_format: true input tinybird_ci.yml
- Remove rollback and rm jobs from GitHub Actions
- Remove release_rollback and release_rm from GitLab CI.
v3.0.0
Major Update to Version 3.0.0
We've upgraded from CLI 2.x to CLI 3.x. The main change in CLI 3.x is that introduces Releases and SemVer based deployments. See our Version Control guides for more details about it.
Important: Updating the CLI to this version is mandatory.
Additional Updates:
- CI job split into Deployment + Test.
- Idempotent deployments in CI and CD.
- Deploy script consolidation: Replaced
ci-deploy.sh
andcd-deploy.sh
with a unifieddeploy.sh
. - Added
postdeploy.sh
as a custom script to be run before the test job. It can be used to run data operations (such as populates), promote release, etc. - Added
append_fixtures.sh
for appending fixtures to the latest CI Branch Release. - Modified
exec_test.sh
to use the latests CI Branch Release. - Added
promote
job to change the state of a Release from Preview to Live. - Added
rollback
job to enabling automated rollback of changes in case of issues. - Added
dry_run_rm_oldest_rollback
andrm_oldest_rollback
jobs to delete the oldest rollback Release by creation date. - Introduced
CI_FLAGS
andCD_FLAGS
fortb deploy
, customizable per Data Project and PR in.tinyenv
. - Rename from Environment to Branch.
- Some CI performance optimizations.
Migration Guide:
For a smooth transition from v2.x to v3.x, please follow our detailed migration guide.
v2.5.1
- Fix error obtaining the data project version when the
.tinyenv
file lacks a newline character at the end. - Upgrade GitHub workflow python-version to 3.11
v2.5.0
v2.4.0
v2.3.0
- Support for a requirements.txt file inside the Data Project folder. That way you can control which version of the tinybird-cli to install.
- Environments in CI are now created with a fixed name using the Pull Request number in GitHub and the AUTHOR in GitLab.
- Environments are not cleaned up after CI finishes. This is a very convenient workflow to debug issues directly in the Environment with the changes of the branch deployed.
- Users updating from previous versions need to do some actions:
- GitHub: Add the closed type like this.
- GitLab: Change the rule to run the clean up job on merge:
.cli_rule:
&cli_cleanup_rule
if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH
changes:
- .gitlab-ci.yml
- ./**/*
when: always
run_ci__cli_telemetry:
extends: .run_ci
rules:
- *cli_cleanup_rule
variables:
<<: *cli_variables
If you have doubts when updating just drop the .github or .gitlab-ci.yml workflow and re-run tb init --git
using the latest version of tinybird-cli to re-generate the CI/CD templates.
-
.tinyenv now supports export
OBFUSCATE_REGEX_PATTERN=<regex>
to have a list of regex separated by | to obfuscate the output of regression tests. It requires version 1.0.1 of tinybird-cli. -
.tinyenv variables written to
GITHUB_ENV
to make them available in all GitHub Actions workflow