Special Hardware requirements or high-performance applications sometimes rule out the use of containers.

When security constraints require air-gapped*ish environments, publicly available resources usually break at the dependency chain.
State[fulness] is a big problem in CI/CD pipelines, servers become snowflakes and builds become unreproducible.

These issues can be tackled by a straight-forward and easy-to-implement pattern:

```
$s = Get-CurrentState
try { something }
finally { Restore-State $s }
```

In this session, we'll explore how such a pattern could be implemented in a build environment such as Jenkins CI.
Creating a minimal DSL that detects and rolls back

* software installations
* registry modifications
* configuration file changes