Failed to compile plug-in action: File Bag only on pipeline
Posted: Thu Jun 22, 2023 4:14 am
Context:
We have our InstallAware hosted on a virtual windows machine. We were using InstallAware 18, but have upgraded to InstallAware X15 to bundle in .NET Framework 4.8.
The Problem:
Now, the build begins to fail in some places but not in others when run. When it fails, the error is:
"Error during build: Failed to compile plug-in action: File Bag", which seems to occur even if we use branches that don't include the new .NET Framework 4.8 changes.
Here is a list of the places where it builds correctly, vs places where it doesn't build correctly. Despite having IDENTICAL command lines/parameters run (I believe):
DOES BUILD:
- In the IDE on the VM.
- On the windows command line on the VM.
- In an IDE on my local system.
DOES NOT BUILD:
- On the windows command line on the cloud pipeline
- On the windows powershell on the cloud pipeline
- On the windows powershell on the VM
I'm at a bit of a loss. The lack of detailed error message is making it difficult to root-cause the error. Any suggestions/support would be appreciated.
What's confusing is that we can get it to run on the command line on the VM, but it doesn't work when we use an Azure pipeline to run the same command line on the VM.
We have our InstallAware hosted on a virtual windows machine. We were using InstallAware 18, but have upgraded to InstallAware X15 to bundle in .NET Framework 4.8.
The Problem:
Now, the build begins to fail in some places but not in others when run. When it fails, the error is:
"Error during build: Failed to compile plug-in action: File Bag", which seems to occur even if we use branches that don't include the new .NET Framework 4.8 changes.
Here is a list of the places where it builds correctly, vs places where it doesn't build correctly. Despite having IDENTICAL command lines/parameters run (I believe):
DOES BUILD:
- In the IDE on the VM.
- On the windows command line on the VM.
- In an IDE on my local system.
DOES NOT BUILD:
- On the windows command line on the cloud pipeline
- On the windows powershell on the cloud pipeline
- On the windows powershell on the VM
I'm at a bit of a loss. The lack of detailed error message is making it difficult to root-cause the error. Any suggestions/support would be appreciated.
What's confusing is that we can get it to run on the command line on the VM, but it doesn't work when we use an Azure pipeline to run the same command line on the VM.