Note: GitHub Actions support on GitHub Enterprise Server 2.22 is a limited public beta. To review the external storage requirements and request access to the beta, see "Enabling GitHub Actions and configuring storage."
Note: GitHub-hosted runners are not currently supported on GitHub Enterprise Server. You can see more information about planned future support on the GitHub public roadmap.
You can use GitHub Actions to create custom continuous integration (CI) workflows that build and test projects written in different programming languages.
- About continuous integration
- Setting up continuous integration using workflow templates
- Building and testing Node.js
- Building and testing PowerShell
- Building and testing Python
- Building and testing Ruby
- Building and testing Java with Maven
- Building and testing Java with Gradle
- Building and testing Java with Ant
You can automate publishing software packages as part your continuous delivery (CD) workflow. Packages can be published to any package host and to GitHub Packages is available with GitHub Free, GitHub Pro, GitHub Free for organizations, GitHub Team, GitHub Enterprise Cloud, GitHub Enterprise Server 2.22, and GitHub One. .
- About packaging with GitHub Actions
- Publishing Node.js packages
- Publishing Java packages with Maven
- Publishing Java packages with Gradle
- Publishing Docker images
Cache dependencies and store artifacts to make your workflow runs more efficient.
Connect services to your workflow using service containers.