- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-20-2024 06:54 PM
Hello,
Reopening this ticket in hopes that either of you had some luck in resolving your bug. I am currently facing the same issue where I can deploy an asset bundle via the local CLI without issue (by deploy I mean the bundle code is written to my workspace and the Workflow is created). However, when I try to deploy my bundle via an Azure DevOps pipeline it only uploads the bundle resource code but no workflow is created.
The interesting similarity to @jorperort reported issue is that no deployment.json file is created in the case where the Workflow isn't created (aka the situation in which I use an Azure DevOps pipeline). I'm not sure why I can deploy the bundle & associated workflow via local CLI when I am authenticated with a PAT but when I use that same PAT in the Azure DevOps pipeline I am unable to deploy the actual workflow (but still in this case the code is written to the .bundle folder I specify).
Any suggestions would be greatly appreciated.