The latest updates from RWX on new features and best practices for CI/CD workflows
RWX now supports running tasks with up to 64 CPUs and 256 GB of memory.
Discover RWX 1.0 with improved support for Docker containers. Try it now!
Dynamic tasks enable building CI pipelines which are adaptive based on things like the commit contents or data from external data sources. They unlock a lot of possibilities for building highly performant CI pipelines.
RWX now supports running tasks with up to 64 CPUs and 256 GB of memory.
Dynamic tasks enable building CI pipelines which are adaptive based on things like the commit contents or data from external data sources. They unlock a lot of possibilities for building highly performant CI pipelines.
When multiple commits are merged in rapid succession, rather than creating a backlog of deployments, a reasonable solution is to skip deploying the earlier commits and only deploy the most recent one.
We built a remote debugger into Mint using a familiar construct: setting a breakpoint. It's as easy as calling mint-breakpoint from a task and then using the local CLI to run mint debug {debugId}.
Shell scripts are commonly used for automating DevOps and CI/CD tasks. Unfortunately they do not provide an easy way to build a map data structure and serialize it directly from a shell script, which usually leads to engineers inventing a custom format instead.
Get the latest releases and news about RWX and our ecosystem with our newsletter.
As a best practice, engineering teams should ensure that the same version of tools and runtimes are used across all environments. The best way to enforce version consistency is checking for it explicitly in a CI pipeline.