Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

In above I have mentioned only the success scenario of a artifact. There can be a fail scenario as well. If an artifact is failed then the user should manually delete the artifact

Implementation

  • add stage repository function so that user can create a stage repository and attach it to articular released repositories.(this functionality is granted only for the admin level users).Proper UI should e provide to the user.
  • restricted this staging repository from being using as a plugging repository from out user as mentioned in the pom.xml files
  • implementing the read action and the write actions and assign them to the developer(role)and the QA person(role) as mentioned in above.
  • implementing the promotion role.(only the merging based on the assumption that new artifact is being deployed.Not a update version)
  • implement a searching algorithm to check the older versions of the artifacts which have already deployed.
  • add searching feature(action) to the promotion role and do the merging part by providing the options regarding the version as mentioned above.(with a proper UI).Here meta data updating should be done.
  • add the simultaneous deployment functionality for the stage repositories.(here need to find a way to check with repository is busy with being a deployment)
  • implementing logs for staging repository