A new version of the git clone plugin was deployed to enable enhanced analytic events within CI pipelines. This update included a change to the plugin’s entrypoint. Customers who had pinned older versions of the clone plugin were still using images that relied on the previous entrypoint, leading to failures in the clone codebase step for Kubernetes-based CI pipelines.
Additional Context:
While the primary impact was on customers using pinned older plugin versions, some executions using the latest plugin version were also affected during rolling deployment and rollback. In these cases, different steps of the same execution were routed to CI-Service pods running different versions, causing inconsistent behavior.
The issue occurred due to a version mismatch between the updated CI system and older, pinned versions of the git clone plugin.
The updated CI-Service expected the new entrypoint introduced in the latest plugin. However, older pinned plugin images still referenced the previous entrypoint, which caused the following error during execution:
fork/exec /usr/local/bin/drone-git: no such file or directory
Since pinned plugin versions differ across customers, only a subset of users was initially affected. Once the plugin version alignment issue was identified, affected pipelines were restored by adjusting CI service configurations to ensure compatibility.
Additional Context:
During rolling deployment and rollback, some executions—regardless of plugin version—were split across CI-Service pods running different versions. For these executions, the init step ran on one pod version while the git clone step ran on another, leading to failures even for customers using the latest plugin.