Skip to content

Commit d40a2dc

Browse files
committed
Build conda recipe on new tags
Ensure that new binaries are generated for releases which are usually not from pull_requests. Using APPVEYOR_REPO_TAG_NAME because yields shorter syntax because it's undefined (ie false) when not a tag and APPVEYOR_REPO_TAG has to be compared to lowercase `true` instead of `True` like everything else. Definitions: APPVEYOR_REPO_TAG_NAME - contains tag name for builds started by tag; otherwise this variable is undefined; APPVEYOR_REPO_TAG - true if build has started by pushed tag; otherwise false; https://www.appveyor.com/docs/environment-variables/
1 parent 51ec8a4 commit d40a2dc

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

ci/appveyor_build_recipe.ps1

+1-1
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ if ($env:PLATFORM -eq "x86"){
1111
$env:CONDA_BLD = "$env:CONDA_BLD" + "-x64"
1212
}
1313

14-
if ($env:APPVEYOR_PULL_REQUEST_NUMBER -or $env:FORCE_CONDA_BUILD -eq "True") {
14+
if ($env:APPVEYOR_PULL_REQUEST_NUMBER -or $env:APPVEYOR_REPO_TAG_NAME -or $env:FORCE_CONDA_BUILD -eq "True") {
1515
# Update PATH, and keep a copy to restore at end of this PowerShell script
1616
$old_path = $env:path
1717
$env:path = "$env:CONDA_BLD;$env:CONDA_BLD\Scripts;" + $env:path

0 commit comments

Comments
 (0)