For many years, I worked with the same tool and never really thought that a familiar process could be presented in a completely different way.

Everything worked, it was easy to understand, and that was enough. While working on my own project, I came across a different approach to visualizing CI/CD for the first time. It made me notice details I had never really paid attention to before.

Until then, all my CI/CD experience had been with Bitbucket CI Bot.

After every Pull Request, I received a report showing

• whether PHPStan passed,

• the coding standards were met,

• and the tests completed successfully.

That was enough to quickly understand whether everything was in good shape. I became so used to this format that I never really considered there might be another way to present the same information.

The first thing that caught my attention was how the entire process was presented as a sequence of stages.

Instead of reading a report, I could immediately see the whole pipeline - from build and code quality checks to testing and deployment.

Later, GitLab became more than just a way for me to visualize pipeline stages — it also became part of real infrastructure problems. In another case, I worked through how Composer, GitLab, Docker, and SSH Agent need to work together when an application depends on a private repository.

It took only a few seconds to understand exactly where the execution was at.

GitLab Pipeline did not change my understanding of CI/CD, but it showed me a familiar process from a different perspective. Instead of a short report with check results, I could see the complete sequence of stages and the connections between them.

Both approaches serve their purpose. CI Bot provides a quick overview of the check results, while GitLab Pipeline makes the entire process visible. That clarity was what pleasantly surprised me.