Deployment pipeline more agile between dev and test, and approval between test and prod?

Mikael Karlsson · ‎08-27-2024

Hi, just started with AES and AEMC and some questions have come up.

How could we configure Deployment Pipeline / AEMC to allow our developers to publish between Dev and Test without any approval? This could happen multiple times before finally deciding to deploy to production, i can't see that they have the option to choose if they intend the submission for test or prod.

Consider something like this which must be common:

Submit app in Dev
1. Approval is created for deployment Dev-Test
  1. Approved, app installed into Test, approval task automatically created for Test-Prod
2. Developer finds bug in Test which needs fixing in Dev (but the production deployment request is still pending and will be pushed to Prod if approved, how can the developer prevent this)

Mikael Karlsson · ‎09-09-2024

I'll try to conclude the thread, today there seems to be no OOTB way to designate if the app submission should go all the way to production or if the submission was just part of normal dev-test procedure. To accomplish what we are looking for we will likely have to modify the existing flow or adding a wrapper control flow to automatically handle the approvals based on data which is available in the deployment request. Perhaps a good feature request for the long run would be to surface the choice of the approval flow just like it's done for the App Service creation subflow to stay clear of customizing the shipped flows.

View solution in original post

Laxmi2 · ‎02-27-2025

Hi

Can we skip some steps and still do deployment to other instance?

example: can i skip

basically the change flow and ATF functionalaties.

can i do it without adding these

Mikael Karlsson · ‎02-27-2025

The guided setup goes over those steps quickly and you don't have to select any tests or suites, just follow the guided setup. I don't think many organizations use those features during deployment yet.

Artur ___kiews2 · ‎09-06-2024

@Mikael Karlsson if you submit app version 1.0.1 and if it will be approved it will go to the TEST for example. If no one will approve to production (1.0.1), devs can submit 1.0.2 and previous deployment request will cancelled.

So devs can do multiple version till no one approve it to prod.

Mikael Karlsson · ‎09-06-2024

Thanks @Artur ___kiews2 ideally our App Engine admins which are the approvers should only need to reject prod deployment in case something violates our guidelines etc and our ambition is to approve whenever possible. So in order for your suggestion to work, our developers must reach out (quickly) to the admins and tell them to not approve a certain request and i don't that will fly here at least.

Or does your citizen developers and remote development teams do their own deployment approvals for prod without App Engine Admin involvement? If the approval was done by the team themselves then sure they could maintain such process.

Artur ___kiews2 · ‎09-06-2024

@Mikael Karlsson The only condition in case of deployment app in App Engine are approvals. In that case good idea will be to modify the flow to check not only if the target instance = production but also certain states in the Deployment request. So approvals for production will appear only if those 2 conditions will meet ( state and target instance )