Forum Discussion
Cannot deploy environment through deployment pipeline
- 2 months ago
Hi JarneT ,
Glad to hear you got it working!
This behavior aligns with how the two publish modes are designed. Quick mode is intended for rapid, session-scoped iteration - libraries published in Quick mode install at notebook session start rather than being fully baked into the environment snapshot. As a result, Quick mode libraries may not be properly packaged for deployment pipeline export, which can cause the "Export failure" error you encountered.
For any libraries that need to travel across pipeline stages, Full publish mode is the recommended approach, as it creates a stable, portable environment snapshot.
Reference: Manage libraries in Fabric environments - Microsoft Fabric | Microsoft LearnHope this helps. Please reach out for further assistance.
Thank you.
Thank you for the reply!
I made a new environment, uploaded the wheel (in full mode) and then published succesfully.
I then went back to my original environment, deleted the wheel in quick mode and re-uploaded it in full mode and now the deployment succeeded as well!
Is deploying from quick mode not supported then, or is this unintended behaviour?
Regards,
Jarne
Hi JarneT ,
Glad to hear you got it working!
This behavior aligns with how the two publish modes are designed. Quick mode is intended for rapid, session-scoped iteration - libraries published in Quick mode install at notebook session start rather than being fully baked into the environment snapshot. As a result, Quick mode libraries may not be properly packaged for deployment pipeline export, which can cause the "Export failure" error you encountered.
For any libraries that need to travel across pipeline stages, Full publish mode is the recommended approach, as it creates a stable, portable environment snapshot.
Reference: Manage libraries in Fabric environments - Microsoft Fabric | Microsoft Learn
Hope this helps. Please reach out for further assistance.
Thank you.