Feature Requests

Description: Customers using the CircleCI OTel integration have access to spans for pipelines, workflows, jobs, tasks, and steps — but CPU and memory utilization data is not currently emitted at the task/executor level. Without this, customers cannot build custom alerting to detect over- or under-provisioned executors, which is a key use case for teams looking to optimize resource usage and control compute costs. Proposed solution: Emit CPU and memory utilization as span attributes at the task/executor level. Suggested attribute names aligned with OTel semantic conventions: process.cpu.utilization system.memory.usage / system.memory.utilization Impact: Enables executor right-sizing without requiring third-party agents or parallel jobs Supports custom alerting on resource anomalies directly from pipeline telemetry Strengthens CircleCI's OTel integration

I have a requirement to trigger a pipeline using CircleCI's v2 API. It is not currently available on the Gitlab integration and the endpoint throws Http status code 500.

Originally asked here: https://discuss.circleci.com/t/auto-cancel-builds-on-default-branch/5536 We would like auto-cancel to apply to the default branch, specifically because we have a deploy action associated with it. The deploy is slow and multiple builds are often racing with each other and we occasionally get an older build that finishes after a newer one, leaving us with older code deployed. (This is only for a staging environment deploy in our case though.) CCI-I-214

https://circleci.com/docs/2.0/artifacts/#artifacts-overview Currently, store_artifacts has two keys: path and destination. path is a path to the file or directory to be uploaded as artifacts. destination (Optional) is a prefix added to the artifact paths in the artifacts API. The directory of the file specified in path is used as the default.Adding the when attribute to a job step allows you to override this default behavior, and selectively run or skip steps depending on the status of the job. - run: name: Upload Failed Tests command: curl --data fail_tests.log http://example.com/error_logs when: on_fail Currently the when attribute is not available to storing artifacts and saving test results. This would allow for greater control. CCI-I-573

Please provide a resource class with an A100 GPU model.

CircleCI's lack of support for tags is really frustrating. This has frustrated me for a long time but today I've realised that there is no way to trigger a tagged build AND include pipeline params like you can for a branch. WHY?!? Please add support for this. Honestly, there's been some internal discussion about moving away from CircleCI and moving to GitHub Actions which I've always been opposed to but if we can't do simple things like trigger a pipeline with a parameter I think we're going to have to make the move. :-( And yes, I am aware that this can be achieved via an API call. In some ways this make it worse as your platform clearly supports the feature you just have not bothered to add it to the UI!

SARIF: https://sarifweb.azurewebsites.net/ Similar to how you expose test results in the UI/API, it would be great to support more generalized static analysis results. SARIF is a common format that can be used across many languages and tools Github supports SARIF format: https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github

Would be nice to be able to trigger certain builds or jobs by commenting on a pull request. CCI-I-1213

For our workflow, there are other branches in addition to the default branch that we would like to disable auto-cancel redundant builds for. CCI-I-1584

The workflow-completed and job-completed webhook event types only report information following a terminal state. Users wanting to track duration live (sub-entities like started_at, created_at and triggered_at) are unable to do so, and must wait until their workflow or job finishes. Would it be possible to allow limited sub-entities (listed above) for a new workflow-triggered event type?