Proposed SIG-Build meeting agenda for Apr-20-22

[dshmz]

Meeting Details

• Date/Time: Apr 20, 2022 @ 05:00 pm UTC / 10:00 am PDT
• Location: Discord SIG-Build Voice Room
• Moderator: Mike Chang
• Note Taker Mike Chang

The SIG-Build Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources.

SIG Updates

What happened since the last meeting?

• Proposal accepted for overide changes for AP crashes. Implemented and in place since April 14th
• AP crashes persist in Linux profile. @spham-amzn has implemented a change to reduce memory and increase retries to the AP builder process. More investigations needed to provide a root cause of the memory "leak" and implementing a permanent fix.
• Log parsing change reverted, was previously causing truncation of the build logs. Investigations needed to find root cause and implement fix or alternative method to expose http links in Blue Ocean

Meeting Agenda

• Discuss agenda from proposed topics

• Updates incoming for the Jenkins server instance. Plugins are being updated to latest. Will be deployed at EoD today (April 20th)

• Codeowners additions for SIG-Build

-Triage the new issues in the queue - https://github.com/o3de/o3de/issues?q=is%3Aissue+is%3Aopen+label%3Asig%2Fbuild+label%3Aneeds-triage+no%3Aassignee.

Outcomes from Discussion topics

SIg reviewers and maintainers groups

• @brianherrera - What's the distinction?
• @amzn-changml - Mostly to add participants to the SIG repos, including external contributors

Ownership paths for SIG-Build

/scripts/build @o3de/sig-build-reviewers @o3de/sig-build-maintainers
/scripts/commit_validation @o3de/sig-build-maintainers
/scripts/license_scanner @o3de/sig-build-maintainers
/scripts/signer @o3de/sig-build-maintainers

• @shirangj - Who owns installer paths?
• @amzn-changml - We have oversight and maintenance of the automation (within the CMake folder), but actual ownership of the installer UI and exe belongs to multiple groups (SIG-UIUX and release)
• @brianherrera - Possibly needs a new SIG to handle installer exe?
• @DMWeiss-divesIn - Who owns the "tools" category of scripts?
• @amzn-changml - Mostly cross cutting, but these ownership groups does not imply maintenance, but oversight. These do need discussion with SIG-Core on actual maintenance responsibilities
• @brianherrera - Cross cutting paths may need a second pass, including the python folder
• @amzn-changml - Also needs sig-security involved in shared dependencies like python

Discuss outcomes from agenda

• Agreed on 1st pass for codeowners paths, @amzn-changml will get PR out for this
• Future discussion:
• • Codeowners mechanisms for PR and other automations (long outstanding tickets/PRs, build failure owners)
• • Discussion on unused scripts from legacy imports
• • Charter updates/maintenance

Action Items

Create actionable items from proposed topics

Open Discussion Items

List any additional items below!

[brianherrera]

We should also discuss about updating the codeowners file for sig-build.

https://github.com/o3de/o3de/blob/development/.github/CODEOWNERS

[amzn-changml]

Agreed