Artifact manager for release automation
An artifact manager generates an abstraction for artifacts and repositories in a deployment platform such that the artifacts may be located uniformly and securely in each deployment environment during the deployment process. The described system includes a release automation platform having a release pipeline which is responsible for deploying build artifacts into multiple deployment environments, testing the build artifacts thoroughly in each environment, and follow organization-specific approval processes to promote the build artifacts to a next deployment environment.
1. A method comprising:
receiving a request to deploy an application defined by an application blueprint in a first deployment environment, wherein the application blueprint specifies a logical artifact name of at least one artifact that is part of the application;
determining a resource location of the at least one artifact that is part of the application according to the application blueprint and to a mapping of logical artifact names to resource locations of repositories associated with the first deployment environment;
deploying a first build of the application in the first deployment environment from the determined resource location of the at least one artifact; and
responsive to determining the first build of the application in the first deployment environment has passed testing, promoting the at least one artifact to a second deployment environment and deploying a second build of the application in the second deployment environment associated with a next stage within a release pipeline.
2. The method of claim 1 , further comprising:
determining a second resource location of the at least one artifact that is part of the application according to the same application blueprint and to the mapping of logical artifact names to resource locations of repositories associated with the second deployment environment; and
deploying the second build of the application in the second environment from the determined second resource location of the least one artifact.
3. The method of claim 1 , wherein the first build of the application is deployed from a first repository of a first repository type, the first repository associated with the first deployment environment; and wherein the second build of the application is deployed from a second repository of a second repository type associated with the second deployment environment.
4. The method of claim 1 , wherein the mapping of logical artifact names to resource locations of repositories is generated according to a process comprising:
generating a specification for a first type of repository configured to store artifacts; and
generating an instance of the specification associated with the first deployment environment having the first type of repository, wherein the first deployment environment is associated with a stage within a release pipeline.
5. The method of claim 4 , wherein the specification comprises a first field indicating a type of version, a second field indicating how the first type of repository is accessed, and a third field indicating an action parameter used to access the first type of repository.
6. The method of claim 1 , wherein the first deployment environment is part of a series of deployment environments representing a release pipeline comprising at least a test environment and a production environment.
7. A non-transitory computer-readable storage medium comprising instructions that, when executed in a computing device, operate a computing system, by performing the steps of:
receiving a request to deploy an application defined by an application blueprint in a first deployment environment, wherein the application blueprint specifies a logical artifact name of at least one artifact that is part of the application;
determining a resource location of the at least one artifact that is part of the application according to the application blueprint and to a mapping of logical artifact names to resource locations of repositories associated with the first deployment environment;
deploying a first build of the application in the first deployment environment from the determined resource location of the at least one artifact; and
responsive to determining the first build of the application in the first deployment environment has passed testing, promoting the at least one artifact to a second deployment environment and deploying a second build of the application in the second deployment environment associated with a next stage within a release pipeline.
8. The non-transitory computer-readable storage medium of claim 7 , wherein the steps further comprise:
determining a second resource location of the at least one artifact that is part of the application according to the same application blueprint and to the mapping of logical artifact names to resource locations of repositories associated with the second deployment environment; and
deploying the second build of the application in the second environment from the determined second resource location of the least one artifact.
9. The non-transitory computer-readable storage medium of claim 7 , wherein the first build of the application is deployed from a first repository of a first repository type, the first repository associated with the first deployment environment; and wherein the second build of the application is deployed from a second repository of a second repository type associated with the second deployment environment.
10. The non-transitory computer-readable storage medium of claim 7 , wherein the mapping of logical artifact names to resource locations of repositories is generated according to a process comprising:
generating a specification for a first type of repository configured to store artifacts; and
generating an instance of the specification associated with the first deployment environment having the first type of repository, wherein the first deployment environment is associated with a stage within a release pipeline.
11. The non-transitory computer-readable storage medium of claim 10 , wherein the specification comprises a first field indicating a type of version, a second field indicating how the first type of repository is accessed, and a third field indicating an action parameter used to access the first type of repository.
12. The non-transitory computer-readable storage medium of claim 7 , wherein the first deployment environment is part of a series of deployment environments representing a release pipeline comprising at least a test environment and a production environment.
13. A computer system, comprising:
a storage device comprising one or more repositories configured to store build artifacts;
a processor configured to perform steps for managing artifacts of an application deployment, the steps comprising:
receiving a request to deploy an application defined by an application blueprint in a first deployment environment, wherein the application blueprint specifies a logical artifact name of at least one artifact that is part of the application;
determining a resource location of the at least one artifact that is part of the application according to the application blueprint and to a mapping of logical artifact names to resource locations of repositories associated with the first deployment environment; and
deploying a first build of the application in the first deployment environment from the determined resource location of the at least one artifact; and
responsive to determining the first build of the application in the first deployment environment has passed testing, promoting the at least one artifact to a second deployment environment and deploying a second build of the application in the second deployment environment associated with a next stage within a release pipeline.
14. The computer system of claim 13 , wherein the processor is further configured to perform the steps comprising:
determining a second resource location of the at least one artifact that is part of the application according to the same application blueprint and to the mapping of logical artifact names to resource locations of repositories associated with the second deployment environment; and
deploying the second build of the application in the second environment from the determined second resource location of the least one artifact.
15. The computer system of claim 13 , wherein the first build of the application is deployed from a first repository of a first repository type, the first repository associated with the first deployment environment; and wherein the second build of the application is deployed from a second repository of a second repository type associated with the second deployment environment.
16. The computer system of claim 13 , wherein the mapping of logical artifact names to resource locations of repositories is generated according to a process comprising:
generating a specification for a first type of repository configured to store artifacts; and
generating an instance of the specification associated with the first deployment environment having the first type of repository, wherein the first deployment environment is associated with a stage within a release pipeline.
17. The computer system of claim 13 , wherein the first deployment environment is part of a series of deployment environments representing a release pipeline comprising at least a test environment and a production environment.