James Brown's blog

CloudBees Won a Customer Impact Award!

CloudBees Won a Customer Impact Award! So What Does “Strongest Impact at a Startup” Mean? The CloudBees award-winning team, on stage at Totango’s Customer Success Summit, March 5-6, San Francisco. Left to right: Angel Viloria, James Brown, Matt Carrico, Summer Weisberg, Nathan Mapp. Market potential and product viability aside, the people at a startup are your singular...

Knowledge as Code: Leveraging your Knowledge

In Part II of the Knowledge as Code journey I discussed how we pushed our content creation into Github. In this finale we will talk about how we’re using it to Continuously Deliver our knowledge. At CloudBees we vehemently refuse to dogfood rather (perhaps more presumptuously) like to drink our own champagne ;-) Enter CloudBees Jenkins Platform and Workflow . <Insert shameless...

Knowledge as Code: Making Creating Knowledge Easy

In Part I I introduced you to Knowledge as Code (and KCS). In Part II I’ll talk about some of the practical hurdles every adopter of KCS will run into and how that shaped our Knowledge as Code journey. The largest hurdle in implementing KCS is a practical one, adoption. How do you get your folks already killing themselves to react to your case volume to create content? We know...

Knowledge as Code: Sourcing your Knowledge

If you’re charged with the stewardship of your customers from an engagement perspective you’ve likely come across Knowledge-Centered Support ( KCS ). The practices KCS espouse aren’t necessarily revolutionary even if they can drive outcomes with as large an impact. The assertion of the Consortium for Service Innovation is that KCS isn’t an outcome, but how you solve problems. KCS...

Jenkins Remote CLI Vulnerability

SECURITY 218 CloudBees Product Security has been made aware of a remote code execution vulnerability mountable by anonymous attacker who have access to Jenkins over HTTP or its TCP port. Impact The Jenkins CLI is currently impacted by this issue. An unprivileged anonymous user could use this flaw to remotely execute code. Anyone with a front facing Jenkins instance (accessible...