From 3489ff2df232e7d9bf5008acd1533a995fb22212 Mon Sep 17 00:00:00 2001
From: Logan Bussell <loganbussell@microsoft.com>
Date: Fri, 25 Apr 2025 11:14:24 -0700
Subject: [PATCH] Use the new build-and-test template for release staging

---
 eng/pipelines/release-staging.yml | 30 ++++++++++++++++++++++++------
 1 file changed, 24 insertions(+), 6 deletions(-)

diff --git a/eng/pipelines/release-staging.yml b/eng/pipelines/release-staging.yml
index c4afe09a9c..d1efe54e6a 100644
--- a/eng/pipelines/release-staging.yml
+++ b/eng/pipelines/release-staging.yml
@@ -1,11 +1,29 @@
+# This pipeline takes the current branch and builds and tests the images,
+# but does not publish them.
+#
+# The images can later be published by running the release-promotion pipeline.
+
 trigger: none
 pr: none
 
+resources:
+  repositories:
+  - repository: InternalVersionsRepo
+    type: github
+    endpoint: dotnet
+    name: dotnet/versions
+
+variables:
+- template: /eng/pipelines/variables/core.yml@self
+
 extends:
   template: /eng/common/templates/1es-official.yml@self
-  stages:
-  - stage: release-staging
-    jobs:
-    - job: release-staging
-      steps:
-      - script: echo "Hello world"
+  parameters:
+    stages:
+    - template: /eng/pipelines/stages/build-and-test.yml@self
+      parameters:
+        internalProjectName: ${{ variables.internalProjectName }}
+        publicProjectName: ${{ variables.publicProjectName }}
+        # We always want staged images to be as up-to-date as possible,
+        # so don't rely on any caching behavior.
+        noCache: true