DotCi is an Open Sourse Project which integrates GitHub, Jenkins, Docker and allows a one click setup of new Jenkins builds with a simple YAML file. DotCi is platform independent and can support Ruby, Java, Python, Node and many other builds. It sets up a brand new prestine build environment for every build, which allows you to have consistent testing results, where build failure due to bad node environment is a thing of the past!


Outline/Structure of the Talk

  • Introduction to Jenkins
    • 1 min Jenkins Pitch
    • List of pain points with Jenkins which we are trying to solve
  • DotCi
    • Goal of DotCi project
    • Feature list and explanation of each feature
    • YAML build configuration
    • GitHub integration
    • Docker Integration
    • Multiple platform support
  • Demonstration
    • Simple YAML config file
    • 1 Click build setup

Learning Outcome

Managing multiple Jenkins builds should not be a pain, this session will demonstrate how each individual team can have as many of their own builds as they desire.

Target Audience

Build administrators

schedule Submitted 6 years ago

  • dima kovalenko

    dima kovalenko - Scaling and managing Selenium Grid

    45 Mins

    Managing the Selenium Grid can be very difficult, especially as you scale it up.  This session will demonstrate how we were able to scale the Selenium Grid with multiple operating systems, in multiple data centers across many continents. With the use of Selenium Grid Extras, and open source project, we were able to get much better control of individual nodes, manage WebDriver versions and much more. 

  • David Tolley

    David Tolley - Migrating the herd - How Salesforce is migrating 35,000 Selenium RC tests

    David Tolley
    David Tolley
    LMTS - Platform
    schedule 6 years ago
    Sold Out!
    45 Mins
    Case Study

    The Quality Engineering team at Salesforce fell into the same pit that most other technology companies have: Selenium tests were so easy to create that we created thousands upon thousands of them. The difference is our Selenium RC pit is over 35,000 tests deep. This talk is about how we are indentifying what each of our tests are doing, how we can transition tests to a different and faster layer and how we are migrating from Selenium RC to WebDriver across a massive scale.