Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "EGI-InSPIRE:NSRW New Software Release Workflow"

From EGIWiki
Jump to navigation Jump to search
Line 29: Line 29:




== MetaDATA ==
== MetaData ==


[[NRMS New Release MetaDATA schema]]
[[NRMS New Release MetaDATA schema]]

Revision as of 15:19, 22 September 2010

Ticket LifeCycle

  1. The SW Provider Creates a Ticket in GGUS accompanied with all the neccesary info
  2. The ticket is Transfered from GGUS to RT, Status of the Ticket is New
  3. 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)
  4. The Repo Processes the ticket
    1. The Repo Downloads the software bundle and puts it on the Unverified Repository
    2. The Repo parses the attached xml
    3. The Repo updates RT with the info extacted from the xml + the Uri where the new software can be found
    4. The Status of the ticket is set to Unverified
  5. RT Notifies the EGI Technology Unit group (i.e the Ticket is Assigned to the EGI TUG)
  6. EGI TUG -- please fill in the intermedate steps here
  7. Depending on the outcome
    1. if Success the Ticket is Marked MoveToStageRollOut, Go To Step X
    2. if failure the Ticket is Marked Rejected, Go To Step Y

...


EGI-SW-Release-Workflow.png

Required Fields

RepoAction : Actions to Be Performed by the Repo, Values MoveToUnverified,MoveToStageRollOut,MoveToProduction,Reject,Depreceate

RepoStatus : Response to RepoActions, Values Uverified,StateRollOut,Production,Depreceated,Failed

Work Flow

MetaData

NRMS New Release MetaDATA schema

Ticket Status Values

Related Info

Feedback from M. David

MS501

MS504

UMD RoadMap

MS504