Skip to content

Commit

Permalink
(GH-77) Push to gallery on new tags
Browse files Browse the repository at this point in the history
Instead of pushing on merges to master, push to the PowerShell gallery
on new tags being added. We want to use tagging for versioning and
getting to version history in the repository, so it's good to just set
that up appropriately.
  • Loading branch information
ferventcoder committed Apr 19, 2017
1 parent 1ba231a commit 44d4f52
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion AppVeyor/AppVeyorDeploy.ps1
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Write-Host "Updating module manifest to version: $env:APPVEYOR_BUILD_VERSION"
# Publish to PS Gallery #
#---------------------------------#

if ( ($env:APPVEYOR_REPO_NAME -notmatch 'chocolatey') -or ($env:APPVEYOR_REPO_BRANCH -notmatch 'master') )
if ( ($env:APPVEYOR_REPO_NAME -notmatch 'chocolatey') -or (!$env:APPVEYOR_REPO_TAG_NAME) )
{
Write-Host "Finished testing of branch: $env:APPVEYOR_REPO_BRANCH - Exiting"
exit;
Expand Down
2 changes: 1 addition & 1 deletion readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ Here's the general process of fixing an issue in the DSC Resource Kit:
Build and Publishing
============================

AppVeyor is used to package up the resource and publish to the Powershell Gallery (on successful build from master branch only).
AppVeyor is used to package up the resource and publish to the Powershell Gallery (on successful build from a newly pushed tag only).

The AppVeyor scripts do the following:
- Test the resources using 'xDSCResourceDesigner'
Expand Down

0 comments on commit 44d4f52

Please sign in to comment.