Deployment Pipeline - Unable to deploy from Dev To Test (even no error thrown)

[Anonymous]

Since Deployment pipline (preview) was launched, I was pretty excited to test the feature as there is immediate demand from my team to setup Release environment for all the reports, datamodels we are currently building.

As soon, i tested it... I am facing this unending rotating circle of "Copying the content" while i tried to deploy reports and dataset from Dev to Test (as per below image 1)

Image 1 :

And when i tried to refresh the entire browser to see what is happening, i am getting this below (Image 2) - 

(so basically i didnt get any error at all)

Image 2:

Not sure what exactly is the problem, despite complying to all the conditions required to use the Deployment pipeline as per Microsoft Documentation.

So any suggestion from the community can be of great help.  Thanks in advance.

[Nimrod_Shalit]

Hi,

this sounds like something that requires a support ticket.

From a first glance at your image, looks like the new WS created in Test isn't in a capacity,

which is required to complete the deployment process. 

please ask a capacity admin in your org to assign it to a capacity and try again.

regarding the experience, it should have provided an error message with the relevant details, so a support ticket will help us investigate why you didn't get one.

Thanks,

[Anonymous]

Thats surprising !!

Because the Workspace i used was hosted on Premium workspace. 

I believe when i Test environment workspace is created itself without any manual itervention i.e. assigning it to premium capacity seperately.  I am attaching 3 screenshots (Sequence by sequence of what i did). Kindly assist.

Step 1 :

Step 2:

Step 3: (when no error coming and i refreshed the browser)....  u see the test env. is created but no contents deployed in it from Dev to Test.

[Nimrod_Shalit]

it will not deploy content as long as the Test WS will not be in a Premium capacity.

As i said, there should be an error message that clearly indicates this problem.

[Anonymous]

True. I am not getting any error msg.

• So, shall i try contacting my PBI adminitrator for facilitating this Test environment into Premium workspace.
• If this works, then shall i again ask my Capacity admin to assign even the deployment workspace to be also allocated to Premium capacity ?

Lets suppose, If the above point doesnt work out, what shall be the next step i should take ? Should i raise a ticket ?

[Nimrod_Shalit]

Please ask your capacity admin to assign it and we will see if it works out.

Regardless if it works or not, please open a support ticket for the 'no error' problem,

if it's possible.

Thanks!

[Anonymous]

We have the same issue.

The automatically created Workspace Name [Test] workspace does not automatically get assigned to the Embedded capacity. The loading icon spins forever with no error message.

Manually assigning it to the Embedded capacity does not work either because the deploy (or deploy back) creates a new workspace: Workspace Name [Test] (1).

Please investigate this ASAP.

EDIT: The issue seems to be that I am not a CAPACITY ADMIN for the Embedded Capacity. I am only a SERVICE ADMIN. This means I can manually assign workspaces to the Embedded Capacity, but they don't automatically get assigned to the Embedded Capacity when created.

EDIT: SOLVED: The solution was to add me as a User With Assignment Permissions. This allows me to create workspaces on the Embedded Capacity by default.

[Anonymous]

I have suggested this proposal to my capacity admin. Let them get back. If this really works out, i will mark this as a solution.

[ChrisRenlund]

We have the same issue when trying to deploy from Test to Prod, even though both workspaces are in premium capacity.

Created a 2-step deployment pipeline yesterday by assigning one of our premium workspaces as a Production workspace. Then used the "Deploy to previous step"-feature to create a Test workspace, which got created as a premium workspace as well (labeled with the diamond). That all went fine, copied and synced from prodution to test within seconds. Today we published a new version of a dataset to Test, refreshed it and then clicked "Deploy to production". That has left us staring at the endless "Copying the content to this workspace" ever since. Refreshing the page brings us back to the screen showing that there are changes in Test not reflected in Production.

[Nimrod_Shalit]

Please open a support ticket, and provide all the pipeline details,

and if you can capture this through Fiddler, it would be very helpful.

[Anonymous]

Didnt know this feature existed for : - 

Deploy to previous step"-feature to create a Test workspace from Deployment Workspace 

Is that possible ? 🙄

[ChrisRenlund]

Yeah, if you choose Production when you assign the first workspace:

And then click the three dots in the top right corner of your production step in the pipeline - there you can find "Deploy to previous stage":

(It's greyed out here because I already deployed from production to test and you can only deploy to previous stage if the previous stage is empty).

So that's all well and good, but now I'd rather be able to deploy from test to prod 🙂