Skip to content

Commit

Permalink
Use custom BuildNumber variable
Browse files Browse the repository at this point in the history
Updating the build number apparently doesn't happen early enough to
affect the GitHubRelease task.
  • Loading branch information
heaths committed Mar 22, 2019
1 parent 2119630 commit 4238d3c
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions azure-pipelines.yml
Original file line number Diff line number Diff line change
Expand Up @@ -169,7 +169,7 @@ jobs:
gitHubConnection: GitHub
repositoryName: heaths/vscode-guid
tagSource: manual
tag: v$(Build.BuildNumber)
tag: v$(BuildNumber)
assets: |
$(Build.ArtifactStagingDirectory)/**/*.vsix
isPreRelease: $[ne(variables['Build.SourceBranch'], 'refs/heads/master')]
Expand All @@ -184,10 +184,10 @@ jobs:
for fname in $(System.ArtifactsDirectory)/**/*.vsix; do
if [ -f "$fname" ]; then
if [[ "$PUBLISH" == "true" ]]; then
echo Publishing: $(System.ArtifactsDirectory)/$fname
vsce publish -p $(Marketplace.AccessToken) --packagePath $(System.ArtifactsDirectory)/$fname
echo Publishing: $fname
vsce publish -p $(Marketplace.AccessToken) --packagePath $fname
else
echo Publishing skipped: $(System.ArtifactsDirectory)/$fname
echo Publishing skipped: $fname
fi
fi
done
Expand Down

0 comments on commit 4238d3c

Please sign in to comment.