Notes on Software Development

The purpose of these sample series is to create a simple set of examples, which showcasesCI/CD as Code, using Jenkins. Main goal is to create a stateless CI/CD setup, which can be bootstrapped from a set of configuration files and scripts so that many problems related to maintenance of the infrastructure and other operational issues are reduced. First Steps to "job as code" Checkout this example from here We are going to introduce necessary plugins to achieve the goal of programmatic job descriptions in this step and configure them accordingly via programmatic means. The first plugin that we are going to introcude is jobDsl plugin . The most common job creation mechanism in Jenkins is that users usually create jobs by cloning/copying an existing project. As experienced by most of us, when the number of jobs grows in Jenkins or the job description gets complicated, use of user interface oriented method becomes...

The purpose of these sample series is to create a simple set of examples, which showcasesCI/CD as Code, using Jenkins. Primary goal is to create a stateless CI/CD setup, which can be bootstrapped from a set of configuration files and scripts so that many problems related to maintenance of the infrastructure and other operational issues are reduced. We created a containerised Jenkins instance in the previous part of these example series . Most of the installation and setup work in that example was done manually via user interface. Our target in this step is to automate most of the manual work in our way towards a stateless Jenkins instance.  Checkout this example from here In summary, this basic setup will handle the following on behalf of an actual human being: Creation of the user(s) on jenkins programmatically. Installation of basic plugins to get up-and-running with Jenkins. ...

The purpose of these sample series is to create a simple set of examples, which showcases   CI/CD as Code , using Jenkins. Primary goal is to create a stateless CI/CD setup, which can be bootstrapped from a set of configuration files and scripts so that many problems related to maintenance of the infrastructure and other operational issues are reduced. A step by step approach is followed while implementing the examples. The documentation regarding each step can be reached using the links below. Sample Steps Introduce a stateful containerised Jenkins Complete the basic setup of Jenkins via code : The goal of this step is to complete  basic setup  of Jenkins completely programmatically. First steps to 'job as code'  : In this step, we are going to head towards configuring jobs programmatically. Stateless Jenkins - Job as Code Part II : In this ...

Summary This blog post aims to provide an introduction to create a database container  with predefined data in it. Therefore, it does not address explanations of basic docker commands and instructions.  Containerisation has many advantages.  One advantage among these is getting up and running quickly with a production ready datasource, which has predefined data in it. This way we can share and use the application data state in local development environments easily. In this article we are going to create such a customised datasource container, in order to speed up our development activities. Even though, mysql is used as the database system in this blog post, similar concepts are applicable to other database systems as well. The steps that we're going to follow to reach our goal are as follows: Creating a Dockerfile for our base container Implementing the scripts for database/table creation and sample data insertion.  Building our customised mysql docker i...

This example demonstrates how we can implement our tests using groovy in a java based project. You might be asking why. Well, implementing tests with groovy has some advantages. However, this article does not try to convince you groovy is a better way to implement your tests. It's just another alternative to implement your tests. If you want to investigate testing java projects with groovy, the article will, then, provide you a starting point for your investigation.

A clear and concise REST API documentation is mandatory for a rest api to be easily used. However, it's error prone and is also hard to maintain an api documentation if we attempt to write it manually. This sample project demonstrates how we can use rest assured tests to generate api documentation with a small amount of manual work. Project Setup This sample uses Spring Boot 2.x as its core framework. In order to achieve our goal it's also necessary to add some additional dependencies and configure some maven plugins.  These configuration needs and dependencies are explained step by step in the following subsections. You can also checkout initial setup for the demonstration using the link below: git clone --branch rest-assured-asciidoc_start git@github.com:entrofi/spring.git The final form of the demonstration can also be checked-out using: git clone --branch rest-assured-asciidoc_finish git@github.com:entrofi/spring.gi t Dependencies The dependencies neede...