Tags » Build Automation

Introduction to Continuous Delivery

So what is the problem? And why do we need Continuous delivery?

Regardless what agile methodology framework we use, and no matter how agile our software development is, as long as we are not moving that developed code into production environment, or at least make it production ready, as fast as how it was developed, then, we are probably not making the best use of the Agile Software methodologies. 755 more words

CD

Build Automation for Dotnet Core Apps

In a previous blog post I documented how I built a “Build Server” to deploy .NET 4.6+ apps on windows 2012 server.

While this worked, and was a reasonably good way to do it, It wasn’t without it’s problems. 2,158 more words

C# Coding

Salesforce DX

This post provides a practioner’s introduction to Salesforce DX (Developer Experience) a new software development lifecycle paradigm for Salesforce. Please note at the time of writing (Spring ’17 – v40.0) Salesforce DX is at public beta status. 1,398 more words

Development Lifecycle

Distributed Service Configuration with Consul, Spring Cloud, and Docker

Introduction

In this post, we will explore the use of HashiCorp Consul for distributed configuration of containerized Spring Boot services, deployed to a Docker swarm cluster. 4,809 more words

Software Development

| Jenkins – Build Configuration |

Objective

Configure Jenkins to build a project on demand, or whenever code is pushed to TFS, and archive (save) the artifacts (output).

Perspective

This article is from a .NET development perspective – using a full Microsoft stack.   328 more words

| Jenkins - Installation and Setup |

What / Why?

Jenkins is Build Automation server software.  It’s the defacto standard for Continuous Integration (CI).  Any serious development team consisting of more than one person, should have a Jenkins server setup. 274 more words

Infrastructure as Code Maturity Model

Systematically Evolving an Organization’s Infrastructure

Infrastructure and software development teams are increasingly building and managing infrastructure using automated tools that have been described as “infrastructure as code.” – Kief Morris (Infrastructure as Code)

1,537 more words
DevOps