Jenkins is *not* CI

(Continuous Integration)

Jenkins does NOT equal continuous integration (CI).

Many teams believe:

“We have Jenkins, therefore, we are practicing CI.”

This is wrong.

Jenkins is just a tool

If a team has Jenkins, but developers work on long-lived branches for days or weeks, then they are not practicing CI.

If merges happen only before release day, they are not practicing CI.

If testing is mostly manual, they are not practicing CI.

If bugs are discovered late, they are not practicing CI.

No TDD = no CI

Without automated tests you CANNOT:

• merge code frequently without fear of breaking things

• ship small, incremental changes

• catch regressions early in the pipeline

• get fast feedback from unit tests

• verify system behavior with acceptance tests

Releases are big, risky, and infrequent.

Do you have CI?

Don’t ask:

“Do we have Jenkins?”

Ask:

• Do we merge into main daily?

• Are we protected by automated tests?

• Do we have Trunk Based Development (TBD) or short-lived branches?

• Can we merge safely multiple times per day?

• Is the main branch always releasable?

If the answer is “no” to most of these, you don’t have CI.

You have a build server.

CI in practice

This workshop is for Senior Engineers & Tech Leads who are:
▪ Stuck with stressful releases
▪ Stay late fixing production deployments
▪ See releases break critical paths that nobody tested

Limited spots. Register now with the early bird discount - 100 EUR off with code EARLYBIRD100