For the self-service deployment, you’ll provide a mechanism for authorized team members to enter some basic information into an application. Once this is done, an environment (with its deployment) will be launched and connection information to this environment will be provided to the authorized team members. Providing self-service resources is a key attribute and benefit of Continuous Delivery and is much more possible when using a cloud provider such as AWS. Ideally, your self-service deployment will launch an environment based on the AMI created during the acceptance stage. The authorized team member enters email address, Git SHA, subdomain and private key name.
Here are the stpes to running a self-service deployment using Jenkins:
- Go to your Jenkins server (Go to OpsWorks, find the same, click on the instance and select the ELB link)
- Login to Jenkins(the default username and password are
- Click the self-service-create-dsl job
- Enter a valid email address for Jenkins from which to send environment login instructions
- Enter HEAD for the SHA parameter
- Click the Build now link
- Jenkins will start creating your environment and email you usage instructions once it is complete
The idea of providing self-service access rather than shared access to resources (for example, shared environments) can be a radical change in many organizations, but it’s a key component in isolating variables and providing team members the autonomy to experiment. It’s also something that requires good governance. Keep in mind that it’s something you might need to push for inside your organization because most live in world of scarcity. But, providing self-service resources becomes a key factor in successfully realizing the benefits of DevOps.
Here’s a list of the resources used in this step: