[jira] [Commented] (LIVY-972) Implement CI for Livy project

["Sumit Kumar (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LIVY-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17700317#comment-17700317 ] 

Sumit Kumar commented on LIVY-972:
----------------------------------

We would also need one ci workflow so we can generate and publish the built artifacts?

> Implement CI for Livy project
> -----------------------------
>
>                 Key: LIVY-972
>                 URL: https://issues.apache.org/jira/browse/LIVY-972
>             Project: Livy
>          Issue Type: Bug
>    Affects Versions: 0.8.0
>            Reporter: Damon Cortesi
>            Priority: Major
>             Fix For: 0.8.0
>
>
> As of February 2023, Travis CI has been deprecated across all Apache projects. 
> We need to implement a replacement in order to ensure passing tests.
> I propose using GitHub Actions - Other large projects like Spark and Airflow make use of them for CI and the infra page has some [more detail on it here|https://cwiki.apache.org/confluence/display/BUILDS/GitHub+Actions+status], but it's a bit dated.
> I imagine three different actions being created:
> * One build-ci-image workflow that creates an image that can be used for CI without having to rebuild every run
> * One unit-test workflow that runs the unit tests for appropriate versions on each push
> * One integration-test workflow that runs the longer integration tests on pull requests



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