Skip to content

use simplified names for compliance folders #5388

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
daxian-dbw merged 1 commit into from
Nov 9, 2017
Merged

use simplified names for compliance folders #5388

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 17 additions & 1 deletion tools/releaseBuild/createComplianceFolder.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,23 @@ foreach($folder in $ArtifactFolder)
# Find Symbols zip which contains compliance files
Write-Host "ArtifactFolder: $folder"
$filename = Join-Path -Path $folder -ChildPath 'symbols.zip'
$name = Split-Path -Path $folder -Leaf

$parentName = Split-Path -Path $folder -Leaf

# Use simplified names because some of the compliance tools didn't like the full names
# decided not to use hashes because the names need to be consistent otherwise the tool also has issues
# which is another problem with the full name, it includes version.
if ($parentName -match 'x64' -or $parentName -match 'amd64')
{
$name = 'x64'
}
elseif ($parentName -match 'x86') {
$name = 'x86'
}
else
{
throw "$parentName could not be classified as x86 or x64"
}

# Throw is compliance zip does not exist
if (!(Test-Path $filename))
Expand Down