Closed mticmtic closed 1 year ago
Added some comments above; also note that the windows build is failing with several errors like this:
Error: error: unable to create file wizard_spider/Resources/TrickBot/TrickBotClientExe/packages/Microsoft.googletest.v140.windesktop.msvcstl.static.rt-dyn.1.8.1.4/Microsoft.googletest.v140.windesktop.msvcstl.static.rt-dyn.1.8.1.4.nupkg: Filename too long
We had the same issue with the last transfer from private repo to public. The added path component
/micro_emulation_plans
pushes some of these strings over the limit. Solving this error may vary from case to case. In this particular case, we probably don't need to check in .nupkg if the github action is going to run nuget, right?
These resources are not part of micro plans so i'm not sure how the micro_emulation_plan
strings affect, but i added lines to .gitignore
to omit certain nuget files which didn't seem to fix the issue. I also tried to override the length limit with git config --system core.longpaths true
but was unsuccessful
@mehaase i could use some extra help on this
These resources are not part of micro plans
Oh, good point. Maybe when we run nuget restore, it’s running for all the plans? I’m on mobile atm but we could look at the build logs to find out.
I checked the build logs and its failing while checking out our repo. That's weird because this same repo was running fine recently, right? I don't know what changed. We should nuke this whole packages/
directory: https://github.com/center-for-threat-informed-defense/adversary_emulation_library/tree/master/wizard_spider/Resources/TrickBot/TrickBotClientExe/packages (and any others like it).
Added some comments above; also note that the windows build is failing with several errors like this:
We had the same issue with the last transfer from private repo to public. The added path component
/micro_emulation_plans
pushes some of these strings over the limit. Solving this error may vary from case to case. In this particular case, we probably don't need to check in .nupkg if the github action is going to run nuget, right?