Skip to content

Instantly share code, notes, and snippets.

@hebasto
Last active August 21, 2023 13:11
Show Gist options
  • Save hebasto/60f4602243f6b79a5bea9720870b93e1 to your computer and use it in GitHub Desktop.
Save hebasto/60f4602243f6b79a5bea9720870b93e1 to your computer and use it in GitHub Desktop.
GitHub Actions CI Notes for Developers

GitHub Actions CI Notes for Developers

In response to limiting free usage of Cirrus CI, the Bitcoin Core project is in the process of partially transitioning to GitHub Actions CI (GHA).

This document aims to outline differences between Cirrus CI and GitHub Actions CI for developers.

1. Tasks Moving to GitHub Actions

Two tasks ae/will be shifted from Cirrus to GiHub Actions:

  • "macOS 13 native" (refer to PR28187).
  • "Win64 native" (refer to PR28173).

In the context of GitHub Actions, these tasks are referred to as "jobs" and will be combined within a single "CI" workflow.

2. Locating Your GHA Jobs

In a pull request, you can find the GHA jobs in the following places:

  • The "Checks" section at the bottom of the "Conversation" tab.
  • The "Checks" tab.

The repository-wide workflows are accessible at https://github.com/bitcoin/bitcoin/actions.

To run GHA in your personal repository, you need to activate them as per GitHub's documentation.

3. Re-running GHA Jobs

Unlike Cirrus, only maintainers have the permissions to re-run GHA workflows within the Bitcoin Core project. Feel free to ping me (@hebasto) in your pull request or on the IRC channel (hebasto) if you need a re-run.

I'm committed to responding as promptly as possible according to my timezone.

4. Performance Considerations

GitHub Actions allows up to 20 concurrent jobs, with a maximum of 5 concurrent macOS jobs.

5. Log Retention

Logs will be retained for a period of 90 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment