Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nice framework, needs a task runner #9

Open
jforberg opened this issue Aug 11, 2014 · 3 comments
Open

Nice framework, needs a task runner #9

jforberg opened this issue Aug 11, 2014 · 3 comments

Comments

@jforberg
Copy link

It seems like every new scripting language these days has its own taskrunner. Ruby has rake, Coffescript has cake, for Coco there is coke and probably some more make puns that I don't know about.

Since running tasks in plain bash is not complicated enough, I propose to add the bake command which can be used to run the accompanying Bakefiles. Each Bakefile would consist of a number of recipes with a variety of different ingredients, and so on.

If anyone thinks this is a good idea I'd be happy to build it.

@John-Appleseed
Copy link

I like the idea of bash task runners.
So if you made this Task runner would it look like this?

Files

- Task/
  - Task1.sh
  - Task2.sh
  - Task_test.sh

Interface

task <task name>    run task
task <task group>   run a group of tasks

Feature

Feature: Bash Task Runner
    In order save development time by running async jobs
    As a developer
    I gain more time prorgramming cooler features

    Unit: Tasks

    Scenario: Automated testing
        Given I have a testing suite like cucumber or bats
        And my step_definitions define for balls
        When I save code in my bash balls server
        Then task_test.sh will tests features within ./Test/* and ./Test/Feature/*

@jforberg
Copy link
Author

@John-Appleseed You're mostly correct. But the focus will not be on saving development time, but rather to get the most "readable" syntax possible by abusing the bash control constructs. Think rspec here, monkey-patching the global class so they could overload the == operator to mean something different.

Bash, of course, doesn't have a == operator.

@stylemistake
Copy link

I wonder if that fits this project :>
https://github.com/stylemistake/bash-task-runner

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants