Solved

Execute and deploy takes entire project

  • 19 January 2023
  • 5 replies
  • 108 views

Hi,

 

When executing and deploying a project it does every single table and change, not just the changes I have made since the last deployment. In other projects, it only deploys the selected tables or changes made. But in our biggest project (deployment takes roughly 15 minutes each time) it does all or nothing.

Even when in a perspective it still does every other table that exists in the entire project.

Other projects don't do this and I can't seem to find the setting that changes this for the big project. Does anyone know how to set this up?

Thanks!

icon

Best answer by Thomas Lind 19 January 2023, 10:05

View original

5 replies

Userlevel 6
Badge +5

Hi Robin

Open the other project where it works and attempt to deploy the whole thing. Be sure to choose the Review Tasks. See what tasks it wants to deploy if any.

Do the same in the project where it always wants to do this.

In the past people who shared parts of the project with other environments experienced this. So they would share the BU Staging database between two environments.

Regards
Thomas Lind

Hi Thomas,

Even if I select 3 out of 400 tasks, it will start with the 3 tasks and then continue to deploy the other 397 remaining tasks.

Thanks for helping out again!

 

Nevermind, figured it out. It was selecting the projects full execution as a package which was just always checked. I unchecked it and now it works.

@Thomas Lind  I meant to select your answer as the best, can you change it for me? Thanks!

Userlevel 6
Badge +5

@r.depagter I’ve changed the best answer now :)

Reply