Skip to content

Build Targets

Jump to bottom
jaswrks edited this page Aug 24, 2017 · 24 revisions

For All Project Contributors

Build-Related Targets

  • $ phing or $ phing build (default). This runs all build-related routines, except for i18n-pots.xml. Another difference is that version-tokens.xml that would normally run in the base directory when doing a full build, is excluded, and instead version-tokens.xml runs in the ~.build directory only, which means that it only impacts the final zip.

    Note: version-tokens.xml will force a version bump using %y%m%d.%now notation in the final build directory; i.e., it forces a version change (in the zip file) from one build to the next — making this the proper way to build for testing purposes. If you need to force a specific version, you can override this behavior using the following.

    $ phing build -D _project_build_version=XXXXXX

  • $ phing build-lite Same as $ phing build, but for lite variation.

  • $ phing build-all Alias for $ phing build and $ phing build-lite together.

Feature-Related Targets

For a Project's Lead Developer

Build-Related Targets

  • $ phing full-build This runs all build-related routines.
  • $ phing full-build-lite This runs all build-related routines for the lite variation.
  • $ phing full-build-all This is a shortcut for $ phing full-build and $ phing full-build-lite.

Release-Related Targets

See also: https://github.com/websharks/phings/wiki/AWS-Uploads

Bleeding Edge Targets

Codex-Related Targets

  • $ phing codex Builds a Codex for the project; based on docBlocks.

For a Git post-receive Handler

  • $ phing post-receive-build Runs only the Composer target at this time.

For a CI Server

  • $ phing test Runs all configured tests for a project.

See also: src/psr4/targets.xml where additional details can be reviewed if you like.

Clone this wiki locally