update docs

Vott · Vott · commit a2689e290c38 · 2020-05-18T19:45:38.000-07:00
diff --git a/RELEASE_GUIDE.md b/RELEASE_GUIDE.md
@@ -8,6 +8,12 @@ Instruction on how to create new GitHub & Web Releases.
 
 ![alt text](./docs/images/release-process.png "Create Release Process")
 
+### AzDO Tasks
+
+[GitHub Release Task](https://github.com/microsoft/azure-pipelines-tasks/tree/master/Tasks/GitHubReleaseV1)
+
+[Azure File Copy](https://github.com/microsoft/azure-pipelines-tasks/tree/master/Tasks/AzureFileCopyV3)
+
 ## Versioning
 
 Follow [NPM Semantic Versioning](https://docs.npmjs.com/about-semantic-versioning#incrementing-semantic-versions-in-published-packages)
@@ -23,7 +29,7 @@ Follow [NPM Semantic Versioning](https://docs.npmjs.com/about-semantic-versionin
 
 The pipeline use [npm-version](https://docs.npmjs.com/cli/version) to update version
 
-### Pre
+#### Pre
 
 All version with `pre`, ie. `preminor` will bump the appropriate didgit & append `-0` to the new version
 
@@ -39,7 +45,7 @@ Examples:
 1. v2.3.0 --> v2.4.0-0
 1. v2.4.0-0 --> v2.5.0-0
 
-#### Exception
+##### Exception
 
 `prerelease` behave similar to prepatch, but would increment the last digit.
 
@@ -51,10 +57,10 @@ v2.3.0 --> v2.3.1-0
 
 v2.3.0-0 --> v2.3.0-1
 
-### Major
+#### Major
 
 v2.x.x --> v3.0.0
 
-### Minor
+#### Minor
 
 v2.2.0 --> v2.3.0
diff --git a/azure-pipelines/templates/create-github-release.yml b/azure-pipelines/templates/create-github-release.yml
@@ -1,7 +1,7 @@
 parameters:
   GitHubConnection: '' # defaults for any parameters that aren't specified
   repositoryName: ''
-  isPreRelease: true
+  isPreRelease: false
   isDraft: false
 
 jobs:
@@ -46,20 +46,24 @@ jobs:
     - bash: |
         set -e
 
+        echo
+        echo "======> Set commit sha"
+        COMMIT_SHA=$(git rev-parse --short HEAD)
+        echo "COMMIT SHA: $COMMIT_SHA"
+        echo "##vso[task.setvariable variable=COMMIT_SHA]$COMMIT_SHA"
+
         ###
         # These variables were set in the "Version Bump" stage.  There are
         # currently no way to pass variables between stages, hence this workaround.
         ###
+        echo
+        echo "======> Set version variables"
         CURRENT_VERSION=$(cat $(Pipeline.Workspace)/variables/CURRENT_VERSION)
         echo "##vso[task.setvariable variable=CURRENT_VERSION]$CURRENT_VERSION"
 
         NEXT_VERSION=$(cat $(Pipeline.Workspace)/variables/NEXT_VERSION)
         echo "##vso[task.setvariable variable=NEXT_VERSION]$NEXT_VERSION"
-      displayName: "Retrieve version variables"
-
-    - bash: |
-        printenv | sort
-      displayName: "Print Env Variables"
+      displayName: "Set variables for release task"
 
     - task: GitHubRelease@1
       displayName: 'GitHub release (create)'
diff --git a/azure-pipelines/templates/create-web-release.yml b/azure-pipelines/templates/create-web-release.yml
@@ -55,5 +55,3 @@ jobs:
           echo "Prod url: $PROD_URL"
         displayName: "Prod URL"
         condition: eq(variables['Build.SourceBranch'], 'refs/heads/master')
-
-
