Skip to content

CloudBees' Blog - Continuous Integration in the Cloud
Syndicate content
CloudBees provides an enterprise Continuous Delivery Platform that accelerates the software development, integration and deployment processes. Building on the power of Jenkins CI, CloudBees enables you to adopt continuous delivery incrementally or organization-wide, supporting on-premise, cloud and hybrid environments.
Updated: 1 day 1 hour ago

Webinar Q&A: Facilitating Continuous Delivery Pipelines with Jenkins Workflow

Thu, 03/26/2015 - 17:05


Thank you to everyone who joined us for the webinar with eSynergy--you can view the recording here.

Below are the link found in the slides from the webinar:

Get The Code:https://github.com/harniman/workflow-demos
https://github.com/harniman/spring-petclinic
https://github.com/jenkinsci/workflow-plugin/blob/master/COMPATIBILITY.md

Tutorial:https://github.com/jenkinsci/workflow-plugin/blob/master/TUTORIAL.md

Jenkins Enterprise by CloudBees Workflow-Related Functionality:http://jenkins-enterprise.cloudbees.com/docs/user-guide-docs/workflow.html

Following are answers to the questions we received during the webinar:
________________________________________________________________

Q: Can 'pause for input" can be accepted via api? A: Yes you can POST to a URL to proceed. 
Q: Any support for Android Emulator in workflow? A: No specific support yet that we are aware of. You can use `sh` steps to launch and tear down the emulator. 
Q: Are you developing any plugins/workflows that uses Puppet/Chef? A: Not currently, though of course you can run such commands from shell scripts. There is a plugin that allows tracking of puppet deployments. 
Q: Pending JENKINS-27295 Booleans end up as Strings in the Groovy script. Is there a workaround? A: Currently you would use Boolean.parse or just check MYPARAM == 'true' 
Q: Can the DSL be extended with new commands?, For example to call things specific to plugins and not present in core? Like running an xcode build. A: DSL steps are contributed to by plugins. 
Q: Is there a list of plugins compatible with Workflow? A: See https://github.com/jenkinsci/workflow-plugin/blob/master/COMPATIBILITY.md 
Q: Can the DSL functions be reused across jobs? A: You can `load` a file of Groovy functions you wrote, or commit a Groovy class to a Jenkins-managed Git repository and then import it from as many flows as you like. 
Q: Can we restrict checkpoint to a particular access group who can click ok? A: Not currently; just based on Job/Build permission. 
Q: If we have 10 commits then would all 10 builds pause at Staging using up 10 executors unless someone clicks yes or no? A: It is not using up executors while waiting (unless you are inside `node`). If you want to automatically cancel older prompts, that would be: https://issues.jenkins-ci.org/browse/JENKINS-27039 
Q: Do we have ability to integrate with Jira? Like opening a task in Jira when the tests fail. A: Its possible the JIRA plugin for Jenkins may implement this. Or if there is a way to access JIRA REST API e.g. from curl/wget you could do this today. 
Q: Do you plan to implement a “task list” screen for a user to see all tasks awaiting their input? A: Not at present. This would be a great RFE. 
Q: How to enable own jars in workflow lib? Is that possible. Is that possible to download workflow lib directory from external git (scm) instead of use of "static" content? A: External JARs in classpath (other than plugins) not currently supported. You can load *.groovy sources (interpreted) from the load step, or use a Jenkins-managed Git repo to save common classes/functions. 
Q: How to take standard input/error and error code in shell script to manage step (sh command)? A: See RFE: https://issues.jenkins-ci.org/browse/JENKINS-26133 which also contains workaround idioms. 
Q: Can you propose interfaces for some commands using not only String but also Arrays? I.e. it is not possible to send mail to many recipients or set more than one submitter in input phrase because of String, not String[] interface? A: For the `submitter` option to `input` you can set the name of an external group, for example LDAP group. Then anyone in that group may approve. In general yes steps can and do take arrays/maps where needed. Possible RFE, but I think https://issues.jenkins-ci.org/browse/JENKINS-27134 would be the better approach in general (integrates nicely with authorization strategy configuration for Jenkins overall). 
Q: How can I add RFE request? A: See https://github.com/jenkinsci/workflow-plugin#development 
Q: When I run the code on slave the current dir and context is set to the workplace directory. Is this way to automatically set it to the job-numbered dir or I have to do it manually? A: You can use the dir step to temporarily change directory (like pushd in shell scripts), or you can ask for a specific _locked_ workspace with the `ws` step. 
Q: Is that possible to put some links into workflow report screen and/or workflow step screen (i.e. to show sonar, junit links)? A: JUnit result archiving is supported. For Sonar use the https://wiki.jenkins-ci.org/display/JENKINS/Sidebar-Link+Plugin 
Q: Do you plan to provide ability to group steps in step list (now each sh is separate step) to improve readability? A: See https://issues.jenkins-ci.org/browse/JENKINS-26107 
Q: Does Input send email to alert the responsible party? A: No but you could use the distinct `mail` step to do so. 
Q: Does workflow support multiconfiguration jobs? E.g. can I define configurations within the workflow to run multiple concurrent builds on different platforms and have each of these follow a workflow? A: You can do so, although there is not currently a good way to separate displayed results by configuration. This is something we are thinking about adding. 
Q: How hard is it to implement the github triggers? A: See https://issues.jenkins-ci.org/browse/JENKINS-27136 You would need Java development experience and knowledge of Jenkins plugin APIs. 
Q: Is build promotions a feature of Workflow? What does build promotion look like in Workflow? A: The equivalent of the Promoted Builds plugin for Workflow would be build stages. 
Q: Does workflow provide functionality to capture test result output of test stages and aggregate it similar to the JUnit test result reports in the build stage? A: You can run test result archiving multiple times per build. Currently all such results are simply aggregated. https://issues.jenkins-ci.org/browse/JENKINS-27395 suggests refinements. 
Q: Is there more than the simple proceed / cancel functionality to the transitions between stages? A: https://issues.jenkins-ci.org/browse/JENKINS-27039 suggests other behaviors. 
Q: Are checkpoints and resuming from checkpoints a feature reserved only for Jenkins Enterprise? A: Yes. OSS Workflow does let builds survive simple Jenkins restarts (or slave disconnections and reconnections). 
Q: Can workflow accommodate a deployment model that is asynchronous? We use Puppet to deploy. The handshake is via MQ so the deployment status is not available immediately. A: I would suggest using the waitUntil step to wait for a deployment flag to be set. In the future there might be a step designed to wait for MQ events, or specifically for Puppet, etc. 
Q: Is wait until asynchronous? A: Yes, checks for the condition repeatedly, at increasingly long intervals if still false. 
Q: If we are using a separate tool for Deploying apps, something like IBM uDeploy how does it integrate into the workflow? A: You would use the `sh` (or `bat`) step to run it as an external process. 
Q: If you have jobs which now continue past a Jenkins reboot, how do you restart jobs that are stuck in a poor state or need some attention? A: You can cancel stuck builds if you need to. 
Q: Is it competing with XebiaLabs XLRelease and/or Nolio ReleaseAutomation? Does it have inframent abstractions, does it has easy keystores for passwords needed? A: Not really competing with that kind of product; more complementary. There is integration with the Credentials system in Jenkins. 
Q: Is it possible to just get an enterprise version of this plugin or does it only come as part of a package? A: Currently only as part of the Jenkins Enterprise package. 
Q: Is the entire pipeline defined in a single file? A: Yes. (Or you could define parts in a different file if that made things more readable.)
Q: Is the Job DSL plugin compatible with it? Or are they sort of competing plugins doing the same thing? (though I know Job DSL does not do workflows). A: Job DSL supports Workflow as of a recent release. 
Q: Can the Job DSL plugin generate workflow dsl? A: Yes it can. 
Q: Are there other ways to create workflow jobs? A: Yes, you can use the Jenkins Enterprise Templates capability. 
Q: Is there a way to have a particular user be able to authorize the proceed / cancel upon reaching an input point? A: Yes, `input message: '...', submitter: 'thatUserID'` 
Q: Can Jenkins be used as an artifact repository? Similar to Artifactory. A: You can archive artifacts from the build, though if you have big files, or want to use them from other tools, you are recommended to use Artifactory/Nexus/etc. 
Q: Is there a way to send an email to solicit input from non-technical users? A: There is a `mail` step. 
Q: Is there an option to launch Hadoop workflow jobs? A: If there is a cloud provider for Jenkins generally, it can be used to run Workflow `node` steps on that kind of slave. 
Q: Wanted to see if Jenkins can be a single place to launch jobs for hadoop, may internally Ooozie scheduler be used to launch, any option? A: If there is a shell command you can run to launch the job, then you can do it from Workflow. 
Q: Nowadays we rely on MultiBranch Project Plugin for support our development process based on Pull Request and Code Review. Is it possible to achieve the same result using workflow plugin? A: Not currently but I would like to add such support: https://issues.jenkins-ci.org/browse/JENKINS-26129 
Q: Where is there any source of work flow plugin job configurations aside from the github page? A: A new tag for StackOverflow has been proposed. 
Q: Is there perforce integration? A: The new Perforce plugin (from Perforce) recently added Workflow support. The older one does not have it. 
Q: Would you want to create a groovy script that contains functions that can be reused in other workflow builds, it should be a plugin? A: Need not be a plugin, can just live in your SCM, etc. 
Q: What is the recommended way to have reusable groovy parts shared among different jobs? A: You can use the `load` step, or you can define classes in a Git repo hosted by Jenkins and which are then available for immediate import. Other options may be added in the future. 
Q: Why is 'Surviving Restarts' implemented in a Plugin, and not in Jenkins Core? A: Technical reasons too involved to go into here. Basically Jenkins was not originally designed to make that possible. Jenkins Enterprise provides a plugin to support Long Running Builds. 
Q: Is Console output of parallel executions in any way grouped, or just all lines mixed up? A: With lines intermingled, but prefixed by branch name. 
Q: I have my workflow script in one SCM repo, but want to trigger the job from all changes in a different repo, can I do that? Or would I need to keep workflow script with my sources? A: Yes, you can use as many repositories are you like from a single build, which may or may not be where the Groovy script is kept. 
Q: Will there be an option to download the example workflow source? A: Yes - https://github.com/harniman/workflow-demos 
Q: How is the Jenkins workflow kept in a source code control system of some kind? For example to see what variables were defined as at some point in the past? A: You can load your whole flow script, or just a part of it, from source control.

--Nigel Harnimanwww.cloudbees.com

Nigel is a Senior Solution Architect at CloudBees.


Categories: Companies

Registration is Open for JUC 2015!

Wed, 03/25/2015 - 20:50
Attend THE conference for Jenkins users, by Jenkins users.Register and Learn More. Early Bird rate ends May 1!
 In the past, the Jenkins User Conference has been a one-day event, but this year for the first time ever it will be a two-day event in three cities, providing you with more content and more networking opportunities with more Jenkins users! (Refer to the graph below to see just how many attendees are expected.)

The main focus of JUC is the use of Jenkins for continuous integration (CI) and continuous delivery (CD) as the fundamental best practice for enterprise software delivery. All JUC presenters are experienced Jenkins developers, build managers, QA, DevOps practitioners, IT managers/executives, architects and IT operations who are luminaries within the Jenkins community. They represent the many organizations around the world that are leveraging the use of Jenkins within the software delivery lifecycle.
In 2014, the community saw an 80% increase in attendance
over 2013. This year, 800-1000 attendees are expected in
each city!
We welcome you and other leading Jenkins developers, QA, DevOps and operations personnel to the Jenkins User Conference World Tour. As the organizing sponsor of the Jenkins User Conferences, CloudBees has helped the community grow the Jenkins User Conferences worldwide over the last four years.

In 2015, the World Tour will bring together the full strength of the Jenkins community—now over 100,000 installations strong—and the ever expanding Jenkins partner ecosystem, allowing attendees to learn, explore, network face-to-face and to shape the next evolution of Jenkins development. Kohsuke Kawaguchi will kick off the event with a keynote address and lead us into the two-day conference. Attend a JUC to get the knowledge you need to make your current and future Jenkins projects a success.
Categories: Companies

Webinar Q&A: Continuous Delivery with Puppet Enterprise and CloudBees Jenkins Enterprise

Fri, 03/20/2015 - 17:40
Thank you to everyone who joined us for the webinar. You can view a recording of the webinar here.
Below are the questions we received from the Q&A: 
Q: Should Jenkins-Puppet comm be sync or async mode? How to configure both modes? In async, how does Jenkins know which environment Puppet deployed?A: Mostly sync. The best strategy is to have the Puppet master(s) be Jenkins slave nodes.  Jenkins can issue commands from there such as r10k runs or command and control tasks such as triggering puppet agent runs.
Q: How does puppet integrate with central authentication (such as Active Directory)?A: Puppet Enterprise includes Active Directory support for RBAC and user management.
Q: When you say "delivering infra services" do you include the underlying baremetal infra or just the apps built on top?A: We focus on underlying OS (network, NTP, SSH, auth, etc) and middleware application (Apache, Oracle DB, ISS, etc).  While Puppet Enterprise can be used to deploy application artifacts, we find we’re not commonly used for that purpose.  In the future, we will be releasing application management features in Puppet Enterprise that are intended to resolve common challenges of using Puppet Enterprise for application deployments.
Q: How to test puppet configuration through Continuous Delivery pipeline?A: We highly recommend using Beaker, our acceptance testing framework.
Q: Where can I find info about the Puppet & Jenkins HA?A: You can find more about Jenkins HA here.
Q: We're a windows shop, can you cover Puppet on Windows servers?A: Yes.  We have extensive Windows coverage to manage everything to system reboots, Registry keys, IIS, MSSQL Server, DSC, and more.
Q: Is there any other technology that can replace puppet in future?A: It’s unlikely. While there are many ways to manage application deployments such as containers, for example, there will always be the need for stateful management of the infrastructure including persistent user data stores, networking, and base OS management.
Q: Can we use puppet & CloudBees to manage application specifics settings?A: Yes. Puppet’s built for managing any configuration for any compute systems.  Puppet Enterprise can easily configure a service and ensure it’s running based on assigned roles and site specific data. Our Hiera tool and Node Classifier application make the management of application specific configuration easy and manageable by those unfamiliar with Puppet.A2: Cloud Features.
Q: Is packaging needed for deploying build artifacts to servers?A: It depends on what is being deployed. If its a java application, then yes but if its scripting languages, you may not need packaging.
Q: Functionality on windows seems to be limited (wikipedia). What are the restrictions?A: That’s out of date. Puppet Enterprise’s Windows support has grown tremendously over the past year and a half.  Puppet Labs takes Windows very seriously and have a dedicated team focused on continuously improving the resources we manage on Windows.
Q: How does continuous delivery work?A: Continuous delivery is about proving any change is deployable to production when the business is ready by deploying the change to a production like environment. Automation is relied upon heavily to minimize human error as much as possible. It is an extension of the continuous integration movement. CI is about automating the testing of software builds as often as technologically possible. The next natural step is automate the deployment of the builds to a production like environment to prove the build not only functions in QA, but continues to function when deployed to its end state. This final step requires automation to manage the bits-on-disk configuration, which is where Puppet Enterprise comes in.
Q: How do you use Cloud Bees and Puppet to deploy in place to clustered servers without having downtime or version mismatch concerns?A: We have a tool called MCollective that can be used for running puppet on cluster nodes, but restrict puppet to running on a percentage based subset at a time.
Q: How do you make the best use of these tools in today's DevOps scenario?A: By managing each Puppet module individually, any team within a given organization can contribute to the Puppet code and management. We recommend using Git for version control with each change utilizing the pull request method for peer review prior to inclusion in the main code base. Combined with automated testing with Beaker, teams can have early visibility when a change they introduce breaks other Puppet code. This inclusion and visibility promote a cross team management effort, enforcing a DevOps culture.
Q: How do you integrate Puppet code testing with Beaker and Jenkins?A: Beaker provides the rspec-beaker gem, which means Jenkins can run Beaker tests just like any other set of rspec tests.
Q: I need to know more about Infrastructure as Code and the scripting languages used to make it happen.A: The Puppet DSL is anti-scripting.  It’s not a programming language as much as a configuration language.  Luke Kanies, the author of Puppet and CEO of Puppet Labs, wrote a nice piece on it a few years ago: https://puppetlabs.com/blog/why-puppet-has-its-own-configuration-languageA2: Other than the Puppet DSL, we often utilize Ruby for custom types and providers in Puppet, as well as custom functions to be used in our DSL.  Further, the Beaker testing framework uses ruby with rspec.
Q: Implementing a DevOps culture, how do I make the transformation?A: I highly recommend “The Phoenix Project” book to understand the what, why and how of DevOps.
Q: What is the on-prem model pricing for enterprise Jenkins?A: Pricing is generally based on number of Jenkins Masters and executors. Please contact sales@cloudbees.com for further information.
Q: What are the differences between Open Source and enterprise versions?A: You can learn more about it here
Q: What type of applications can be used to automation the deployment process. e.g. Java, nodejs, etc.?A: Jenkins support deploying any type of applications including Java, C, C++, .NET, NodeJS etc. The automation and deployment process for each of these language varies and Jenkins provides integration with a variety of these through plugins.
Q: What are the start and End points of CI/CD?A: CI usually starts when a developer commits code and involves additional steps such as build, unit test, code coverage and integration tests.A2: CD builds on CI and takes the automation further adding additional stages such as functional testing, performance testing etc… and each of these stages prove certain level of code quality which eventually could be deployed to production (but not always).
Q: Will this be available offline?A: Yes.
Q: I would like to understand Git, Jenkins and Puppet Integration.A: Git is fully supported as an SCM within Jenkins.
Q: Can it be integrated with JOC?A: Jenkins Enterprise is fully integrated with JOC.
Q: How do we configure Puppet to report back to Jenkins?A: Yes. Jenkins typically is responsible for build and promoting code from lower environments to high environments while proving certain level of code quality and puppet could take the artifacts generated and deploy it to different environments.
Q: How does puppet manage tracking of events started though puppet (logs for example)?A: You can find more about it here
Q: How do you achieve deployment and rollback of services using puppet?A: We don’t talk in terms of rollback, but roll forward. There are several types of changes in infrastructure that are not possible to rollback to a previous state.  Instead, it’s important to understand how the process of changing something to a previous state differs than the process of changing something to a new state.
Q: How do you upgrade the version of Jenkins without downtime?A: Using Jenkins Enterprise HA plugin its possible to upgrade with minimum downtime. You can find more information about the HA plugin here
Q: What are the differences between standalone and master/node?A: Using a central Puppet master is important to gain visiblitity into reporting in addition to having central inventory and node management functionality with Node Manager and PuppetDB in Puppet Enterprise.
Q: What will be difference between if I say Jenkins and Enterprise Jenkins?A: Jenkins usually refers to the Jenkins Open source version where as Jenkins Enterprise refers to the CloudBees Jenkins Enterprise.
Q: Can I use Enterprise Jenkins freely without taking any subscription?A: Jenkins Enterprise requires subscription but trials are available up on request.
Q: For CI I am using Jenkins. For CD should I use Enterprise Jenkins?A: Jenkins Open Source has several plugins that can help you achieve CD as well. Jenkins Enterprise provide additional capabilities that let you scale, manage, optimize and secure your implementations.
Q: Can I use opensource Jenkins for CD?A: Yes. There are a lot of plugins, like workflow, in the community that can help in building CD.
Q: Can I use Enterprise Jenkins without Puppet lab?A: Yes, but if you’re doing continuous delivery of infrastructure configuration, you MUST use a configuration management tool.  Puppet is de facto configuration management tool.
Q: Also, how do you integrate Xebia into this setup?A: XebiaLabs has a plugin to Jenkins you can utilize.
Q: Is GIT the default Puppet repo?A: r10k, our code management tool, works with SVN or git, but we find git tends to be used more successfully in customer environments.
Q: How does CloudBees keep up with the frequent Jenkins releases?A: CloudBees Jenkins Enterprise is based on LTS release and support the same for a year.
Q: I can use Enterprise Jenkins freely but for Support do I need to pay?A: Jenkins Enterprise requires a license to use.
Q: How do you integrate rspec testing? Is that more of a component module testing framework?
A: We highly recommend using the Puppet Labs Beaker acceptance testing framework for module testing.

-- Udaypal Aarkoti
www.cloudbees.com

Udaypal is the Solutions Architect Director at CloudBees.

--Carl Caum
www.puppetlabs.com

Carl is the Technical Marketing Manager at Puppet Labs, Inc.
Categories: Companies

Deadlines Fast Approaching: JUC 2015 Call for Papers

Tue, 03/17/2015 - 22:28

Don’t miss your chance to speak at a 2015 Jenkins User Conference! JUC provides a great opportunity for Jenkins experts, beginners, fans and all in between to connect, learn and have fun celebrating what JenkinsCI can do.

Speaking at JUC is the best way to share your Jenkins experiences, stories and expertise. Submit your talk proposal by the below deadlines to be considered.

Please note: To be considered to speak at JUC East Coast US and JUC Europe (London), you must submit your proposal by SUNDAY, MARCH 22, 2015. That is only FIVE days away!

2015 JUC Cities & Call for Papers Deadlines
  • East Coast US: Deadline to Submit - March 22, 2015
  • London: Deadline to Submit - March 22, 2015
  • West Coast US (Bay Area): Deadline to Submit - May 3, 2015
  • Israel: Deadline to Submit - May 15, 2015

If you are not interested in speaking, you can still contribute to the community. Contact alytong13@gmail.com to nominate a Jenkins user you would like to hear from at JUC!

Categories: Companies

Where in the World is Jenkins? - March 2015

Wed, 03/04/2015 - 20:59





CloudBees employees travel the world to a lot of interesting events. This month the Bees are busy. If you are attending any of these March events, be sure to connect with us!
  • FREE Jenkins and Docker Event - Thursday, March 5 
    Learn about workflows in Jenkins Enterprise and how to leverage Docker in your build process. Get more information here.
  • Jenkins Workflow Summit, London - Tuesday, March 10
    If you are a serious Jenkins user who is interested in the area of pipelines, workflows, orchestration and continuous delivery, then this is the event for you. Join Kohsuke Kawaguchi and Jesse Glick at the Royal Exchange, London to learn about the workflow plugin they have been working on. Come ready to participate -- we want to solve your problems and help you achieve your goals with workflow and beyond.
    Reserve your spot here.
  • Webinar: Continuous Delivery with Puppet Enterprise and CloudBees Jenkins Enterprise - Tuesday, March 17
    In this 60-minute webinar, you'll learn how Puppet Enterprise together with CloudBees Jenkins Enterprise can help you achieve continuous delivery of infrastructure services.
    Register for the webinar here.
  • Webinar (presented in Italian): CloudBees e Emerasoft presentano Jenkins Enterprise - Thursday, March 19
    CloudBees Continuous Delivery Platform, fondandosi su Jenkins CI, lo strumento open source più diffuso di Continuous Delivery, fornisce una vasta gamma di soluzioni CD. Utilizzabili in locale o sul cloud, soddisfano le necessità specifiche aziendali di sicurezza, affidabilità e facilità d’uso.
    Register for the webinar here.
  • Serena xChange 15 (Washington, DC) - Sunday, March 22-Wednesday, March 25
    At Serena's global user conference, learn how to achieve CI and CD Across the Enterprise with Jenkins with Andy Pemberton.
    View more information on his talk here and learn more about the conference here.
  • Webinar: Facilitating Continuous Delivery Pipelines with Jenkins Workflow - Wednesday, March 25
    Register and attend to discover how the new workflow engine of Jenkins CI and its Groovy-based DSL with support for complex control structures, human interaction and restartable checkpoints will give another dimension to your continuous delivery pipelines and greatly simplify your life.
    Register for the webinar here.
Categories: Companies

Save the Date for JUC 2015

Wed, 03/04/2015 - 20:25
Big news! Most of the dates and locations for the 2015 Jenkins User Conference (JUC) World Tour have been finalized.

Save the date(s):
  • US East (Washington DC): June 18-19
  • Europe (London): June 23-24
  • Israel: July 16 (ETA)
  • US West (Santa Clara): September 2-3
WAIT! There's more...This year, the JUC agenda will now cover two days! That means two-times as many learning and networking opportunities with other Jenkins users.
CALL FOR PAPERS IS OPEN FOR ALL JUC CONFERENCESWe are looking JUC speakers! The Call for Papers is open and you can apply here. This is a great way for YOU to give back to the Jenkins community. Share your Jenkins knowledge and success. Jenkins speakers add so much value to the overall JUC experience.

As a thank you for speaking, you will receive free admission to the conference! Apply soon, because the Call for Papers deadline for US East and Europe locations expires on March 22, 2015.

If you are not interested in speaking but would still like to contribute something to the community, let us know who you want to hear from! Nominate or refer that perfect speaker you have in mind and we’ll do the rest. Contact alytong13@gmail.com

JUC SPONSORSHIPSLastly, give back to the community by becoming a JUC sponsor. This opportunity is available to any organization – from a vendor selling into the Jenkins ecosystem to a company that has found success through Jenkins. Find out more here. (NOTE: JUC is not a moneymaking venture for the community – so sponsorships do make a difference.)
Categories: Companies

CloudBees Heads To Las Vegas For IBM Interconnect

Wed, 02/18/2015 - 17:11

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!LEARN: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.ACHIEVE RESULTS: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%.INTERACT: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!WIN: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 PappasMarketing Funnel ManagerCloudBees
Follow her on Twitter
Categories: Companies

Celebrate Jenkins on February 26

Thu, 02/12/2015 - 21:23
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.
OTHER WAYS TO CELEBRATEWe want YOU to be involved in the celebration. This blog post on the jenkins-ci.org 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




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