-
Notifications
You must be signed in to change notification settings - Fork 1
User Stories
User Stories and Prioritization
1: Title: Creating new branches Priority: 1 Units (Story Points): 3 The user can create new branches for the project.
2: Title: Successful builds. Priority: 1 Units (Story Points): 3 Keeps a list of all branch builds that succeeded.
3: Title: Failed builds. Priority: 1 Units (Story Points): 3 Keeps a list of all branch builds that failed.
4: Title: Mainline Tree. Priority: 1 Units (Story Points): 3 All branches are added to a tree like structure of the mainline. Newer branches are connected to their direct predecessors.
5: Title: Active/Inactive branches. Priority: 1 Units (Story Points): 3 Branches can be made inactive or active.
6: Title: Build all branches. Priority: 2 Units (Story Points): 2 All branches can be built so that the efficiency or different branches can be compared.
7: Title: Selective building. Priority: 2 Units (Story Points): 2 A group of branches selected by the user can be built together.
8: Title: One project Priority: 2 Units (Story Points): 2 New branches do not get created as projects.
9: Title: Adding multiple branches. Priority: 2 Units (Story Points): 2 Multiple branches can be added to the project at once.
10: Title: Duplicate branches Priority: 3 Units (Story Points): 1 Branches can be duplicated and edited so that updated versions of a code can exist when only minor changes are made.
11: Title: Automatically build new branches Priority: 3 Units (Story Points): 1 When a new branch is created, it is built automatically.
12: Title: Build test cases for branches. Priority: 3 Units (Story Points): 1 Generate test cases for branches.
Hours per Unit: 0.5 Hours per Unit Hours per Week: 20 Hours per Week
- Iteration 1:
** Week 1: User Creating New Branches (1) User Duplicate Branches (2) User Automatically Build New Branches (3)
** Week 2: User Build All Branches (4) User Successful Builds (5) User Failed Builds (6)
- Iteration 2:
** Week 3: Mainline Tree (User Story Number) Selective Building (User Story Number) Active/Inactive (User Story Number)
** Week 4: One Project (10) Adding Multiple (11) Build Test Cases For Branch (12)
Building Test Cases (12) Task A: Coverage Getting a complete coverage to test all scenarios Task B: Categorical Getting the right amount of categories to be tested Task C: Diversity Checking the solutions against big data.
Project Description: Making Jenkins understand branches of a project. Imagine a project with many branches, created at different times in the past. Currently, managing this in Jenkins is not a very straightforward process. Jenkins users usually have to duplicate each branch as a separate project in Jenkins. This project aims to fix this problem by integrating knowledge of branching structure into Jenkins so that Jenkins can automatically manage them. It should also be possible to mark branches as active/inactive.