Resource Profiles Apply and Failed Builds Show Why
The profile you pick now sets the container CPU and memory it actually runs with, and a source build that fails no longer sits in Building forever.
What's changed
- Choosing a resource profile sets the container CPU and memory requests and limits accordingly; previously every container ran with the same defaults regardless of profile
- The container page shows the CPU and memory it actually runs with, and the API exposes a metrics endpoint plus the same values on the container resource
- A source build whose checkout or build step fails is marked Build failed, with the reason, recovery guidance and a link to the failed build
- Builds are reconciled against the build system, so a lost callback can no longer leave a container stuck