Create Pipeline Design authored by Neil-Jocelyn Schark's avatar Neil-Jocelyn Schark
On a meta view, the pipeline is split into two different pipelines, which run on different occasions.
![merge_train_eng.drawio](uploads/af9afc9236aa7e5595fd33a11bfd689e/merge_train_eng.drawio.png)
So to summarize it, we have two different pipelines (branch and merge request pipelines).
The branch pipeline is to check, if the code you are just writing is somewhat okay, as it runs the static code analysis and unit tests.
The merge request pipeline then checks if your code really works in a wider context, as it also runs the integration tests. At first only on you local changes, for easier debugging, if you remove all WIP or Draft tags, also in a simulated merge with the target branch.