Changelog

Note: If you are running CircleCI Server, you will need version 4.4.3 of server to take advantage of these runner features.

Keep reading

Runner Release

• Fix bug causing the kube-api server to sometimes prematurely terminate task pods for containerized jobs.
• Improve Task Lifecycle step with dynamic Kubernetes pod lifecycle status for containerized jobs. Providing more detailed information on each step in the lifeycle, making it easier to debug issues if they arise.

Changes

• Fixed a bug where the Task lifecycle and service container steps appear to run indefinitely, even after the task has already completed.

• Log duration for downloads of a task-agent binary initiated by the runner agent are output to local downloads. This should help with troubleshooting issues when customers are experiencing problems downloading agents.
• Fix bug where failed task Pods weren’t removed on task cleanup and had to wait for garbage collection, wasting customers’ cluster resources.
• Additional security patches.

Critical security fix

Keep reading

• Improved retries of select errors on startup of a container task
• The task-agent binaries and pidfile are now installed at more conventional locations for both machine and container runner
• GA release of machine runner 3.0

• Improved the retry logic on task pod startup to prevent errors.
• Release of the Linux machine runner 3.0 preview. For more information see, Installing Machine Runner 3.0 on Linux.

• Reduce claiming interval from 10 seconds to 5 seconds
• Improve robustness when starting tasks on newly created nodes
• Default to a non-root user in the container runner Docker image