search

microsoft / coe-starter-kit

Other
737 stars 216 forks source link

[ALM Accelerator - BUG]: Solutions with long paths on unpack fail pac solution clone/sync #7207

Open bnc-cvx opened 9 months ago

bnc-cvx commented 9 months ago

Describe the issue

We have a few solution where their solution components have really long names.

Also, these same solutions are named with very long names (at or close to 50 characters long).

Every attempt at exporting these solutions via ALM Accelerator causes an error when the export pipeline tries to execute the "pac - Clone or Sync Solution" image

Expected Behavior

Would like to be able to export solutions that might be named with long names and be able to export solutions that have components named with long names.

What component are you experiencing the issue with?

ALM Accelerator Pipelines

What solution version are you using?

November 2023

Steps To Reproduce

  1. Create a solution with a name that's long. For example, create a solution with the name "ReallyLongSolutionNameIMeanLikeVeryVeryLon"
  2. Create a component within the solution and provide it a really long name. For example, create an environment variable with the name "ReallyLongEnvironmentVariableNameLikeAsLongAsTheyLetMeMakeItWhichIsLongerThanTheSolutionButThat"
  3. Attempt to deploy the solution via ALM Accelerator.
  4. An error similar to what's shown here will occur: image The error message usually states Error: Could not find a part of the path '...'

Anything else?

No response

AB#1622

RajeevPentyala commented 9 months ago

@bnc-cvx It's a known Windows OS issue related to long paths, as mentioned here. Unfortunately, there isn't much that can be done about it. You may want to refer to the similar github issue #5964 and check if the workaround mentioned there works for you.

mikefactorial commented 9 months ago

@bnc-cvx we're working through incorporating recent updates to the build tools and pac to help here. microsoft/coe-alm-accelerator-templates#333

mikefactorial commented 9 months ago

@bnc-cvx It's a known Windows OS issue related to long paths, as mentioned here. Unfortunately, there isn't much that can be done about it. You may want to refer to the similar github issue #5964 and check if the workaround mentioned there works for you.

@RajeevPentyala added you to the internal thread on this.