On 21st December at 1:10 PM PST, we received a report from 2 of our customers about issues with their pipeline executions in our Prod-2 cluster for their CI pipelines.
A firehydrant was triggered after some time for the same.
Time | Event |
---|---|
1:24 PM | Confirmed no pipeline-service deployment was done and issue is observed only for few Prod2 and Prod1 CI customers. |
1:28 PM | Verified CI Automation was running fine but we were able to reproduce the issue |
2:04 PM | Prod2 CI service was rolled back to previous version, and confirmed with customers the issue is mitigated |
We rolled back the CI build in Prod2 cluster to unblock the customers.
Resolution time*: 1hour 46 minutes
Resolution time = time reported to time restored, either through Rollback or HF
There was a change in a common deserialiser -
where we added handling that if the value is a string of Json list example → "[1,2]"
is given then it will be converted to List of String irrespective the field expecting it to be type String, thus its throwing Exception during execution.
This was mainly observed for a customer having this value set in their envVariables in RunStep in the CI stage.