Feature Requests

Currently, if TI skips tests due to a previous Commit/report, there is no real indicator other than in the logs. Ideally, we should be able to see indicators and a message to tell the customer and users that there was a skipped scan and the reason. If it was due to a previous run/commit on the same branch, ideally, a link to the Build/Execution where that happened should be provided.

We would like to see support for Test Intelligence and Kotest together.

When setting up notification for pipeline it should have option to customization such as adding detailed information to the notification body, author needs to tag on message etc.. For example, n the event of a failure, you can tag the PR author, customize the message body, and post to the Teams channel.

we need to trigger other stage when one of the stages is expired.

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

We use an on-prem bitbucket data center (Bitbucket v7.1.1) installation and the bitbucket trigger doesn't support triggering upon push of a new branch. The workaround was to use a custom trigger however it removes the ability to abort pipelines executed when the same branch is updated causing duplicates.

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.

As per https://developer.harness.io/release-notes/continuous-integration/#version-154 , CI_INCREASE_LOG_LIMIT when enabled increases the limit of the CI logs to 25MB. However, this will be enabled across the account and will affect all the pipelines. This request is to have an option at the pipeline level so that it can be enabled only for the pipelines it is needed.

When a CI stage is present in a pipeline and it gets triggered by a trigger of type ARTIFACT the pipeline throws this error Invalid request: CI stage cannot be triggered by trigger of type: ARTIFACT

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