Small manufacturer of safety systems

One development process for software and hardware: GitLab, CI and OpenProject, self-hosted

Industry
Safety systems (hardware and software)
Company size
Small company
Frybad's role
Advice on the development process; set-up and integration of the tooling
Stack
GitLab, GitLab CI, OpenProject, paperless-ngx, virtual machines, SMTP, LDAP, SAML2

Starting point

At this manufacturer, hardware and software are developed together: firmware, designs and models, plus tests that run on the real device and can take hours. The new development cycle was to carry all of it through one Kanban flow, from task to tested version. The tooling was missing: version control with pipelines, task and project management, and a place for the documents that hardware development produces. Everything had to run in-house and be usable with one sign-in.

What we did

  • Process first. With the customer we defined how tasks, code, designs and test results move through the Kanban flow and which tool takes which role.
  • Tools on their own VMs. GitLab for code, designs and models, GitLab CI for builds and the hook-up of the hardware tests, OpenProject for tasks and projects, paperless-ngx for documents. All on virtual machines in the customer’s environment.
  • Integrations. E-mail via SMTP for every tool; sign-in via LDAP and SAML2 coordinated so that one account works everywhere.
  • Accompaniment. From advice to day-to-day use by the team.

Why hardware tests belong in the pipeline: a test that runs on the device cannot be repeated at will. When the pipeline triggers it and records the result against the commit, it is traceable which version was tested, and the test is not forgotten.

What this means for your project

If you are introducing a development process or want to run tools like GitLab in-house, start with Software development & architecture. If it is about pipelines and operations, it is Cloud-native DevOps & SRE.

Result

Example from a client project.

The Kanban development cycle runs on GitLab, GitLab CI, OpenProject and paperless-ngx in-house, with one sign-in for every tool.

Not included: numbers.

What we would do differently today

Sign-in first. Coordinating LDAP and SAML2 for four tools is easiest before the first accounts exist. Every account merged afterwards costs time.

Plan for test artefacts. Hardware tests produce large result files. Retention and storage for them belong in the CI planning, not in the first full disk.

Similar situation?

Tell us how your development runs today and which tools should stay in-house. We will say where we would start.