CI/CD for TIA Portal

CI/CD for TIA Portal means treating PLC code like software: versioned in Git, tested automatically in a pipeline and compiled before rollout. Instead of manual acceptance on every change, a pipeline guards every change against regressions automatically.

What does it look like?

AnyAutomation Studio provides two building blocks: test suites are plain-text JSON files next to the project — diffable and reviewable in Git. The tia-test-runner command-line tool runs them headless on the build server and writes JUnit XML that GitLab CI, Jenkins and similar systems display directly. --rerun-affected runs only suites whose block changed.

The end-to-end flow

The full value comes from the chain: AI generates → Openness imports → SCL unit tests verify → Git and CI/CD track every change. One-time acceptance becomes continuous quality assurance. Details in the unit testing documentation.

Frequently asked questions

What is CI/CD for TIA Portal?

CI/CD for TIA Portal means keeping PLC code versioned in Git, testing it automatically in a pipeline and compiling it before deploy — continuous integration and continuous delivery for automation projects.

Which CI systems are supported?

The runner produces JUnit XML and runs headless, so it works with GitLab CI, Jenkins and any pipeline that can run a command-line tool.

How do I integrate PLC tests into GitLab or Jenkins?

The tia-test-runner is called as a build step, runs the suites and returns JUnit XML that the pipeline shows as a test result. HTML reports can be stored as artifacts.

Can I version TIA projects in Git?

Yes. AnyAutomation Studio has built-in Git version control; test suites are plain-text JSON files versioned like any other code.

Does PLCSIM Advanced run in the pipeline?

Yes. Tests against PLCSIM Advanced run automatically, so the pipeline tests reproducibly without physical hardware.