Accelerate CI by commonizing thrift build and leveraging cache
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 1.6k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 33
Description
Building thrift compiler takes several minutes and occupies approximately one out of four or five in the total CI duration.
It can be improved by optimizing workflow and leveraging cache so as to avoid building thrift many times.
**Reporter**: [Kengo Seki](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=sekikn) / @sekikn
**Assignee**: [Kengo Seki](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=sekikn) / @sekikn
**Note**: *This issue was originally created as [PARQUET-2205](https://issues.apache.org/jira/browse/PARQUET-2205). Please see the [migration documentation](https://issues.apache.org/jira/browse/PARQUET-2502) for further details.*
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the repository's CI workflow configuration and how the Thrift compiler is built across jobs; identify repeated builds and existing cache boundaries. Done means the compiler is commonized or cached so CI avoids unnecessary repeated builds and the overall CI duration is reduced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100