𝗪𝗶𝗿𝗶𝗻𝗴 𝗧𝗵𝗲 𝗚𝘂𝗮𝗿𝗱𝗿𝗮𝗶𝗹𝘀

𝗪𝗶𝗿𝗶𝗻𝗴 𝗧𝗵𝗲 𝗚𝘂𝗮𝗿𝗱𝗿𝗮𝗶𝗹𝘀

I want to reach Level 5 engineering. I document the climb in real time.

My tests lived on one machine. They passed locally. They meant nothing once others touched the code.

I built a GitHub Actions pipeline. It runs four jobs in order:

• test
• pact-consumer
• pact-verify
• deploy-check

If one job fails, the rest stop. This is a guardrail.

I learned two lessons.

First, fix your baseline. I found a failing test before starting. I fixed it with aliases. If you start with red, your team ignores red.

Second, remove duplicate roles. I had a port conflict. My YAML and my tests both tried to start servers. I removed the YAML step.

Now, breaking changes block the merge. Gherkin proves the system works. Pact proves contracts match. You need both.

The final step is branch protection. Set your repo to require status checks. Without this, the pipeline is only a dashboard. It must be enforcement.

CI is not about the config file. It is about the discipline of what green means.

Ninety minutes of work makes the infrastructure real.

Source: https://dev.to/diyaburman/wiring-the-guardrails-2oli Optional learning community: https://t.me/GyaanSetuAi