erik/kobalt
erik/kobalt
1
0
Fork 0
mirror of https://github.com/ethauvin/kobalt.git synced 2025-04-25 16:07:12 -07:00
Code Releases Activity

Fixes.

Browse source
This commit is contained in:
Cedric Beust 2015-12-21 04:50:09 +04:00
parent 07717274b2
commit e839ff508d
1 changed files with 6 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

11
kobalt-incremental-tasks.md
View file

@ -1,9 +1,10 @@
Kobalt's incremental task algorithm is not based on timestamps but on checksums.
You make a task incremental by declaring it `@IncrementalTask` instead of `@Task`. The only other difference is that instead of returning a `TaskResult`, incremental tasks return a `IncrementalTaskInfo`:
You make a task incremental by declaring it `@IncrementalTask` instead of `@Task`. The only other difference is that instead of returning a `TaskResult`, incremental tasks return an `IncrementalTaskInfo`:
```
class IncrementalTaskInfo(val inputChecksum: String?,
class IncrementalTaskInfo(
val inputChecksum: String?,
val outputChecksum: String?,
val task: (Project) -> TaskResult)
```
@ -11,10 +12,10 @@ class IncrementalTaskInfo(val inputChecksum: String?,
This class contains three fields:
- A task closure, which is your effective task: `(Project) -> TaskResult`
- An input checksum (`String`)
- An output checksum (`String`)
- An input checksum (`String?`)
- An output checksum (`String?`)
These checksums are numbers that each task calculates for their input and output. For example, the "compile" task calculates an MD5 checksum of all the source files. Similarly, the output checksum is for produced artifacts, e.g. checksum of `.class` files or `.jar` files, etc...
These checksums are numbers that each task calculates for their input and output. For example, the `"compile"` task calculates an MD5 checksum of all the source files. Similarly, the output checksum is for produced artifacts, e.g. checksum of `.class` files or `.jar` files, etc...
Example of an incremental task: