A workflow is triggered by an event and contains jobs with steps that run on hosted or self-hosted runners.
Workflows can be triggered by repository events, schedules, or manual dispatches, with filters for branches, tags, and paths to control execution.
Use contexts, environment variables, inputs, and outputs to pass information between different jobs and steps in a workflow.
Control the execution order of jobs using the `needs` keyword and manage parallel runs with concurrency groups to prevent race conditions.
Avoid duplicating code by creating reusable workflows that can be called from other workflows, passing secrets and inputs as needed.
A practical demonstration shows how to use different input types for manual triggers and how job dependencies affect skipped or failed jobs.
A complex multi-OS Java build workflow is refactored into a cleaner, maintainable pipeline by extracting common logic into a reusable workflow.
The speaker answers questions about comparing GitHub Actions to other CI/CD tools, optimizing performance, and its future evolution.
Hubert Burda Media
München, Germany
1:05:06Chris Ayers
36:33Marcel Lupo
45:28Julien Delange
58:19Bassem Dghaidi
56:19Pawel Piwosz
24:19Johannes Haux
44:42Michael Cade
50:02Liviu Costea
Jobs that call for the skills explored in this talk.
Optomi LLC
Schiller Park, United States of America
Optomi LLC
Oakbrook Terrace, United States of America
Optomi LLC
Oakbrook Terrace, United States of America
Optomi LLC
Stone Park, United States of America
Optomi LLC
Harwood Heights, United States of America
Optomi LLC
Wood Dale, United States of America
Optomi LLC
River Grove, United States of America
Optomi LLC
Berkeley, United States of America
Optomi LLC
Elk Grove Village, United States of America
