An amazing two weeks, our first time back to a strict Agile sprint schedule after the magnificent chaos of the alpha launch phase.
Here’s what we shipped:
Nobody needs to see 700 lines of messages from Aptitude, Bundler or NPM, so we made it possible to arbitrarily fold blocks around your log output, you can use the API two ways:
hfold "A Title For The Block" sudo your-noisy-command –goes=here
$ hfold "A Title For The Block"
$ sudo your-noisy-command –goes=here
$ and –another=one –in-the-same=block
$ hfold –end
These are perfect for things like Bundler and NPM installation spam and they don’t catch standard error, so that you can always see if something went wrong. Folds stay open as long as they are being written to, so you can still see the logs streaming by, and as soon as it the fold is closed we disappear the contents.
Faster Startup Time
We improved our pooling and provisioning tools that now operations start in about ~20-35s typically. This is the right balance for us between costs and performance whilst we’re in the un-billed Alpha/Beta phase.
We now create a few “default” scripts and environments when creating a new project to make it clearer how the pieces fit together, and what belongs where. We needed this mostly to facilitate the next item in the list.
Running Tasks Directly
We have a concept of combining a Task with an Environment to make a Job, the reasoning behind this setup being that you can setup a “Capistrano Deployment”, for example once and reuse the same thing in your Staging and Production environments, for collaboration this is super important, however many of our early testings are people who are the sole developer on their project, and they don’t really need this “power user” feature.
To make it easier for them, and… we have to admit, we use this button a lot too, we made it possible to run a task directly, at least conceptually. We really create the Job for your transparently after asking which Environment to use.
This turns out to be a great interface too, since if a Job for this task already exists, it’ll be transparently visible, and logically we think “I want to run a deployment *click* … in staging”, where the click action is showing us a list of which environments we have to hand, this turns out to work really well!
We hope you enjoy the new features, don’t forget that Harrow is free for 30 days to try, and is also available to run on your own hardware if you need it.
See you back here in a fortnight for new awesome features!
Want to try Harrow.io? Start immediately with a 14 day free trial or learn more
Harrow.io is a platform for Continuous Integration, testing and deployment, built by the team behind Capistrano.
Add powerful automation and collaboration capabilities to your existing tools.
- Automate any software, in any language.
- Create self-documenting, repeatable web-based tasks
- Make them available for your team-mates
- Trigger tasks automatically based on Git changes and webhooks.
- Get notified by email, slack, etc.
- Free for small projects
Test, deploy and collaborate online easily, using tools you already know and love.
Works seamlessly for PHP, Node.js, Ansible, Python, Go, Capistrano and more!
No credit card required – completely free for small or public projects.