The easiest way to get your workflow going is by using one of the many workflow and action templates available on the Github Marketplace. Workflows are defined using a YAML file in the. Workflow:Ī Workflow is an automated process that is made up of one or multiple jobs and can be triggered by an event. Step:Ī step is a set of tasks that can be executed by a job. Jobs can run independently of each other or sequential if the current job depends on the previous job to be successful. Job:Ī job is made up of multiple steps and runs in an instance of the virtual environment. Runners can be hosted on Github or self-hosted on your own machines/servers. After picking up a job they run the job's actions and report the progress and results back to Github. Then runner waits for available jobs it can then execute. Runner:Ī runner is a machine with the Github Actions runner application installed. Events can also be configured to listen to external events using Webhooks. For example, a workflow is triggered when somebody pushes to the repository or when a pull request is created. Event:Įvents are specific activities that trigger a workflow run. You can create your own Actions or use publicly shared Actions from the Marketplace. Actions:Īctions are the smallest portable building block of a workflow and can be combined as steps to create a job. Core conceptsīelow is a list of the core concepts used in Github Actions that you should be familiar with when using it or reading the documentation. If that is not enough for your needs you can pick another plan or go the self-hosted route. Great free plan:Īctions are completely free for every open-source repository and include 2000 free build minutes per month for all your private repositories which is comparable with most CI/CD free plans. You can also create your own templates which you can then publish as an Action on the Github Marketplace. Github provides multiple templates for all kinds of CI (Continous Integration) configurations which make it extremely easy to get started. Multi-container testing:Īctions allow you to test multi-container setups by adding support for Docker and docker-compose files to your workflow. This means that it can be managed in the same place as all your other repository related features like pull requests and issues. Github Actions is fully integrated into Github and therefore doesn't require and external site. Why care about Github Actions?īefore we get into the technical detail let's discussed why developers should care about Github Actions in the first place and which benefits they provide. In this article, we are going to look at the core concepts of Github Actions and even dive into creating your own custom workflows. This enables you to include Continues Integration (CI) and continuous deployment (CD) capabilities and many other features directly in your repository. These workflows are made out of different tasks so-called actions that can be run automatically on certain events. Github Actions enables you to create custom software development lifecycle workflows directly in your Github repository.
0 Comments
Leave a Reply. |