Guides

Creating custom continuous integration workflows

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

Publishing software packages

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.

GitHub Packages is not available for private repositories owned by accounts using legacy per-repository plans. Also, accounts using legacy per-repository plans cannot access GitHub Container Registry since these accounts are billed by repository. For more information, see "GitHub's products." .

• About packaging with GitHub Actions
• Publishing Node.js packages
• Publishing Java packages with Maven
• Publishing Java packages with Gradle
• Publishing Docker images

Caching and storing workflow data

Cache dependencies and store artifacts to make your workflow runs more efficient.

• Storing workflow data as artifacts
• Caching dependencies to speed up workflows

Using service containers in a workflow

Connect services to your workflow using service containers.

• About service containers
• Creating Redis service containers
• Creating PostgreSQL service containers