Git Ur Pro Dev Workflow and Go From Continuous Integration Zero to Hero

Continuous Integration methodologies and tools can deliver huge efficiency gains for web development teams. However, overburdened with feature requests and new projects, many development teams never have the time to learn and implement a CI workflow. Now is that time.

In this training, we provide hands-on instruction on how to quickly setup a powerful continuous integration workflow for your team using Lando, Github, TravisCI, and several popular hosting platforms (Pantheon and Platform.sh) that can be easily repurposed on other projects.

Topics Covered in the first half of the day: Lando

• Docker and Docker Compose Basics

• Lando Basics

• How Lando makes Docker and Docker Compose easy

• Using Lando with Drupal

• Extending Lando’s Drupal recipes

  • Frontend node-driven tooling

  • Custom build steps

  • Event driven system

  • Auxiliary services like Solr, Redis, Memcache, Redis, Etc

• Advanced Lando Usage for Pro Users

  • Configuring services

  • Complex build steps

  • Custom requirements and scripting

Topics Covered in the second half of the day: CI

• What is Continuous Integration and Continuous Delivery?

• The why and how of GitHub Flow

• Overview of CI services

• Using TravisCI for test and build

• How to improve QA processes

• Basic automated testing concepts

Who Should Attend:

Although we encourage non-developers to attend, to participate in the hands-on portions of the training, you’ll need…

• A laptop with Git and Lando working

• A Github account

• A platform.sh or Pantheon account

• Experience using basic Git commands

• A working code editor

• Basic knowledge of code syntax

What You’ll End Up With:

• GitHub D8 repo

• Fully Baked Local Dev

• Composer Build Process

• Continuous Integration

• Continuous Delivery

• Automatic QA Environments

• Automated Testing (via Travis)

  • Linting/Code Standards/Unit Test/Behat Tests

• Hosting (Platform.sh or Pantheon)

Contact us if you need suggestions on resources to meet these prerequisites.

Non-technical stakeholders who are involved in the day-to-day development process will gain a thorough understanding of how a CI workflow works and why one should be adopted, but they’ll get the most out of the training by attending with one or more of their development team.