The Score Specification provides a developer-centric and platform-agnostic Workload specification to improve developer productivity and experience. It eliminates configuration inconsistencies between environments.
We've been looking at how we can use Score to support slightly more abstract workloads and we've seen that the > 1 containers places somewhat of a limitation on what Score implementations can accept and transform and how teams can iterate and learn about Score.
By removing this constraint, we allow teams that are migrating to Score to start with an "empty" workload, add their resource requirements and copy the outputs to their existing CI pipeline. Then they can incrementally work on this and then bring their app in once it is ready.
We've been looking at how we can use Score to support slightly more abstract workloads and we've seen that the > 1
containersplaces somewhat of a limitation on what Score implementations can accept and transform and how teams can iterate and learn about Score.By removing this constraint, we allow teams that are migrating to Score to start with an "empty" workload, add their resource requirements and copy the outputs to their existing CI pipeline. Then they can incrementally work on this and then bring their app in once it is ready.