Application of storage retention policies to a software deployment pipeline in response to code branch mergers
Techniques are provided for application of storage retention policies to a software deployment pipeline in response to code branch mergers. One method comprises, in response to a request to merge a first code branch of a first stage with a second code branch of a second stage of a software deployment pipeline: initiating a transition of the software deployment pipeline from a software repository associated with the first stage to a software repository associated with the second stage; and applying a software retention policy to the software repository associated with the first stage. The merge of the first code branch with the second code branch may be performed in connection with a pull request. The transition of the software deployment pipeline from the software repository associated with the first stage to the software repository associated with the second stage may be performed in connection with a build promotion.
1 . A method, comprising:
in response to a merge event that merges a first code branch of a first stage of a software deployment pipeline with a second code branch of a second stage of the software deployment pipeline:
automatically initiating a transition of the software deployment pipeline from at least one software repository associated with the first stage of the software deployment pipeline to at least one software repository associated with the second stage of the software deployment pipeline; and
automatically applying, responsive to the merge event, one or more software retention policies to the at least one software repository associated with the first stage, wherein the one or more software retention policies are specified for the at least one software repository associated with the first stage;
wherein the method is performed by at least one processing device comprising a processor coupled to a memory.
2 . The method of claim 1 , wherein the merge event is detected by monitoring one or more events published on a message queue.
3 . The method of claim 1 , wherein the merge of the first code branch of the first stage of the software deployment pipeline with the second code branch of the second stage of the software deployment pipeline is performed in connection with a processing of a pull request.
4 . The method of claim 1 , wherein the transition of the software deployment pipeline from the at least one software repository associated with the first stage to the at least one software repository associated with the second stage is performed in connection with a processing of a build promotion.
5 . The method of claim 1 , wherein the transition of the software deployment pipeline from the at least one software repository associated with the first stage to the at least one software repository associated with the second stage one or more of moves and copies one or more software items from the at least one software repository associated with the first stage to the at least one software repository associated with the second stage.
6 . The method of claim 1 , wherein the at least one software repository associated with the first stage and the at least one software repository associated with the second stage are part of a storage system.
7 . The method of claim 1 , wherein the one or more software retention policies are based at least in part on one or more of: an age of one or more software items associated with the software deployment pipeline, a last download time of the one or more software items, a repository location of the one or more software items, a designated number of retained builds based at least in part on a given build identifier and one or more designated search criteria for the one or more software items.
8 . The method of claim 1 , wherein the automatically applying the one or more software retention policies comprises executing one or more retention scripts for the at least one software repository associated with the first stage.
9 . An apparatus comprising:
at least one processing device comprising a processor coupled to a memory;
the at least one processing device being configured to implement the following steps:
in response to a merge event that merges a first code branch of a first stage of a software deployment pipeline with a second code branch of a second stage of the software deployment pipeline:
automatically initiating a transition of the software deployment pipeline from at least one software repository associated with the first stage of the software deployment pipeline to at least one software repository associated with the second stage of the software deployment pipeline; and
automatically applying, responsive to the merge event, one or more software retention policies to the at least one software repository associated with the first stage, wherein the one or more software retention policies are specified for the at least one software repository associated with the first stage.
10 . The apparatus of claim 9 , wherein the merge event is detected by monitoring one or more events published on a message queue.
11 . The apparatus of claim 9 , wherein the merge of the first code branch of the first stage of the software deployment pipeline with the second code branch of the second stage of the software deployment pipeline is performed in connection with a processing of a pull request.
12 . The apparatus of claim 9 , wherein the transition of the software deployment pipeline from the at least one software repository associated with the first stage to the at least one software repository associated with the second stage is performed in connection with a processing of a build promotion.
13 . The apparatus of claim 9 , wherein the transition of the software deployment pipeline from the at least one software repository associated with the first stage to the at least one software repository associated with the second stage one or more of moves and copies one or more software items from the at least one software repository associated with the first stage to the at least one software repository associated with the second stage.
14 . The apparatus of claim 9 , wherein the automatically applying the one or more software retention policies comprises executing one or more retention scripts for the at least one software repository associated with the first stage.
15 . The apparatus of claim 9 , wherein the one or more software retention policies are based at least in part on one or more of: an age of one or more software items associated with the software deployment pipeline, a last download time of the one or more software items, a repository location of the one or more software items, a designated number of retained builds based at least in part on a given build identifier and one or more designated search criteria for the one or more software items.
16 . A non-transitory processor-readable storage medium having stored therein program code of one or more software programs, wherein the program code when executed by at least one processing device causes the at least one processing device to perform the following steps:
in response to a merge event that merges a first code branch of a first stage of a software deployment pipeline with a second code branch of a second stage of the software deployment pipeline:
automatically initiating a transition of the software deployment pipeline from at least one software repository associated with the first stage of the software deployment pipeline to at least one software repository associated with the second stage of the software deployment pipeline; and
automatically applying, responsive to the merge event, one or more software retention policies to the at least one software repository associated with the first stage, wherein the one or more software retention policies are specified for the at least one software repository associated with the first stage.
17 . The non-transitory processor-readable storage medium of claim 16 , wherein the merge of the first code branch of the first stage of the software deployment pipeline with the second code branch of the second stage of the software deployment pipeline is performed in connection with a processing of a pull request.
18 . The non-transitory processor-readable storage medium of claim 16 , wherein the transition of the software deployment pipeline from the at least one software repository associated with the first stage to the at least one software repository associated with the second stage is performed in connection with a processing of a build promotion.
19 . The non-transitory processor-readable storage medium of claim 16 , wherein the transition of the software deployment pipeline from the at least one software repository associated with the first stage to the at least one software repository associated with the second stage one or more of moves and copies one or more software items from the at least one software repository associated with the first stage to the at least one software repository associated with the second stage.
20 . The non-transitory processor-readable storage medium of claim 16 , wherein the automatically applying the one or more software retention policies comprises executing one or more retention scripts for the at least one software repository associated with the first stage.