Ixchel Ruiz

Lights, Camera, GitHub Actions!

We refactored a complex 244-line CI/CD workflow into a clean 74-line reusable pipeline. This session shows you how.

Lights, Camera, GitHub Actions!
#1about 3 minutes

Understanding the core components of GitHub Actions

A workflow is triggered by an event and contains jobs with steps that run on hosted or self-hosted runners.

#2about 7 minutes

Configuring workflow triggers with events and filters

Workflows can be triggered by repository events, schedules, or manual dispatches, with filters for branches, tags, and paths to control execution.

#3about 10 minutes

Sharing data between jobs with contexts and variables

Use contexts, environment variables, inputs, and outputs to pass information between different jobs and steps in a workflow.

#4about 6 minutes

Managing job dependencies and concurrency

Control the execution order of jobs using the `needs` keyword and manage parallel runs with concurrency groups to prevent race conditions.

#5about 4 minutes

Creating modular pipelines with reusable workflows

Avoid duplicating code by creating reusable workflows that can be called from other workflows, passing secrets and inputs as needed.

#6about 6 minutes

Demoing manual inputs and job dependency results

A practical demonstration shows how to use different input types for manual triggers and how job dependencies affect skipped or failed jobs.

#7about 13 minutes

Refactoring a repetitive Java build with reusable workflows

A complex multi-OS Java build workflow is refactored into a cleaner, maintainable pipeline by extracting common logic into a reusable workflow.

#8about 15 minutes

Answering audience questions on GitHub Actions

The speaker answers questions about comparing GitHub Actions to other CI/CD tools, optimizing performance, and its future evolution.

Related jobs
Jobs that call for the skills explored in this talk.

Featured Partners

From learning to earning

Jobs that call for the skills explored in this talk.