MCU-Driver-HAL and CI Combined WG Meeting 2021-06-10

Owned by Bill Fletcher, created
Jun 11, 2021
2 min read

Date

Jun 10, 2021

Participants

  • Saheer Babu

  • Fathi Boudra

  • Pavel Chromý

  • Evelyne Donnaes

  • Eric Finco

  • Bill Fletcher

  • Ian Fyall

  • Chokri Gammoudi

  • Erwan Gouriou

  • Haley Guo

  • Martin Kojtal

  • Jason Martin

  • Laurent Meunier

  • Anmar Oueja

  • François Ozog

  • Andy Powers

  • George Psimenos

  • Kenney Qu

  • Marcelo Salazar

  • Qinghao Shi

  • Paul Sokolovskyy

  • (Arm)Wilfried

  • Bechir JABRI

  • Filip Jagodzinski

  • Hugues Kamba-Mpiana

  • jerome coutant

  • Konstantinos Chatzis

  • Mark Hicken

  • Shrek

Slides

Notes

AO: There will be a public wiki space for this project. Suggest adding it (to the slides).

QS: (in response to Chokri) Mean Greentea has features beyond MVP? Yes, Greentea is a tool. Need basic features from Greentea and so no harm if we bring Greentea into MVP but leave alone the advanced features.

CG: Not sure if can use GitHub action and Docker and LAVA. Jenkins would be a straightforward option. Also running cost would be lower longer term compared to cloud option.

QS: You mean haven’t tried GitHub action with LAVA? Also some concerns between GitHub actions and Jenkins performance. Haven’t yet tried. Maybe Linaro can confirm.

PS: Didn’t yet try it in LITE. Have been using Jenkins for a decade but for new projects we are moving to GitHub actions. Our view it’s a more streamlined option. We didn’t yet look at performance.

ED: Trying to get something simple up and running for MVP and believe it will benefit from GitHub actions. In the ADR need to manage scalability and not be tied to GitHub actions.

EF: Why not do a test first and then ADR based on the result?

ED: Not aware of any blockers yet.

QS: Also ADR is a way to inform people what we’re doing. It’s not concrete (in fact we are making an ADR to revise an old one). Based on some simple experiments believe it can work incl. with LAVA.

FB: For MVP GitHub action or Jenkins doesn’t change the integration with LAVA. Will still use (same) scripts in either case and just the credential system will be different. So consider it low risk to use GitHub actions in this case.

CG: Mention Jira? Don’t know if it’s accessible.

MH: It’s a Linaro cloud instance

AO: It’s public and accessible - atlassian.net domain. People do need an account to make changes.

BF: Mailing lists are also public at http://op-lists.linaro.org

Recording