docs: guide - always execute an action
Signed-off-by: guillaume <guillaume.derouville@gmail.com>
This commit is contained in:
parent
467620f094
commit
1ed5fdcab1
24
docs/guides/1229-always-execute.md
Normal file
24
docs/guides/1229-always-execute.md
Normal file
@ -0,0 +1,24 @@
|
|||||||
|
---
|
||||||
|
slug: /1229/always-execute
|
||||||
|
displayed_sidebar: europa
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to make sure an action is always being executed ?
|
||||||
|
|
||||||
|
Dagger implemented a way to tell Buildkit not to rely on cache for a specific action.
|
||||||
|
|
||||||
|
The `docker.#Run` and `core.#Exec` definitions have an `always` field:
|
||||||
|
|
||||||
|
```cue
|
||||||
|
// If set to true, the cache will never be triggered for that specific action.
|
||||||
|
always: bool | *false
|
||||||
|
```
|
||||||
|
|
||||||
|
Any package composed on top of it (`bash.#Run` for example) also exposes this field as it will inherit it from `docker.#Run`:
|
||||||
|
|
||||||
|
```cue
|
||||||
|
test: bash.#Run & {
|
||||||
|
always: true
|
||||||
|
...
|
||||||
|
}
|
||||||
|
```
|
Reference in New Issue
Block a user