Allow VMs to launch in multiple subnets
Depending on customer networking configuration and demand for VM executors, it can be challenging to allocate a single subnet that is large enough to meet demand and allow room for expansion. It would be helpful if Circle accepted multiple subnets when launching VMs, as it's often easier to add a second non-contiguous subnet than create a new large one and migrate all usage. While subnets could ideally be in multiple availability zones, I realize this makes cache EBS volume management more challenging. Requiring that all subnets are in the same AZ is a reasonable restriction for an initial version of this feature.
Encrypted EBS Volumes for vm-service
Please provide option to have encrypted EBS data volumes for vm-service
Server should show users its version number
Whenever I submit a support request for CircleCI server, the form asks me for the version number, and I never know. To get the version, I have to ask our IT people, who administer it and upgraded it. Is there any reason to hide the version number from regular users? Shouldn't you just make it available to all users in some easy to find spot on the UI?
Restrict Personal repos
Currently, if we integrate a GitHub Org with CircleCI. It allows users of that Org to trigger build for repos in that org as well as repos in their personal account. There should be option to restrict build only to the repos in the Organization.
AWS ECR authentication using Nomad builder IAM instance profile
When using CCI Server, we have more freedom regarding Nomad builders, so we give the builder instances permissions to download any and all of our ECR images. What we would like is for the Docker executor the freedom to use those ECR images without any credentials passed either via project environment variables or contexts. However currently the CircleCI configuration is preventing us from doing that as it always requires an aws_access_key_id and aws_secret_access_key Ex. docker: - image: our_ecr_image:latest aws_auth: aws_access_key_id: AWS_ACCESS_KEY_ID aws_secret_access_key: AWS_SECRET_ACCESS_KEY Can we get a setting which will use the Nomad builder instance profile instead? docker: - image: our_ecr_image:latest aws_auth: use_instance_profile: true The AWS SDK uses any and all possible credential sources, so in theory if no credentials are passed it should use the Instance Metadata to authorize unless you intentionally block that. Thanks Igor Serko, Lyst Ltd
CircleCI runner for Server (on baremetal)
Want to run builds on custom hardware (from Raspberry Pi to self-manufactured hardware running on aarch64 + Linux-based mobile OSes), even on CircleCI Server Static (baremetal = non-AWS/GCP environment) CCI-I-1656
Allow frontend customizations to menu, announcement banner in Server
Add the ability to add custom items to the Support menu (e.g. internal company support page link), and banner notifications after a user has signed in (e.g. maintenance window announcements) CCI-I-1367
Build Metrics for CircleCI Server
They are looking for detailed build metrics. They want to better understand performance issues so they can identify patterns so that they better maintain stability over peak. These build metrics include frequency of their builds, success (pass/fail), which repos are building most frequently, build times, why did builds fail. They need to know if their build times are getting better to see if their success is getting better. CCI-I-820