[
https://issues.apache.org/jira/browse/HDDS-17830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Doroszlai updated HDDS-17830:
------------------------------------
Fix Version/s: 2.3.0
Resolution: Implemented
Status: Resolved (was: Patch Available)
> Run populate-cache before build in forks
> ----------------------------------------
>
> Key: HDDS-17830
> URL: https://issues.apache.org/jira/browse/HDDS-17830
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: CI
> Reporter: Attila Doroszlai
> Assignee: Attila Doroszlai
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.3.0
>
>
> Caches in fork can get outdated and/or evicted due to:
> - populate-cache on push runs only for commits touching specific files (POM,
> etc.) on master (and some release branches). If the fork is synced (master
> updated) to ineligible commit, the workflow is skipped even if POM files were
> changed by other commits between previous and new HEAD.
> - scheduled-cache-update may get skipped for over a week by GitHub
> ([example|https://github.com/lpavanvenkat/ozone/actions/workflows/scheduled-cache-update.yml]:
> no runs between 2026/10/08 and 2026/10/22)
> - populate-cache is not run on push to dev branch
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]