Feature Requests

Step in CI stage to upload artifacts to our Nexus artifact repository similar to 'Upload Artifacts to JFrog Artifactory' step.

Early new year App Store will stop accepting apps build on previous SDKs as IOS sdk 18 has been released on September 16,2024. Currently, Harness supports Xcode 15 on IOS sdk 17 as per following documentation: https://github.com/wings-software/harness-docs/blob/main/harness-cloud/macos-14-Readme.md

Ability to use Docker build secrets. Add the option to specify secrets against the built in Build and Push mechanisms.

Currently Harness publishes to GCR but not to AWS's public ECR. Harness should also publish the images to ECR since i'm certain most users leverage AWS for their builds and deploys. Getting rate limited on Dockerhub is a pain.

I want upgrade the plan to execute my operations through the pipeline CICD.

Hello all. I need edit access on pipelines because pipelines created in LSE cannot be run here (some params are missing). Please enable edit access on pipeline for me. I am a comp owner and this hinders my ability to create proper pipelines for my comp.

We would like the ability to hide or restrict unapproved plugins from being used in steps. Harness admins should have the capability to disable certain plugins to prevent their usage. For example, developers currently use Kaniko for building images, but we want to block this to ensure compliance with our internal policies.

We inform you of an issue I’m experiencing while attempting to download harness logs. I can able to download harness pipeline logs through API call but few of the builds I’m not able to download it. API Call : API_KEY="***********************************" ACCOUNT_ID="VNlPYoF1QMOwZmE0CmZLsQ" ORG_ID="harness_core" PROJECT_ID="Yousuf" PIPELINE_ID="LPS_Helm_Pull" PIPELINE_EXECUTION_PREFIX_KEY=$ACCOUNT_ID/pipeline/$PIPELINE_ID/31/-m3rzszdpR3aIcB5s3LruKg curl https://app.harness.io/gateway/log-service/blob/download?accountID=$ACCOUNT_ID&prefix=$PIPELINE_EXECUTION_PREFIX_KEY \ -X "POST" \ -H "content-type: application/json" \ -H "x-api-key: $API_KEY" I’m able to download logs succefully for – Success | LPS_Helm_Pull (Build Id: 71) | Yousuf | Harness I’m not able to download logs for – Failed | LPS_Helm_Pull (Build Id: 31) | Yousuf | Harness Can you please try from your side and let me know I’m able to download even from failed builds. For Ex: Failed | LPS_Helm_Pull (Build Id: 65) | Yousuf | Harness

We use GitHub's pull request feature exclusively for ensuring that code passes certain tests before it's allowed to be merged. This can be things like linting, code quality checks, or executing test builds. Having the ability for Harness to run a build when a PR is created (works today) and then report back the commit status (pass/fail) to the pull request will allow us to bypass the use of GitHub actions. We're aware that we can setup a webhook, but this must be done on each repo and will become quite laborious. Sonarqube is a good example of a thirdparty application that reports back the status of a PR and allows (or disallows) the merging capability of the PR I believe this is GitHub Statuses here: https://docs.github.com/en/rest/commits/statuses?apiVersion=2022-11-28 Sonarqube docs: https://docs.sonarsource.com/sonarqube/latest/devops-platform-integration/github-integration/#reporting-your-quality-gate-status-in-github Deepsource is another great example of how to integrate a thirdparty into the GitHub PR process: https://discuss.deepsource.com/t/improved-github-pull-request-integration/442

We'd like the ability to upload code coverage reports to Sonarqube in a step. We use typescript and can generate the report.xml but, we'd like a step that will allow us to upload this to Sonarqube.