I am having intermittent problems running PackageManagerCLI as part of a Continuous Integration system. I have a pipeline of several jobs running under Jenkins to compile libraries, update and build a project and create a package. Currently the last job in the pipeline is to install the package that has been built before running some tests. It fails intermittently as shown below. Typically if I re-run this build job the command works. Any ideas how to avoid this problem?
Hi,
there is already an issue to solve this in our bug tracker db.
CDS-50240 ComponentManager: Improve PlugInCache robustness
The Workaround is to delete\rename this Cache files in 'C:\ProgramData\AP\PlugInCaches\
BR
Edwin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Edwin Schwellinger hat geschrieben:
Hi,
there is already an issue to solve this in our bug tracker db.
CDS-50240 ComponentManager: Improve PlugInCache robustness
The Workaround is to delete\rename this Cache files in 'C:\ProgramData\AP\PlugInCaches\
BR
Edwin
Thanks for the fast response, I have put the suggested workaround in place and after ten builds have had no problems (previously it was failing 50% of the time).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am having intermittent problems running PackageManagerCLI as part of a Continuous Integration system. I have a pipeline of several jobs running under Jenkins to compile libraries, update and build a project and create a package. Currently the last job in the pipeline is to install the package that has been built before running some tests. It fails intermittently as shown below. Typically if I re-run this build job the command works. Any ideas how to avoid this problem?
Hi,
there is already an issue to solve this in our bug tracker db.
CDS-50240 ComponentManager: Improve PlugInCache robustness
The Workaround is to delete\rename this Cache files in 'C:\ProgramData\AP\PlugInCaches\
BR
Edwin
Thanks for the fast response, I have put the suggested workaround in place and after ten builds have had no problems (previously it was failing 50% of the time).