Mastering GitHub Actions: Automate and Supercharge Your Development Workflow 

Theophilus Kibet - Software Eng @Kyosk 

Continuous Integration & Continuous Deployment 

What is Continuous integration? 

What is Continuous integration? - is a software development practice where developers frequently merge their code changes into a central repository, after which automated builds and tests run. 

Developer 1 Developer 2 Developer 3 Code Repository No CI 

Developer 1 Developer 2 Developer 3 Code Repository CI With CI 

What is Continuous Deployment? 

What is Continuous Deployment? - is a strategy in software development where code changes to an application are released automatically into the production environment(or qa, uat e.t.c). 

Tools used for CI/CD 1. Github Actions 2. Jenkins 3. Circle CI 4. TeamCity 5. Gitlab 6. Bamboo 

Github Actions? - Enables developers to define, customize and execute workflows directly within their GitHub repositories. 

Github Actions? - Enables developers to define, customize and execute workflows directly within their GitHub repositories. 

Workflows - refers to a series of automated steps or tasks that are defined in a YAML configuration file and executed in response to events in a GitHub repository. - This YAML file is placed in the .github/workflows directory in your repository, and it specifies the workflow's structure, including the jobs, steps, and actions to be executed. 

Workflows - refers to a series of automated steps or tasks that are defined in a YAML configuration file and executed in response to events in a GitHub repository. - This YAML file is placed in the .github/workflows directory in your repository, and it specifies the workflow's structure, including the jobs, steps, and actions to be executed. 

Triggers - Workflows are triggered by specific events that occur in the GitHub repository. - These events can include code pushes, pull requests, issues, comments, and more. 

Jobs - A series of steps executed by the same runner. - A workflow can have one or more jobs. 

Jobs - A series of steps executed by the same runner. - A workflow can have one or more jobs. 

Runners - are the environments where your GitHub Actions workflows are executed. - GitHub-hosted runners -> ubuntu, windows, macOs - Self-hosted runners -> your infrastructure 

Steps - actions or tasks that are executed sequentially within the job e.g building code, running tests or deploying applications. 

Steps - actions or tasks that are executed sequentially within the job e.g building code, running tests or deploying applications. 

Actions - reusable, shareable units of code that can be used within the steps of a workflow. - Found on github marketplace or created by you. 

Parallelism - Jobs within a workflow are executed concurrently on separate runners (virtual or self-hosted machines), which can significantly speed up the workflow's execution. 

Secrets and Environment variables - Workflows can securely access sensitive information, like API keys and credentials, by using GitHub's secret management. - You can also define environment variables that are available to the workflow steps. 

Workflow Artifacts - Workflows can produce and store artifacts, which are files or data generated during the workflow's execution. 

Notifications - GitHub Actions can be configured to send notifications or alerts to various communication channels, such as Slack, Microsoft Teams, or email. 

Show me the code!!!! 

Questions? 

Resources ● Github Actions Documentation ● Android CI-CD by VictorKabata @_kibetheophilus github.com/kibettheophilus 

No content