Unity Build task's "Logfile name" parameter assumes relative paths
See original GitHub issueAzure Pipelines encourages building artifacts into the $(Build.ArtifactStagingDirectory)
folder, and from there it is convenient to publish those artifacts.
I like to put my logs under $(Build.ArtifactStagingDirectory)\build_logs
and publish the artifact there so they can be inspected later. The Unity Build task lets me specify the log file, but it concatenates whatever I put there with the path to the source directory, so it looks like this: c:\a\1\s\c:\a\1\a\build_logs\editor.log
Notice that c:\
appears twice.
The Unity Build task should instead use a proper path joining function instead of string concatenation so that if the log I specify is a fully-qualified path, it disregards the path that it would prepend to a relative path.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
How to write to a file with a relative path - Unity Forum
I need a path to the Unity execution file in order to open .exe file. Code (CSharp): Process. Start(@"path")
Read more >Special folder names - Unity - Manual
Most API functions assume that everything is located in the Assets folder, and so don't require it to be mentioned explicitly. However, some...
Read more >Manual: Command line arguments - Unity
If no project name is given, then the last project opened by Unity is used. If no project exists at the path given...
Read more >MSBuild Reserved and Well-known Properties - Microsoft Learn
Property Reserved or well‑known Description
FrameworkSDKRoot Well‑known Path to the root folder for .NET Framewor...
MSBuildExtensionsPath Well‑known
MSBuildLastTaskResult Reserved
Read more >Could not load file or assembly or one of its dependencies
Check if you are referencing an assembly which in turn referencing an old version of unity. For example let's say you have an...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This issue is resolved in V3 of the build Task I hope to release as soon as I finish work on #56. You will be able to achieve what you describe above by entering
-logFile $(Build.ArtifactStagingDirectory)\build_logs\EditorLog.log
into the additional args field.Not for me. I’ve checked all the screens around My Seats that I can find, and none of them show a seriali number: