Hi, this is Kohsuke Kawaguchi - the creator of Jenkins! I have left Jenkins for a bit, but I am still very passionate about developer productivity.
At CloudBees, I'm looking to apply AI to CI triage process - helping teams resolve failures faster and with less manual effort. We have been talking to several DevOps teams managing CI/CD pipelines and a pattern of pain seems to be emerging - ‘When a pipeline fails, it’s always the same story - we get the same questions over and over, and no one seems to know who’s actually responsible or how to fix it.’ Do any of these sound familiar when you think about triaging failures? - *There’s unclear ownership*: When pipeline issues arise and the cause is unclear, often they get dumped on the CI team, even when they may not be responsible! This creates a bottleneck and slows down resolution. - *Same questions, again & again*: DevOps engineers keep getting asked to look into CI failures that may have already been resolved several times - even though they are communicated & documented. It’s frustrating and wastes time. - *Ignored documentation & playbooks: *Several guides have been written, but other teams often find them too complex or don’t bother looking before escalating issues to the CI team. If these challenges resonate with you, then I want to talk to you so that we can solve your challenge better. Just fill out this form <https://forms.gle/N9QWCZpkJS6V5V229> and we will reach out to you. This is not a sales call. As we explore this landscape, your experience could directly influence what we build! Excited to hear from you 👋 -- Kohsuke Kawaguchi -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-users/CAN4CQ4ycigCwBhQhAg%2BwOcxNfDmjp5Mo8RAXpdhmWV6XQjkRVQ%40mail.gmail.com.
