Feature Requests

We using the same repo for building our dev and production images, and only the tag name that differentiate from being dev or prod, could you guys please add support to change the key to add env name for example, or env name that could change this? This is a blocker to use the functionality

I noticed that the compression options are limited to Tar and Gzip. It would be beneficial to have an effective compression algorithm like Zstd available. This could significantly speed up the upload and download processes, enhancing overall efficiency.

Add a feature to select a especific iOS version in Harness Cloud infraestructre for MacOS machines

Currently the build pod that is spun up when running a CI stage using k8s infrastructure has a deadline of 24 hours. This can be noticed on the pod spec of the build pod spec.activeDeadlineSeconds. This makes it impossible for steps that have a timeout configured over 1 day. Ideally the build pod should respect the timeout configured on the steps and shall make running steps for longer durations (including days/weeks)

VM Pools for Windows require a lot more time for their image creation and "healthy" State to be established. There needs to be a method to be able to adjust the init timing on the VM creation.

Feature request as suggest by Harness team to enable system level error retry mechanism for the below failures : - Pod eviction Failure to connect to addon client Connectivity errors between delegate and ci lite engine ref : https://support.harness.io/hc/en-us/requests/72479?page=1

We are looking to perform something like the following: https://docs.jfrog-applications.jfrog.io/jfrog-applications/jfrog-cli/binaries-management-with-jfrog-artifactory/build-integration#adding-files-as-build-dependencies Where teams can add build dependencies to a build This could potentially be a part of the build info plugin ( https://developer.harness.io/docs/continuous-integration/use-ci/build-and-upload-artifacts/build-and-push/build-and-push-to-docker-jfrog/#publish-build-metadata-to-a-docker-image-in-jfrog-docker-registry ) , but it may make sense as a process, so that it can be operated separately from a build

Provide an option within the Docker build plugin to control whether the image should be pushed to Artifactory immediately after the build, allowing teams to scan the image for vulnerabilities or issues before pushing it to the repository.

Currently the pipeline execution list screen only allows for filtering on the repository that the pipeline yaml is stored. For use cases that use global templates, this filter is pretty useless as there is only one option, the repo the template is stored. Can we add the ability to filter executions based on the codebase URL? this will allow actually filtering based on service repository in the case of a common template

I have a gradle config that we will be using account wide based authed with pipeline defined environment variables. Currently I have to store the gradle config as a file type secret even if its not a secret. Is it possible to support file type variables?