Implement testing and validation processes to ensure only authorised changes are promoted to Higher Environments

[AEM_Forum]

Hi,

In an AAM implementation, how to ensure only authorized changes are promoted to production (Development, Test, and Production Environments)?

Like someone designated for this task will look at all changes and approve some and disapprove others and only approved changes move forward.

My understanding is that if we integrate SVN (source code system), only bug free code could be checked in and only checked in code could be moved up in the higher environments.

Before checking in, we perform correct amount of testing.

Is this view correct, or any other option is available, either out of box or through any tool?

The other point is that typically out of all AMC products, only AEM has Java code along with JS, CSS, etc, but all other AMC products have just JS or just configurations.

If it is JS, it could be stored in a source code control system, like SVN, how to version configurations?

Also, how to move configurations to higher environments automatically, given that they are not stored in SVN?

In the absence of automatic deployments options, do we have to manually configure?

Appreciate your support.

Thanks,

Rama.

[dsrehan3]

Hi, check this out for the first section of your question - Beta Environment

[Gaurang · Accepted solution]

Hi Rama,

Most of the code and deployment for AAM is managed by Adobe since it is a deployed solution and you consume it like a service. Consider it similar to website that you access and provide your inputs and wait for output.

Hope this helps you.

Thanks,

Gaurang