Application Packaging & Deployment| Appian 7.8 Is there any best

Application Packaging & Deployment| Appian 7.8

Is there any best practices around the same topic..
We have an application being tested in QA environment but it's going under continuous iterations both ( design & business)

So when ever we push the new changes from Dev to QA, do we need to make new Application Patch sets and add only changes to QA or add the new changes to existing Application bundle already deployed to QA, and then redeploy the full application again even few Appian objects updated/added and rest Appian objects remains as earlier but will end up creating new versions for Appian objects which were never updated

Which one is the best approach and why ?

Thanks,
Abhinav

OriginalPostID-152458

OriginalPostID-152458

  Discussion posts and replies are publicly visible

Parents
  • I would recommend to create patch everytime you want to deploy code with objects you want to move. By doing this tou will get following benefits:

    1. It will help you to track what changes went and will help you to rollback changes if anything goes wrong

    2. You will have proper understanding about the changes going in higher environment as tou can track them via versions

    3. Adding only the objects with changes will help tou in quickly review and deploy.

    Hope it answers your doubts
Reply
  • I would recommend to create patch everytime you want to deploy code with objects you want to move. By doing this tou will get following benefits:

    1. It will help you to track what changes went and will help you to rollback changes if anything goes wrong

    2. You will have proper understanding about the changes going in higher environment as tou can track them via versions

    3. Adding only the objects with changes will help tou in quickly review and deploy.

    Hope it answers your doubts
Children
No Data