DevOps + Infrastructure

Supported by

The DevOps + Infrastructure track is about getting services up and running in a sustainable controllable way. Not just for Drupal sites but also for other services and technologies.

How we develop our Drupal sites has changed significantly in the last few years. Composer based workflows, containerized local development, automated testing, continuous deployment and other practices are no longer “nice-to-haves” but business critical parts of every development cycle. Come learn how to deploy better quality code, speedily and frequently, and unlock new efficiencies and value for your business or organization.


Suggested topics:

  • Composer based workflows (e.g. GitHub, Bitbucket, Gitlab)

  • Automated testing and continuous delivery/deployment (e.g. Travis and CircleCI)

  • Container Orchestration, Virtualization and Cloud Infrastructure

  • Why my business or organization should adopt DevOps practices

  • Best practices in modern deployment, hosting, scalability, and performance

  • Best tools and practices for DevOps

  • Case studies of Distributed Monitoring and Automation at Scale


Track chairs

Profile picture for user robertDouglass
Chief Customer Success Officer
Profile picture for user ricardoamaro
Senior Site Reliability Engineer

Session proposals

How open source will help you to survive the next Drupalgeddon

Profile picture for user dasrecht
System Engineer

Security isn’t a product - this should be a metaphor you already heard quite a lot by now. But how to mitigate the next known or unknown threat? Think about security as an onion.

Visual Regression Testing + You

Chaos Wizard

Visual Regression: the process of capturing, tracking, and analyzing screenshots to catch unexpected changes as they happen. This session will discuss setting up a bare bones workflow and taking it further with headless and full-browser testing.

Willy Wonka and the Secure Container Factory

Managing Director
Dave Hall Consulting

Hold your breath, make a wish
Count to three

Come with me and you'll be
In a world of pure implementation
Take a look and you'll see into your pipeline
We'll begin with a spin
Securing containers of your creation
What we'll see will have lots of explanation

The container is a lie!

Profile picture for user Crell
Director of Developer Experience

How containers (not Docker, containers), work, from the CPU through the operating system all the way to cloud hosting.

Standarized DevOps Pipelines for Drupal

Profile picture for user willhallonline
Principal Devops Engineer

Can we standardise Drupal DevOps pipelines between different platforms, agencies, self-hosters and cloud providers? What are our expected deployment practices and how do we achieve scale between the smallest and largest demands of DevOps pipelines? In this session I intend to discuss and show how DevOps practices can be shared between different platforms and different DevOps pipeline providers (GitLab CI, Circle CI, Travis CI,, Jenkin

Continuous Integration with CircleCI, GitLab CI and Webhooks

Profile picture for user leymannx
Lead Web Developer
Ayusa-Intrax GmbH

Are you afraid of code releases on Friday afternoon? You don't have to be anymore. With the right continuous integration strategy you could release during peak times without any problems. An overview of automated deployment routines for Drupal with webhooks, CircleCI and GitLab CI.

Automate your Drupal site using Behat with Mink and Drupal extension

Profile picture for user Parvateesam
Sr. Drupal Developer
Tata Consultancy Services

Behat, an open-sourced behavior-driven framework for PHP.  Behat is a tool that makes behavior-driven development (BDD) possible. With BDD, you write human-readable stories that describe the behavior of your application.

These stories can then be auto-tested against your application. And yes, it’s as cool as it sounds!



GitLab Review Apps with Drupal

Profile picture for user morenstrat
DevOps and Backend Developer
Reinblau eG

Automatic Drupal instances per Git branch under your control, on your own server.

When working with a (remote) team and/or for your sprint review, it is essential that your colleagues, product owners or stakeholders can easily try out your software, that is, not only see, but also make use of what you have implemented. Preferably, this should be possible for each branch in your repository.