v2.15

What's Changed

• Added option to allow scan code job to extend needs by @NazmiAltun in #9
• Append candidate- to service tags in docker-composes file by @NazmiAltun in #10

Full Changelog: v2.14...v2.15

v2.14

Full Changelog: v2.13...v2.14

v2.13

What's Changed

• Dotnet sonar scanning added by @NazmiAltun in #8

Full Changelog: v2.12...v2.13

Passing Git commit SHA to dockerfile on build

What's Changed

• Pass current git commit SHA to docker image via docker build args by @NazmiAltun in #6

New Contributors

• @NazmiAltun made their first contribution in #6

Full Changelog: v2.10...v2.12

Merge test build and run jobs

What's Changed

• Merge jobs by @andreyleskov in #4

Full Changelog: v2.8...v2.9

Control cache push

What's Changed

• Allow to disable or enable cache load and push by @andreyleskov in #3

Full Changelog: v2.7...v2.8

Pass parameters to docker run

What's Changed

• Add docker run parameters by @andreyleskov in #2
  Full Changelog: v2.6.2...v2.7

v2.5

Use candidate tag for service image during the build and tag it at the end.

Old behavior will produce the service image with tags during the build stage (before any tests) and push to the cache registry.
In situations when we deploy from cache registry(to dev environment, for example) it leads to unwanted deployment before CI competes

Filter for test artifacts upload

Tests jobs can specify a path to results including excludes symbols via new upload_path optional settings, defaulting to "TestResults"
The provided value will be passed to upload-artifacts action "path" parameter

A possible use-case is to filter out some results in test output folder that should not be uploaded, for example dotnet dumps

Support for multiple nuget projects

Multiple NuGet projects support

Users can specify several NuGet sections in the config file with the same structure, then for each section, a separate pair of build+publish jobs will be generated.
Job name format for NuGet build and publish now includes slug from the nuget item section.

Better dependency support for nuget

Nuget section have a new optional field publish_after. It is an array of job names than should be finished before publishing the nuget package.

Backward compatibility

This release is backward-compatible, e.g. producing the same workflow for old nuget sections.
nuget config section can be an array, or a map (old behavior). A map will be treated as an array with single NuGet section.
If publish_after field is missing, default dependencies would be generated