Comments
Sort by recent activity
Please correct me if i am not getting it right. In the 5th and 6th steps of using PRE/POST DEPLOYMENT SCRIPTS, 5. . Deploy this change to all environments, including prod and all dev workstations 6. Re-link static data This means ,that i can re-link the table back to source control, only after making sure that, all DEV workstations(which is local to each developer) have done a PULL and applied the changes. So,if any DEV workstation fail to do so,and trying to do a PULL and APPLY CHANGES after i re-link the table ,then, it can fail. Kind Regards minijebu / comments
Please correct me if i am not getting it right.In the 5th and 6th steps of using PRE/POST DEPLOYMENT SCRIPTS,5. . Deploy this change to all environments, including prod and all dev workstations6. ...
Hi Alex, I have not thought about the option of moving the change to every workstation. I am trying to see if on each DEV work stations,we can do a PULL once and APPLY all the changes at once. Since we have so many DEV workstations , i find it difficult to apply the changes on each of them once i PUSHed each step in this process.I hope i understood you correctly on : 'AND TO EVERY DEV WORKSTATION' . And since we are in the moving phase of of automated deployment,currently the production is not yet part of it.We are working on it. Right now,the deployment is to a shared DEV environment only. So,i can actually rollback the changes i did and I will go for PRE/POST DEPLOYMENT SCRIPTS. Kind Regards minijebu / comments
Hi Alex,I have not thought about the option of moving the change to every workstation.I am trying to see if on each DEV work stations,we can do a PULL once and APPLY all the changes at once.Since w...