GitHub GitHub Universe 2019 Day 1 Keynote, 15 Nov 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: From code to cloud - GitHub Universe 2019

Description

From code to cloud, with GitHub Actions and Packages

We’ve made GitHub Actions and Packages a part of every developer account with included minutes, storage, and data transfer—and it’s free for all public repositories. You can use Actions to automatically publish new package versions to GitHub Packages, trigger package installs with Actions, and install packages and images hosted on GitHub Packages or your preferred registry of record with minimal configurations.

Learn more about automation on GitHub: https://github.com/features#ci-cd

About GitHub Universe:
GitHub Universe is a two-day conference dedicated to the creativity and curiosity of the largest software community in the world. Sessions cover topics from team culture to open source software across industries and technologies.

For more information on GitHub Universe, check the website:
https://githubuniverse.com

A

Okay, to start us off with Cody cloud, to tell you how we've added with github actions and get uh packages a complete DevOps platform github, please welcome Dana Lawson Dana.

B

Thanks NAT I am so excited to be here today to tell you all about how we're bridging the gaps in the software development lifecycle.

B

The github engineering team has been hard at work since the last universe when we introduced actions and since then, we've also introduced a little thing called packages in a previous life as an essay in a DEA LMNOP now VP, we all have felt the pain of getting our code in production and we wanted to do it reliably systematically, because if it touches production, it is production and now, thanks to get hub packages and github actions, we've enabled some pretty incredible: workflows, codified and inside repositories on github I.

B

Think it's a game changer, because as a DevOps engineer at heart and will always be, this was one of the areas that was just so hard with all those disparate systems to bring them together. So I'm really really proud of the overwhelming response we've gotten from our community.

B

So let's dive in a little bit about actions. If it's new to you code cloud is our complete DevOps workflow made possible by these two new features. Earlier this year we introduced CI and CD and with the reception of those products we shared some really inspirational code. If you're new to get actions and packages, I'm gonna get you up to speed real quick, but before I do that I wanted to. Let you all know that, starting today, right now, it's available to everyone. That's right! You all can get your actions out there.

B

So what does actions do for you? Well, you can do matrix builds. That means you can tell you different operating systems, Linux Mac's windows, with different versions of your code in one click. Well, if you set it up that way, obviously I can't, but my team can live searchable log, so you can see where you have those breaks in your build systems and my favorites the built-in secret store, it's always a pain, to try and get those secrets in when you're trying to push your code out to production, but now having it on one place.

B

It just makes it so much easier and what about getting packages? It's like the peanut butter and jelly of this amazing sandwich for your code to cloud experience right. Good people like peanut butter and jelly still it's available for public and private repositories. We support NPM, docker nougat and some others. It works with actions or any CI that you already have implemented, which is awesome, and we also give you those package analytics.

B

So you know where that package came from, who wrote it and who's using it and where it's at now the best part of actions in our code to cloud workflow is to apply all the real-life situations you're bound to encounter, and some of our community has created some of the most important actions to date. That I'm about to tell you about so get your notebooks out, because you're gonna need this one. That's right in action to order your pizza, because I don't know about you being the lone developer.

B

I needs my pizza, but here's my favorite action, that's been created. That's right! You can now use this action to change all the pictures. In your repository to my favorite actor Nick Cage. Have you actually use that one? It's awesome, but let me get serious for a minute.

B

All of these open source projects that you're seeing here are using github actions to power, their CI and CD and their general automation the problems that every team has encountered and are faced by millions more people all over the world are the ones that these teams have encountered and we all have to get our code into production because that's what we do it for to share it with the world and now some of us do this multiple times a day million times a month.

B

Are we deploying because that is what our customers and our people need? So a couple of cool companies, I am a huge Pinterest fan, believe it or not. I have a whole dinosaur board. If you all want to go check it out, look for me it's there, but just take Pinterest.

B

For instance, they were able to reduce their build time from 80 minutes to 10, with the use of github actions and packages, and it's just incredible how you can take and connect your workflow in any way that makes sense for you and your business like I, said github being the ecosystem and the interconnected community. It's not just about the open source projects. These amazing partners have also built and shared their actions for us to use.

B

So you don't have to start from scratch and so take a look to go see what you can already reuse, because that's what it's about when we do code, it is the ultimate team sport. It's sharing our mind share, but don't take my word for it to show you more about actions and packages live. Let me introduce my friend and colleague, Jeremy.

C

C

So, who here is ready to jump in and see a live demo of actions all right? So what I have here today is a repo and I've gone ahead and set up node module in here and I'm. Gonna. Show you how easy it is to get started with CI CD and a bunch of different other workflows with github actions. So, as you heard today, yeah everybody's gonna see this actions tab and you can just go ahead and click on it right.

C

There, I'm gonna click, new workflow, one of the things that you'll notice is we've automatically detected that this is using JavaScript as its primary language. So we have a set of starter workflows to make it really easy for you to get started in this case, we're suggesting two of them one of them's, to build and test a nodejs project.

C

This could be an app a module web service or deploying or another one to do, CD, which will deploy to get packages as well as NPM, but obviously github cares about a lot of languages beyond just JavaScript and node. So we have starter workflows to help you get started with just about anything. We have support for any language any platform in any cloud. So if you need to be able to deploy to Google cloud to AWS or to Azure, we have easy workflows to help you get started and get those deployments going.

C

If you're using other languages like rust, Python Ruby go, we have support for all of those as well. If you click here, you can see the tens of templates that we have for just about every single language you can imagine out there, and these are actually all open source and we've already had people contributing to these templates as well. But get up actions is more than just see, ICD one of the great things about it is you can automate any of that happens on github, so it could be. Maybe a new issue created.

C

You want to go ahead and have an automation kick off and look to determine who that issue should be assigned to or to automatically label it. Maybe you want to close stale issues. Maybe you want to greet new contributors to your repository. We have a set of workflows to help you get that going and get up. Actions is really the glue that connects all these experiences together, and it's not just events that happen on github.

C

It's events that happen with any other tool that integrates with github, so maybe Prometheus is generating some health events for you that you then want to kick off at rollback or a redeploy again. You can connect that all together with github actions, so let's scroll back up to the top and actually just get started here with node. So I'm gonna click set up this workflow and, as you would imagine, we went ahead and created a gamal file directly in your repo.

C

So you can manage all of your CI CD and configuration Rytas code, you'll notice that this template gets you set up with a matrix, build as Dana talked about a second ago, I'm testing across multiple different versions of node, I'm testing on Linux and then doing way to expect we check out the code set up the environment and run some scripts directly in line. But if you're like me, has anybody ever made a mistake in yeah Mille? Maybe you've gotten the spacing wrong, haven't got it all right. Well, we have come to your rescue.

C

One of the things you'll notice is we've added autocomplete directly into the editor, so you can easily learn our gamal syntax and how to go in and edit that so maybe, instead of running directly on a Linux VM, maybe I want to do a container. I can specify my image and have that all done right there directly in the editor, but as Dana was saying, we now have over 1200 actions.

C

People have added and over here on the right hand side, maybe you don't always want to build it yourself, because we want to stand on the shoulder of giants just like we do with open source. We want workflows to be the same way. You can go ahead and see many of the different popular actions right here and go ahead and search for them. Maybe I want to deploy to kubernetes. You can see, there's multiple different actions, different partners and people have contributed.

C

Maybe I want to use Chrome for headless testing or I want to deploy an extension to the chrome store or to Firefox, or a word plus plug-in the community's created tons of extensions to be able to automate all the CI CD scenarios and a lot more, maybe just sending a slack message or sending something off on Twilio. It's all supported right there, and also we have an easy link to documentation right here. So it's even easier to get started. Let's go ahead and go ahead and commit this file and start a pull request.

C

So just like you would imagine, as soon as the pull request is created, we have actually automatically gone ahead and kicked off CI, just like you would expect so. The merge box right in your pull request is right. There you can see we're going ahead and queuing up those three simultaneous builds and they're already in progress. So let's go over here and just like you can have a conversation. I can just go over to this checks, tab and right. When I'm there you'll see live streaming logs directly in github, come on there we go.

C

You can see we have emoji. We have syntax, highlighting everything that you expect. Maybe if there was a failure, I want to copy a link right to this line and share it with someone that makes it really easy to go. Do that we have search directly in there as well, if I want to search through all my logs and I can see all these jobs that quickly pass, because we have really fast hosted runners that are free for all public repos.

C

Now, let's go over and look at a little bit more complicated setup here. If that was kind of a starter set up I'll go over to this other one. This is the same project, I've just kind of built, a larger CI, CD workflow in it one of the things you'll notice is again like we talked about before you can have multiple different events, so in this case I'm looking at a pull request, that's targeting a master branch. You have lots of different filtering options on here.

C

Whether you want to include branches exclude branches, have matching specific patterns down below here. I have a couple different jobs, so I have this build job, that's kicking off a matrix, but this matrix is even larger. So it's not just testing across multiple node versions. It's multiplying that by all these different operating systems as well, so I'll actually have 12 different builds, kicked off simultaneously.

C

Each one of these operating systems will have three different: a can get that full parallel test coverage all at once, right on github and I'm, also happy to announce that we have self hosted runner support now directly in there.

C

So if you want to be able to run on your own hardware, that is all supported directly in github and it's completely free of charge because you're already paying for the hardware yourself whether or not you want a VM in the cloud or you're using on prim hardware, or you just want to run it on a Raspberry Pi. We have support for everything down below here. You'll notice that I'm doing a dual published so I'm, also publishing to NPM and then I'm also publishing to get hub packages and you'll also see here.

C

Obviously, I need an auth token. If I want to deploy to NPM, so we now have a secret store built directly into every single github repository, and all you have to do is jump over to settings and configure those secrets nice and easily. But now, let's look at what happens when I actually go ahead and run this. So let's go over here and we can go to actions and just like you would expect on the actions tab once you've been using it for a while. You have lots of different builds that have been triggered.

C

Everything that you would expect great filtering options. Let me jump down here and you can go ahead and see earlier today. I ran all these tests in parallel they've all deployed successfully.

C

We've also went ahead and published this package, so I'm gonna jump over here and show you the package that was deployed and again we have github packages so right next to your code. Right next to that repository, you can have your whole CI and then your CD and your packages right there. So, in this case, I can click on fib tools and I can see how easy it is to get started.

C

I can see the readme I can see some stats, the different versions, everything that you would expect to see for a package that you're publishing I can even go up to the organization and see all the different packages that this organization is doing and we have support for many different languages. Just as Dana was saying whether it be docker, maven, Gradle, nougat, NPM, Ruby gems, you can publish lots of different types of packages and then share that code, but I know one of the things that matters the most to you.

C

Is you really want to be able to save your time so I'm also happy to say. We now have caching support built directly into github actions.

C

It's just as easy as going ahead and adding a simple caching action on there and I always feel like the proof is in the pudding when you look at a real repo, so recently rails actually has been using github actions and they've switched over to now using caching, so you'll notice up here takes about six and a half minutes once they added the caching action now down to one and a half minutes, it's a five minute reduction in their builds, and this isn't just for Ruby.

C

You can cache anything that you need any packages that you have from any language, binary outputs anything like that. But finally, it's not just all about packages. You can also deploy to the cloud as well. So what I did here was I created a multi cloud deployment, as you would expect. I have a couple different workflows that can deploy to Google, Amazon and Azure all right there and then also right in my pull request. I can actually see the environments that these are going to as well.

C

So you can get one-click access right to that environment right from the pull request. Then, if I go back over to code, you'll notice, just like your packages, are there your pull requests everything else that you expect you'll notice. We now have a set of environments right there as well, so I can see a history, an activity log of all the different deployments that I've done to all my different environments as well. So, let's jump back to the slides that gives you a quick look at everything that we've been doing recently.

C

You know recently, we just announced artifact caching, as well as self hosted runners with arm support and x86 support as well with packages. You saw that we now have Gradle packages in addition to everything else. I showed, and we also have proxy supports.

C

If you want to port your NPM r/c directly to get her packages we'll go ahead and look on get our packages if there's something, if not we'll, fall back and grab it from NPM directly and if you want to learn more about, what's going on with actions and packages, feel free to stay right here in this room and Samina and I are doing a talk immediately. Afterward. Thank you very much.