The queue orb was previously used to avoid multiple pipeline race conditions and conflicts. Serial-job provides native support for the functionality provided by the queue orb. Overtime we will expand the use cases we support to cover additional challenges like multi-job or workflows. The first release is serial-group for individual jobs.
The queue orb was previously used to avoid multiple pipeline race conditions and conflicts. Serial-job provides native support for the functionality provided by the queue orb. Overtime we will expand the use cases we support to cover additional challenges like multi-job or workflows. The first release is serial-group for individual jobs.
This allows an individual job to be serialized across the organization, project or branch based on the parameters you provide. Serialization will ensure the jobs are executed in the order in which the pipelines are started via commit, api or other triggering method.
To learn more about your options see the documentation.
This is currently a manual process, which requires making changes in GitHub.
To avoid users having to refer to the docs for instructions, we added a “delete” icon next to the OAuth trigger (Project Settings > Triggers), which opens a modal containing instructions for how to disable the OAuth trigger manually.
A bug that was causing the loading spinner to spin infinitely when no additional pipelines were available after clicking the ‘See more’ button on the pipelines page has been fixed.
Users of CircleCI’s GitHub App integration would occasionally not be able to see a list of repositories to choose from when creating a new project. This bug has been fixed.
CircleCI periodically updates the keys used to sign OIDC tokens in alignment with security best practices. No customer action is required to continue using OIDC with previously configured services.
It is now possible to configure pipelines to be triggered only on pushes to non-draft Pull Requests.
Who Can Use This?
This functionality is available to all customers that use GitHub.
If your organization is currently integrated with GitHub only through OAuth, an admin must take the one-time action of installing the CircleCI GitHub App to enable this functionality.
Getting Started
Go to your project’s Project Settings > Pipelines, and ensure you have a “GitHub App” pipeline defined
Go to Project Settings > Triggers, and define a GitHub App trigger
In the “run on” menu, select “Pushes to open non-draft PRs”
Trigger your GitHub App pipeline by pushing to a non-draft PR
When creating a new pipeline (Project Settings > Pipeline), the field “Config File Path” now contains a default value (circleci/config.yml) that the user can edit, instead of a placeholder.
The “Add Pipeline” form (Project Settings > Pipelines) now includes links to a Google Form that helps customers troubleshoot common issues related to GitHub App installation and permissions.
The “Add Pipeline” form (Project Settings > Pipelines) now includes links to a Google Form that helps customers troubleshoot common issues related to GitHub App installation and permissions.
The “build forked pull request” setting in Project Settings > Advanced has been updated to clarify that it only applies to OAuth pipelines, not GitHub App pipelines.
The “build forked pull request” setting in Project Settings > Advanced has been updated to clarify that it only applies to OAuth pipelines, not GitHub App pipelines.
We have introduced a new pipeline iteration experience for new users in organizations integrated with GitHub App. This assisted experience is available after setting up new projects or through the Workflow and Jobs pages, where users can chat and receive real-time support for their pipelines.
The “only build pull request” setting in Project Settings > Advanced has been updated to clarify that it only applies to OAuth pipelines, not GitHub App pipelines.
The “only build pull request” setting in Project Settings > Advanced has been updated to clarify that it only applies to OAuth pipelines, not GitHub App pipelines.
Organization admins can now enable the in-app Error Summarizer via a modal on the same page, eliminating the need to navigate to Organization Settings. If a user is not an organization admin, the modal will inform them that they need to contact their organization admin to enable the setting in Organization Settings > Advanced.
Set resource requirements (requests and limits) on the orchestrator init container (https://github.com/circleci/runner-init). This change helps ensure the Pod is schedulable when resource quotas are applied.
Added options to configure the image name for the orchestrator container. This can be used for hosting the image in a private registry or within an air-gapped environment on CircleCI server. Note this change requires version v101.1.3 of the Helm chart.
The host OS that Docker jobs run on has been upgraded to support new features and ongoing security and bug patches. This upgrade will roll out to all customers over the next few weeks. Affected customers have been notified via email. Learn more about this change in Discuss: Docker Executor Infrastructure Upgrade.
CVE patches for web-ui-insights and webhook-service
Bug fixes
Fixed a vulnerability where artifacts relating to public repositories could be accessed without authentication
Fixed a bug where workflows in a terminal state with blocked jobs were incorrectly cancelled when a new workflow was triggered with redundant pipeline cancellation enabled.
Pipelines can now be triggered on a wider range of GitHub events, including pull request events, giving you more control over when your builds run.
The full range of trigger options available are:
All pushes
Tag pushes
Pushes to default branch
PR opened or pushed to, default branch pushes, tag pushes
PR opened
PR merged
PR marked ready for review
“run-ci” label added to PR
This allows teams to trigger builds only when needed, reducing unnecessary spending.
Customizing Triggers for Different Pipelines
This functionality can be leveraged to configure different pipelines in the same project to run on specific events. For example:
A “build-test-deploy” pipeline (config.yml) runs on “all pushes”
A “benchmark” pipeline (benchmark.yml) runs on “PR opened”
A “cleanup” pipeline (teardown-env.yml) runs on “PR merged”
We plan to expand the available events and conditions to choose from. Let us know what additional triggers your team needs by filling out this form, so we can prioritize adding them next.
Who Can Use This?
This functionality is available to all customers that use GitHub.
If your organization is currently integrated with GitHub only through OAuth, an admin must take the one-time action of installing the CircleCI GitHub App to enable this functionality.
Getting Started
Go to your project’s Project Settings > Pipelines, and ensure you have a “GitHub App” pipeline defined
Go to Project Settings > Triggers, and define a GitHub App trigger
In the “run on” menu, select your preferred event
Trigger your GitHub App pipeline by performing the selected action on GitHub.
Github App organizations can now take advantage of Github Checks. Customers often use GitHub checks to verify and validate that specific jobs or workflows have been completed before taking action like merging code.
Github App organizations can now take advantage of Github Checks. Customers often use GitHub checks to verify and validate that specific jobs or workflows have been completed before taking action like merging code.
GitHub App support within CircleCI allows customers to have multiple “pipelines” defined within a single project. Github doesn’t share this same capability or concept when it comes to GitHub Checks. GitHub checks the workflow name is the key and if workflows in two different pipelines share the same name they would overwrite each other’s status. CircleCI had to introduce a way to ensure that status updates were unique and identifiable by workflow across pipelines. Because of this, we introduced a pipeline definition ID in the workflow name for GitHub Checks for GitHub App integrations. These are non-mutable and allow the organization to build GitHub Check rules that are name-based.
NOTE: Some customers have both Github App and GitHub OAuth enabled on their application and may have both Github Status and GitHub checks enabled. Those customers will see GitHub Check updates for the GitHub App integration.
A new Windows Server 2022 CUDA image has been released. Learn more about the available tags and image contents in our docs. Join the conversation in Discuss.
Users tracking releases with CircleCI can now see Argo Rollouts background validation and inline analysis results included in the details for an individual release. This enhanced integration between CircleCI’s Release Agent and Argo Rollouts allows for easier investigation into failed deployments.
Fixed the volume for GOAT and task-agent binaries to be read-write. It was unnecessarily read-only and caused issues with the circleci-cli orb, which overwrites the circleci symlink with the CLI.
Version 3.1.0 introduces substantial performance and reliability improvements to container runner. These updates are designed to enhance the overall efficiency and stability of operations at scale. For more background and technical details on these changes, you can visit our Runner Init repository and documentation.
To upgrade, ensure that the Helm chart is at least version v101.1.2. The chart is pinned to the major version tag of the runner, enabling automatic upgrades on redeployment. If you wish to remain on the existing architecture (3.0.x), you can do so by setting the tag to kubernetes-3.0. This version will continue to receive only critical bug fixes and security patches. You can check the configuration details in the Helm chart repository.
The provider manager’s connection pool size is now configurable under domain_service.providersMangerMaxPoolSize. The default is set to 10.
Bug Fixes
Fixed a bug where OIDC tokens failed to be injected into a job, causing the environment variables $CIRCLE_OIDC_TOKEN and $CIRCLE_OIDC_TOKEN_V2 being missing.
Resolved a bug where machine_provisioner.providers.gcp.network_tags were incorrectly assigned as labels on VM instances instead of as tags.
Fixed a bug that prevented remote Docker from working in air-gapped environments. An external reaper container repository has been exposed for this and can be configured via docker_provisioner.reaperContainerRepository.
Fixed an issue with IRSA roles on AWS GovCloud, which uses the S3 partition aws-us-gov instead of the default aws. This is now exposed in the values file under s3.partition.
New Known Issues
Setting a custom reaper container repository (via docker_provisioner.reaperContainerRepository) is currently incompatible with Windows VMs and prevents Windows jobs from running.
The “Insights Snapshot Badge” functionality on CircleCI is deprecated and will stop working on a to-be-announced date. We will update our community forum and send communication to impacted users when we have determined an EOL date.
The provider manager’s connection pool size is now configurable under domain_service.providersMangerMaxPoolSize. The default is set to 10.
Bug fixes
Resolved a bug where machine_provisioner.providers.gcp.network_tags were incorrectly assigned as labels on VM instances instead of as tags.
Fixed a bug that prevented remote Docker from working in air-gapped environments. An external reaper container repository has been exposed for this and can be configured via docker_provisioner.reaperContainerRepository.
Fixed an issue with IRSA roles on AWS GovCloud, which uses the S3 partition aws-us-gov instead of the default aws. This is now exposed in the values file under s3.partition.
New known issues
Setting a custom reaper container repository (via docker_provisioner.reaperContainerRepository) is currently incompatible with Windows VMs and prevents Windows jobs from running.
The provider manager’s connection pool size is now configurable under domain_service.providersMangerMaxPoolSize. The default is set to 10.
Bug fixes
Network tags in GCP now function as expected.
Fixed a bug that prevented remote Docker from working in air-gapped environments. An external reaper container repository has been exposed for this and can be configured via docker_provisioner.reaperContainerRepository.
Improved handling of AWS errors by machine-provisioner
