Scribd
Upload
62 views2 pages

GHA Notes

notes

Uploaded by

eshwar.lpd
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
62 views2 pages

GHA Notes

notes

Uploaded by

eshwar.lpd
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

What is GitHub Actions?

It’s a continuous integration and continuous delivery (CI/CD) workflow automation service from Github.
we can create workflows that build and test for every pull request to your repository, or deploy merged pull requests to
production.

Basic Building blocks of GHA

1) Workflows
2) Jobs
3) Steps

 Workflows: *A workflow is a configurable automated process that will run one or more jobs.
*Workflows are defined by a YAML file, checked in to .github/workflows directory in a repository.
*Repository can have multiple workflows, each of which can perform a different set of tasks.
*Can have one workflow to build and test pull requests, another workflow to deploy your application
every time a release is created, and still another workflow that adds a label every time someone
opens a new issue.
*You can reference a workflow within another workflow. Workflow reusage.
* Workflow can run when triggered by an event in your repository, or they can be triggered manually,
or at a defined schedule.
An event is a specific activity in a repository that triggers a workflow run. For example, activity can originate from
GitHub when someone creates a pull request, opens an issue, or pushes a commit to a repository. You can also
trigger a workflow to run on a schedule, by posting to a REST API, or manually.
 Jobs: A job is a set of steps in a workflow that is executed on the same runner.
step is either a shell script that will be executed, or an action that will be run.
Steps are executed in order and are dependent on each other.
Since each step is executed on the same runner, you can share data from one step to another. For example, you
can have a step that builds your application followed by a step that tests the application that was built.

You might also like