root
/
kafka
mirror of https://github.com/apache/kafka.git
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity
kafka/.github/workflows
History
TaiJuWu 3783385dc1
KAFKA-17542: Use actions/labeler for automatic PR labeling (#17208) 
Reviewers: Chia-Ping Tsai <chia7712@gmail.com>, David Arthur <mumrah@gmail.com>
 		2024-09-19 19:39:12 -04:00
..
README.md MINOR Fix is-public-fork input type (#17227) 2024-09-19 14:13:06 -04:00
build.yml MINOR Fix is-public-fork input type (#17227) 2024-09-19 14:13:06 -04:00
ci-complete.yml MINOR Always publish build scan in CI Complete workflow (#17195) 2024-09-14 08:48:42 -04:00
ci.yml MINOR Fix CI workflow for push event (#17239) 2024-09-19 17:07:31 -04:00
deflake.yml MINOR: Handle new Gradle exit code behavior in deflake.yml (#17158) 2024-09-11 14:22:54 +08:00
docker_build_and_test.yml KAFKA-17193: Pin all external GitHub Actions to the specific git hash (#16960) 2024-08-23 12:37:12 +02:00
docker_official_image_build_and_test.yml KAFKA-17193: Pin all external GitHub Actions to the specific git hash (#16960) 2024-08-23 12:37:12 +02:00
docker_promote.yml KAFKA-17193: Pin all external GitHub Actions to the specific git hash (#16960) 2024-08-23 12:37:12 +02:00
docker_rc_release.yml KAFKA-17193: Pin all external GitHub Actions to the specific git hash (#16960) 2024-08-23 12:37:12 +02:00
docker_scan.yml MINOR: Add 3.7.1 to docker_scan action (#16962) 2024-08-26 11:53:50 +02:00
labeler.yml KAFKA-17542: Use actions/labeler for automatic PR labeling (#17208) 2024-09-19 19:39:12 -04:00
prepare_docker_official_image_source.yml KAFKA-16998 Fix warnings in our Github actions (#16410) 2024-06-24 12:53:49 +08:00
stale.yml KAFKA-15073 Close stale PRs [2/n] (#17166) 2024-09-11 15:10:03 -04:00

README.md

GitHub Actions

Overview

The entry point for our build is the "CI" workflow which is defined in ci.yml. This is used for both PR and trunk builds. The jobs and steps of the workflow are defined in build.yml.

For Pull Requests, the "CI" workflow runs in an unprivileged context. This means it does not have access to repository secrets. After the "CI" workflow is complete, the "CI Complete" workflow is automatically run. This workflow consumes artifacts from the "CI" workflow and does run in a privileged context. This is how we are able to upload Gradle Build Scans to Develocity without exposing our access token to the Pull Requests.

Disabling Email Notifications

By default, GitHub sends an email for each failed action run. To change this, visit https://github.com/settings/notifications and find System -> Actions. Here you can change your notification preferences.

GitHub Actions Quirks

Composite Actions

Composite actions are a convenient way to reuse build logic, but they have some limitations.