Adding manifest generation to build (#16815)

* adding manifest generation to build, ensure it only runs on go 117 windows
Azure · Jan 14, 2022 · 2ab9041 · 2ab9041
1 parent c430206
commit 2ab9041
Show file tree

Hide file tree

Showing 3 changed files with 14 additions and 0 deletions.
diff --git a/eng/pipelines/templates/jobs/archetype-sdk-client.yml b/eng/pipelines/templates/jobs/archetype-sdk-client.yml
@@ -84,6 +84,7 @@ stages:
             pool.name: azsdk-pool-mms-win-2019-general
             image.name: MMS2019
             go.version: '1.17'
+            generate.bom: true
           Linux_Go116:
             pool.name: azsdk-pool-mms-ubuntu-2004-general
             image.name: MMSUbuntu20.04

diff --git a/eng/pipelines/templates/steps/build-test.yml b/eng/pipelines/templates/steps/build-test.yml
@@ -65,6 +65,18 @@ steps:
       displayName: 'Dump Test Proxy logs'
       condition: succeededOrFailed()
 
+  - task: AzureArtifacts.manifest-generator-task.manifest-generator-task.ManifestGeneratorTask@0
+    displayName: 'Generate BOM'
+    condition: and(succeededOrFailed(), eq(variables['generate.bom'], 'true'))
+    inputs:
+      BuildDropPath: $(Build.ArtifactStagingDirectory)
+
+  - template: /eng/common/pipelines/templates/steps/publish-artifact.yml
+    parameters:
+      ArtifactPath: '$(Build.ArtifactStagingDirectory)/_manifest'
+      ArtifactName: 'manifest'
+      CustomCondition: and(succeededOrFailed(), eq(variables['generate.bom'], 'true'))
+
   - task: PublishTestResults@2
     condition: succeededOrFailed()
     inputs:

diff --git a/eng/pipelines/templates/variables/globals.yml b/eng/pipelines/templates/variables/globals.yml
@@ -1,2 +1,3 @@
 variables:
   GoLintCLIVersion: 'v1.23.6'
+  Package.EnableSBOMSigning: true