PHPackages silverstripe/buildtools - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [DevOps & Deployment](/categories/devops) 4. / 5. silverstripe/buildtools AbandonedLibrary[DevOps & Deployment](/categories/devops) silverstripe/buildtools ======================= Phing build tools for the SilverStripe project 83.4k5[4 issues](https://github.com/silverstripe-archive/silverstripe-buildtools/issues)PHP Since Jun 4Pushed 9y agoCompare [ Source](https://github.com/silverstripe-archive/silverstripe-buildtools)[ Packagist](https://packagist.org/packages/silverstripe/buildtools)[ RSS](/packages/silverstripe-buildtools/feed)WikiDiscussions master Synced 1mo ago READMEChangelogDependenciesVersions (1)Used By (0) Phing Buildtools for the SilverStripe Project ============================================= [](#phing-buildtools-for-the-silverstripe-project) **DEPRECATED These tools have been replaced by the [cow release tool](https://github.com/silverstripe/cow)** Overview -------- [](#overview) The goal of this project is to aid SilverStripe developers in automating various aspects of their build through [phing](http://phing.info). The tools are designed to run as a standalone package, pulling the modules to be packaged from Packagist. It is primarily geared towards core developers preparing a SilverStripe release, but can also be a starting point for custom build setups. Notable features: - Creating and uploading release archives - Multi-module tagging and checkout of tags and branches - Multi-module changelogs with automatic sorting by "commit tags" The phing targets are generally compatible with SilverStripe 2.4 and newer. Installation ------------ [](#installation) Install buildtools into a local directory: ``` composer create-project silverstripe/buildtools ``` Usage ----- [](#usage) Run `vendor/bin/phing -l` to see a full list of available targets, and `vendor/bin/phing help` for in-depth help. The most important command is `vendor/bin/phing release`. It roughly takes the following steps: - Checks out the base release branch (e.g. `3.1`) for core modules and the installer - Ensures no local changes are present - Writes a combined changelog from core modules, and pushes the committed Markdown file - Tags core modules and pushes those tags - Temporarily overwrites the `composer.json` version constraints with the new tag, and generates a `composer.lock` file by running `composer update` - Pushes the `composer.lock` file, tags the release, and removes it again (it should just exist in the tag) - Creates archives (separately for cms+framework and standalone framework) - Uploads archives to `silverstripe.org` - Checks out the base release branch again **Caution:** The task uses a lot of `--force` in its git commands, for example overwriting existing tags. It is your responsibility to ensure tag overwrites should indeed take place. While you can generally abort and restart the release task, it is recommended to start with a fresh composer project each time you run it. License ------- [](#license) ``` Copyright (c) 2007-2014, SilverStripe Limited - www.silverstripe.com All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of SilverStripe nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ``` ### Health Score 25 — LowBetter than 37% of packages Maintenance10 Infrequent updates — may be unmaintained Popularity25 Limited adoption so far Community15 Small or concentrated contributor base Maturity41 Maturing project, gaining track record Bus Factor1 Top contributor holds 87.5% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Community Maintainers ![](https://www.gravatar.com/avatar/b0cba8b534e20e6ab4fff555a97b237a18436ebca1446fc0b29c8a8b504038b9?d=identicon)[GuySartorelli](/maintainers/GuySartorelli) ![](https://avatars.githubusercontent.com/u/111025?v=4)[Ingo Schommer](/maintainers/chillu)[@chillu](https://github.com/chillu) ![](https://www.gravatar.com/avatar/be6648e60fbab6f70bfc34dd8c14259562d28a47510a934ea9c01fe98633f3c2?d=identicon)[sminnee](/maintainers/sminnee) --- Top Contributors [![chillu](https://avatars.githubusercontent.com/u/111025?v=4)](https://github.com/chillu "chillu (49 commits)")[![dhensby](https://avatars.githubusercontent.com/u/563596?v=4)](https://github.com/dhensby "dhensby (3 commits)")[![mateusz](https://avatars.githubusercontent.com/u/118653?v=4)](https://github.com/mateusz "mateusz (3 commits)")[![halkyon](https://avatars.githubusercontent.com/u/138450?v=4)](https://github.com/halkyon "halkyon (1 commits)") ### Embed Badge ![Health badge](/badges/silverstripe-buildtools/health.svg) ``` [![Health](https://phpackages.com/badges/silverstripe-buildtools/health.svg)](https://phpackages.com/packages/silverstripe-buildtools) ``` ### Alternatives [deployer/deployer Deployment Tool 11.1k25.4M207](/packages/deployer-deployer)[appwrite/server-ce End to end backend server for frontend and mobile apps. 55.3k84.2k](/packages/appwrite-server-ce)[pragmarx/health Laravel Server & App Health Monitor and Notifier 2.0k1.0M2](/packages/pragmarx-health)[felixfbecker/language-server-protocol PHP classes for the Language Server Protocol 22476.7M6](/packages/felixfbecker-language-server-protocol)[heroku/heroku-buildpack-php Toolkit for starting a PHP application locally, with or without foreman, using the same config for PHP and Apache2/Nginx as on Heroku 8161.3M10](/packages/heroku-heroku-buildpack-php)[tiamo/phpas2 PHPAS2 is a php-based implementation of the EDIINT AS2 standard 4674.7k](/packages/tiamo-phpas2) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)