Skip to content

Understanding the CI

Jump to bottom
Rohan Sawahn edited this page Aug 3, 2020 · 12 revisions

Our CI pipelines are split according to their responsibities:

  1. Unit Testing pipeline
  2. Linter pipeline
  3. Release pipeline

Unit and Lintertests

The Unit Testing pipeline and the Linter pipeline are required to pass before merging a pull request. We do not target the Squeak trunk as that proved too unreliable a target. We also only test on linux, as the macos pipeline does not work with our unit tests. This is due to the way we download tdlib and can be fixed in the future. We also wanted to create a pipeline executing tests against the Telegram Test Data Center, this also was not implemented due to time constraints but it probably is the best integration test one could run.

Release Pipeling

Whenever you merge into the Masterbranch (i.e. after a successful sprint) the Release pipeline will generate a new release which can be found here.

Clone this wiki locally