Difference between revisions of "EGI-InSPIRE:NSRW New Software Release Workflow"
Jump to navigation
Jump to search
Line 19: | Line 19: | ||
[[File:EGI-SW-Release-Workflow.png ]] | [[File:EGI-SW-Release-Workflow.png ]] | ||
== Required Field == | |||
== Work Flow == | == Work Flow == |
Revision as of 15:33, 22 September 2010
Ticket LifeCycle
- The SW Provider Creates a Ticket in GGUS accompanied with all the neccesary info
- The ticket is Transfered from GGUS to RT, Status of the Ticket is New
- RT Notifies the Repo there is a new ticket to be processed, Status of the Ticket remains new (i.e the Ticket is Assigned to the REPO)
- The Repo Processes the ticket
- The Repo Downloads the software bundle and puts it on the Unverified Repository
- The Repo parses the attached xml
- The Repo updates RT with the info extacted from the xml + the Uri where the new software can be found
- The Status of the ticket is set to Unverified
- RT Notifies the EGI Technology Unit group (i.e the Ticket is Assigned to the EGI TUG)
- EGI TUG -- please fill in the intermedate steps here
- Depending on the outcome
- if Success the Ticket is Marked MoveToStageRollOut, Go To Step X
- if failure the Ticket is Marked Rejected, Go To Step Y
...
Required Field
Work Flow
MetaDATA
NRMS New Release MetaDATA schema