The Wercker command line interface (written in golang) that allows you to run your builds locally.
Introducing our CLI
As you can see the output coming from wercker CLI is a lot more compact. This allows you to focus on the output coming from steps. We’ve added some colors to the CLI so you can easily distuingish between differents steps, and if the step has passed or failed.
This does mean that by default, we do not display the environment variables during a build. If you need access to the environment variables, then you can enable the verbose mode. This will show you the environment variables. Just pass the
--verbose flag to a command. Example:
wercker --verbose build.
Nothing changes when using the hosted wercker solution. This output will still contain all the environment variables. Currently only the
build command supports the new compact output. Other commands will receive a facelift the coming weeks.
You can download the command line interface here
Why not join our early access club. We’ll invite you to try our beta products and treat you nice.
As usual, if you want to stay in the loop follow us on twitter @wercker or hop on our public slack channel. If it’s your first time using Wercker, be sure to tweet out your #greenbuilds, and we’ll send you some swag!