How we built the agents that built AWS Emulator – About Amazon

This post was originally published on this site.

Each issue is given to an agent in the third team, whose job is to fix that single issue. They check out the code, root-cause the issue, and edit the code until it’s addressed. They must then pass their code change through a gate that ensures it meets our bar. This gate obviously blocks changes that don’t compile. But it also includes agents that review against coding standards, verify the code is secure, and ensure that the change did not regress fidelity. If any of those checks fail, the change is sent back to the agent for rework; if they all pass, it is merged to mainline. We’ve seen thousands of issues fixed every day as hundreds of agents concurrently work on the codebase. Without this merge gate, we wouldn’t trust what our agents are building. We focus a lot on optimizing it because it’s so critical to how quickly and reliably the agents build.

Leave a Reply

Your email address will not be published. Required fields are marked *