Reliable Deployments at GitHub

The GitHub engineering team recently blogged about  how they ensure fast and reliable deployments.  Raffaele Di Fazio, software engineer at GitHub, provided a deep dive into the deployment mechanics at GitHub.

GitHub is deployed on multiple Kubernetes Clusters and also on physical servers. As the deployment process impacts the GitHub customers and the internal users, safeguarding deployment reliability was critical for the team. The GitHub engineering team started fetching data from the deployment tools in order to fully understand the problem space:

• CI/CD builds duration
• Duration of individual steps of the deployment pipeline
• The total duration of the deployment pipeline
• The final state of a deployment pipeline
• Number of rolled back deployments
• Occurrences of deployment retries in any of the steps of the pipeline

The team also analyzed some general metrics, such as the time taken for a pull request to merge along with the number of pull requests deployed/merged. Many of these metrics collected align with the four key metrics identified in Forsgren et al’s “Accelerate” that differentiate between low, medium and high software delivery performers: lead time, deployment frequency, mean time to restore (MTTR) and change failure percentage.

#github #devops #news

What is GEEK

Buddha Community

A Simple Guide to Github Page Deployment

Long story short: Jekyll is a template engine changing

markdowndocuments on staticHTMLwebpages, that you can then host anywyere, because you don’t need databases or server that has PHP or Python.

Usual Process

Normally the process of adding new post looks like this:

• I write markdown document with setting parameters like title, date and tags
• when I’m happy with what I wrote (never), I commit changes and push it to repository on GitHub. Repository name comes from my nick and is also address for blog asvid.github.io
• Github after pushing to branch master builds website from sources using Jekyll - probably something like running jekyll build
• result of Jekyll build is not present in a repository, but you see it right now after visiting bloga page

#github-pages #github-page-with-jekyll #jekyll #github-actions #github #deployment #continuous-deployment #web-development

How to Compare Multiple GitHub Projects with Our GitHub Stats tool

If you have project code hosted on GitHub, chances are you might be interested in checking some numbers and stats such as stars, commits and pull requests.

You might also want to compare some similar projects in terms of the above mentioned stats, for whatever reasons that interest you.

We have the right tool for you: the simple and easy-to-use little tool called GitHub Stats.

Let’s dive right in to what we can get out of it.

Getting started

This interactive tool is really easy to use. Follow the three steps below and you’ll get what you want in real-time:

1. Head to the GitHub repo of the tool

2. Enter as many projects as you need to check on

3. Hit the Update button beside each metric

In this article we are going to compare three most popular machine learning projects for you.

#github #tools #github-statistics-react #github-stats-tool #compare-github-projects #github-projects #software-development #programming

Deploying Django app on Heroku with GitHub

Heroku provides many powerful features for deploying a project up on a live server to access it from anywhere in the world. The easiest way is to integrate it with GitHub and deploy code living on GitHub. Heroku can automatically build and release (if the build is successful) pushes to the specified GitHub repository.

#django #deployment #python #github #heroku #deploying

Deploying my portfolio website on Github Pages using Github Actions.

I recently deployed  my portfolio site and wanted to try out github actions and this is my experience of automating the deployment.

This article is more focused on how you can use the GitHub actions and how easy it is to deploy your code to GitHub pages rather than the portfolio site code.So every time you make an update or build to your website ,the changes are automatically reflected and this automated deploying process makes work much faster.

The way GitHub action works is you create actions in your repositories by creating one or more yaml files and these are called workflows.Workflows now can handle build tasks like CI CD. This means you use the action to test your code and push the site to the desired hosting platform (in this case GitHub pages ) when the main branch changes .

First step assuming that you have a GitHub account is to create a repository having your website code in it.Now I have a bootstrap website but in the future I do plan on adding node JS so I already added package.json.

#workflow #portfolio #github #github-actions #github-pages

Simple Jenkins for AWS Deployment via GitHub Hooks( Continues Deployment)

Connect GitHub webhooks to Jenkins ssh credentials to deploy the application.

STEPS

1. Spin up an EC2 instance and connect.
2. Jenkins Installation.
3. Github Integration ( https://medium.com/devops-dudes/setup-ssh-between-jenkins-and-github-660137e3895c)
4. Creating a JOB
5. Deployment

1. Spin up an EC2 instance and connect

This is just straight up to create an instance and connect to it

#jenkins #github-hooks #github-actions #github