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

Dmitry Konstantinov edited comment on CASSANDRA-21367 at 5/12/26 9:15 PM:
--------------------------------------------------------------------------

Maven Central rules have been updated to not misclassify the Cassandra 
dependencies loading pattern as scraping and ban it.
Proper m2 cache re-use is till needed.

it looks like we rely on the host level m2 directory in our Jenkins logic:
{code}
# re-use the host's maven repository
container_id=$(docker run --name ${container_name} -d --security-opt 
seccomp=unconfined --rm \
    -v "${cassandra_dir}":/home/build/cassandra -v 
${m2_dir}:/home/build/.m2/repository/ -v "${build_dir}":/dist \
    ${docker_envs} ${docker_volume_opt} \
    ${image_name} sleep 1h)
{code}
where m2_dir Jenkinsfile set it to:
{code}
script_vars = "${script_vars} m2_dir=\'${WORKSPACE}/build/m2\'"
{code}
so, it looks like we had an logic for m2 re-reuse but due to workspaces cleanup 
on every build (cleanWs plugin invocation) and/or short-living VMs used for 
build it does not work


was (Author: dnk):
Maven Central rules have been updated to not misclassify the Cassandra 
dependencies loading pattern as scraping and ban it.

> Cassandra CIs fail on artifacts resolution
> ------------------------------------------
>
>                 Key: CASSANDRA-21367
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21367
>             Project: Apache Cassandra
>          Issue Type: Bug
>          Components: CI
>            Reporter: Dmitry Konstantinov
>            Priority: Normal
>         Attachments: image-2026-05-12-15-09-17-114.png
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> the last few days we are observing an issue with artefacts downloading from 
> Maven Central by our CI jobs.
> It is not about one specific dependency, it looks like it is just a random 
> failure on downloading a dependency and the dependencies are present in Maven 
> Central..
> {code}
> Error messages:
> Could not collect dependencies: Failed to collect dependencies at 
> com.google.code.java-allocation-instrumenter:java-allocation-instrumenter:jar:3.1.0
>  -> org.ow2.asm:asm-analysis:jar:6.0
> {code}
> Examples:
> * 
> https://ci-cassandra.apache.org/job/Cassandra-trunk/2479/cloudbees-pipeline-explorer/?filter=49
> * https://ci-cassandra.apache.org/view/Cassandra%206.0/job/Cassandra-6.0/18
> * similar story for Github check action: 
> https://github.com/netudima/cassandra/actions/runs/25628788972/job/75308556615#step:4:3526
> The same issue is observed on local machines if m2 cache is cleared. It looks 
> like Maven Central Cloudflare rate limiting is more aggressive now..
>  !image-2026-05-12-15-09-17-114.png|width=400! 



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to