Inspiration
I got an inspiration, when I started deployment manually and when there is the unavailability of the workforce. It becomes a very tedious task and time-consuming.
What it does
The "Deployment Automation" has the capability to timely deploy continuous software deliveries at the onsite environment and offshore environments. It picks the ". properties file from an absolute path and perform tasks accordingly. After deploying the packages to the offshore environment, it creates the docker image of the whole application from the dockerfile and then pushes the image to the docker hub, from where the client site, pull the image and run it as a container.
How I built it
I create a shell script, which read ". properties" file. This file includes artifactory link of packaged deliveries, environments name(where to deploy) and it's IP with defined variables respectively. I create jobs in Jenkins with "init" job as a starting job and schedule it every 2 min. This init job read variables from ". properties" file. And, deploy packaged deliveries in respective environments.
Challenges I ran into
The challenge is how to append incremental files in the complete files in different environments. Since each incremental files have a different format of representation. So, I need to find out the pattern that definitely looks out for incremental file and append accordingly.
Accomplishments that I'm proud of
I made the whole manual deployment to automation deployment. I feel happy now since I do not need to remain online for deployment. The job picks the PDN(Processed Definition Number) file which includes artifactory path server name, and user and does the processing as required. And, using the docker image, the whole application will get deployed at onsite without doing manual deployment at onsite. This also enables offshore environment in sync with the onsite environment.
What I learned
I learned shell scripting, Jenkins, Git, SVN, Docker. And, more important I learned how to make a designed process and workflow for automation.
What's next for Deployment Automation
That depends on business needs and new updates.
Log in or sign up for Devpost to join the conversation.