Skip to content

Coding & Software AI

CI/CD

Continuous integration and continuous delivery/deployment

Automated practices for testing, building, and releasing software changes.

Example

Every pull request automatically runs tests, checks, and a preview deployment.

Why it matters

It makes repeated testing and release work more consistent and less manual.

You'll hear it

“The automated checks passed, but release still needs approval.”

Can you control it?

Sometimes

Sometimes. Some products or workflows let you influence CI/CD, while others keep it fixed or manage it automatically. Check the settings and documentation for the tool you are using.

Common questions

Does automation guarantee a safe release?
No. Missing tests or incorrect configuration can let problems through.
Can different stages have different permissions?
Yes. Testing and releasing can be separated to limit consequential actions.
Does every code change have to go live immediately?
No. Projects can use review gates or planned release schedules.

AI chatbot

Still have questions?

Ask the AI chatbot about this term or another AI concept.

Up to 500 characters.

Ask LATHIC about AI. Relevant glossary entries may be included.

Your question, the glossary entries it matches, and a rotating pseudonymous identifier go to Microsoft Azure’s OpenAI service through Vercel AI Gateway to generate an answer. Zero retention and no training are required of the provider, and LATHIC does not save your question or answer. Privacy Notice