1
Ticket System (sub-function of Project Manager)
2
===============================================
6
* Service to create, monitor and manage ticket related activities.
7
* Define and create a ticket including:
9
* describe the targeted feature
10
* Links to any bugs/BPs/other design docs that are related
11
* People/teams working/owning on the ticket
12
* Components involved (packages/PPAs/feature branches/infrastructure required to code/test/build/deploy)
13
* PPA(s) dedicated to the ticket
14
* describe the test suites that need to be run (smarts can be added in the long run to assist users in choosing the Right test to run).
15
* Knowing what image is supposed to be ‘frozen’ for developing against
17
* Provides test and status of a ticket:
19
* Built images in the image store
20
* Status of the ticket as it progresses through the CI engine
21
* Clear indication of merge/build/test failures and where the failure occurred, make it obvious to developers what a corrective course of action should be
22
* Provide a means to execute a landing when all criteria have passed
24
* Coordinates the landing of multiple components:
26
* Ensures that a feature landing is an atomic event
27
* Communicates status as this is done
28
* Provides feedback when something goes wrong and a course of action
29
* Back-out the landing on failure
31
* Provides ticket management:
33
* list and status of all tickets
37
* Built into the Project Manager
41
* track MPs targeting feature branches
42
* track packages built as a result of the MP/development done (PPA? Archive?)
43
* integration test runner for both environments (the isolated one and the automatic merges against the currently landed)
added
removed
docs/components/ticket-system.rst
