Improve the engine CI

[swift-kim]

Build

• Build for each arch/mode/profile

Analyze

• Formatting & Linter → Add a format checker to the CI pipeline #90
• API checker (ensure no internal API is used by the wearable embedder) → Check non-public API usage #140

Release

• Automatic release (the GitHub Release task didn't work when I tested last time 🤔)
• File server for hosting releases (we need our own domain)
• Admin dashboard (to check the number of downloads for each release, etc.)

Test

• (meta) Add a self-hosted instance to the Pipelines (pricing: $15/month) to run tests on a local machine
• Run integration tests (run sample apps on a set of test devices and check if they behave correctly)
• Run regression tests (measure the performance of sample apps and compare with the previous results)
• Add unit tests for the Tizen embedder and run

[swift-kim]

See also:

• The official Flutter CI
  • https://ci.chromium.org/p/flutter
  • https://ci.chromium.org/p/flutter/g/engine-try/builders
  • https://www.chromium.org/developers/testing/chromium-build-infrastructure/tour-of-the-chromium-buildbot
  • https://github.com/flutter-tizen/engine/tree/flutter-2.0.1-tizen/ci/dev

[bwikbs]

I'm working on Add unit tests for the Tizen embedder and run task

I guess I would have to wait for @HakkyuKim work result.

[WonyoungChoi]

I would like to suggest two things about the CI environment.

1. Use docker image for build and test environment.

We can get an easily manageable and extensible CI environment by using docker image. I was able to get a docker image with an environment to build the engine code by optimizing https://github.com/flutter-tizen/tizen_tools/pull/3.

• Dockerfile for PoC: https://github.com/WonyoungChoi/tizen_tools/blob/dockerfile/Dockerfile

The uncompressed size of the generated docker image is about 3.2GB, so there is no big problem in using it for engine build.
We can add more scripts like the symbol checker to the tizen_tools repo and the docker image also.

2. Move to the Github Actions

I tested the engine build with the Github Actions using the docker image generated above.

• Workflow : https://github.com/WonyoungChoi/engine/blob/buildtest/.github/workflows/build.yml
• Build : https://github.com/WonyoungChoi/engine/actions/runs/1033273597

I used my linux PC in the company network (behind proxy and firewall) as a self-host and the incremental builds were also possible in that case.
If we use Github Actions, we will be able to reduce costs and secure management efficiency.

[bwikbs]

I have a question ! this doesn't cost money? Are there any limitations for free?

[WonyoungChoi]

@bwikbs yes, Github Actions is free for public repositories.
for more detailed limitations, you can see in

• GH hosted runner : https://docs.github.com/en/actions/reference/usage-limits-billing-and-administration#usage-limits
• Self hosted runner : https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners#usage-limits

[HakkyuKim]

@WonyoungChoi
Thanks for the information!
I would like to use Github Actions instead of Azure in flutter-tizen/plugins#150.
I have one question though,

I used my linux PC in the company network (behind proxy and firewall) as a self-host

Does this mean we can just attach without notifying the company?
How are you planning to proceed?

[WonyoungChoi]

@HakkyuKim Sorry for late response. I missed your mention.
Yes we can just attach machines without notifying technically. But I think we need some security approvals about using local agents. Let's talk about details in your seat on Thursday with @swift-kim.

[HakkyuKim]

@WonyoungChoi No problem and sounds good to me!

[swift-kim]

The migration to GitHub Actions is being worked on: #176 (will use GitHub-hosted runners for security reasons).

[swift-kim]

Closing in favor of #239 and further new separate issues.