Server

Currently, as the doc mentioned, the job maximum runtime is 5 hours, and no option to change it. https://circleci.com/docs/2.0/configuration-reference/#jobs > Jobs have a maximum runtime of 5 hours.Server customers, especially static install, they don't need to care about the price of the time of running instances. And some machine learning builds need more than 5 hours. CCI-I-1436

I should be able to specify a cluster of nomad builders to run my jobs on. As a Server admin I should also be able to limit what repos can build on dedicated nomad builder fleets. CCI-I-799

Customers would like the ability to view and restrict how build resources are being used on a project level

Currently, GitHub Checks is only supported for CircleCI Cloud. We would like this feature to be available for CIrcleCI server with Enterprise git. See https://circleci.com/docs/enable-checks/#introduction

Currently CircleCI server does not support scheduled pipelines. This feature request is to have this feature available on CircleCI server.

This feature request is to introduce a UI similar to our developer hub on cloud for users on server to see which orbs have been imported by their CircleCI Server Admins. In cloud, users can navigate to the developer hub to see all available orbs. > https://circleci.com/developer/orbs In Server, admins can import their orbs which are not visible to the users who are not admins. This leaves non-admins users unable to see which orbs have been imported into their enterprise environment.

Currently, the Release Agent and Deployment Management capabilities (such as deploy markers, rollout visibility, and release tracking) are only available on CircleCI Cloud. Customers running CircleCI Server would benefit from similar functionality to track, visualize, and manage deployments across their environments directly from the CircleCI UI. Adding this support to Server would bring feature parity with Cloud and help on-prem users achieve the same end-to-end release visibility and governance that Cloud users enjoy.

Along with metrics, it would be good to have a way to configure OTLP traces so that teams can verify API calls, etc.

Overview We're requesting a comprehensive Licensing Insights Dashboard to provide detailed analytics on user activity, track deactivation reasons, and allow permanent exceptions for critical users. Key Requirements: Dashboard Visualization Centralized overview of CircleCI licensing usage Visual charts and graphs showing active/inactive user trends Customizable time period selection User Activity Metrics: Detailed analytics on builds triggered and pipelines executed Usage metrics with filtering by timeframe (daily/weekly/monthly) Activity threshold indicators User Status Tracking: Complete user listing with current status (active/inactive) Detailed deactivation reasons with timestamps Admin accountability for deactivation actions Historical status change logs for auditing Critical User Protection: Ability to designate users as "critical" to prevent automatic deactivation Management interface for critical user list maintenance Confirmation prompts and notifications when critical users are modified Reporting Capabilities: Exportable reports on licensing usage and status changes Real-time data integration with existing CircleCI APIs Scheduled report delivery options Business Objectives: Increase transparency into license utilization Optimize resource allocation by identifying inactive users Maintain security compliance through detailed audit trails Prevent workflow disruptions by protecting essential users This feature will significantly enhance our license management capabilities while ensuring business-critical operations remain uninterrupted.

Our current AWS security group design uses multiple shared security groups that grant different access. Instead of reusing these groups, we have to create a dedicated group for VMs launched by Circle because it only allows a single security group in the configuration. It would be helpful to support multiple security group IDs, all of which are attached to launched VMs. CCI-I-1612