-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use compute engine to build coverage and app engine to publish the re… #24395
Use compute engine to build coverage and app engine to publish the re… #24395
Conversation
PR #24395: Size comparison from b36439e to 55581e2 Increases (14 builds for bl702, cc13x2_26x2, k32w, nrfconnect, psoc6, qpg, telink)
Decreases (5 builds for cc13x2_26x2, esp32, qpg, telink)
Full report (54 builds for bl602, bl702, cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, psoc6, qpg, telink)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a README.md explaining the reason of having an app_engine folder. Also maybe naming could be more explicit, like "static_website_serve.yaml" or similar.
PR #24395: Size comparison from b36439e to 93cfc36 Increases (3 builds for k32w, nrfconnect, qpg)
Decreases (1 build for qpg)
Full report (11 builds for k32w, linux, mbed, nrfconnect, qpg)
|
PR #24395: Size comparison from b36439e to c7505b4 Increases (9 builds for cc13x2_26x2, esp32, k32w, nrfconnect, psoc6, qpg, telink)
Decreases (6 builds for bl602, bl702, cc13x2_26x2, esp32, telink)
Full report (54 builds for bl602, bl702, cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, psoc6, qpg, telink)
|
PR #24395: Size comparison from b36439e to 189c2a6 Increases (9 builds for bl602, bl702, cc13x2_26x2, k32w, nrfconnect, psoc6, telink)
Decreases (7 builds for bl602, bl702, cc13x2_26x2, esp32, psoc6, telink)
Full report (54 builds for bl602, bl702, cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, psoc6, qpg, telink)
|
…sult
Currently, we use cloud build + compute engine to generate the coverage report against connectedhomeip SDK. cloud build is used to schedule the build within compute engine with ipv6 support and fetch and publish the coverage result in google cloud bucket.
But this setup is not fully conform to GCE security policy since cloud build use external IP address which prevent it talk to compute engine directly.
Switch to use compute engine + app engine to conduct coverage statistic, compute engine is used to build the coverage report and deploy the coverage result to app engine in daily basis.