[jira] [Resolved] (HIVE-30046) Move Thrift gen code validation in GitHub actions

["Ayush Saxena (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HIVE-30046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ayush Saxena resolved HIVE-30046.
---------------------------------
    Fix Version/s: 4.3.0
       Resolution: Fixed

> Move Thrift gen code validation in GitHub actions
> -------------------------------------------------
>
>                 Key: HIVE-30046
>                 URL: https://issues.apache.org/jira/browse/HIVE-30046
>             Project: Hive
>          Issue Type: Task
>          Components: Build Infrastructure
>            Reporter: Stamatis Zampetakis
>            Assignee: Ayush Saxena
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.3.0
>
>
> HIVE-29747 introduces a check in the Jenkins CI pipeline to validate generated Thrift code. Another alternative would be to put this check in GitHub actions (existing or new) to lighten the main pipeline and potentially speed up the runs.
> The goal of this ticket is to measure the overhead (Thrift code generation) in both cases ( Jenkins vs. GitHub actions) and pick the one that leads to faster build times and/or better resource utilization. If it turns out that having it in Jenkins superior then we can document this here and resolve this ticket as won't do.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)