GitHub GitHub Universe 2022 - Cloud, 24 Mar 2023

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: GitHub Actions: CI/CD for millions - Universe 2022

Description

In this session, Brian A. Randell will provide an update on the current state of the GitHub Actions nation and show you why GitHub Actions is the CI/CD platform for millions of open source and enterprise developers and everyone in between. You’ll learn about lots of great new features and get a look at GitHub’s upcoming roadmap for the future.

As always, feel free to leave us a comment below and don't forget to subscribe: http://bit.ly/subgithub

Thanks!

Connect with us.
Facebook: http://fb.com/github
Twitter: http://twitter.com/github
LinkedIn: http://linkedin.com/company/github

About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com

A

A

Hello, GitHub Universe, I'm, Brian, Randall and I work at GitHub, and today, I want to give you an update on GitHub actions. Our CI CD platform for millions of Developers GitHub actions is the number one CI CD platform on GitHub this last month we crossed over 1 billion minutes of cloud-based usage in a single month. That's just crazy. Those minutes translate into over 300 million jobs outstanding now, while I love crazy stats. What makes me even happier is the broad adoption that those numbers translate to in customers, open source projects and Community contributions.

A

The GitHub Marketplace currently has over 15 000 community actions with thousands of those verified from Publishers like Microsoft, AWS and Google. So let's dig into actions today. Github actions is Enterprise grade CI CD that supports the core features. You'd expect in a modern CI CD platform, and we hear this directly from Individual customers too. We've worked with Pinterest on their CI CD workflows, Pinterest moved many of its largest source projects, including Gestalt and texture, to GitHub. By using actions and in their words it's been an incredibly successful project.

A

They've reduced build time significantly and no longer need to babysit their CI CD and can focus on code contributions.

A

It's super easy to get started with GitHub actions, because it's just a tad click away from your repo using the config s code concept, your GitHub actions are stored as version files right in your repo. Everything is integrated with your code, taking you from nothing to action in seconds at times, I can't believe it's been years since we've released our first version of GitHub actions, but we've not been taking it easy. Over the last year, we've been hard at work to make actions even better.

A

We've added features to help you scale your processes as well as Implement control features. You have requested, for example, reusable workflows and custom actions. Allow you to take advantage of code, reuse for building an action or workflow once and then reusing it throughout your organization.

A

The ability to reference actions from internal repos makes it much easier to share actions through your company. This provides you with the ability to limit self-hosted Runners to specific workflows, and this allows you to ensure that critical workflows always have a runner available to them. We've worked hard to improve the starter workflow experience. We've made it easier to discover security related workflows from the getting started experience now.

A

You can easily find workflows to set up analysis tools from varicoder sync, for example, and we will recommend security, specific workflows to you, based off the content of your repository, allowing you to implement those security workflows that much faster with open, ID connect. We've made deployments more secure. Openid connect allows your workflows to exchange short-lived tokens directly from your cloud provider.

A

This eliminates the need to save hard-coded Secrets needed to access cloud services. Example. Providers that are currently supported by oidc include Amazon web services, Microsoft Azure Google Cloud platform and hashicor vault. Beyond what I've already mentioned, we have implemented some of the most requested user experience improvements.

A

The ability to rerun an entire workflow, see all the previous runs and rerun with debugging makes actions and workflows much more pleasant to work with we've increased the artifact cash to 10 gigabytes, which allows you to store more cache files for your workflow, which helps your workflows run faster job. Summers is another great feature. It allows you to display any information you would find relevant in your workflow summary like test or scan results.

A

Dynamic names for workflow runs allows you to customize the name of the workflow run that is displayed on the actions tab, allowing you to give the workflow run a more helpful name and in the interest of making sure our customers have access to the latest Runners. We have added GitHub, hosted Runner images from Mac, OS 11 and 12 Windows, Server 2022 and Ubuntu 22.04.

A

Beyond all those great features, we've already shipped I'm, also very excited about the beta of custom GitHub hosted Runners. These Runners allow you to create Runners with more cores more memory and storage than a standard hosted Runner. This will help you potentially complete. Your builds even faster beyond the extra performance. What's really cool is the ability to define static. Private IP address ranges. This allows your GitHub hosted, Runners access to internal resources for your CI CD process by only having to open a small Port range in your firewall.

A

Our Runners have the latest tools installed and help scale on demand, as you need it.

A

Finally, coming soon in beta will be providing Auto scaling, self-hosted Runners on top of kubernetes we've heard from many customers that they want a GitHub supported way to create self-hosted scaling, ephemeral, Runners, similar to how the GitHub hosted Runners work in the cloud.

A

We are working on a kubernetes solution to this problem, our solution that will be free and that you won't have to pay for any sort of per job tax. This will support both GitHub Enterprise server, 3.5 or later, as well as GitHub Enterprise cloud.

A

Now, let's switch over to a demo of many of these great new features. So now we're going to go in and look at some example: GitHub actions deploying an application securely to Microsoft azure.

A

So, as you can see here, I'm at my repo for popular repos web app and what this is is a very simple web app that goes through GitHub and looks at the popular repos based upon the programming language being used. As you can see over here. In the right hand, side I have a list of environments that I've deployed to this includes staging review, lab and production, and if I click on production, it'll open a new tab and show me the deployment history that I've made for this particular environment.

A

Now, if I click view deployment, it'll take me to the website and show me the popular repositories.

A

So you can see the number one repository here going down the list and you can see I can filter by different languages. So there's JavaScript, c-sharp Etc, but you know I know some of my team members at GitHub are gonna, be a little sad because we're missing Ruby, let's go change that I'm gonna go back over here into my repo and you'll notice. Of course, I have my source code available here now.

A

I can use something like GitHub code spaces if I wanted, but this is going to be a simple edit, so I'm just going to switch over here to one of my other tabs that I've already opened and show you the source code for this home.js file and to see over here on line six. It goes through the different programming languages, so I'm just going to click edit and come into this nice new editing, experience and come over here and put a comma and then we'll add Ruby how we missed her.

A

So we'll click commit changes and we'll say update so that Ruby gets some GitHub love because we love our programming languages and, let's see if we can get a little Emoji here, a little heart there. We go Gotta, Have emoji, and you see here it's going to be committed by me, but I'm going to create a new branch and you'll see it's automatically, giving it a name and we'll propose those changes.

A

So, as you can see I'm in here at my new open, pull request and down here on the right hand, side are all the features you come to know and love the ability to add reviewers, assignees labels and more I'm good to go with this I'm just going to create the pull request now right away.

A

What you see is that actions is picked up, that I have started this pull request and it's starting a couple of workflows here: deploy site, reusable, including code analysis and deploy site, reusable deploy app, and so, if we come over here to one of my other tabs, we'll see that I have deploy with reuse.yaml and you'll notice that we have two jobs in here: the code, analysis and Bill, deploy, which I just showed you over on the pull request page now. This is great.

A

This one is using a workflow that is shared throughout our organization, so it's over in our workflows, repo and we're pulling it in so anytime. We want to adjust code analysis. We can just update that Central File, and this will update all of our pull requests. So the nice thing about this is, we can go back and just update the central file and all of our workflows will be able to take advantage of it then going down here. We see we have our deploy app, which is using our shared building, deploy ammo file.

A

So if we come over and click that one you'll see this one goes through and has a bunch of information here, but most notably, it only has information about which Azure environment I want to work with. All of our secrets, as we'll see later, are being taken care of through oidc. So we scroll down a little bit. We can see things related to our jobs that we're running on installing dependency and you'll notice. The ability to use our caching feature, just as we talked about earlier down here a little further.

A

We can see our Azure login and notice. With this Azure login. We don't have to provide anything secret, we're just giving it the client ID the tenant ID and the subscription ID. Now this is going on. Let's go over and take a look at how things are going so I'm going to come back over here and we'll open up my actions. Tab now, we'll see that we've come up here and update so that Ruby gets some love. So we'll click on that and we can see our nice workflow stream as it's going through.

A

So our code analysis, workflow job ran just fine. Our deploy, app and build is running and based upon the fact that it came through as a pull request, it's pushing into our deploy review environment and now, if I, right click on this and open in a new tab, we will see there's the website but notice the URL. This is not my prod environment. This is a review environment and now we can see all of our different languages, including Ruby, and there you go rails being the number one project.

A

So that makes me happy so now what I want to be able to do is go out and make sure that this gets out into production again. I want to take advantage of some of those great features that we've added, including things like approvers. So I'm going to come back over here and you'll, see that octobrine patch has recent pushes within a minute ago. So I can come over here and take a look. We can see the changes. I made, go, look at the pull request, that's going on and it looks like it's good.

A

All the checks have passed, I'm really happy now and so I'll come over here and click. Merge, pull request, confirm the merge and there we go so now that's going to start another workflow. So let's come over here to over to our actions tab and we can see that we've got two different items going on the first one down. Here is a cleanup PR that I'll show you in a second and then, of course, as you'd expect the merging pull request.

A

So it's going to go through and run code analysis again right, gotta double check before we go into Main and then it's going to do deploy app and build. But what we'll see is, instead of taking this route down here, we're going to come up through staging and then production.

A

Now one of the great things about working with this type of setup is that we have the ability to protect our environments with Branch protection rules, and so, if we come over here to this other tab called environments which I got to by going into settings, we can see that first of all, we have required reviewers, so Chris, Jeremy or myself is going to have to approve this before It ultimately goes to production.

A

You notice also down here that only code coming out of main is allowed to go into production, so we don't have to worry about a developer accidentally, getting code that isn't really ready for Prime Time into our main environment and then finally, you'll notice down here we do have a feature called environment secrets, and that would be useful if maybe using something self-hosted that didn't support oidc, but because we're talking to Azure and it does support IDC, we don't have to have any secrets stored in our environment.

A

Now, let's go back to our workflow and we'll see it's almost done there, but it's also running this other code security scan. Now, if we take a look at our different items that are going on here and we come back over, we can see the environments being worked on here and come over here right. We can see the jobs running going through. It's done its build, it's done its deploy review and then it's going to get ready to deploy into staging you notice.

A

We can get Run details to see how long something is taking and you can jump straight to your workflow file to see what is being executed once again. These are just nice little paper cuts that we've got rid of now coming back in here. It says: okay, we've deployed successfully to staging, but now we want to go to production in order for production. I have to come over and get someone to approve this.

A

So we click you deployments and it says: okay, someone needs to sign off so I'm, going to check the box that it can go into production and I'm, going to specify that I said it's. Okay,.

A

All right so the ship it squirrel, says ship it we'll click approve and deploy, and now that's going to kick off the final deployment stage into production.

A

Now, while it's running, let's go back over to my workflow list and let's show you that we have this cleanup PR one of the nice things we can do is we can have extra workflows that do other things inside GitHub, one of the things we took advantage of earlier when I deployed the application out to staging was I also did a review deployment using staging slots and so now I'm just cleaning that up. So this is just a nice little housekeeping workflow that we're able to call out while we actually do our main job.

A

So let's go back to our actions and we'll see we're almost there and it's deploying into production. You notice down here we can see the deployment reviews I approved it 41 seconds ago. You can see the comment. I made scroll down a little further. We can see annotations that are showing up telling us that hey we've got some deprecated actions that we might need to clean up. So I can go in if I needed to and create an issue for that Etc.

A

Fantastic, look at that I've got a green check, mark I click, the link and now my change going through a nice pull request process with code analysis, security scans. All done. We see all our popular repositories and there again Ruby our love language is got rails at number one.

A

Hopefully you can see that we've not been standing still. We want GitHub actions to be your number. One choice for CI CD GitHub has a public roadmap where you can see what new features we have planned and when we are estimating their release. You can follow these links for more information on all of github's upcoming features, as well as a filtered view, just showing actions related updates.

A

Thank you so much and enjoy the rest of GitHub universe.