Continuous integration
Continuous integration regularly merges changes into a shared codebase. Automated checks can reveal certain conflicts earlier.
Continuous integration, or CI, is the regular integration of small changes into a shared development state. Automated builds and tests can check whether that state passes the defined checks.
In a hypothetical product import, sku is renamed to productCode while another part of the program still uses the old name. A suitable integration test on the shared version can reveal this break. Separately tested changes might miss it.
CI does not simply mean turning on a particular tool. Checks must suit the application, and failures need attention. A green run establishes only the checks actually performed. It guarantees neither freedom from errors nor automatic approval for production.
Sources
Related terms
- Continuous deliveryContinuous delivery prepares software changes for release through a repeatable process. Approval for production can remain a deliberate decision.
- Software releaseA software release is an identified software version made available for a particular use. Publishing it does not automatically switch every system to it.
- Return-PathReturn-Path records the SMTP reverse path in a header. It explains the technical route for error reports, not a person’s identity.
- Envelope-FromEnvelope-From identifies the SMTP sender for transport and error feedback. It must be distinguished from the visible sender address.
- DMARC aggregate reportA DMARC aggregate report summarises a reporting mail system’s domain checks over a period. It helps examine sending sources and misconfigurations.
- DMARC policyA DMARC policy describes the requested handling of failed domain checks. It repairs neither sending sources nor their alignment.
Articles on this topic
Cloud & Operations with ASES
Hosting, deployment, maintenance and support