Open LightCZ opened 7 years ago
(Some ideas)
(Probably it does not matter but you have forward slash after \Solution) --releasify C:\BuildAgent\work\1015bb07ae0502fb\Solution/Release/FeelCareSID.1.0.201.nupkg
See if you have a valid nuget package. Are you able to open FeelCareSID.1.0.201.nupkg file using nuget package explorer -? Is there content in the Nuget package under lib\framework-?
Have you tried to run the squirrel.com --releasify yourself manually from the build agent -?
Try using 7z.exe command line from the build agent, do you get any errors -?
and lastly, try to delete this folder it could be locked/read only mode for some reason from the build agent server: C:\Users\
Thats the thing. When you run it directly from build agent it works flawlessly. Running from teamcity as a process, this error appears.
This might be related to #1060.
You can try changing the TeamCity build agent service to use a windows user. This may affect other things your building with TeamCity - you should also use a restricted user if your going to do it.
Wow, this deffinitely looks related. I ll try to change this on our agent. Would be nice to determine why is this happening under system account tho.
I had a similar problem using LocalSystem and Octopus Deploy. 7Zip just broke. Switching to a windowsuser fixed it. See https://octopus.com/docs/installation/installing-tentacles/running-tentacle-under-a-specific-user-account-for-use-in-powershell
We were able to resolve this by adding a SQUIRREL_TEMP
environment variable in TeamCity to point to a temp directory in the teamcity build path (i.e., add env.SQUIRREL_TEMP
with a value of %teamcity.build.workingDir%\SquirrelTemp
). You can add an environment variable to the build process under the TeamCity Build Configurations > Parameters section.
It appears to have something to do with limitations on the %LocalAppData%
location for the system user when you are running the agent as a System user. Changing the agent to a local account did resolve the problem, but we didn't want to make this change across all build agents. Simply setting the SQUIRREL_TEMP environment variable as described above allowed it to build and leave the build agent running on the System account.
Here are some indicators we found to assess the problem:
[Exec] C:\BuildAgent\work\689c651b5369f733\src\SquirrelApp.csproj(166, 5): error MSB3073: The command ""C:\BuildAgent\work\689c651b5369f733\packages\squirrel.windows.1.7.8\tools\Squirrel.exe" --releasify C:\BuildAgent\work\689c651b5369f733\src\bin\Package\SquirrelApp.0.1.0.nupkg" exited with code -1.
SquirrelSetup.log
on the actual build machine under C:\BuildAgent\work\689c651b5369f733\packages\squirrel.windows.1.7.8\tools
with the following message.
2017-10-31 20:08:30> Utility: Failed to extract file C:\BuildAgent\work\689c651b5369f733\src\Releases\SquirrelApp-0.1.0-full.nupkg to C:\Windows\system32\config\systemprofile\AppData\Local\SquirrelTemp\tempa
7-Zip [64] 16.04 : Copyright (c) 1999-2016 Igor Pavlov : 2016-10-04
Scanning the drive: 0 files, 0 bytes
Creating archive: C:\BuildAgent\work\689c651b5369f733\src\Releases\SquirrelApp-0.1.0-full.nupkg
Items to compress: 0
Files read from disk: 0 Archive size: 22 bytes (1 KiB)
I'm working on a PR to add this information to the documentation as well.
Since Squirrel migrated to new 7-zip solution we are having problems on build agent (teamcity build agent) It looks like some file could not be "extracted"/ found but there is no log message on what is going on
The error log looks like this: