[CI][Java] Use current cookbooks projects to validate new release versions
- 主要語言
- Java
- 星號
- 94
- 分支
- 152
- 平均合併
- 3 天 16 小時
- 30 天內合併 PR
- 11
描述
Current there are recipes to validate Arrow components at:
There are a CI process to create components for new Arrow Java releases:
These two projects are working independently.
The purpose of this ticket is to {**}define a way about how to use cookbooks to validate new releases version{**}.
`[~jwozniak]` @raulcd @lwhite1
**Reporter**: [David Dali Susanibar Arce](https://issues.apache.org/jira/browse/ARROW-17073) / @davisusanibar
**Note**: *This issue was originally created as [ARROW-17073](https://issues.apache.org/jira/browse/ARROW-17073). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
貢獻指南
研究方向
首先,比對 apache/arrow-cookbook 專案中的 recipes 與 Apache Arrow Java nightly site 發布的 Java release components。定義 cookbook 驗證應如何與新的 Java releases 連接,以及哪個 CI 結果可以確認某個 release 已完成驗證。issue 中沒有指定特定的檔案或測試。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- java
- 領域
- ci-cd, release, testing-qa
- Issue 類型
- 功能
- 難度
- 5/5
- 預估耗時
- 一週以上
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 20/100