Uploaded August 2023 | Updated September 2026, 1 hour ago
ActionIQ adopted Jenkins as our CI/CD system and as a general automation solution here at ActionIQ because of its maturity, and because it has a massive market share in the CI/CD ecosystem. With a large community, extensive plugin library, and a long-maintained core codebase, we thought Jenkins was a reasonable choice.
During this talk, ActionIQ covered a handful of the sharp edges and thorns built into Jenkins, as well as some of the poor decisions they made while implementing Jenkins at ActionIQ. Hopefully the talk saved some other startups the pain they felt while developing their CI/CD system.
ActionIQ adopted Jenkins as our CI/CD system and as a general automation solution here at ActionIQ because of its maturity, and because it has a massive market share in the CI/CD ecosystem. With a large community, extensive plugin library, and a long-maintained core codebase, we thought Jenkins was a reasonable choice.
During this talk, ActionIQ covered a handful of the sharp edges and thorns built into Jenkins, as well as some of the poor decisions they made while implementing Jenkins at ActionIQ. Hopefully the talk saved some other startups the pain they felt while developing their CI/CD system.
