Continuous Integration using Powershell and Jenkins

Getting Started with Continuous Integration


Application Modernization enables the migration of monolithic applications to new Microservices architecture with Cloud Native Support including Continuous Integration and Continuous Delivery to meet the current business needs.


Jenkins is a Continuous Integration software tool for testing and reporting changes in a large code base in Real-Time. Jenkins enables developers to find and solve defects in a code base rapidly and to automate testing of the builds.


PowerShell is an automated task framework from Microsoft, a command line shell and a scripting language integrated into the .NET framework, used within other applications. It automates Batch Processing and creates system management tools.


Challenges for Continuous Integration with Jenkins and PowerShell


  • Enable file sharing between nodes/systems.
  • A common user who has all permission to perform a task.
  • Avoid adding every node or system as an agent in Jenkins to perform a task.
  • Making Powershell script compatible with every version of PowerShell.
  • No third party plugin.
  • Creating a hook concept for different repos on GitHub and Bitbucket.


Solution Offerings for Continuous Integration


  • GitHub and BitBucket Repo set up to keep the source code.
  • PowerShell Script to execute the Source Code Deployment.
  • Alerts generated in the form of Email depending upon the deployment status.
  • Logs generated for every job build.
  • Set up WebHook for GitHub and BitBucket Repo.
Read more