Skip to content

Releases: thomhurst/ModularPipelines

2.27.0

08 Feb 14:47
54bbe3f
Compare
Choose a tag to compare
  • Improved JSON deserialization of modules by including Assembly information within the TypeDescriminator field

Breaking

  • context.Dotnet().Test now returns a CommandResult. Previously it would try to log results to a .trx file and parse them out, however different test frameworks use different formats and values for these trx files. So logging to a trx file and parsing it into a strong type model is now left to the user if they wish to do so. The Test command will still throw an error (and therefore fail your module) if tests fail.

2.26.8

04 Feb 19:14
Compare
Choose a tag to compare
  • Log stringified module return objects in debug mode

2.26.0

29 Jan 16:03
7a24c69
Compare
Choose a tag to compare
  • Trap Application Interupt Signal to ensure AlwaysRun modules are run

2.25.0

28 Jan 17:21
Compare
Choose a tag to compare
  • TimeoutException for clearer exception messages

2.24.9

25 Jan 16:54
c3a8b82
Compare
Choose a tag to compare
  • Easier to read CommandException message

2.24.4

25 Jan 14:05
f101393
Compare
Choose a tag to compare
  • File.MoveTo(Folder) method

2.24.1

22 Jan 13:47
4e89470
Compare
Choose a tag to compare

Breaking

  • The Docker options helpers have been rewritten. Options, properties and method calls may have been renamed, changed or moved.

2.23.0

21 Jan 17:41
Compare
Choose a tag to compare
  • When constructing custom classes that represent commands, you can now use Placeholders for greater control over the placement of arguments when using [PositionalArgumentAttribute] combined with [CommandPrecedingArgumentsAttribute]

Breaking

  • DotNet options have been rewritten. Some options, properties and method call names may have changed.
  • ModularPipelines.NuGet package is deprecated and the commands to interact with NuGet are now part of the ModularPipelines.DotNet package

2.22.0

18 Jan 20:41
aa8d67c
Compare
Choose a tag to compare
  • Log commands standard output and standard error even if they throw exceptions

Breaking

  • CommandException now doesn't expose a CommandResult object. Things like StandardOutput are available directly from the exception

2.21.12

18 Jan 13:02
f7e1a27
Compare
Choose a tag to compare
  • Add npm run options