Adding option to define ReportFilename to gather final report in mo…

…re computer friendly format - json (#10)

Makefile

@@ -1,5 +1,5 @@
 APP_NAME=docker-bakery
-VERSION=1.2.0
+VERSION=1.3.0
 
 .DEFAULT_GOAL: all
 

README.md

@@ -17,6 +17,7 @@
 - [Config](#config)
   - [Properties config section](#properties-config-section)
   - [Commands config section](#commands-config-section)
+  - [Other config attributes](#other-config)
 - [Dockerfile.template](#dockerfiletemplate)
 - [Usage](#usage)
   - [Command help](#command-help)
@@ -84,6 +85,7 @@ Structure of the `config.json` file is as follows:
 		"defaultBuildCommand": "docker build --tag {{.IMAGE_NAME}}:{{.IMAGE_VERSION}} --tag {{.DEFAULT_PUSH_REGISTRY}}/{{.IMAGE_NAME}}:{{.IMAGE_VERSION}} --tag {{.DEFAULT_PULL_REGISTRY}}/{{.IMAGE_NAME}}:{{.IMAGE_VERSION}} {{.DOCKERFILE_DIR}}",
 		"defaultPushCommand": "docker push {{.DEFAULT_PUSH_REGISTRY}}/{{.IMAGE_NAME}}:{{.IMAGE_VERSION}}"
 	},
+	"reportFileName": "custom-report-filename.json",
 	"verbose": false,
 	"autoBuildExcludes": [
 		"some-image-name-that-will-be-excluded-from-build-when-parent-changes"
@@ -122,7 +124,11 @@ Structure of the `config.json` file is as follows:
 <a id="commands-config-section"></a>
 ## Commands config section
 This section contains two templates used for building and pushing docker images. It allows for specifying custom parameters. 
-Commands defined here as templates will be filled with available defined properties from the config section + the dynamic properties set during runtime.  
+Commands defined here as templates will be filled with available defined properties from the config section + the dynamic properties set during runtime. 
+
+<a id="other-config"></a>
+## Other config attributes
+  `reportFileName` - if set it will be used as a file name to store information (in JSON format) about successfully built images. 
 
 <a id="dockerfiletemplate"></a>
 # Dockerfile.template
@@ -206,4 +212,4 @@ Applying `docker-bakery` is quite simple. Take a look [here](https://github.com/
 
 <a id="limitations"></a>
 # Limitations
-At the moment docker multi-stage builds are not fully supported. Only the first line `FROM` is taken into consideration when determining the parent of the image and its place in the hierarchy. 
+At the moment docker multi-stage builds are not fully supported. Only the first line `FROM` is taken into consideration when determining the parent of the image and its place in the hierarchy. 

bakery/service/bakery.go

@@ -224,6 +224,9 @@ func PrintReport() {
 	for _, r := range commandResults {
 		fmt.Printf(color.GreenString("\t%s %s => %s\n", r.Name, r.CurrentVersion, r.NextVersion))
 	}
+	if len(config.ReportFileName) > 0 {
+		commons.WriteToJSONFile(commandResults, config.ReportFileName)
+	}
 	errorCount := len(commandErrors)
 	if errorCount > 0 {
 		fmt.Printf(color.RedString("Following (%d) errors occurred during image processing:\n", errorCount))

bakery/service/entities.go

@@ -12,6 +12,7 @@ type Config struct {
 	RootDir           string            `json:"rootDir"`
 	Verbose           bool              `json:"verbose"`
 	AutoBuildExcludes []string          `json:"autoBuildExcludes"`
+	ReportFileName    string            `json:"reportFileName"`
 }
 
 // Commands is used as part of the config to contain template of build and push commands