GitHub GitHub Universe 2019 - GitHub Product Updates, 14 Dec 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Actions Packaged: Using GitHub Actions and GitHub Package Registry - GitHub Universe 2019

Description

Presented by Jeremy Epling, Senior Director of Product Management, and Simina Pasat, Director of Product Management, GitHub

This session will focus on the latest updates for GitHub Actions and GitHub Package Registry, and how to use them to build, test, and deploy your code. We’ll also walk through examples of repositories using GitHub Actions and GitHub Package Registry for their production CI/CD with multiple different configurations. At the end of this talk, you’ll have an end-to-end understanding of GitHub Actions and GitHub Package Registry, as well as how to use them with your project.

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

I hope you had a great morning and you really enjoy the keynote I think it was a great keynote and a great way to start this foggy day in San Francisco. Maybe for some summer, is a bit of a slow time at work. But for us at github this summer was super busy and super exciting.

A

We worked on new products, new features and we launched ton of improvements and for Jeremy and I on the actions and packages team things were extra special and extra busy, because in May we launched the beta for github packages, bringing packages and source code together on github and in August we launched the extended beta for actions, v2 bringing integrated, CI, CD capabilities into github, and today, just few months later, we announced that both of these products, github actions and github packages are available for everybody in github to use.

B

So, hey everybody, I'm, Jeremy, Epling and I lead code, the cloud teams, a github on the product side and.

A

I'm, seaman, opposite and I'm a product manager on github packages, so developers are at the center of github and when we think about developers there is so many definitions out there. Maybe some of you know what Urban Dictionary is saying that a developer is a person who transforms caffeine into code.

A

But now, let's be serious code doesn't mean that much until the moment when it becomes useful to somebody until that open-source package or that product, or that mobile app gets in the hands of your users, whoever your users might be so for us developers are these super smart people working together in teams and transforming code into end value to our customers.

A

But you know between writing the code and delivering that end value, there's a lot of different things that have to happen in the meanwhile. So we find these teams and these developers siloed between different systems, managing permissions configurations, copying secrets, and by the end of the day we even forget where we started from because sometimes were even in remote locations and on different time zones. So, with github actions and github packages, we are bringing this code to cloud features in the table where you and your teams are already collaborating and for open source repositories.

A

This means that they don't only have their code, their issues and their wiki's on github. Now they also have their CI CD running directly on github, and this means that when somebody is getting started with an open-source repo and they want to fork it, it's gonna be super easy for them to get started and directly build that project. Starting from the configurations.

A

Each hub actions and github packages are available. Today they are GA and if you liked the keynote, that was only the tip of the iceberg, because Jeremy and I will show you a bit more details about actions and packages and also lots and lots of demos with all the cool things that we released in the last few months.

B

Yeah Smita was saying with github actions, there's really a lot that you can do, while most of the core workflows really are CI CD for most of what you do as a developer, you can really automate anything in github any events and we'll walk through some of this in the demos later, but whether it be creating an issue, editing a pull request. Somebody new comes to your repo, a deployment happens. Any of those events can all be automated.

B

You know what the goal behind that is to make it really easy for you to focus on what matters which is writing the code for your project. You don't want to be always out triaging, bugs and kind of dealing with all these repetitive tasks. You want to be able to automate those away, and one of the great things is because these are just files checked into a repository. You can go and look at how other projects work as well.

B

Maybe you know you like the way the node project works or kubernetes if they're using actions, and then they have those workflow files checked in right there. You can go ahead and fork. Those remix them put them into your workflows as well, and then we have a market places of over 1200 actions. That's constantly growing or you can see what more and more developers are doing to make it easier to kind of automate all the different tasks you have.

B

So, as we talked about a little bit in the keynote, we have all the core things you would expect for a built in CI and we'll go through that, whether that being like expressions matrix, build support for containers, Windows, Mac, Linux everything you have streaming logs, we have a built in secrets, store and then to speed up your builds, artifact, caching and then now self hosted runners.

A

For github packages, we're bringing your packages and your code source together on github, and this means a couple of things for teams who want to keep things private within their organization. It means I, can push and their publisher packages to github, and only people from their organizations will be able to see and to install those packages. This means these teams, don't have to sync permissions between different systems and to deal with all that stuff.

A

When a new developer comes to the team or when a developer leaves the team for open source developers and teams, this means that they can publish their packages to github and there's a direct correlation between the repository and the package in the last few months. During this beta, we saw over 10,000 users using packages and they published tens of thousands of packages, so we're super excited to see what will come next.

A

Github packages has support for public and private registries and there's no magic there. If the package corresponds to a public repository, then the package will be public. If the package corresponds to a private repository, then the package will be private and there is no need to manage permissions between these two between packages and code, because there's one login for code and packages and everything is under github.

A

What is means is that you can log into github, with the same account that you always use use the same search and you'll find packages use the same permissions that you have read and write to know if you can only install permission, only install packages or also publish packages. We have support for some of the some of the most important registries there and p.m. docker maven, rubygems and nougat, and just few weeks back, we released support for Gradle as well as you can expect.

A

It works with any CI and with github actions, and we think we're really gonna like this one, because we paid extra attention on how github actions and github packages work together. Of course, if you want, you can use github packages from your local machine, but we really recommend letting the robots doing the work and automating this one being part of github. We really believe in integrations and api's, so github packages has a full graphical support and webhook supports, so you can automate your work.

A

Those, however, you prefer there's also packaged analytics for maintainer and for consumers alike. So, as a consumer, you can see how many downloads a package has, if it's popular or not, what are the details, previous versions and so on. And finally, during the beta, we heard from a lot of people that it's really important to have an easy configuration and especially for NPM easy configuration is key, so we are offering proxy support for NPM, which means github packages will proxy the packages that you need from NPM and deliver them straight to your project.

A

So this was a bit in a nutshell about actions and packages. But now we want to show you some cool demos about what they are really about.

B

Great thanks to Mina, so I'm gonna walk through a couple demos, and these will be different than the keynote. So one of the things that you'll notice is before we just walk through kind of creating a new workflow. So, as you saw before in the keynote we clicked here and we were able to create a new workflow, it automatically detected my language, but let's dig in a little bit more and see what's actually happening in some of these workflow files.

B

So, as we said, we're automatically detecting that Java scripts, the primary language in this case and automatically suggesting a set of workflows. But what we've done is we want to really make sure we're embracing the community with each one of these ideally and we've already seen a lot of open source contributors as people from node or helping us figure out. What's the best way to have node CI work and the same for go and every one of these different languages that we support. So each one of these is actually an open source repository.

B

So if I were to click right here, you can see we have an actions organization on github and then we have a repo with all the starter workflows, so anybody can come and contribute directly what these are. So, maybe, if you're wanted to browse the workflows, see what the actual code is behind these before committing to one of them, you can go through and see what each one of these are.

B

You can go up and see that we have a myriad of different CI workflows and then we also have a set of workflows for automation as well. So whether or not you want to greet new contributors or you want to go ahead and mark an issue, a sale or anything like that, it's all supported with a set of workflows to make it very easy just to get started there. So now, let's jump back to where we were a second ago.

B

And one of the things you'll see is that this is true for all the starter, other starter workflows as well, so whether it be Python Ruby anything all these are open-source and we're ready to see your contributions directly to those if I were to go ahead and click and get started on one of these, you saw before a little bit of kind of how we have autocomplete and things like that to make it a little bit more approachable as you come through.

B

So again, we have a lot of different features here that you can go ahead and have so when you think about what does it mean to build CI CD? Well, basically, you have a directed acyclic graph and that's the way to think about it. Basically, we have a set of jobs and a workflow is composed of a set of jobs within a job. You have a set of steps and the jobs are the graph, so each one of these are running on a different runner. This could be a self-hosted runner that you have.

B

It could be like a Raspberry Pi under your desk. It could be something in the cloud or it could be one of github runners itself and we have runners for Windows, Linux and Mac that are free for open source and then for every single private repository, there's included minutes as well, but we'll go through more a little bit later and then, as I'm going through and editing these files.

B

There's multiple different events that I could have so I could have a push event or I could do issue create again any of these events that happen on github. You can go ahead and subscribe to these as well. So then, if I go over here to give you an idea, almost anything that we generate a webhook event for these are actually fully sub ported directly and github actions. So we go down here.

B

You can go ahead and look so, whether or not you want to say, hey I want to trigger our workflow off a check, run or a check sweet or whenever a tag is created. Maybe you want to kick off a release whenever a tags created or you want to kick off a release. Only on a specific pattern of when that tags created- maybe you want to say, like v-star, we can go ahead and do that as well.

B

If you want to filter down to a set of branches and only say for this set of branches, if you want to filter down to just a path, maybe you have a large mono repo, and then you only want you want to have separate workflows for different paths than that. So you want to go through and say hey if code changes in this directory, let's go ahead and do this bill. If it changes this directory do a different build again.

B

All that support is built directly into actions, whether or not there's a deployment deployment status, forking almost any event that happens on github, it's all there, and then we have a general event called the repository dispatch event. So this allows any third party system to actually plug in with github actions and trigger any kind of workflow. So this could be Prometheus. This could be JIRA ticket is created. It could be almost any event. That's out there.

B

You can go ahead and hook up, and it just gives you that flexibility to really make actions the glue that connects all these different pieces across your workflow. So we really want you to be able to automate everything from idea all the way to production as well and not just have CI CD.

B

So, let's jump back over here and one of the things that you'll notice here is a couple different things in this Marc flow in this markdown file. Sorry, in this yamo file, you'll notice, here we have the matrix, build and we're going ahead and building across multiple different versions of node. Again, this matrix syntax isn't just something that's specific to node. You could be doing this with multiple versions of go or Ruby or dotnet or anything there you can even do includes and excludes on these as well.

B

So you can say: hey actually on this specific leg of the matrix. I want to go and add this set of variables to that and specialize the build there or I want to exclude these other options. You can have it fail fast.

B

So if one of the things in the matrix fails, it's going to go ahead and stop running the whole matrix, so you don't kind of burn up all that compute, if you don't want to, if we kind of crack open one of these you'll notice that we really went for an explicit syntax for how we go and build these so here with actions, you'll notice that the first thing you have to do is check out and again.

B

This is because we're more than just the ICD if you're looking for you, know an issue created or you're, making a kind of a chat, ops bot where you want to say when everybody adds a comment to the PR, that's a slash, deploy it's gonna kick off a deploy. You don't want to be cloning code at that point. So again you go ahead and check out the repo, and then we have a set of actions to make it get started very easily with all the different languages and platforms we support.

B

So under actions we have setup node. We also have a lot of different set up actions. You can see if we're here set up Java set up Ruby go again, all these easy ways to get started and kind of help you with some of the basics, especially if you're doing cross-platform builds, there's, definitely differences between Linux and Windows and Mac on how some of these environment variables need this be set up if you want to set up proxy and authentication and all these other cases.

B

So these are helper actions that make it really easy, but one of the cool things you'll notice here is, you can just do run and then we will just run a bash command like directly here and then you can set environment variables and that's all scoped to this one step here, but you notice, some of these just say uses and it says, uses actions, setup node.

B

So what this is actually doing is it's going to the actions org and going ahead and grabbing the code directly off there and from there you can actually go and let's jump over and look at what that is here.

B

And then right down here, we can go ahead and see the code for this specific action. So there's a couple different things we have going on here. One of them is everyone: has this actions yamo file and what this does is just specify the basics of creating an action so that you can go ahead and share that in the marketplace and have other people go ahead and use that. So it's a pretty similar similar format, you would imagine you can go through, give it a name, description, author.

B

You can specify a set of inputs in this case this set up. One is: has a couple inputs for the off that you want the specific node version that you want: a registry URLs to make sure npm, publish, works, properly, scope, information that you would need as well as well as version and then there's two different ways to write actions. One of them is to just create a container and we'll execute that container.

B

Another one is to use javascript to write your action and you just have a set of javascript, which is what we used in this case just sitting right there in the repository. So let me jump back up over here and we'll jump over to the source directory and get an idea of what that looks like. So, if I go over to this setup node in this case, we ended up writing this in typescript.

B

But you can see we have a set of helper modules to make it really easy so directly in the actions or we have a core module that you can use so again doing cross-platform see ICD, isn't always the most straightforward thing. You have to execute things differently. The file systems work a little bit.

B

So we have a set of helper functions to make that really easy to support that, but other than that you're, just writing, JavaScript or typescript, or anything that compiles down or trans piles directly down into JavaScript to go ahead and create your action, which makes it really easy and approachable. So you can go through and see what's going on here we can see we're grabbing the version from that version parameter.

B

We saw before we're going ahead and downloading a version if it's not there, setting up the authentication and then setting up a set of problem a chore so that we can get better errors for what's happening for that specific language. So again, this gives you a little bit of an idea of what does it mean to go ahead and build an action and there's a talk later tomorrow afternoon, that'll dig a little bit more on how to go and build actions and what that looks like so.

B

Let's jump back to where we were before and I'll show you a couple more things here. One of the other things that you saw from the demo was the set of marketplace actions and we have lots of different actions rectly in the marketplace so from right. Here you can go ahead and search. So if you want to maybe work on a fireplace firefox, add in I can go over here, search for Firefox, there's an add-in right there. I can go ahead and see the number of stars.

B

If I wanted to click on this I can get an idea of the listing. I can see the gamal that I need to copy and paste directly in and I. Can click right here go over here and just copy and paste that yeah mol directly in and again, this is searching the entire marketplace again. If you wanted to go over, you can go over and view the full listing on the marketplace to get all the information on that.

B

Let's go over and check out one more of these, so we saw that there were some kubernetes ones as well, so we can click on this one right here and jump over to the full marketplace listing and one of the things you'll notice is you have a full readme file. As an author of these, we have creator verification as well. So we can tell you if it's an organization that you can trust, is this officially from that official organization like?

B

Is it the specific one that you know the code cuff team built for doing code coverage or is it from this case a sure? Is it from Google? Is it from AWS? You can see stars, you can see contributors, you can see if there are open issues, pull requests and then go through and get more information on what that is and how to go. Use that action. So now, let's jump over to another repo and walk through a little bit more detailed CI system.

B

So in this one is we, as I mentioned before, you can have multiple different filters and events. So in this case it's pull request. We have a push event: we're filtering these down to branches. You can include exclude branches, you can filter on tags and paths, as we talked about before you can set up matrices across multiple different things, so you don't have to have a single matrix. That's just note or a single variable. You can multiply these out. So in this case, what's gonna happen?

B

Is it's gonna run these three node versions across these four OS versions, so I'm gonna kick off 12 simultaneous jobs that are all gonna run in parallel, every single time, I run my CI. This is similar as we walked you before, checking out the repo setting up the environment and going ahead and running a couple scripts.

B

Then down here, you can see some more of these use cases for these set up actions, so this case I really want to target a specific version of node I want to have the registry and proxy and authentication information all set up for me. So again, all I'm gonna have to run, is NPM, publish and then we have a built-in secret store directly in to github as well. So if I were to go over here and click on settings, I can go down and right here, there's a secret store built into every single repository.

B

So you can see I named this one NPM token again, if you want to add a new secret, it's as simple as going to here typing in a new secret, the name and then providing a value and again that's securely stored by github. And then, if you wanted to use self-hosted runners as well, we now have self hosted runner support as well. So you can see I've already configured this Linux VM and it's not in use right now.

B

But if I wanted to add another runner, we have an easy set of scripts that you can go. Do to download that runner on your own hardware and again we support Linux, Windows and Mac OS and next week will also be supporting arm architectures arm 32 arm 64 as well as x86 as well, and we're continuing just to expand the breadth of that matrix so that you can test everything that you need to be able to test to have a full CI CD experience.

B

Before one of things we talked about too was wanting to have fast builds, so a key to that is having caching support and I'm really excited that we now have caching support. So in this case, maybe you want to cache your node modules directory. This could be nougat packages, or this could be some binaries that you went and built as well.

B

So we can jump over actually and check out that repository itself, because again, all these actions are open source I'll scroll down here, and we have a set of examples right here to kind of give you an idea of how do you go ahead and use this action? What does it mean? Okay, the cache action. We need a specific path to be provided, so we know what we're gonna be.

B

Caching, and then you can generate that key yourself and again that T key could be tied to a path, a specific runner, a branch that you want to cache. And obviously, if there's a hundred percent cache hit, it's gonna be really fast, but we also have fallback as well. So we you don't have to have a hundred percent cache hit. You could say: oh, let's fall back. Let's check this other branch, maybe from awhile ago, grab the relevant packages there.

B

So you'll get some speed benefit, maybe not as much with an exact cache hit and then, if I click down here, you'll also notice that we have examples for just about every language. Again, our goal is to have every language every platform, every cloud so whether you use Go Java, maven, NPM you're using yarn PHP again. We have good examples. The community is helping us author to make sure that you can use caching and build ci CD really into end for what you need.

B

Now, let's go ahead and look at what does it mean when we actually publish one of these so down before you solve that workflow? That I was showing here a second ago where not only have I gone through and did the build, but I also published here to NPM and github packages, and now Samina is going to come up and show you what we've been working on with github packages.

A

So Jeremy showed you all about actions or not all about but a lot about actions and how to publish a package, but these packages are only useful when somebody wants to consume them and need them and uses them. So, let's assume that I want to use the package that Jeremy just published there's a couple ways: I could do that.

A

One is that I could go to Google, let's say and search for a Fibonacci note package and install whatever I find on Google, because it's a super safe way to use my source code now, I won't do that. Another way I could do is to go to github into use, search and to see what packages I find there that's a little bit better, but in this case I want to use a package that somebody in my organization published because I really trust these people. So what I can do is to go to my organization.

A

Space on github and I will see here. I have a lot of repositories and next to the repository step, there's a package tab and these packages are all the packages that were published by somebody in my organization. So what is signals to me is a I can trust these packages.

A

These are people that have already commit rights to the repositories in the org, so I can trust them and install packages that they published as well, and you can see here that github packages has support for many ecosystems, so there's here a docker image and there's a maven package, there's a Gradle one and there's also support for nougat and Ruby gems. But in this specific scenario, what I care is about installing a node package and looking at the node packages looks like this. One over here is really popular.

A

It has over 1,000 downloads, good job journey, so I will click on this package, and here on this page I will be able to see a lot of useful information. So, first of all, it's a latest version, which means it's probably the version that I should install and at the top there's the install instructions generated by github. So I can simply copy these instructions, put them in my project and then get started with this package.

A

I can also configure my project to use github packages as a proxy, so it gets all the in for all the other packages that I have specified in my package, JSON straight from NPM js.

A

Now, here there's a description for the package, but if I wanted to make things a bit more clear for developers that are wanting to use the package or include more information, I can simply edit it it's a simple, simple, markdown file. So it's easy to get started.

A

What else I have more package details, such as the organization and the repository that this package belongs to the date when it was published and also download activity. So this was the repository that Jeremy published earlier today and then I can also see previous versions that were published in the neck last few days.

A

So with that I want to pass back to Jeremy and to show us some more stuff about actions. Great.

B

Thanks one of the things that we talked about before was CI CD is amazing for getting productivity back in making sure that you can deploy packages and get those into production and get all of your building and testing, especially in parallel, but another key part of that is actually deploying web services so when to spend some time kind of showing some of the work that we've done around there as well.

B

So let's go in here and look at one of these workflows, so you can see we have a couple different workflows, all upload, this one right here for deploying Google. So again we have a set of starter workflows that make it really easy for you just to grab ones in this case. This is one that Google supports themselves and you can go ahead and see their recommended way of deploying to gke.

B

So in here you can see we're automatically going to kick off this deployment. Whenever there's a change to pull requests in the master branch, you set a set of environment variables up front again. We have environment variables at the work flow level. You have to go ahead and configure a couple, different secrets to get that image in there correctly and then a lot of the things that you would expect for deploying the kubernetes. If you've done that before I can go ahead here, check out the repo they go ahead and create a github deployment.

B

What this actually does is creates a little bit of deployment UI in the air repo as well. So what that does is if I were to go over here to code, you'll notice, this environments, tab appears, if you go ahead and create a github deployment, and it will also show that in the pull request as well, so you don't just see the workflow run.

B

You also see the actual deployment specifics, and if you dig into this, you can kind of see all the different environments, this AWS environment, Google and Azure- that are there as well as a history of all the different deployments that have happened.

B

So, let's jump back into this workflow.

B

So for here, I've created the github deployment and then they've also created a setup g-cloud action as well. So what this enables you to do is to make sure you have the latest version of the g-cloud CLI installed. You can go ahead and specify that here and get the basic setup for your account key email, everything, an easy action to get started there, and then they run a couple scripts just going ahead and authenticating into g-cloud, going ahead and building a docker image and again you're.

B

Just using the normal commands that you'll be running locally as well go down here, publish and again you can publish to github package registry. We have great container support as well. In this case, it's getting published to the Google container registry, go ahead and set up a couple, more items and then do a deployment right here and then update your deployment status at the end so again a familiar easy way to go approach these. These are all bash scripts that we're just running directly.

B

Inline here you'd be able to run these on your local machine to test and debug those as well one by one just to make sure it's all working exactly the way that you expect and then as well with actions. Obviously, if you've been doing a lot of workflows and CI CD, you need an easy way to kind of get an idea of what is the state of my system or my builds going well or my deployments going bad. Where is it failing?

B

Maybe you have someone that kind of looks after the build on your engineering team and we have a really easy experience for doing that directly and github actions. You can go over here and you saw me earlier create a new workflow. I can also see all the different workflows that are in this repository right here. On the left hand, side I can go ahead and scroll down and see each one of the runs of those workflows, so in this case I'm at all workflows view, but let's dig in just specifically to the Google one.

B

So I'll click right here and now, we've filtered the list. You can see that added right there to the search bar just down to the deploying to gke ones. I can go through here and I can see all there was a failure. A couple of them succeeded. I can go ahead and see the branch who triggered that how long ago was it? How long did the deployment take and then be able to jump into specifics like going ahead and view that individual run or being able to pull out a workflow file?

B

I can even click over here and easily search, maybe I to go filter all these by the branch or a specific events. It's all right there right in my search box or I, can search directly here to to maybe see who was it that triggered that build or who didn't trigger that build.

B

But again, it's again with actions, it's not just CI CD. So we looked at packages. We looked at also web service deployments. There's a lot of other really interesting things, and this is one of my favorite actions they got build recently- is that the yarn team has actually been using this to determine if a bug is reproducible or not so let's go over here and look for this.

B

And we can go ahead and click on one of the bugs here and one of the things that you'll notice they built this really creative github action. So whenever someone's filing an issue in the yarn repo a lot of times, they want to know, is this bug, reproducible or is it not, and it's a lot of work for the kind of maintainer x' to go through? Sometimes the person filing the issue? Does that hard work? Sometimes they don't.

B

But now what you can do is, if you just do proper code fencing on a on when you file the issue, you can come in here and put a block of code and then what they will do is they created this github action via this yarn bot that will automatically run that set of code, see if the issue is reproducible and go ahead and label it as well. So again, this shows the kind of variety of things you can do. Wow. We have full support for everything.

B

You would expect, with CI CD conditional statements to run steps or not run steps to get back call the github API to get an insight into specifically. What's going on with your builds again, you can do all of that, but there's really this whole other world of things that we can automate, whether it be if an issue is reproducible or welcoming a new contributor, or maybe you have in your Enterprise. You have a set of corporate compliance policies that you need to say hey.

B

Whenever somebody joins a repository, we need to go ahead and take some action or whenever somebody leads the company, we want to go ahead and make sure that we remove their access to the repository. All of these are the examples of different things that you can go ahead and automate with github actions all right. Now, let's switch back to the slides.

B

So, as you saw, we went over a couple different things with github actions you can see we can build on Linux Windows Mac, as well as having container builds one of the interesting things about containers as well as not only what can we build inside the container, so you can provide a set of steps that we can go run there. We also have multi container testing and that one of the talks tomorrow is going to go into even more details of how to set that up.

B

So in that case, imagine you're doing a web service and you have maybe like a node web service and then you minitest with a Postgres database. We have full set up right there and our CI CD workflow, so that you can easily and automatically network those together to do functional into end testing directly in your CI CD Matrix builds and caching to have those fast parallel testing streaming searchable law again with color coding. Everything that you would expect right there to quickly find that issue.

B

You can even link to specific lines of the log, send that to somebody else, if you're not sure what the error is and get their feedback on, that we have a built-in secret store and then finally, we now have self hosted runners, including next week, ARM architecture, support and x86 support for.

A

Packages you can publish your public and private packages and you have one login for your code and packages, and this also means you'll have the same it hub, api's and web hook. Support for your forget hub packages.

A

It has support for multiple ecosystems, NPM docker, maven and Gradle nugget and ruby gems, and finally, where it's really well with actions and with any CI now I, you might be wondering what it costs if you're an open-source maintainer or a team working on open source repositories, both github actions and github packages are completely free for open source and public repositories.

A

If you are using private repositories, we also have really good news for you. Github actions offers a simple pay-as-you-go pricing with included minutes on each plan to get started and it's the same for packages. You will get it for every one. Every plan and you'll have included storage and downloads on every plan. So what does it mean in practice for github actions? We are charging you per minute and you will have a generous amount of minute on any plan.

A

You are for private repositories, so if you're on github free and that means you're paying precisely zero dollars for github, you will get 2,000 minutes of free 2,000 minutes of yeah for private repositories and if you're on organization, you can get up to 50 thousands minutes for an enterprise organization for per billing entity.

A

If you want more, it's easy, you can just enable overages either through your billing settings, UI or byte into your sales account manager, and you can just pay as you go for the extra minutes and if you want to use your own self, hosted machines either in a VM somewhere or on your Prem.

A

It's all for free for github packages, it's similar, so github charges for the storage used by your packages and for the Downloads made for the packages so for the data transfer out and you will get included, amounts from free to pro, to team, to enterprise and, for instance, for enterprise. You get 50 gigabytes of storage for your enterprise, account and 200 gigabytes for data transfer out, and this is already included in what you're paying today.

A

If you need more, you can pay additionally for storage and for data transfer out now, if you use github packages and github actions together, and we think you really should the data transferred out from github packages it's for free when use with github actions. So if you use an action, doing npm install or the Downloads from github packages will be for free.

A

Ok, so I think that's about it. We are really excited about bringing actions and packages general available available. Today you can go ahead and check them out, go and try them out in your repositories. It's for free. If you have public repos. If not, you have plenty already included to get started and yeah come to us. The github as github boost, ask us questions and also go to Kayla's and add session tomorrow afternoon at the Embarcadero stage. Thanks.