We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Developer Workspace As Code - Is Developer Heaven in the Cloud?

Formal Metadata

Title
Developer Workspace As Code - Is Developer Heaven in the Cloud?
Title of Series
Number of Parts
490
Author
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
Developer workspaces are assembled using outdated wiki pages and usually require weeks to "get right". What if the IDE and workspace setup (in the broadest sense) lived directly with the code? In the age of devops many things live with the source code. We compose our applications from Kubernetes/OpenShift objects, CI/CD pipelines and IDEs have their configuration in dot files, all defined along with the source code of our precious applications. But how do you define the common development environment/workspace for your developers? Let's take a look at the devfile - a declarative format for specifying the developer workspace with all the tools the developers need to code, build, test and debug the applications and how it enables Eclipse Che to be the next-gen Kubernetes-native IDE for developer teams.