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

Jiashen Zhang edited comment on PARQUET-2233 at 1/25/23 6:25 PM:
-----------------------------------------------------------------

[[email protected]] for parquet-mr, I found we already have a 
[workflow|https://github.com/apache/parquet-mr/blob/master/.github/workflows/test.yml]
 that is working  and doing same thing as Travis except running on different 
arch. Github Action probably doesn't provide arm64 and I am seeing this task is 
making progress. Do we need build and pass tests on different arch? for 
parquet-format, travis.yml doesn't exist and it is runing with Action already. 


was (Author: JIRAUSER280855):
[[email protected]] for parquet-mr, I found we already have a 
[workflow|https://github.com/apache/parquet-mr/blob/master/.github/workflows/test.yml]
 that is working  and doing same thing as Travis except running on different 
arch. Github Action probably doesn't provide arm64 and I am seeing this 
[task|https://issues.apache.org/jira/browse/PARQUET-1980] is making progress. 
for parquet-format, travis.yml doesn't exist and it is runing with Action 
already. 

> Parquet Travis CI jobs to be turned off February 15th
> -----------------------------------------------------
>
>                 Key: PARQUET-2233
>                 URL: https://issues.apache.org/jira/browse/PARQUET-2233
>             Project: Parquet
>          Issue Type: Improvement
>          Components: parquet-mr
>            Reporter: Xinli Shang
>            Priority: Major
>
> Greetings Parquet PMC,
> Infrastructure has reached out to you regarding the Travis CI Open Source 
> policy changes, and the resulting need for Apache projects to migrate away 
> from using Travis.
> So far, we have received no response from your PMC.
> On February 15th, we will begin the final phase of this migration, turning 
> off Travis builds in order to bring our Travis usage down to 0.
> We have found the following repositories mention or make use of .travis.yml 
> files:
>  * parquet-mr.git
>  * parquet-cpp.git
> You must immediately move to migrate your builds from Travis. If you do not, 
> you will soon be unable to do builds that now rely on Travis.
> Many projects have moved to using GitHub Actions, and migrating to GHA is 
> quite straightforward. Other projects use Jenkins providing ARM support, with 
> nodes using the arm label
> If you are unsure how to proceed, I would be happy to explain your next steps.
> Please at least respond to acknowledge the need to migrate away from Travis, 
> and to tell us your current plans.
> Thank you!



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

Reply via email to