I like transparency. I also like repeatable processes – once you have a repeatable process, you can measure and you can improve.
To that end, here is our plugin deployment process:
- Develop fixes, features on your local environment
- Commit changes and edits to your local repository against the relevant Jira issue
- Once you have a complete package you are happy to deliver, ensure you update the version number in the main file of the plugin
- Request a pull (or push if you have priviliges) to the relevant Bitbucket repository for the plugin
- Create a zip of the plugin (if you’re zipping from your local repo, remember to delete the .git folder from the zip)
- Test the new plugin on debug.wpintense.com where we have extensive logging, monitoring and regression testing
- Once confirmed ready, upload the zip file to the wpintense plugins folder and edit the relevant .json file to include the updated version number
- Test the automatic update works properly using demo.wpintense.com (all our plugins are installed there)
He is always on at least one of his computers when he's awake, so get in touch and he'll get right back to you.
Latest posts by Dave Hilditch (see all)
- Installing and configuring the fastest possible WordPress stack on Ubuntu 16.04 - June 12, 2017
- My apologies for a rant you just received from a former contractor - June 6, 2017
- Why is wpintense a scam? - June 6, 2017