How to organize teams for CI/CD implementation?

Question

Angular

We want to implement CI / CD in our company (project). At the moment, we have two teams that are sawing mono-releases in parallel (semi-annual, 4-5 sprints).
The composition of the teams is approximately the following: 5 fronts, 5 backs, 3 SQL, BA, PM and a QA team
There was a proposal to divide the teams into profiles: Front team separately, back + skl - each will have its own backlog, and they work, in principle, independently, front is just a consumer of apexes that releases back + skl We
don’t yet understand whether such a model is effective or it’s better to make small teams, but full-stack ones (front + back + skl)
Share your experience, please

Answer 1

Can you please tell me how you see the connection between the current and / or proposed by you separation of teams and CI / CD processes? In my opinion, CI / CD can be equally successfully used in any of the structures you voiced, but your question is apparently not about that.

Answer 2

CI/CD is not the organization of commands, it is the organization of the process of automatic assembly/deployment/testing.
To do this, a devops / admin or a developer rummaging around in this topic comes up with rules (branching name conventions, versioning, sets up the appropriate tools and infrastructure (teamcity / jenkins / some kind of bitbucket thread with pull requests. In order for a build to be assembled by commit, unit tests pass, the result is deployed to the test environment, autotests were launched, the result was returned to the pull request and confirmed the
action.To deploy to the test environment with one button, so that the deployment to the production was done with one button with preliminary confirmation and appraisal also in digital form.That's all.And the
commands
are like anything can be done.