I started using rules, as you suggested, I noticed some changes:
Below you can see example MR. When opening merge requests, my pipeline is splited into two parts, regular, and detached. Regular (three step) has test, build and deploy. Detached (upper) has only build and deploy.
- Right now, test results are not displaying in MR overwiev (like it was before).
- For some reason, deploy step (after manual build) is always failed (with error: The deployment job is older than the previously succeeded deployment job, and therefore cannot be run)
- Merging is not possible, until all manual actions are completed (this will probably be fixed with “Skipped pipelines are considered successful” in Settings->General->Merge Requests)
I tried to find a root of “detached pipeline” behaviur. The “detached” label popup mentions “Pipelines for Merged Results” which is premium feature (not used by me, there is no “merge trains” or “pipelines for merged results” in my settings)
Can you help me with that?
even with checking “skipped pipelines are considered successful” all the manual steps has to run before merge request is merged. Is this a bug?