0.8.0
- Improvements:
- UI: Trigger symbol is now visible before a manual trigger is reached (#97)
- UI: Console output now supports basic ANSI escape sequences (#91)
- UI: Default expand behavior now configurable (#99)
For details see https://github.com/flosell/lambdacd/wiki/Configuration - Started to add features for clean shutdown (#103)
- Made pipeline runners stoppable (#78)
- Made persistence mechanism stoppable
- Bug fixes:
- Breaking Changes:
-
Changed the default persistence format from JSON to EDN to fix #101. This change should be backwards and forwards
compatible (i.e. you keep your history when upgrading to 0.8.0 and when downgrading to an earlier version). However,
if your history is critical, consider backing up your LambdaCD home-dir just in case. -
Removed deprecated function
lambdacd.presentation.pipeline_state/most-recent-build-number-in
-
LambdaCD no longer depends on Logback as a logging implementation and gives you more freedom to choose a logging
implementation. If you see the following message you need to add a dependency to a library that's compatible with SLF4J:SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
The default dependencies were:
[ch.qos.logback/logback-core "1.0.13"] [ch.qos.logback/logback-classic "1.0.13"]
-
LambdaCD no longer depends on ring-server and leaves the decision on how you serve the UI to you. If you see the
following error, you were probably using ring-server and need to add it to your dependencies:Exception in thread "main" java.io.FileNotFoundException: Could not locate ring/server/standalone__init.class or ring/server/standalone.clj on classpath.
The default dependency was:
[ring-server "0.3.1"]
-