Dynamic release baselines in a continuous delivery environment

A system comprising:

• a release automation server implemented at least partially in hardware comprising:
• an application;
• and
• a deployment environment associated with a server type;
• a configuration manager implemented at least partially in hardware comprising:
• a server hosting logic executable to:
• create one or more ordered sets of instructions or resources;
• configure the server according to the server type using the one or more ordered sets of instructions or resources;
• and
• deploy the application in the deployment environment on the server type;
• and
• a user interface to accept inputs to map a configuration baseline for the application to run in the development environment to the server associated with the server type;
• the system further comprising a computer processor implemented at least partially in hardware to execute the application in the deployment environment using the ordered set of instructions or resources;
• wherein the server hosting logic being executable to create the one or more ordered set of instructions or resources comprises server hosting logic executable to:
• create a runlist that includes the ordered set of instructions or resources;
• and
• associate the runlist with the server type;
• wherein associate the runlist with the server type comprises:
• identify the ordered set of instructions based on the server type and deployment environment, and map the runlist onto the ordered set of instructions to facilitate configuration of the deployment environment based on a selected configuration manager node;
• wherein the selected configuration manager node comprises a selection from one of a Chef node, a Puppet node, a CFEngine node, a Salt node, or a Ansible node;
• and
• the server hosting logic executable to further comprising:
• deploy the application on a node associated with the server type;
• detecting a change in the ordered set of instructions or resources;
• and
• report the change in the ordered set of instructions or resources after deployment of the application.

A non-transitory computer-readable medium having program instructions stored therein, wherein the program instructions are executable by a computer processor to perform operations comprising:

• identifying a deployment environment for an application;
• determining a server type for the deployment environment;
• determining a configuration manager node associated with the server type;
• generating an ordered set of instructions or resources for the deployment environment for the application based on detection of a selection of a particular instruction or a particular resource from a list comprising a plurality of instructions and a plurality of resources corresponding to a combination of the deployment environment and the server type;
• and
• executing the application in the deployment environment based on the ordered set of instructions or resources;
• wherein generating the ordered set of instructions or resources comprises:
• creating a runlist that includes the ordered set of instructions or resources;
• and
• associating the runlist with the server type;
• wherein associating the runlist with the server type comprises:
• identifying the ordered set of instructions based on the server type and deployment environment, and mapping the runlist onto the ordered set of instructions to facilitate configuration of the deployment environment based on the selected configuration manager node;
• wherein determining the configuration manager node comprises selecting from one of a Chef node, a Puppet node, a CFEngine node, a Salt node, or a Ansible node;
• and
• the operations further comprising:
• deploying the application on a node associated with the server type;
• detecting a change in the ordered set of instructions or resources;
• and
• reporting the change in the ordered set of instructions or resources after deployment of the application.