Skip to content

Commit 4dacafb

Browse files
committed
Use production OptProf tooling
We pick up certain pipeline templates providing OptProf functionality from the DartLab.OptProf repository. Currently we get these from the "main" branch of that repo, but as with other repos "main" is the bleeding edge of OptProf changes. This potentially exposes us to bugs and instability. Instead we want to use the "Production" tag rather than the latest main. This should be better tested and more stable. This is based on https://devdiv.visualstudio.com/DevDiv/_git/VS/pullrequest/515949.
1 parent fd6ac06 commit 4dacafb

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

eng/pipelines/official.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,8 @@ resources:
5050
- pipeline: DartLab.OptProf
5151
source: DartLab.OptProf
5252
branch: main
53+
tags:
54+
- production
5355
repositories:
5456
# This name is the default value for the 'dartLabTemplatesResourceName 'parameter in single-runsettings.yml.
5557
- repository: DartLabTemplates
@@ -60,7 +62,7 @@ resources:
6062
- repository: DartLabOptProfTemplates
6163
name: DartLab.OptProf
6264
type: git
63-
ref: refs/heads/main
65+
ref: refs/tags/Production
6466
# This repo is used to create the insertion PR into the vs-green repo.
6567
- repository: VSCodeExtensionRepo
6668
type: git

0 commit comments

Comments
 (0)