Merge queue functionality
Auto-rebase and sequence merges to a branch to allow for more stable/accurate tests.
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
Github Checks on Server
As of now, Github checks are not available for servers (CircleCI Enterprise), would request to bring this feature in future updates. Thanks CCI-I-1343
Filter pipelines by workflow name
In the "All Pipelines" dashboard page, it isn't currently possible to filter by workflow. We have a project that runs several different workflows in its pipeline, some of which are run infrequently on a cron schedule. As it stands, it's difficult to find the latest run of one of these scheduled workflows as it gets buried under all the other workflows taking place. We have to paginate through many pages of pipelines to eventually find it. This would be solved if we could filter pipelines by workflow name in the UI.
Make it easier to see which user created a Context
When a user creates a Context (especially if it contains the 'All Members' group), it should be easier to see who created this based on GitHub username and to be able to set up alerting on this.
Customize maximum build runtime to be more than 5 hours in 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
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?