How to exclude dev packages from CI release build? #21847
Replies: 1 comment 4 replies
-
|
@xperiandri those packages are not supposed to be referenced in release. If you can provide the command line you used and a binlog, it will help. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
This is my pipeline (configuration is release) parameters:
- name: buildConfiguration
displayName: 'Build Configuration'
type: string
values:
- Debug
- Release
default: Release
steps:
- checkout: self
fetchDepth: 0
submodules: true
- task: PowerShell@2
displayName: "Override target frameworks"
inputs:
pwsh: true
targetType: 'inline'
script: |
$contentToAdd = @'
<Project>
<PropertyGroup>
<OverrideTargetFramework Condition="''!='hint: Android' OR ''!='hint: Webassembly'">$(DotNetVersion)-android;$(DotNetVersion)-browserwasm;$(DotNetVersion)</OverrideTargetFramework>
</PropertyGroup>
</Project>
'@
Add-Content "solution-config.props" $contentToAdd
- task: PowerShell@2
displayName: "Override target frameworks"
inputs:
pwsh: true
targetType: 'inline'
script: |
$contentToAdd = @'
<Project>
<PropertyGroup>
<OverrideTargetFramework Condition="''!='hint: iOS' OR ''!='hint: MacCatalyst'">$(DotNetVersion)-ios;$(DotNetVersion)-maccatalyst</OverrideTargetFramework>
<UnoDisableHotDesign>true</UnoDisableHotDesign>
<UnoDisableMCPSupport>true</UnoDisableMCPSupport>
</PropertyGroup>
</Project>
'@
Add-Content "solution-config.props" $contentToAdd
enabled: false
- task: PowerShell@2
displayName: 'Uno-check'
inputs:
pwsh: true
targetType: 'inline'
# --target ios `
# --target maccatalyst `
script: |
dotnet tool install -g uno.check --version 1.32.17
uno-check -v --ci --non-interactive --fix `
--target wasm `
--target android `
--skip androidemulator `
--skip androidsdk `
--skip dotnetnewunotemplates `
--skip git `
--skip openjdk `
--skip vswin `
--skip vswinworkloads `
--skip unosdk `
--skip xcode
- task: DotNetCoreCLI@2
displayName: 'Restore Console app'
inputs:
command: 'restore'
projects: '$(ConsoleApp)'
feedsToUse: 'config'
nugetConfigPath: 'nuget.config'
arguments: '-c ${{parameters.buildConfiguration}}'
- task: DotNetCoreCLI@2
displayName: 'Build Console app'
inputs:
command: 'custom'
custom: 'msbuild'
projects: '$(ConsoleApp)'
arguments: >-
/p:Configuration=${{parameters.buildConfiguration}}
/nr:false
- task: DotNetCoreCLI@2
displayName: 'Build Tests'
inputs:
command: build
projects: |
Client.Tests/**/*.[cf]sproj
Console.Tests/**/*.[cf]sproj
arguments: >-
--no-dependencies
--configuration ${{parameters.buildConfiguration}}
- task: DotNetCoreCLI@2
displayName: 'Run Tests'
inputs:
command: test
projects: |
Client.Tests/**/*.[cf]sproj
Console.Tests/**/*.[cf]sproj
arguments: >-
--no-build
--configuration ${{parameters.buildConfiguration}}
--collect "Code coverage"
--logger trx
- task: PublishTestResults@2
inputs:
testResultsFiles: '$(Agent.TempDirectory)/*.trx'
testRunTitle: 'Test Results' |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. Without a binlog we cannot help, can you provide one? |
Beta Was this translation helpful? Give feedback.
-
Hello, @jeromelaban. Here is the binlog: |
Beta Was this translation helpful? Give feedback.
-
|
A I see, the length of the lines hid something important. The That being said, the fact that the hot design packages are present in the list generally means that a debug build is done, then a release build is done on the same folders right after without doing a nuget restore or a delete of bin/obj folders. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I see this output with Uno SDK 6.4.24
I suppose the issue is that the app references dev packages. Am I right?
@jeromelaban
Beta Was this translation helpful? Give feedback.
All reactions