0.4.0

• Improvements:
  • Cleaned up status inheritance to make it more consistent
  • Support variable arguments instead of step-vector as input for chain-steps (#29)
  • Internal refactorings to prepare for more component-oriented structure
  • Contexts always contain :step-results-channel which can be used to access a stream of step-state updates,
    e.g. to create custom persistence components or runners (still experimental)
  • Cleaned up dependencies
• Bug fixes:
  • Fix bug in retriggering that left next step in undefined state (#26)
• API changes:
  • Steps returning no :status will now be treated as failures instead of receiving status :undefined
  • Removed deprecated :result-channel argument for execute-step
  • Removed deprecated core/new-base-context-for
  • core/execute-step does no longer output the result-channel data to a :result-channel in ctx.
    Was replaced with :step-results-channels which provides a stream of complete, aggregated step-result data
  • Calling lambdacd.steps.support/chain-steps with a vector instead of just the steps is now deprecated (#29)

0.3.2

• Improvements:
  • Remove styling for undefined step-status (#23)
  • All container steps inherit their childrens status by default (#24)
  • Add a run-container step that can group nested steps (#21)
  • Ignore step-results cloned by retriggering in determining start and stop timestamps in pipeline history (#22)
  • UI: build-history now in descending order (i.e. recent builds first) (#25)
• API changes:
  • the :result-channel argument for execute-step is now deprecated. Pass custom result-channels in via the ctx instead
  • Generating a new base context moved to execute-step, therefore core/new-base-context-for is now deprecated, just use ctx instead

0.3.1

• Bug fixes:
  • Fix updated scrolling (#18)

0.3.0

• Bug fixes: #14, #15, #17
• Improvements:
  • Display status in output at the end of a build step (#4)
  • Display total build time in history (#16)
  • Indicate lost connection to LambdaCD in UI
  • Allow retriggering of nested steps (#5)
  • Redirect to new build when retriggering
  • Support hardcoded result-maps in chain-macro
  • Support setting environment-variables in shell/bash (#9)
• API Changes:
  • removed deprecated argument lists for lambdacd.internal.execution/execute-steps

0.2.3

• Bug fixes: #13

0.2.2

• Bug fixes: #8, #10, #11, #12
• New features:
  • support/print-to-output simplifies printing to the output-channel within a step
  • support/printed-output in return allows you to get everything that was printed within that step, typically to return at the end of a step
• Improvements:
  • with-git removes its workspace after all child-steps are finished
  • Display build status in history (#3)
• API Changes
  • lambdacd.internal.execution/execute-steps is now deprecated. use the public lambdacd.core/execute-steps instead. (#7)
    lambdacd.core/execute-steps takes keyword-arguments instead of argument lists for optional parameters.
  • lambdacd.internal.execution/execute-step is now deprecated. use the public lambdacd.core/execute-step instead. (#7)

0.2.0

• Recording start and update timestamps for every build step
• Cleanup old endpoints: /api/pipeline and /api/pipeline-state
• Improve retriggering: Create a new pipeline-run instead of overwriting existing builds
• Make bash-step killable
• Breaking Changes:
  • removed core/mk-pipeline as a method to initialize the pipeline.
    Replaced with a more flexible core/assemble-pipeline and a few single functions that take over things like running
    the pipeline and providing ring-handlers to access the pipeline. For details, see examples.