The current Ant file does compiles Platypus and plugins, runs unit tests, and creates the jars and the .zip file for distribution.
Continuous delivery (as described in the book, Continuous Delivery, by Jez Humble and David Farley, presents a highly automated process that includes running all tests, on all platforms, as well as validating the deployment package. To this end, the following steps would be ideal to include in the core Ant file. This mark indicates the task has been done.
- Convert Groovy acceptance tests to Groovy-based unit tests - Some example of to clarify this? Atul
I could take this up - Atul ;-)
- Upload reports from all tests to pz.org
- Run quality reports and upload those to the same site
- Verify that executable version contains pristine config file
- Create the three downloadables:
- Binaries with User Guide
- User Guide only
- Source code with Javadoc
- Nightly upload to Platypus website (on days when check-ins occur)
- Validate deployment package by upload to Windows, Linux, and other platforms, via VMs or the cloud.
- Platypus PDF plugin won't run on GAE. However, other plugins might. Test this and check for viability.
- Explore Amazon EC2 and/or Rackspace as alternate
- Run -fontlist
- Create a PDF document (and validate contents)
- Create an HTML document (and validate contents)
- Automate Javadoc
- Automate production of User Manual