v4.2.0

Fixed

• Set repo-specific user output in deploy-debian.mk

Added

• dogu-release target to start an automated dogu release

v4.1.0

Make apt deploy target configurable

Added

• Include a new variable APT_REPO which controls which apt repository should be used as a deploy target.
  ces-premium deploys into the premium repository while any other value deploys into the public repositories.
  (Issue 45)

v4.0.0

Please note: Default behaviour for go projects changed!
The "CGO_ENABLED=0" variable is not set per default any more!
You have to set it via the Makefile, if needed.

Added

• Introduce GO_ENV_VARS for go environment variables

v3.0.1

• Fixes Issue 34: make unit-test and make integration-test depend on the go sources and won't download go-junit-report each time they run

v3.0.0

Please note: Breaking change ahead.

Added

• Update vendor target to check for new gomod dependencies

Changed

• Separate the debian package building and deploying targets
  • package-debian.mk only holds deb package building targets now
  • deploy-debian.mk holds the deb package deployment targets now

When you are upgrading to this version and want to deploy deb packages, you have to
include the deploy-debian.mk into your Makefile, below the package-debian.mk.
For example, see the Makefile in this repository.

v2.1.1

• Changed reviewdog -ci flag to -reporter flag in jenkins build
• static-analysis-ci now also executes the goal to create static-analysis.log

v2.1.0

Added

• Add Go modules support (#31)
  • Go module is activated by setting GO_ENVIRONMENT=GO111MODULE=on before including variables.mk
  • When working with go modules dependencies-gomod.mk has to be included.

Fixed

• Furthermore this commit fixes a weird unit-test behaviour when the go-junit tool is older than the tests.

v2.0.0

New release v2.0.0 🎉 🍰

Please note: Breaking change ahead.

Added

Support of proper integration tests (#28)

By default all go packages in the project are subject to the integration-test target. To reduce the foot print and test run time the variable containing the selected packages can be overwritten in the main Makefile like this (after including the variables.mk files but before the integration test inclusion.

This example extracts only the package paths for the packages tasks and registry:

PACKAGES_FOR_INTEGRATION_TEST=$(shell go list ./... | grep 'tasks\|registry')

Provide custom clean target (#26)

• Added customizable clean target
  • This comes handy if more files and directory should be removed during clean than the common stuff
  • Appending one's own clean target is easily done by defining the variable ADDITIONAL_CLEAN with a custom target name

Changed

Moved update-makefiles target to its own file (#28)

Previously the main Makefile was the place to accommodate the update-makefiles target.
Since it is encouraged (even more: necessary) to edit the main Makefile in order to customize a project's build process this file is never going to be updated. In order to allow the migration process of updating this routine moves to the self-update.mk file.

After updating to this version you SHOULD remove the update-makefiles from the main Makefile in order to avoid make target conflicts.

Please note, if the update-makefiles target is called, all filial makefiles under build/make/ are deleted. The directory build/make/ are not supposed to contain manual changes. Instead file a Feature Request in the makefiles repo and update to the following release version.

support integration test target (#28)

• Changes in test makefiles to support proper integration tests

Please include these files for your tests. It is possible to include neither, only one, or both files for unit and integration tests. Both need test-common.mk included beforehand.

• test-common.mk
  • this should be included first because both depend on it
• test-unit.mk
• test-integration

Removed

The test-related filial makefiles integration-test.mk and unit-test-docker-compose.mk are deleted in favour of new makefiles which sort better in a directory listing (#28)

Fix

• Moved a debian related variable to package-debian.mk to remove an error message (#30)
• Removed cleaning the directory under ${DEBIAN_BUILD_DIR} during clean
  • This is a specific clean target which belongs to the project's makefile
  • Appending one's own clean target is easily done by defining the variable ADDITIONAL_CLEAN with a custom target name (#25)

v1.0.6

Change owner and group to 0 when using tar

Resolves #23

v1.0.5

The temporary conffiles file $(CONFFILES_FILE_TMP) is removed after usage so it is not filled with duplicates if the deb package is built again.

This resolves #20