Currently, our deployment logs for certain steps are larger then 2mb causing the drone job to not be marked as 'completed' when the step itself has. Therefore the drone pipeline for this job, remains in a continuos running state and never ends.

We can implement various work around, but it would be beneficial to have log size limits to not be hard coded and be soft coded environmental value we can set.