In my previous blog Concourse CI: A new way to approach CI-CD , I introduced Concourse CI. It is a tool to implement CI-CD pipelines to deliver software. If you have not read that post, please read that first. It will only take 15-20 minutes and make it easy for you to understand what I am trying to explain in this blog. As explained in the introductory blog, all pipelines are in the form of code. Pipeline code contains resources, jobs and tasks. This same pipeline code will also need credentials to connect to SCM (Source Control Management) tools like Git or PaaS such as Cloud Foundry. This pipeline code will also be stored in a source code repository either with the application code or in a separate repository. This will give access to these secure credentials to anyone who has access to the repository. One simple approach to hide these credentials is to use a separate params.yml file. We can define template variables in our pipeline code. Values for these template va...
DevOps is essential to software delivery. Applying DevOps principles to software development and delivery has become a necessity as more and more Enterprises are adopting this philosophy. A philosophy focused at faster delivery of software with reduced risks and more collaboration among teams. And who doesn't want faster delivery of software? One of the first place to start when adopting DevOps is implementing CI-CD to automate the process of integration, build, test and delivery. Continuous integration is a process where developers continuously integrate their code to source code repository. When implemented with DevOps, this also includes build, unit testing and integration testing. This provides faster feedback to the team related to any build errors or defects. In this blog, I will explain what Concourse CI is, how it is different from other CI tools, what are its core concepts and how teams can use it implement an effective CI-CD pipeline for their applica...