Onboard Java Devs in Seconds
@bradmicklea
Anyone, anytime can contribute to a
project without installing software.
TODAY: INTEGRATION IS CONTINUOUS
CONTINUOUS
INTEGRATION
>80%
... BUT DEVELOPMENT IS DISJOINTED.
CONTINUOUS
INTEGRATION
DISJOINTED
DEVELOPMENT
95% >80%
WHY IS THIS A PROBLEM?
1. Onboarding developers take time (and pulls in experts)
2. “Works on my machine
”
3. IP on desktops is hard to secure
How Long to Setup A New Dev In A Team?
(Single Selection)
OpenShift.io Introduction
25.7 5.89.9
ENVIRONMENT MANAGEMENT
+ BUILD / TEST WAITING
ADMINISTRATIV
E TASKSBRAINSTORMING, DESIGN AND CODING
TODA
Y
TODAY NEARLY 25% OF THE
DEVELOPMENT TEAMS’ TIME IS
SPENT MANAGING MACHINES.
TEAM SIZE 30 person team
TEST TERM 6 months
TEAM EXPERIENCE 70% expert // 10% advanced // 20% beginner Similar findings were published in a 2013 LinkedIn study.
Your IP and App
DESKTOPS: HARD TO SECURE & SHARE
IDE Runtime
Hard to Share / Hard to Secure
Project Files
COMMON SOLUTION:
STANDARDIZE THE DESKTOP
// Pros
- Greater (but imperfect) consistency
- Quicker project-to-project moves
// Cons
- One size fits none (devs / projects)
- Secret exceptions
- Onboarding still slow
EVERY DESKTOP HAS LIMITATIONS
Sharing Controlling Scaling
REAL SOLUTION:
A SHAREABLE AND SECURE WORKSPACE
IDE RuntimeProject Files
Centrally Hosted Workspace
EASY to Share / EASY to Secure
OpenShift.io Introduction
WITH ECLIPSE CHE TEAMS SPEND
LESS TIME CONFIGURING AND
MORE TIME CODING.
33.2 5.82.4
25.7 5.89.9
ENVIRONMENT MANAGEMENT
+ BUILD / TEST WAITING
ADMINISTRATIV
E TASKSBRAINSTORMING, DESIGN AND CODING
AFTER
BEFORE
39% more time for coding.
ECLIPSE CHE ON OPENSHIFT
Today: Single user Che in MiniShift / OpenShift
November: Multi-user Che in OpenShift
OPENSHIFT.IO: PRE-INTEGRATED OSS
- Organize with issue management
- Analyze code using machine learning
- Code with Eclipse Che
- Build and test continuously with Jenkins
- Deploy pipelines through Fabric8
- Approvals
- Canary deployments
- Release rollbacks
- Elastic scaling
Move to an end-to-end,
integrated, cloud-native
development platform.
Use enterprise-proven
continuous integration and
development processes.
Use crowd-sourced and
analytically produced
insights to mitigate risk.
More Information
THANK YOU!
@bradmicklea

Introduction to Eclipse Che

  • 1.
    Onboard Java Devsin Seconds @bradmicklea
  • 2.
    Anyone, anytime cancontribute to a project without installing software.
  • 3.
    TODAY: INTEGRATION ISCONTINUOUS CONTINUOUS INTEGRATION >80%
  • 4.
    ... BUT DEVELOPMENTIS DISJOINTED. CONTINUOUS INTEGRATION DISJOINTED DEVELOPMENT 95% >80%
  • 5.
    WHY IS THISA PROBLEM? 1. Onboarding developers take time (and pulls in experts) 2. “Works on my machine
” 3. IP on desktops is hard to secure
  • 6.
    How Long toSetup A New Dev In A Team? (Single Selection)
  • 7.
    OpenShift.io Introduction 25.7 5.89.9 ENVIRONMENTMANAGEMENT + BUILD / TEST WAITING ADMINISTRATIV E TASKSBRAINSTORMING, DESIGN AND CODING TODA Y TODAY NEARLY 25% OF THE DEVELOPMENT TEAMS’ TIME IS SPENT MANAGING MACHINES. TEAM SIZE 30 person team TEST TERM 6 months TEAM EXPERIENCE 70% expert // 10% advanced // 20% beginner Similar findings were published in a 2013 LinkedIn study.
  • 8.
    Your IP andApp DESKTOPS: HARD TO SECURE & SHARE IDE Runtime Hard to Share / Hard to Secure Project Files
  • 9.
    COMMON SOLUTION: STANDARDIZE THEDESKTOP // Pros - Greater (but imperfect) consistency - Quicker project-to-project moves // Cons - One size fits none (devs / projects) - Secret exceptions - Onboarding still slow
  • 10.
    EVERY DESKTOP HASLIMITATIONS Sharing Controlling Scaling
  • 11.
    REAL SOLUTION: A SHAREABLEAND SECURE WORKSPACE IDE RuntimeProject Files Centrally Hosted Workspace EASY to Share / EASY to Secure
  • 12.
    OpenShift.io Introduction WITH ECLIPSECHE TEAMS SPEND LESS TIME CONFIGURING AND MORE TIME CODING. 33.2 5.82.4 25.7 5.89.9 ENVIRONMENT MANAGEMENT + BUILD / TEST WAITING ADMINISTRATIV E TASKSBRAINSTORMING, DESIGN AND CODING AFTER BEFORE 39% more time for coding.
  • 13.
    ECLIPSE CHE ONOPENSHIFT Today: Single user Che in MiniShift / OpenShift November: Multi-user Che in OpenShift
  • 14.
    OPENSHIFT.IO: PRE-INTEGRATED OSS -Organize with issue management - Analyze code using machine learning - Code with Eclipse Che - Build and test continuously with Jenkins - Deploy pipelines through Fabric8 - Approvals - Canary deployments - Release rollbacks - Elastic scaling Move to an end-to-end, integrated, cloud-native development platform. Use enterprise-proven continuous integration and development processes. Use crowd-sourced and analytically produced insights to mitigate risk.
  • 15.