# CI/CD

### What is CI?

CI stands for 'Continuous Integration', which describes the automated process from writing code to deploying the application. Basically, this process consists of the following steps:

* Development
* Version control
* Build
* Test
* Report Release

<figure><img src="/files/IOusIhpNojDNsPeniFxA" alt="" width="325"><figcaption></figcaption></figure>

### What is CD?

CD stands for 'Continuous Delivery', which describes the process of releasing new features on a regular basis through different environments. A common setup for this is the 'DTAP' street (in Dutch 'OTAP straat'), which stands for 'Development' (Ontwikkel), 'Test', 'Acceptance' and 'Production'.

The idea is that you first deploy new features to a 'Development' environment so that the development team can test the new features here. If these work well, you can deploy to the 'Test' environment where testers can test the new features. After this, the deployment can take place to the 'Acceptance' environment where the customer can test and 'accept' the new features and then be deployed to the 'Production' environment where the new features can be used by the end users.

This process ensures that new features can be deployed on a regular basis to the next environment for testing, until they end up in the 'Production' environment. This way, the development team can work on a new feature while the testers are still testing the previous new feature and while the customer is testing an even earlier new feature to be able to accept it so that it can go to 'Production'.

<figure><img src="/files/tk0D89FAtwR96TuXuzjH" alt="" width="563"><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://valtimo-cloud.gitbook.io/untitled/learn-more/ci-cd.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
