Wednesday, February 18, 2015

CloudBees Heads To Las Vegas For IBM Interconnect

Cloud, Mobile, DevOps and Security collide next week at the IBM Interconnect show in Las Vegas. This is proving to be the one of the biggest conferences of the year as IBM incorporates 3 of their most dynamic events. 
So who's going? We know CloudBees is!
Don't miss Kohsuke Kawaguchi, CTO of CloudBees and Jenkins founder, presenting “Automating Continuous Delivery with Jenkins and IBM UrbanCode Deploy" on Monday 2/23 at 2PM in Islander A Ballroom at Mandalay Bay. 
This presentation will look at how new features in Jenkins, such as traceability and Workflow, are helping enterprises orchestrate their entire software delivery process. Attend to hear how Jenkins works together with IBM UrbanCode Deploy to deliver higher quality software in a repeatable fashion.
What are you trying to accomplish this year? Faster time to market? Reduced costs of IT infrastructure? More automated processes? Make sure you pick up a copy of the Orbitz case study while visiting Booth #500 to learn how they were able to cut release cycles by more than 75%.
Want to see CloudBees Jenkins Enterprise in action? Stop by Booth #500 to interact with a Jenkins expert to get your very own demo. Don't forget to ask about Workflow!
Think you are a Jenkins Master or maybe just are striving to be one? Then you don't want to miss out on your own Jenkins Master t-shirt. You will be the envy of the office when you return home sporting these threads!

Christina Pappas
Marketing Funnel Manager

Follow her on Twitter

Thursday, February 12, 2015

Celebrate Jenkins on February 26

Big news! The Jenkins project has officially exceeded 100K active users mark sometime in January. As of January 31, we were at 102,992. Congratulations! If you use Jenkins, YOU are one of the 100K active Jenkins users.

In a couple recent project meetings, we have all decided that February 26 will be Jenkins Celebration Day.

Let's make some noise. Here is what we are doing starting NOW:
  • Write a blog post about anything Jenkins-related. Publish your blog post and Tweet out a link to it. Please include the official Jenkins Celebration Day hashtag #Jenkins100K in your post.
  • On February 26, there will be a raffle with four names picked at random. The grand prize winner will receive a 3D Jenkins Butler model. (Watch one being created here - special thanks to Jeremy Kissell!) Five others will get their pick of Jenkins swag (up to $20) from the Jenkins online store.


We want YOU to be involved in the celebration. This blog post on the website is the central place to go for all things related to the big day.
  • Recording – The Jenkins Governance Board: Dean, Tyler, Andrew and I will be recording some thoughts about the Jenkins project. On February 26, we will share that recording with you here.
  • Twitter/Facebook/social media – For those of us on social media that want to proudly celebrate our community, there is a special badge that you can use as your profile image on Twitter or any of the other social media forums. Feel free to use the badge for as long as you want – but let’s get as many of us using it as possible between now and February 27. The image is also linked from the Jenkins community blog post.
  • Social Media Images 
    • CloudBees is donating a series of images that we can all push out on whatever social media platforms we use.
    • Push out your favorite(s) on Twitter, Facebook, G+...
  • Certificate (available here soon) – You will be able to view the official “I am part of the Jenkins 100K” certificate. Print it out and proudly display it on the wall of your cube or office.
  • Visibility – The Jenkins Community will be issuing a press release on February 26 announcing our milestone news.
  • Sign the “card” – Consider this blog post a Congratulations card to the entire community. Share your thoughts there in a comment on anything Jenkins-related that you want.
This milestone is BIG for the Community. You should be proud to be a part of it. Let’s make some noise for Jenkins!


Kohsuke Kawaguchi is Founder, Jenkins CI, and Chief Technology Officer, CloudBees. You can follow him on Twitter @KohsukeKawa

Thursday, January 29, 2015

Call for Papers- JUC 2015

The Butler is looking for submissions for his Jenkins User Conference 2015. This is your chance to inspire, educate and share with the community your stories of how you've used Jenkins to continuously build that awesome project or how you developed that popular plugin for the community.
If you're hooked, here are some suggestions to get your creative juices flowing:
  • How does scale Jenkins within the enterprise?
  • How does Jenkins orchestrate continuous delivery?
  • How does Jenkins assist you in plug-in development?
  • What are the Jenkins techniques you use to solve testing/building problems in specific application areas such as mobile, enterprise/web/cloud and UI testing
  • Do you have war stories from a problem you encountered, the Jenkins solution you administered to solve it and the results you got?
  • What are Jenkins best practices, tips and tricks?
  • Are you or your company currently using Jenkins in the cloud? Tell us your story!
  • The Butler beyond Java (Jenkins with PHP, Ruby, etc.)

For the first time EVER...the Jenkins User Conference is moving from a 1-day conference to a 2-day conference for San Francisco and London - that means an additional 18 innovative sessions to attend!

Would you like to sponsor a JUC near you? There are various event sponsorship opportunities available: Gold to Silver packages, exhibitor packages in our world-class expo hall, sponsor speaking sessions, free conference passes, and numerous branding opportunities. Please contact for inquiries.

We are looking forward to receiving your proposals!

Wednesday, January 28, 2015

Results of Puppet Labs' State of DevOps Survey Solidify Case for Continuous Delivery

Over 9,000 people from over 100 countries participated in the 2014 State of DevOps Report conducted by Puppet Labs, IT Revolution Press and ThoughtWorks. Much like we saw in 2013, there is a common acceleration of DevOps within IT organizations but this latest report dives a bit deeper and illustrates a clear impact that acceleration is having on the enterprise.

A number of findings from 2013 were re-confirmed including the frequency of application deployment and lower failure rates found amongst high-performing organizations. However, I thoroughly enjoyed the additional questions that support the statement that IT is not just a cost center, it's a source of profitability, an opportunity for greater market share and a threat to the competition.

Continuous Integration and Continuous Delivery are both earmarked as best practices that correlate most strongly to high IT performance. You can read the entire report yourself here but here are some findings that stuck out to me:
  • "IT performance and well-know DevOps practices, such as those that enable continuous delivery, are predictive of organizational performance." 
  • "It’s not dev versus ops, it’s dev plus ops. When the outcome of a dev and ops interaction is win-win, IT performance wins."
  • "Companies with high IT performance are twice as likely to exceed their profitability, market share and productivity goals." 
  • "Developers breaking large features into small incremental changes and merging their code daily into trunk are strongly correlated with both IT and organizational performance."
  • "Continuous improvement and learning is what sets successful companies apart, enabling them to innovate, get ahead of the competition — and win."
Want to learn more about Continuous Delivery and DevOps? Download this research paper conducted by EMA for Ten Factors Shaping the Future of Application Delivery. Download it here.

Christina Pappas
Marketing Funnel Manager

Follow her on Twitter

Tuesday, January 27, 2015

CloudBees Raises $23.5m - Because Software is Eating the World

Software and IT used to be a tool (out of many others) that helped businesses be more efficient, reduce cost and sometimes improve sales. In the last decade the situation has radically changed. Software is not a tool that "helps" businesses anymore. Software has become *the* business. Everything companies do, from interacting with prospects, customers, partners, handling their production, creating business differentiation is either highly influenced or fully defined by software. And this is not just some kind of particularism that would only apply to "online companies." This is true of pretty much any company. Think about the automotive industry as an example. Here is an industry that's well grounded in heavy industrial concerns: factory plants, raw material, assembly lines, international shipping, mass recalls, etc. Yet, what increasingly differentiates a car in the eyes of buyers is defined! Auto-pilot features and soon-to-come self-driving cars, software is "eating the world."

This transformation is forcing companies to adapt the way they think about IT processes, how business differentiation gets created and pushed to market. Rather than long 18 to 24-month release cycles where risk is high and value creation sparse, companies are moving towards "Continuous Delivery" (aka CD), where business value is continuously pushed to market, in small iterations and measured to see whether it yields expected results. This not only hugely reduces risk (large projects, time to market, etc.) but makes it possible to react to market changes and competitive moves much faster.

Adopting Continuous Delivery involves many changes within an organization. And ultimately, it implies to have a way to automate the process that starts with value creation (i.e. new software) down to its actual release, going through sophisticated automated build, tests, integrations, staging, validations, etc. The more automated a pipeline gets, the more code-release-measure iterations are possible in a give timeframe and the more value can be pushed to market. Automation is king.

CloudBees is offering the #1 solution on the market to implement enterprise Continuous Delivery at scale, based on the open source Jenkins CI project. With the rapid adoption of Continuous Delivery within organisations, CloudBees went through spectacular growth in 2014. This being just the tip of the CD-iceberg, we decided to gives ourselves the means to to achieve our objectives. Consequently, today we are announcing a US $23.5m capital expansion, led by Lightspeed Venture Partners, including follow-on investment from Matrix Partners, Verizon Ventures and Blue Cloud Ventures.

This investment will make it possible for us to further SCALE-UP and SCALE-OUT.

SCALE-UP as we further invest in our go-to-market to help more and more companies around the globe successfully adopt Continuous Delivery at scale.

SCALE-OUT as we expand the type of use cases and deployment types our solution supports so we can help an even wider range of companies to benefit from Continuous Delivery.

We will be making a lot of announcements in the next weeks and months, so stay tuned.


Sacha Labourey

Wednesday, January 21, 2015

CloudBees in 2015: WE ARE HIRING (Big Time...)

2014 has been a fantastic year for CloudBees. We made some hard strategic decisions and they were exactly the right ones. As a result, we've enjoyed very big growth in 2014 (more to come on that topic) and we have much more in the pipeline for 2015. So what about 2015?

Our motto for 2015 is "SCALE-UP and SCALE-OUT."

SCALE-UP because we are going to accelerate investment in our growth engine (sales and marketing). This will directly translate into hiring in sales (inside, as well as outside roles), marketing (US and EU) as well as support (US and EU). Note that our inside sales hub is in Richmond, VA.

SCALE-OUT because we want to expand to cover more space, more use cases, more depth with Jenkins and Continuous Delivery. Whoever you are (S, M, L or XL), wherever you are (private/public/hybrid cloud, traditional datacenter, etc.), we will satisfy your needs and be #1. That will directly translate into engineering and product management hires. Quite a few of them actually! And the good news is that we are pretty flexible location wise. While we'd rather hire in existing offices (Los Altos (CA), Richmond (VA), Brussels (BE) and Neuchâtel (CH)), we actually have developers in no less than 12 countries today. Those are NOT remote employees: we are, at heart, a distributed company. Distributed is how we operate, how we communicate and how we make decisions. As an example, if you are a top developer, are deadly bored where you are now, feel like you can make a difference on the market and grow a name for yourself, but unfortunately you are not living in the Bay Area, ping us: we are the teleportation machine you need.

We have a few open positions listed on our Career page, but there are more to come so you can either stay tuned and refresh your browser or... not wait and just ping us by sending your résumé with a few words about what would make you excited to work on.



Tuesday, January 20, 2015

Best Practices for Setting up Jenkins Auditing and Compliance

Many Jenkins users look for a recommend a strategy for keeping an audit trail. This article is supposed to be a gap filler until more comprehensive compliance capabilities in CloudBees Jenkins Enterprise/CloudBees Jenkins Operations Center are developed.

There are two open source plugins that enable you to track “WHO did WHAT?” in Jenkins: 
  • Audit Trail Plugin: adds an “Audit Trail” section in your Jenkins main configuration page, where it is possible to define where to save logs on who performed particular operations on Jenkins.

Audit Trail - output fileScreen Shot 2015-01-13 at 09.32.28.png

  • Job Config History Plugin: stores all the changes made to jobs (history), saving the config.xml of each job. For each change, it is possible to see the record of the change, compare the difference between the new and the old version and restore a previous version. It is also possible to keep track of the changes made to the system configuration.

Job Config History - compare differences GUI option

Screen Shot 2015-01-13 at 09.24.30.png

Although the Job Config History plugin looks somewhat more complete, this, differently from the Audit Trail Plugin, does not track any information regarding the job execution and the exit status.

Audit Trail - executions of jobs

For this reason, many users use both The Audit Trail plugin and the Job Config History plugins to track both the changes and the executions of jobs.

Packages Traceability

For artifacts and packages, Jenkins keep track of those using the fingerprint. However, when they go outside Jenkins, there is no way to track them. Lately Jenkins has become more and more a tool for continuous delivery (CD), and integrating with automation tools is essentials. For this reason, CloudBees has partnered with vendors who offer popular tools, like Chef and Puppet, to enhance Jenkins traceability.

Thanks to the Deployment Notification Plugin applicable to Chef and Puppet, it is possible to keep track of the artifact even when it leaves the jenkins environment to be deployed on a remote server. The information maintained by Jenkins for each deployed package are the date/time, the hostname of the remote server, the environment and the deployment path.

Puppet Plugin - traceability

Audit when Using the Workflow Plugin

With the new Workflow plugin, it is possible to configure an entire continuous delivery pipeline in a single job with a simple Groovy-based script, rather than using different jobs and several plugins to orchestrate the execution of the “flow.”

While it is possible to directly insert the Groovy code in the box of the workflow-job ad-hoc configuration page, it is recommended to store the workflow script in a repository and just load it from inside the Groovy box.

Workflow plugin - loading groovy script from repository

In the example above, the workflow script is stored in a local repository, checked out in the building machine, loaded and its functions accessed directly. This guarantees audit and version control since each change made to the script will be committed to the SCM and thus it is possible to keep track of who changed what.

This applies to all Configuration As Code approaches (i.e. DSL plugin, Literate plugin).

Audit when Performing Cluster Operations Using Jenkins Operations Center

With the new (December v1.6) release of Jenkins Operations Center by CloudBees, it is possible to perform management operations to all the client masters in one pass:
  • Restart client masters
  • Backup client masters
  • Run Groovy script on client masters
  • Upgrade Jenkins core on client masters
  • Install new plugins on client masters
  • Enable/disable plugins on client masters
  • Upgrade/downgrade plugin on client masters
Jenkins keeps track of these operations treating them as normal jobs and giving each operation a specific place on the file system where to store execution information and logs.

The same are accessible from the Graphical User Interface (GUI):

Cluster Operations - logs in GUI

If authentication is enabled, information on “WHO did WHAT and WHERE” is visible here.

Although at the moment there is not a unique and satisfying way to implement audit trail, the options presented above, combined together, should give a good coverage to all the activities performed on Jenkins.

Valentina Armenise
Solutions Architect, CloudBees

Follow Valentina on Twitter.