When upgrading Appian, how do you test the upgrade and continue your normal development and deployment lifecycle simultaneously?

We have 3 cloud based environments: DEV, QC & Production.

When the Appian platform is being upgraded on the cloud, we can schedule the date/time it happens for each environment.

General good practice is that you should upgrade your non-production environments first. After a period of regression testing on those environments, you upgrade your production environment.

Now, if we upgrade our non-development environments first for a period of a week to give the developers and software testers time to do their regression testing, we cannot deploy any new features or bug fixes to production during this time as the Appian versions on DEV/QC are different to Production. This is a major problem if during that week of testing a critical bug is found in production that needs to be fixed and deployed to production ASAP.

How do you all handle this?

  Discussion posts and replies are publicly visible

Parents
  • Thank you both for the feedback.

    Considering we only have the 3 environments, my initial thoughts were that we should first upgrade our QC environment for a week of regression testing. This way, we can deploy urgent hotfixes from DEV to Production.

    However, can you please confirm....during this time of regression testing on QC, can we still deploy from DEV to QC because DEV on on a lower version than QC?

Reply
  • Thank you both for the feedback.

    Considering we only have the 3 environments, my initial thoughts were that we should first upgrade our QC environment for a week of regression testing. This way, we can deploy urgent hotfixes from DEV to Production.

    However, can you please confirm....during this time of regression testing on QC, can we still deploy from DEV to QC because DEV on on a lower version than QC?

Children