Skip to main content

yaml orchestration for bash

Project description

Sometimes I find make too old, autoplay unfrustrates me.

Getting started

Install with pip install autoplay.

It will look for jobs in autoplay.yml in the current directory or fallback on the autoplay/autoplay.yml file which defines a few default jobs. The twine job for example will build .po files and make a python package that it will upload with twine, to automate python package release:

autoplay debug twine
autoplay twine mode=dryrun

Create a file with name autoplay.yml containing:

  someglobal: foo

name: example
  example_var: ./autoplay-example
  multiline_var: |
- test -f $example_var || echo "$multiline_var" > $example_var
- cat $example_var

name: test
- example

Then, see the commands it would execute with autoplay run example mode=dryrun


CLI Development Environment

We’re investing in a development command that would allow to run several jobs simultaneously, with an urwid based interface. It would allow to define jobs like this in your autoplay.yml:

name: dev
- eslint --watch
- yarn start
- django-admin runserver
- py.test --watch

That you could run with autoplay run dev mode=ide.

Tox-like and docker based executors

The default executor is linux which executes in a bash subshell. However other executors are available such as executor=docker (for baking development environments) and executor=virtualenv (for build matrix).

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Files for autoplay, version 0.5.0
Filename, size File type Python version Upload date Hashes
Filename, size autoplay-0.5.0.tar.gz (5.2 kB) File type Source Python version None Upload date Hashes View

Supported by

Pingdom Pingdom Monitoring Google Google Object Storage and Download Analytics Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN DigiCert DigiCert EV certificate StatusPage StatusPage Status page