Page History

...

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

1. adding a default staging repository and assign the all permissoin configurations of that repository to the admin useradd 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.

1. restricted this staging repository from being using as a plugging repository from out user as mentioned in above in the pom.xml files

1. implementing the read action and the write actions and assign them to the developer(role)and the QA person(role) as mentioned in above.
2. Testing the roles(developer) with the staging repository.

1. implementing the promotion role.(only the merging based on the assumption that new artifact is being deployed.Not a update version)

1. implement the logs and make use them for the a searching algorithm to check the older versions of the artifacts which have already deployed.

1. 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.

1. 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)

1. implementing logs for staging repository