AEM Cloud pipelines - no way to build core now full stack has been removed as an option?

[TB3dock]

we use "full stack" for all our non prod pipelines.  It builds, tests and deploys our front end code (react/js/css etc) in ui.xxx dir, our backend java code in core dir, and the dispatcher configs in dispatcher dir.

We have always wanted to separate our dispatcher, so we can a) make redirects and domain changes outside of our 3 week release cycle, and b) reduce the time take to build our FE and BE. However, this was never possible because adobe forced you to split the FE and BE into different pipelines, and we never make only changes to FE or BE, for every FE change there are corresponding java changes to models etc. and to release them separately will always break the site.

Every now and again we check in cloud manger to see if Adobe have added anything which helps us with our unacceptably long build times, and we now see this:

Adobe have disabled the full stack build for non prod, by the look of things, but they have only added dispatcher (strangely called "web tier config") and FE builds, there appears to be no option to build the backend (e.g. java in the core dir)

Any suggestions to whats going on?

[EstebanBustamante]

Hey @TB3dock, usually, the "Full stack" type of pipeline is disabled because you can only have one of these types per environment. Could you please double-check your pipelines to see if you already have one defined? 

In regards to your pipeline use case, is there any error or issue you are seeing that is blocking you to split the Dispatcher deployment from the regular "full stack" deployment (FE and BE)? 

Reference:

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-...

[TB3dock]

Yes, we cant split out dispatcher into its own pipeline, because then you have to separate FE and BE into separate pipelines, which makes it unusable.

We always change FE and BE code together, e.g. we edit models or servlets in Java, then edit the components in the FE to use these changes. It would be unusable for these to be in different projects or built and deployed separately, from both a developer point of view, and breaking the environments point of view (as if one is deployed without the other, it wont work).

We want to separate dispatcher, so we can make emergency changes to apache configs, but we cant separate FE and BE code or builds.

[EstebanBustamante]

Sorry, I am not following up. Did you try this configuration? Are you seeing any errors? At least I could detach the Dispatcher configs into its own pipeline(WebTier) and the other pipeline will deploy the FE+BE (Fullstack) without issues. So I am not sure what behavior are you seeing on your end.

[TB3dock · Accepted solution]

I have found the answer, and its quite unbelievable. Adobe have named two different thing the same thing.

"full stack" is both:

1) the legacy full stack pipeline, which builds and deploys dispatcher, front end and backend code as one. WE use this for all our pipelines, but dont want to.

2) the Backend code only, if you split into dispatcher (renamed "web tier"), Front end, and backend (now named "full stack", in direct conflict with the existing use of the term.