Understanding Codenvy - for Containerized Developer Workspaces
•Transferir como PPTX, PDF•
1 gostou•1,159 visualizações
Understanding Codenvy, a platform for building containerized developer workspaces E
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Semelhante a Understanding Codenvy - for Containerized Developer Workspaces
Semelhante a Understanding Codenvy - for Containerized Developer Workspaces (20)
Mais de Lynn Langit
Mais de Lynn Langit (20)
Último
Último (20)
Understanding Codenvy - for Containerized Developer Workspaces
- 1. Understanding Codenvy @LynnLangitContainerized Developer Workspaces June 2015
- 2. Current Approaches to Developer Workspaces... ● Manual: Step-by-step, administrative, & error-prone ● Desktop: Expensive, fixed size & not secure ● Virtualization: Large, slow, hard to synchronize & non- portable ...are not working
- 3. Contribute Your Code in Seconds Developer workspaces to modify, run and debug code in the cloud or on-premises DevOpsDevelopers Repeatable one-click automationVery Fast cloud-based IDE Provision developer workspaces that are simply shareable and securely managed Craft code, then command Docker-based microservices to run and debug from anywhere
- 4. Getting Started – Hello Codenvy
- 5. Get started with Codenvy Projects ● New: Open a Codenvy Template ● New: Import a GitHub Repo ● Existing: Click on a Codenvy Project URL
- 6. The Projects section allows you to: -- create an instance of existing project -- create a new project -- import a project
- 7. IDE Features IDE Features Example for Java
- 8. Build / Run Features Click the blue link to open the view
- 9. Using Codenvy Factories & Projects
- 10. Use Supported Languages and Libraries Plug Ins
- 11. Factory = Blueprint (JSON) Project = Instance Codenvy Objects
- 12. Enabling Developer Contributions “The Intuit internal engineering hackathon on Codenvy supported 4000 engineers on 17 nodes, and they never installed a thing.” - Jeff Brewer, Distinguished Engineer, Intuit
- 13. Enterprise-Controlled Services Three-Tier Composable Services Open Source Modules Composable Architectures -> Dependencies Modern Architectures include: Continuous Delivery Shifts operation burdens to development Microservices Increases setup, update and maintenance Containers Decomposes applications into modules
- 14. Dependencies -> Installation (Wiki) Nightmares Django and PHP with Eclipse Tomcat with IntelliJ Compile and install Ruby Mozilla Webmaker with Vagrant
- 15. GitHub Contribution Flow “Developers are looking for companies that not only use and contribute to open source, but also create a culture of open, community-style development.” -- Guy Martin, Samsung
- 16. Build Your Contribution Factory Build contribution factory Embed linked factory button into GitHub ReadMe file Track usage with Codenvy Analytics
- 18. Click the button to open the pull request
- 20. Try it
Notas do Editor
- Current approaches to reducing configuration complexity are non-solutions: Manual Config: Step-by-step, administrative, & error-prone Desktop Boxes: Expensive, limited in size, & insecure VMs: Large, slow, hard to synchronize, & non-portable Impacts of open contribution structures are significant: Contributor Support: Committers support contributor onboarding and issues, decreasing their own contribution time. Contribution Review: Committers review each pull & change request from contributors, further decreasing their contribution time. Proof 1: Electric Cloud + LinkedIn study: "Devs spend 13 hrs / week configuring environments." Proof 2: OpenDeis: "We spend up to 4 hours of serial time to review each pull request." Proof 3: David Blevins: "At TomiTribe, we spend 2 hours helping each contributor get started."
- Current approaches to reducing configuration complexity are non-solutions: Manual Config: Step-by-step, administrative, & error-prone Desktop Boxes: Expensive, limited in size, & insecure VMs: Large, slow, hard to synchronize, & non-portable Impacts of open contribution structures are significant: Contributor Support: Committers support contributor onboarding and issues, decreasing their own contribution time. Contribution Review: Committers review each pull & change request from contributors, further decreasing their contribution time. Proof 1: Electric Cloud + LinkedIn study: "Devs spend 13 hrs / week configuring environments." Proof 2: OpenDeis: "We spend up to 4 hours of serial time to review each pull request." Proof 3: David Blevins: "At TomiTribe, we spend 2 hours helping each contributor get started."
- Current approaches to reducing configuration complexity are non-solutions: Manual Config: Step-by-step, administrative, & error-prone Desktop Boxes: Expensive, limited in size, & insecure VMs: Large, slow, hard to synchronize, & non-portable Impacts of open contribution structures are significant: Contributor Support: Committers support contributor onboarding and issues, decreasing their own contribution time. Contribution Review: Committers review each pull & change request from contributors, further decreasing their contribution time. Proof 1: Electric Cloud + LinkedIn study: "Devs spend 13 hrs / week configuring environments." Proof 2: OpenDeis: "We spend up to 4 hours of serial time to review each pull request." Proof 3: David Blevins: "At TomiTribe, we spend 2 hours helping each contributor get started."
- http://docs.codenvy.com/user/factories/#what-are-factories http://docs.codenvy.com/project-lifecycle/ Projects To Create Factory Config New Project Wizard Import Project Project Template To Use Share or Embed Clone Destroy
- Key point: Open source drives composibility, modularity and microservices
- https://github.com/codenvy-demos/spring-petclinic
- https://codenvy.com/products/pricing