-
Story
-
Resolution: Fixed
-
Minor
-
None
-
-
Evergreen - Milestone 1
- blocks
-
JENKINS-51877 Write JEP about auto-configuration for a given environment (Docker, Azure, AWS...)
-
- Closed
-
- relates to
-
JENKINS-51599 Incrementalify the docker plugin
-
- Resolved
-
-
JENKINS-51180 Make docker client updatable like the rest
-
- Closed
-
-
JENKINS-49853 Provide a cloud-friendly installation for AWS
-
- Resolved
-
- links to
(1 links to)
I suppose this is just a short term improvement, talking about the milestone1 and are mostly working to get something rolling, and using the Docker socket seems like indeed a pretty easy way to already have something.
For what you're saying, we'll need to start some more involved wizard I think, but can't find any JIRA or Epic for this "what is the UX when Jenkins Essentials starts up the very first time?" thing.
I'll defer that to rtyler with his "the one Croy Cloud Chief Product Officer" (yes, C3PO) cap on for this part. Or at least we need to discuss the longer term roadmap I guess.