1602208203

GitHub Actions Tutorial - Basic Concepts and CI/CD Pipeline with Docker

In this GitHub Actions Tutorial we go through the following topics:
First I explain what GitHub Actions actually is and we will look at specific developer workflow use cases that you can automate with GitHub Actions .
After that I explain the basic concepts of GitHub Actions, including the GitHub Events and Actions and workflow and HOW GitHub Actions actually automates these workflows using these components.
Having understood what GitHub Actions solves and how it makes it possible, I will go through the most common workflow, which is CI/CD pipeline.
I will explain shortly why it is not just another ci/cd tool or what are the benefits of GitHub Actions ci cd pipeline.
Finally we will go through a hands-on DEMO, where I explain the syntax of github actions workflow file, and then I show you a complete ci pipeline setup with my example Java Gradle project, which we will build into a Docker Image and push to a private Docker repository on DockerHub.

▬▬▬▬▬▬ T I M E S T A M P S ⏰ ▬▬▬▬▬▬

0:00 - Intro
01:03 - What is Github Actions?
01:29 - What are developer workflows? Use Cases for GitHub Actions
04:50 - Basic Concepts of GitHub Actions: How GitHub Actions automates those workflows? GitHub Events & Actions
06:41 - GitHub Actions CI/CD
07:18 - Why another CI/CD Tool - Benefits of Github Actions
09:50 - DEMO - Create CI Workflow or Pipeline
13:04 - Syntax of Workflow File
20:40 - Where does this Workflow Code run? GitHub Action Runner
24:35 - Build Docker Image and push to private Docker Repo

#github #docker #devops

What is GEEK

Buddha Community

GitHub Actions Tutorial - Basic Concepts and CI/CD Pipeline with Docker

Derek Champlin

1595578080

Working with GitHub Actions

GitHub has become one of the most widely used Source Code Repository. Its Distributed Version Control System helps the developers for faster development and Integration of their code. Recently, it launched GitHub Actions in beta which enabled developers to create automated workflows to build, test, and deploy their source code on GitHub.

In this article, we will discuss about GitHub Actions and how it can be used to build an automated software development life-cycle workflow.

Below are the things we will discuss in this article:

About GitHub Actions

Using GitHub Actions, we can create custom workflows that will help to build, test, package, release or deploy the code without leaving the GitHub UI. It enables us to build Continuous integration and Continuous Deployment capabilities directly in our repository. Here are some important features about GitHub Actions.

**YAML based process: **The workflow is written in YAML. Hence it is easy to create, read and use the actions that make up the workflow.

**One Place for everything: **By using GitHub Actions, we can build and test the developed code directly in our repository. There is no need to worry about integrating the source code repository with other build and deployment tools. Everything can be done in one single place.

**Easy to integrate code: **Since enabling CI/CD directly in the repository is possible using workflows, creating merge requests(MRs), building, testing and integrating them become way more seamless.

#tech (re)view #build #cd #ci #ci-cd #github #github actions #gitlab-ci #gradle #java #test

Matt Towne

1589791867

Serverless CI/CD on the AWS Cloud

CI/CD pipelines have long played a major role in speeding up the development and deployment of cloud-native apps. Cloud services like AWS lend themselves to more agile deployment through the services they offer as well as approaches such as Infrastructure as Code. There is no shortage of tools to help you manage your CI/CD pipeline as well.

While the majority of development teams have streamlined their pipelines to take full advantage of cloud-native features, there is still so much that can be done to refine CI/CD even further. The entire pipeline can now be built as code and managed either via Git as a single source of truth or by using visual tools to help guide the process.

The entire process can be fully automated. Even better, it can be made serverless, which allows the CI/CD pipeline to operate with immense efficiency. Git branches can even be utilized as a base for multiple pipelines. Thanks to the three tools from Amazon; AWS CodeCommit, AWS CodeBuild, and AWS CodeDeploy, serverless CI/CD on the AWS cloud is now easy to set up.

#aws #aws codebuild #aws codecommit #aws codedeploy #cd #cd pipeline #ci #ci/cd processes #ci/cd workflow #serverless

Isobel Matthews

1602208203

GitHub Actions Tutorial - Basic Concepts and CI/CD Pipeline with Docker

In this GitHub Actions Tutorial we go through the following topics:
First I explain what GitHub Actions actually is and we will look at specific developer workflow use cases that you can automate with GitHub Actions .
After that I explain the basic concepts of GitHub Actions, including the GitHub Events and Actions and workflow and HOW GitHub Actions actually automates these workflows using these components.
Having understood what GitHub Actions solves and how it makes it possible, I will go through the most common workflow, which is CI/CD pipeline.
I will explain shortly why it is not just another ci/cd tool or what are the benefits of GitHub Actions ci cd pipeline.
Finally we will go through a hands-on DEMO, where I explain the syntax of github actions workflow file, and then I show you a complete ci pipeline setup with my example Java Gradle project, which we will build into a Docker Image and push to a private Docker repository on DockerHub.

▬▬▬▬▬▬ T I M E S T A M P S ⏰ ▬▬▬▬▬▬

0:00 - Intro
01:03 - What is Github Actions?
01:29 - What are developer workflows? Use Cases for GitHub Actions
04:50 - Basic Concepts of GitHub Actions: How GitHub Actions automates those workflows? GitHub Events & Actions
06:41 - GitHub Actions CI/CD
07:18 - Why another CI/CD Tool - Benefits of Github Actions
09:50 - DEMO - Create CI Workflow or Pipeline
13:04 - Syntax of Workflow File
20:40 - Where does this Workflow Code run? GitHub Action Runner
24:35 - Build Docker Image and push to private Docker Repo

#github #docker #devops

Harber Jazlyn

1604286810

CI/CD with Vue, Firebase Hosting and Github Actions

Even if you’re the only developer in a project, you still have to make sure you automate your deployment process and follow certain steps in order to prevent bugs sneak into production code. Writing tests is the first step of it. But then, running those tests everytime you make a change in the code is a time consuming process where you can benefit from some automation.

This is where Github Actions come into play: How about creating a workflow in Github Actions which will run the tests for you when you make a pull request and won’t allow merging to master and deploying to production if the tests fail? That would really help with avoiding unintentional deployment of buggy code. Another important point is not forgetting to deploy your code into production when a pull request is merged to master. The Github workflow that we are going to create will also handle that by automatically deploying to Firebase Hosting when a pull request is completed.

Let’s see how it’s done step by step:

Creating a Vue Project

First of all, make sure your Vue CLI is up-to-date. As of this writing, the latest version is 4.5.8. You can check your current installment with this terminal command: vue --version .

If you have an older version, you can update by npm update -g @vue/cli or if you never had installed before you can install it globally by npm install -g @vue/cli.

Next, let’s create a brand new vue project called “vue_ci_cd” with the command vue create vue_ci_cd_example.

Not all settings are relevant for the purpose of this tutorial, but make sure the following settings are handled as follows:

Please pick a preset: Manually select features
Pick a unit testing solution: Jest
Pick an E2E testing solution: Cypress (Chrome only)

It will then install all the necessary dependencies for the app. If everything goes well, you should be able to run the app with this command cd vue_ci_cd_example && npm run serve .

#firebase #github #vuejs #ci-cd-pipeline #github-actions

Mikel Okuneva

1602316366

GitHub Demo Days - Using GitHub Actions for testing cloud native applications

What makes a project successful? For developers building cloud-native applications, successful projects thrive on transparent, consistent, and rigorous collaboration. That collaboration is one of the reasons that many open source projects, like Docker containers and Kubernetes, grow to become standards for how we build, deliver, and operate software. Our Open Source Guides and Introduction to innersourcing are great first steps to setting up and encouraging these best practices in your own projects.

However, a common challenge that application developers face is manually testing against inconsistent environments. Accurately testing Kubernetes applications can differ from one developer’s environment to another, and implementing a rigorous and consistent environment for end-to-end testing isn’t easy. It can also be very time consuming to spin up and down Kubernetes clusters. The inconsistencies between environments and the time required to spin up new Kubernetes clusters can negatively impact the speed and quality of cloud-native applications.

Building a transparent CI process

On GitHub, integration and testing becomes a little easier by combining GitHub Actions with open source tools. You can treat Actions as the native continuous integration and continuous delivery (CI/CD) tool for your project, and customize your Actions workflow to include automation and validation as next steps.

Since Actions can be triggered based on nearly any GitHub event, it’s also possible to build in accountability for updating tests and fixing bugs. For example, when a developer creates a pull request, Actions status checks can automatically block the merge if the test fails.

Here are a few more examples:

#engineering #enterprise #events #open source #actions #ci/cd #cloud native applications #cloud native architecture #devops #devops ci/cd #github actions #kubernetes #open source