What Jenkins is good for, is ensuring a consistent environment with a single purpose. On the contrast, I dislike GitHub, because engineers are repurposing it for every single component separately, so we end up with 20+ workflows which isnt anywhere near maintainable. With the hurdle of Jenkins declarative pipeline coding in the way, at least they make sure, that whatever they add works in the overall context of ci/cd.
But yeah, I understand the docker context issue, that’s why I don’t use that feature explicitly.
What Jenkins is good for, is ensuring a consistent environment with a single purpose. On the contrast, I dislike GitHub, because engineers are repurposing it for every single component separately, so we end up with 20+ workflows which isnt anywhere near maintainable. With the hurdle of Jenkins declarative pipeline coding in the way, at least they make sure, that whatever they add works in the overall context of ci/cd. But yeah, I understand the docker context issue, that’s why I don’t use that feature explicitly.