Solved

Will different cumulative update and fix pack versions cause deployment issues between environments?

  • 18 June 2020
  • 1 reply
  • 4 views

Badge +2

We are currently running K2 5.2 (5.0003.1118.0). To get to the latest, we're planning on applying:
1) K2 5.2 May 2019 Cumulative Update
2) K2 5.2 May 2019 CU FP 41

We have 3 environments that we will be upgrading - Dev, Preprod and Prod. Our plan is to deploy to Dev, test cycle, then upgrade to Preprod, test cycle, then upgrade to Prod. This will likely take 3 weeks to complete. We have ~30 Prod workflows: 5 in K2 Five (app and workflow) and 30 legacy (migrated from K2 Blackpearl workflows, using ASP.Net front end forms).

 

My question is for work going on during this time, could there be any problems with deployment version mis-match (either in K2 Five or our legacy workflows)? 

The example scenario is: we upgrade our Dev environment first. We have a solution that needs to be promoted from Dev, to Preprod to Prod. We create a deployment package in the upgraded Dev environment, and want to deploy it to our un-upgraded Preprod and Prod environment. 

icon

Best answer by lkimberly 19 June 2020, 16:58

View original

1 reply

Userlevel 4
Badge +13

Hello  @adiamond ,


 


I did a quick test in 5.2 deploying a package created from a higher environment on 5.2 May 2019 CU FP 40 to a lower environment on 5.2 May 2019 CU and didn't encounter any deployment issues. So for your scenario, the P&D tool should not block you from deploying the package on the intended prepod and then to prod environments. Of course, we still always recommend that all environments be on the same version to avoid any incompatbility issues that may arise. As for legacy workflows in particular, just make sure the target environment has the legacy client tools installed. 


 


 


Regards,


Kimberly 


K2 will not accept any liability for any issues arising from actions taken in respect of information provided by any forum member.

Reply