Do you separate CI and CD in your architecture?

Market insights

Stack

Apply

Upload your CV — we will connect you with the employer directly through our pool.

Description

Do you separate CI and CD in your architecture? Most setups I’ve seen treat CI as the release system too (build, test, deploy, rollback...). I don't like this approach. GitHub, GitLab, Jenkins — these are great services but they are not really designed to manage releases. Do you separate CI/CD? If yes, what tools do you use, & why? Or do you keep everything in one pipeline? Curious to hear different thoughts [link] [handle]

Employer contacts (email/phone/telegram) are hidden from the public preview — send your CV, and we will connect you directly.