Both SBE and SBRP having build pipelines which define custom jobs that directly call into the /eng/common/templates/steps/source-build.yml template. This requires defining the container name to be used. This means that has to be manually maintained rather than getting it for free from Arcade. We should investigate if it's possible to reuse more of the Arcade infra to avoid this. The use case is different here from product repos in that we only want to execute source build legs. If nothing else perhaps we can use the eng/common/templates/jobs/source-build.yml template, if not one that's higher level than that.
Both SBE and SBRP having build pipelines which define custom jobs that directly call into the
/eng/common/templates/steps/source-build.yml
template. This requires defining the container name to be used. This means that has to be manually maintained rather than getting it for free from Arcade. We should investigate if it's possible to reuse more of the Arcade infra to avoid this. The use case is different here from product repos in that we only want to execute source build legs. If nothing else perhaps we can use the eng/common/templates/jobs/source-build.yml template, if not one that's higher level than that.