Roadmap
The topics below are planned for upcoming releases, roughly in priority order. Each
one has a specification in the repository's
specs/ folder; the
order may change as real-world feedback comes in.
Next
Source exclusions
Exclude paths from a task's src with ! entries (src: [src, '!src/**/*.md']),
so a source folder can be narrowed without long globs. An excluded path is hidden
from container tasks too, so a task can't read what isn't part of its cache key.
Container runtime options
Declare Docker runtime and security options such as --shm-size or a seccomp
profile on container tasks and services, for workloads like browsers or sandboxed
workers that need them.
Later
- Task resources — CPU and memory requests/limits per task, enforced on Docker and Kubernetes and used for resource-aware local scheduling instead of a flat worker count.
- Matrix tasks — define a task once with a
matrixof variants (Node versions, architectures) and run one independently cached task per combination. - Service state snapshots — cache the state a task leaves inside a service, such as a seeded database, so it can be restored instead of recreated.
- Multi-arch packaging — let
hammerkit packagebuild and push multi-platform images. - Distributed computing — offload compute-intensive tasks to remote hardware
with very little configuration. Server registration (
hammerkit remote) has landed; see the spec.
Shipped
Task catalog (1.22.0)
Tested, versioned build files for common tools that a project includes straight from git instead of copying them.
Shipped: includes from a git repository
with with inputs, and the catalog entries for npm, Yarn, pnpm, pip,
Go, Cargo, .NET, Docker, tsc, ESLint, Prettier, Jest and Helm.
Agent-ready caching (1.7.0)
Make one shared cache work across coding-agent sandboxes, developer workspaces and CI, so work done in one place is never repeated in another.
Shipped in 1.7.0: cache keys independent of the checkout location, the registry
cache backend, cache pull / cache push, read-only mode,
cache retention, skipping
dependencies of cached tasks,
task timeouts, and explain,
graph, run --dry-run and the build summary. See the
release blog and
agents, workspaces and CI.
Distributed caching (1.6.0)
Distribute the local cache, so other developers and CI can reuse already built results.
Shipped in 1.6.0 as pluggable cache backends: declare a
local or s3 cache backend and hammerkit pulls and pushes task results
automatically, sharing them between developers and CI runs.
Run on Kubernetes (1.6.0)
Run the same build file on the local Docker daemon or on a Kubernetes cluster.
Shipped in 1.6.0 through environments.
Services (1.5.0)
Tasks sometimes require a service to run, for example a database for an API or an integration test. The goal was to define those services and have hammerkit start them for a task and stop them when they are no longer needed.
Implemented in 1.5.0 with container services and Kubernetes services.
Platform requirements (1.5.0)
Define local tasks that require a specific platform. The goal was to either skip local tasks where the platform requirements are not met or run them on a suitable machine.
Labels, available since 1.5.0, can be used to achieve this.