Files
grpc-library/.gitea/workflows/pr.yml
T
DongHyeonka 8d705bcaaf
main / main-check (push) Successful in 5m22s
fix(ci): JDK를 Temurin 목록에 있는 이름으로 고정한다
main.yml 첫 실행(Gitea run 1)이 setup-java에서 멈췄다: 「Could not find
satisfied version for SemVer '21.0.11+10'」. Temurin이 내놓는 이름은
`21.0.11+10.0.LTS`다. 템플릿 setup-gradle-java action에서 그대로 가져온
값이라 템플릿에서도 같은 이유로 깨질 수 있다(템플릿 Actions는 아직 꺼져
있어 드러나지 않았다).

같은 21.0.11 빌드를 목록의 이름 그대로 적는다. `21`처럼 줄만 적으면 새
패치가 나올 때마다 빌드 JDK가 말없이 바뀐다.

검증: Gitea run 1 로그의 사용 가능 목록에 21.0.11+10.0.LTS가 있다. 고친
workflow의 실행 결과는 이 커밋의 main 실행이다.
2026-11-08 11:22:12 +09:00

33 lines
1.2 KiB
YAML

# Pull-request stage. The job is the Gradle stage `ci`; which modules, lanes and gates that means is
# decided in build.gradle, not here (docs/work/gates.md).
name: pr
on:
pull_request:
permissions:
contents: read
jobs:
ci:
runs-on: ubuntu-latest
timeout-minutes: 60
steps:
- uses: https://github.com/actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
with:
# bufBreaking compares the schema with the merge base of the target branch.
fetch-depth: 0
- uses: https://github.com/actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00 # v4.7.1
with:
distribution: temurin
java-version: "21.0.11+10.0.LTS"
# Validates the checked-in wrapper jar and caches Gradle's downloads.
- uses: https://github.com/gradle/actions/setup-gradle@3f131e8634966bd73d06cc69884922b02e6faf92 # v6
with:
build-scan-publish: false
cache-read-only: true
- run: ./gradlew ci --stacktrace
# Every strict lane is in a stage some workflow here executes. It plans the stages with
# --dry-run, so it cannot be a dependency of `ci` and is the one second line.
- run: ./gradlew verifyStrictLaneStages --dry-run --stacktrace