Build Intelligence custom S3 cache path.
under review
P
Papaya whip Hoverfly
When we use Build Intelligence and the cache is saved in our S3 bucket, it gets saved in a directory like this,
<s3bucket_name>/<harness_account_folder_name>/<BuildIntelligence_keys/files>
We'd like to be able to customize this path.
Log In
ompragash
Thanks for the clarification. Understood that the ask is to structure the Build Intelligence cache path in customer-managed S3 using Harness context such as account, org, project, and pipeline identifiers, instead of storing all Gradle/Maven cache objects under a broad account-level prefix.
We will review the support for this and update this post accordingly.
ompragash
updated the status to
under review
P
Papaya whip Hoverfly
yes, so we will be having multiple pipeline across enterprise so for that, we might need to track the build intelligence path which is mandatory. if there is no path set it defaults to
s3bucket><harness_account_id>.gradle/ * we gets here lot of objects currently i have 20 k for pipeline multiple runs so lets think of 15k pipelines
same for mvn 3bucket><harness_account_id>.mvn/*
can you update the default path to
<+account.identifier>/<+org.identifier>/<+project.identifier>/<+pipeline.identifier>/{some_key}
ompragash
updated the status to
pending feedback
ompragash
Just to confirm, are you asking for a configurable S3 prefix/base path for where Build Intelligence stores its cache objects, while keeping the generated Build Intelligence cache keys and files underneath that prefix?