This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description

Radish is a task runner that understands version control.

You define a command that applies to multiple subprojects in your repository and thenradish will figure out which projects have changed and run the command for just those projects. Radish isn’t a replacement for make, gulp, gradle, rake, or any other task runner. It’s a supplement for orchestrating other runners and scripts with some smarts from your version control repository.

If you’re using a CI/CD server like Concourse or GoCD which supports pipelines as first-class citizens you probably have no need for radish on your CI/CD server. It might still be useful on your dev machine, though.


Radish is available on PyPi as radish-run and can be installed on most systems with pip:

$ pip install radish-run

How to use

An example invocation of radish:

$ radish command tests --from 19abc023 --to 2514ecb1
Changed paths:
  - extensions/cool-extension/
  - frontend/js/

Running tests for extensions/cool-extension/:

Running tests for frontend/js/:

All commands ended successfully and ran in 9.75s.


radish configuration is a yaml file named Radishfile, because I can.

  - extensions/*/  # Mark each subdirectory in extensions as a path
  - frontend/js/

commands:  # Runs from the directory denoted by paths above
    default: bin/rspec spec
    frontend/js/: npm test

An example use case

Take that you’re building a single page web app, it consists of two parts: - The backend that delivers JSON - The frontend that holds all the clicky bits that end-users see

Because cross-functional teams this project is in one repository, which is a great win for productivity. But it has a downside: when there are only changes to the backend, then all the tests for the frontend is still run. Finally, after running all tests it can get deployed, but then both sites get deployed despite nothing changing on the frontend.

So this is a crazy situation. It shouldn’t be. So this is where radish comes in. You tell radish about test and deploy, and what that means for both the backend and the frontend, then on your CI server you run the commands with the last green commit. Radish then figures out what has changed from the current commit and the last one, and only runs the command for those projects.



  • Define a path/project to always run, no matter whether there are changes or not
  • Run a different command if there are changes to the project
  • Allow for changed files to be passed in to commands. Primarily a feature for local dev boxes, so you only run the command against changed files.
  • Dependencies between projects. If the frontend-payment project changes then run the command in the frontend project as well.
  • Custom differs for Ci systems so they can smartly figure out what the last green commit was, instead of relying on HEAD~1 as the poor mans “what was the last change?”

Local development

To get started make with your current global version of Python do:

$ git clone
$ cd radish/
$ make develop
$ make test

This will install all dependencies, check out the test repo, and then run all the tests.


Beerware License

Release History

Release History


This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
radish_run-0.1.0-py3-none-any.whl (9.1 kB) Copy SHA256 Checksum SHA256 py3 Wheel Sep 14, 2016
radish-run-0.1.0.tar.gz (8.0 kB) Copy SHA256 Checksum SHA256 Source Sep 14, 2016

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting