Massive Art Build Bundle

0.4.0 2018-09-25 06:45 UTC


The Massive Build Bundle provides a massive:build command which runs build targets.

Targets are classes which execute arbitary code, and are registred in the dependency injection container via. tags. Targets can depend on other targets.

Virtual targets can be created in you applications configuration file. These virtual targets simply declare depenencies, enabling you to configure custom build processes.

The aim of this bundle is to provide an extensible, decoupled, way of building software project environments, especially in a development context.

If you often find youself executing several Symfony commands consecutively to establish your environment, then this bundle is for you.

This tool is not mean to replace Make or Ant or Phing. The bundle should only be used to execute build steps which are contained in the client application.

Defining targets

You can define new build targets in you applications configuration file:

            target_one: ~
            target_two: ~
            target_three: ~
            target_one: ~

The above will allow you to execute:

$ php app/console massive:build main


$ php app/console massive:build quick

Creating build classes

You create builder classes in your application / bundles. Each build class should have a specific responsiblity.

A minimal example:


namespace My\Web\Application;

use Massive\Bundle\BuildBundle\Build\BuilderInterface;

class MyBuilder implements BuilderInterface
    protected $context;

    public function getName()
        return 'mybuildername';

    public function getDependencies()
        return array();

    public function build()
        $application = $this->context->getApplication();
        $input = $this->context->getInput();
        $output = $this->context->getOutput();

        $output->writeln('Hello World!');

    public function setContext(BuilderContext $context)
        $this->context = $context;
  • getName: Return a name for the builder.
  • getDependencies: Return the names of any builders that this builder depends on.
  • build: Execute all logic in this method
  • setContext: Called automatically by the master build command, contains the Input, Output and Application.

Registring the builder class

You can register the builder class in the dependency injection container and# then tag it with

<service id="" class="My\Web\Application\Builder\FooBuilder">
    <tag name="massive_build.builder" />

Accessing the container

You can access the service container by implementing the ContainerAwareInterface:

// ...

class MyBuilder implements ContainerAwareInterface, BuilderInterface
    // ...

Adding global options and customization

You can make options available to your commands (e.g. to specify that they should destroy the database, or that the name of user "x" should be set to "y").

By taking this approach you are free to customize the build command in anyway that you like.

To so this you need to extend the massive BuildCommand and configuring the MassiveBuild bundle to use your extended class.


namespace Sulu\Bundle\CoreBundle\Command;

use Massive\Bundle\BuildBundle\Command\BuildCommand;
use Symfony\Component\Console\Input\InputArgument;
use Symfony\Component\Console\Input\InputOption;

class SuluBuildCommand extends BuildCommand
    public function configure()

        // change the name of the command from "massive:build"

        // add an option
        $this->addOption('destroy', null, InputOption::VALUE_NONE, 'Destroy existing data');

Launching the build

You can launch all the builders with the following command:

$ php app/console massive:build

Launch a specific target:

$ php app/console massive:build mytarget

If you want to see which targets are available, use the --nobuild option:

$ php app/console massive:build --nobuild
Build Targets

| # | Builder  | Deps               |
| 0 | database |                    |
| 1 | phpcr    | database           |
| 2 | fixtures | database           |
| 3 | user     | database, fixtures |

By default if you specify a specific target, the build system will build any dependencies it has, to disable this use the --nodeps option.

$ php app/console massive:build --nodeps


  • Symfony: 2.4+