[
https://issues.apache.org/jira/browse/HADOOP-19820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Fabbri updated HADOOP-19820:
----------------------------------
Description:
Epic to organize all tasks related to CI performance and quality of life (QoL)
improvements.
We occasionally are blocked on CI runs that take over 24 hours:
[https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-8225/8/]
Other runs tend to take ~3 hours. Ideally CI should be as fast as possible
(10-30 minutes is ideal, if unrealistic).
was:
Jira to start gathering tasks for CI performance improvements.
I recently was blocked on a CI run that took over 24 hours:
[https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-8225/8/]
Other runs tend to take ~3 hours. Ideally (IMHO) CI should run in 10 minutes.
Would love to help move in this direction but I'm not sure where to start.
Besides looking at profiles etc. I would love suggestions from others on what
the lowest hanging fruit is for improving build, test, and CI time and
reliability.
> CI and Test Improvements (CI is too slow)
> -----------------------------------------
>
> Key: HADOOP-19820
> URL: https://issues.apache.org/jira/browse/HADOOP-19820
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build, test, yetus
> Affects Versions: 3.5.0
> Reporter: Aaron Fabbri
> Priority: Major
> Labels: pull-request-available
>
> Epic to organize all tasks related to CI performance and quality of life
> (QoL) improvements.
> We occasionally are blocked on CI runs that take over 24 hours:
> [https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-8225/8/]
> Other runs tend to take ~3 hours. Ideally CI should be as fast as possible
> (10-30 minutes is ideal, if unrealistic).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
