Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

better order component based on dependencies for packDeploy #521

Closed
KevinGossentCap opened this issue Nov 8, 2022 · 1 comment
Closed

Comments

@KevinGossentCap
Copy link
Contributor

VBT is already partially more or less ordering datapacks in some kind of order so that there is little dependencies errors at deployment.
But the dependency tree (I suppose) is not great and we frequently face errors of components that fail deployments because of dependent component not yet deployed.
It happens for products, but also for omniscripts/flewcards. You can easily use "industry CPQ LWC" and "ESM" as examples as they are vlocity own tools.
If a dependency tree is created as a pre-deployment step to list the datapacks in the right order, all deployments will see benefits as we'll loose a lot less time (especially while waiting for omniscript/flewcards compilation waiting timeout...)

@manas-sf
Copy link
Contributor

manas-sf commented Nov 9, 2022

There is not much that could be done on reordering datapacks. VBT is already following the best possible way out. Unfortunately it still fails for some dependencies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants