Epic
Major Problem Description
When a new user installs Jenkins, they are greeted with the main, empty, dashboard which suggests that they "create jobs." This makes no mention of plugins or the configuration options that are relevant to helping the user make Jenkins match their needs.
Proposal
Instead of changing the post-install defaults, which may not properly represent the user's needs, the first-time user experience should help guide the user through configuration and plugin installation quickly so they can use Jenkins for their needs. Effectively it should be as easy as possible for a user to arrive at a good configuration for their usage.
Part of this would entail:
- Changing how plugin bundling works, no automatically installing plugins just for backward compatibility
- Encouraging use of pipeline-as-code enhancements discussed previously
Impact
This would primarily change the way in which first-time users would use Jenkins.
Open Questions
- is blocking
-
JENKINS-33281 Release Jenkins 2.0
-
- Closed
-
[JENKINS-31157] 2.0: Out of the box experience
| Epic Child |
New:
|
| Epic Child |
New:
|
| Epic Child |
New:
|
| Epic Child | New: JENKINS-31176 [ 165835 ] |
Aaron D. Marasco
made changes -
| Epic Child | New: JENKINS-31255 [ 165981 ] |
| Description |
Original:
* See [wiki|https://wiki.jenkins-ci.org/display/JENKINS/2.0+Out-of-the-box+experience] for the context and the background* This epic is tracking 2.0 planning tickets that are around the out of the box product experience, so that new users can start using Jenkins, without assembling pieces first. |
New:
h1. Problem Description When a new user installs Jenkins, they are greeted with the main, empty, dashboard which suggests that they "create jobs." This makes no mention of plugins or the configuration options that are relevant to helping the user make Jenkins match their needs. h1. Proposal h1. Impact h1. Open Questions This epic is tracking 2.0 planning tickets that are around the out of the box product experience, so that new users can start using Jenkins, without assembling pieces first. |
| Description |
Original:
h1. Problem Description When a new user installs Jenkins, they are greeted with the main, empty, dashboard which suggests that they "create jobs." This makes no mention of plugins or the configuration options that are relevant to helping the user make Jenkins match their needs. h1. Proposal h1. Impact h1. Open Questions This epic is tracking 2.0 planning tickets that are around the out of the box product experience, so that new users can start using Jenkins, without assembling pieces first. |
New:
h1. Problem Description When a new user installs Jenkins, they are greeted with the main, empty, dashboard which suggests that they "create jobs." This makes no mention of plugins or the configuration options that are relevant to helping the user make Jenkins match their needs. h1. Proposal Instead of changing the post-install defaults, which may not properly represent the user's needs, the first-time user experience should help guide the user through configuration and plugin installation quickly so they can use Jenkins for their needs. Part of this would entail: * Changing how plugin bundling works, no automatically installing plugins just for backward compatibility * Encouraging use of pipeline-as-code enhancements [discussed previously|https://jenkins-ci.org/content/jenkins-20-proposal-pipeline-code-front-and-center] h1. Impact This would primarily change the way in which first-time users would use Jenkins. h1. Open Questions * |
| Description |
Original:
h1. Problem Description When a new user installs Jenkins, they are greeted with the main, empty, dashboard which suggests that they "create jobs." This makes no mention of plugins or the configuration options that are relevant to helping the user make Jenkins match their needs. h1. Proposal Instead of changing the post-install defaults, which may not properly represent the user's needs, the first-time user experience should help guide the user through configuration and plugin installation quickly so they can use Jenkins for their needs. Part of this would entail: * Changing how plugin bundling works, no automatically installing plugins just for backward compatibility * Encouraging use of pipeline-as-code enhancements [discussed previously|https://jenkins-ci.org/content/jenkins-20-proposal-pipeline-code-front-and-center] h1. Impact This would primarily change the way in which first-time users would use Jenkins. h1. Open Questions * |
New:
h1. Problem Description When a new user installs Jenkins, they are greeted with the main, empty, dashboard which suggests that they "create jobs." This makes no mention of plugins or the configuration options that are relevant to helping the user make Jenkins match their needs. h1. Proposal Instead of changing the post-install defaults, which may not properly represent the user's needs, the first-time user experience should help guide the user through configuration and plugin installation quickly so they can use Jenkins for their needs. Effectively it should be as easy as possible for a user to arrive at a good configuration for their usage. Part of this would entail: * Changing how plugin bundling works, no automatically installing plugins just for backward compatibility * Encouraging use of pipeline-as-code enhancements [discussed previously|https://jenkins-ci.org/content/jenkins-20-proposal-pipeline-code-front-and-center] h1. Impact This would primarily change the way in which first-time users would use Jenkins. h1. Open Questions * |
| Epic Child | New: INFRA-459 [ 166247 ] |