WHAT IS GITHUBACTIONS?
GitHub Actions are a custom software developmet workflow automation tool
We can automate, customize, and execute our software development workflows
right in our repository with GitHub Actions. We can discover, create, and share
actions to perform any job we need, including CI/CD, and combine actions in a
completely customized workflow.
In short:
GitHub Actions are an automated process that allows us to build, test, release
and deploy any code project on GitHub, but we can also use it to automate any
step of our workflow such as merging pull requests, assigning levels, triaging
issues etc
Learn.sandipdas.in
GITHUB ACTIONS COMPONENTS
1.WORKFLOW
Workflow is a configurable, automated process that we can use
in our repository to build, test, package, release, or deploy your
project. Workflows are made up of one or more “jobs” and can
be triggered by GitHub events.
Workflow Files
Workflows can be created inside the .github/workflows directory
by adding a .yml/.yaml workflow file. For example, add
.github/workflows/build_and_deploy_action.yaml to your project.
Workflow Sytax
Github Actions files are written using YAML syntax and have
either a .yml or .yaml file extension
Workflow Name
The name of your workflow is displayed on the Github
actions page. If you omit this field, it is set to the file
name.
Learn.sandipdas.in
6.
GITHUB ACTIONS COMPONENTS
2.ON EVENTS The on keyword defines the Github events that trigger the
workflow. We can provide a single event, array, or events
or a configuration map that schedules a workflow.
Scheduled Events
schedule event allows us to trigger a workflow at a
scheduled time
Learn.sandipdas.in
7.
GITHUB ACTIONS COMPONENTS
3.JOBS
A workflow run is made up of one or more jobs. Jobs define
the functionality that will be run in the workflow and run in
parallel by default.
Job Collection
A workflow usually consists of one or more jobs identified by unique
job id (e.g. my-job), jobs ruins in parallel unless queued with the
"needs" attribute. Each job runs in a fresh instance of the virtual
environment specified by "runs-on"
Needs
Identifies any job that needs to be completed successfully before this
job runs.
Runs-on
Type of Virtual Machine to run the job on.
example: ubuntu-latest,windows-latest, macOS-latest,
self-hosted
Learn.sandipdas.in
8.
GITHUB ACTIONS COMPONENTS
4.RUNNERS
A runner is a machine with the Github Actions runner application installed. Then
runner waits for available jobs it can then execute. After picking up a job they run
the job's actions and report the progress and results back to Github. Runners can
be hosted on Github or self-hosted on your own machines/servers.
GitHub Hosted Runers
Windows and Linux virtual machines: 2-core CPU,7 GB RAM, 14GB SSD Disk space
MacOs Runner: 3-core CPU, 14GB RAM, 14GB SSD Disk Space
A GitHub-hosted runner is a virtual machine hosted by GitHub with the GitHub Actions runner application installed.
GitHub offers runners with Linux, Windows, and macOS operating systems.The virtual machine contains an environment
of tools, packages, and settings available for GitHub Actions to use.
Self Hosted Runers
We can host our own runners and customize the environment used to run jobs in your GitHub Actions workflows.
Self-hosted runners offer more control of hardware, operating system, and software tools than GitHub-hosted
runners provide. Supported os as below:
Linux: RHEL Linux 7 +, CentOS 7 +, Oracle Linux 7+, Fedora 29+, Debain 9+, Ubutu 16.04 +, Linux Mint 18+ etc
Windows (64bit): Windows 7, 8.1, 10, Server 2012 R2, Server 2016 , Server 2019
Mac: macOS 10.13 (High Sierra) or later
Learn.sandipdas.in
9.
GITHUB ACTIONS COMPONENTS
5.STEPS
A Job contains a sequence of tasks called steps.
Steps can run commands and actions.
Step Name
Specify the label to display for this step on GitHub
Uses
Specify an action to run as part of step in our workflow job
With
A map of input parameters is defined by the action in it's
actions.yml file
Run
Instead of running an existing action, a command-line
program can be run using an operating system shell.
Multiple commands can be run in a single shell instance
by using "|" (pipe) operator
Learn.sandipdas.in
10.
GITHUB ACTIONS COMPONENTS
6.MATRIX STRATEGY
A build matrix allows you to test across multiple operating
systems, platforms, and language versions at the same time.
You can specify a build matrix using the strategy keyword and
pass it to runs-on.
Learn.sandipdas.in
11.
GITHUB ACTIONS COMPONENTS
7.ENV
GitHub sets default environment variables for each GitHub Actions
workflow run. We can also set custom environment variables in our
workflow file using "env".
Env defines a map of environment variables that are available to all jobs
and steps in the workflow. You can also set environment variables that are
only available to a job or step.
Default Environment Variables
CI, GITHUB_WORKFLOW, GITHUB_RUN_ID, GITHUB_RUN_NUMBER, GITHUB_ACTION,
GITHUB_ACTIONS, GITHUB_ACTOR, GITHUB_REPOSITORY, GITHUB_EVENT_NAME,
GITHUB_EVENT_PATH, GITHUB_WORKSPACE, GITHUB_SHA, GITHUB_REF,
GITHUB_HEAD_REF, GITHUB_BASE_REF, GITHUB_SERVER_URL, GITHUB_API_URL
GITHUB_GRAPHQL_URL
Learn.sandipdas.in
12.
GITHUB ACTIONS COMPONENTS
8.SECRETS
Secrets are encrypted environment variables that we create in an
organization, repository, or repository environment. The secrets that
we create are available to use in GitHub Actions workflows. Sensitive
values should never be stored as plaintext in workflow files, but rather
as secrets
Secrets get accessed in workflow like this: ${{ secrets.SECRET_KEY_HERE }}
Limit We can store up to 1,000 organization secrets, 100 repository secrets, and
100 environment secrets.
Learn.sandipdas.in
13.
GITHUB ACTIONS COMPONENTS
9.CACHE
The workflow runs often reuse the same output as the previous ones and can therefore be
cached for an increase in performance. Every job run on Github-hosted runners starts in a
clean virtual environment and doesn't use cache by default.
Caching is made possible by the Github cache action which will attempt to restore a cache
based on the key you provide. If no match for the cache key is found it will create a new one
after the successful completion of the job.
key (Required): The key identifies the cache and is created when saving the cache.
path (Required): The file path of the directory you want to cache or restore.
restore-key (Optional): An ordered list of alternative keys to use for finding the cache if
no cache hit occurred for the key.
cache-hit: Boolean variable with success state of the cache action
Input parameters:
Output parameters:
Learn.sandipdas.in
14.
PRICING
GitHub Actions usageis free for both public repositories and
self-hosted runners.
For private repositories, each GitHub account receives a
certain amount of free minutes and storage, depending on
the product used with the account.
Any usage beyond the included amounts is controlled by
spending limits. Jobs that run on Windows and macOS
runners that GitHub hosts consume minutes at 2 and 10
times the rate that jobs on Linux runners consume.
If your account's usage surpasses these limits and you have
set a spending limit above $0 USD, you will pay $0.25 USD
per GB of storage per month and per-minute usage
depending on the operating system used by the GitHub-
hosted runner
Learn.sandipdas.in
15.
COMMUNITY ACTIONS
Actions arestandalone commands that are combined into steps to create a job. Actions are the
smallest portable building block of a workflow. We can create our own actions or use actions
created by the GitHub community, the actions created by GitHub community and ready to use, are
called Community Actions.
We can explore all community actions here: https://github.com/marketplace?type=actions
Example Usage
Learn.sandipdas.in
16.
CUSTOM RUNNERS SETUP
&
DEMO
RepoSettings Actions Runners
Learn.sandipdas.in
Available Choices Are MacOs, Linux, Windows. For Our
Demo We will use LInux
After Selecting desired os type installation, simply follow
the commands
17.
GITHUB ACTIONS DEMO:NODEJS
Learn.sandipdas.in
In this demo, we will use GitHub
actions to make Node.js build and
make a GitHub release from it.
In this demo, we will be utilizing
multiple GitHub Community
Actions
![UiPath Automation Suite Installation (Hands-On) [2/3]](https://cdn.slidesharecdn.com/ss_thumbnails/automationsuitecommunitysession2-251015095633-a6d862f1-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
