Skip to content

0.13.1
Compare
Choose a tag to compare
@flosell flosell released this 26 Mar 14:12
· 167 commits to master since this release
0.13.1
This tag was signed with the committer’s verified signature. The key has expired.
flosell Florian Sellmayr
GPG key ID: 70794554AF507349
Expired
Learn about vigilant mode.
0e97ced

Added

Fixed

  • Marking builds as dead if the datastore sees them as running but they are not (e.g. because LambdaCD was not cleanly shut down previously).
    This introduces the new :status :dead (#134)
  • junction did not behave like a sequential step, i.e. it did not pass the results of the condition to the arguments of the branch steps (#162)
  • made lambdacd.stepresults.merge/merge-step-results default behavior consistent with other step-result merging strategies: should concatenate colliding lists

Deprecated

  • Built-in Git-Support (lambdacd.steps.git) should be considered deprecated now and will be removed in the future. Use the more modern lambdacd-git library instead.

  • A couple of functions were only public by accident and should not be considered part of the public API. They will be moved or become private in the future:

    • lambdacd.presentation.pipeline-state/not-retriggered?
    • lambdacd.presentation.pipeline-structure/pad
    • lambdacd.presentation.pipeline-structure/step-display-representation-internal
    • lambdacd.runners/should-trigger-next-build?
    • lambdacd.steps.control-flow/synchronize-atoms
    • lambdacd.steps.shell/kill
    • lambdacd.steps.status/choose-last-or-not-success
    • lambdacd.steps.support/{replace-args-and-ctx,to-fn,to-fn-with-args,unify-results}
    • lambdacd.ui.ui-page/{css-includes,js-includes,favicon,app-placeholder,title,header,ui-config,ui-page}

  • lambdacd.presentation.unified/unified-presentation is unused and therefore deprecated and will be removed in the future. Use pipeline-structure-with-step-results instead.

  • lambdacd.steps.support/merge-globals is no longer necessary, normal step result merging (merge-step-results,merge-two-step-results) should already conserve and merge globals just fine

  • A couple of functions were moved to make the package structure more clear. The existing functions still exist but are now deprecated and will be removed in the future.

    • lambdacd.steps.result/flatten-step-result-outputs moved to lambdacd.stepresults.flatten
    • lambdacd.steps.result/{merge-step-results,merge-two-step-results} moved to lambdacd.stepresults.merge
    • lambdacd.steps.result/*-resolver moved to lambdacd.stepresults.merge-resolvers
    • lambdacd.steps.status/successful-when-* moved to lambdacd.stepstatus.unify
    • lambdacd.steps.status/is-active? moved to lambdacd.stepstatus.predicates
    • lambdacd.steps.support/assoc-build-metadata! moved to lambdacd.stepsupport.metadata
    • lambdacd.steps.support/unify-only-status moved to lambdacd.stepstatus.unify
    • lambdacd.steps.support/{capture-output,printed-output,print-to-output,set-output,new-printer} moved to lambdacd.stepsupport.output
    • lambdacd.steps.support/{killed?,if-not-killed} moved to lambdacd.stepsupport.killable
    • lambdacd.steps.support/{chaining,chain-steps,always-chaining,always-chain-steps,injected-args,injected-ctx,last-step-status-wins} moved to lambdacd.stepsupport.chaining
    • lambdacd.ui.ui-server/ui-for moved to lambdacd.ui.core
Assets 2