Alright! You've made your changes and you're ready to do some end-to-end testing. In other words, you want to build pestle's
.phar file and see if your stuff actually works.
Pestle uses the venerable phing build tool to create its
phar file. Unfortunately, when PHP started shipping with the ini setting
phar.readonly set to
1, they semi-broke our build system. In order to build a
.phar, you'll need to invoke
phing with the following.
$ php -d phar.readonly=0 vendor/bin/phing package_phar
This uses the PHP
-d command line option to set the
phar.readonly=0 value to zero, and then invokes the
package_phar build step.
Once this command finishes running, you should have a brand new
pestle.phar in your root project directory.
$ ls pestle.phar pestle.phar
Build a Release
Right now the release process is only semi-automated. We're working towards 100% automation, but something something cobbler's children.
To build a release, we
- Create a fresh clone of the repo
- Update the version string in
- Build the library by running
- Commit your changes.
- Tag the current commit with the version from #3
- Push the tags (
git push --tags)
- Check Travis
- Once travis is passing, run
build.shto build the latest
- Upload the
- Once uploaded, make a copy in the form of pestle-x-x-x.phar to capture the version
Right now, every step here can be completed by anyone except #10 and #11, which requires access credentials to pestle.pulsestorm.net.
If you love build systems and have opinions on way to automate this, your feedback and participation is welcome.