Dino
Forum Replies Created
-
@devnihil Thanks for your reply. Yes, I mean specifically for the update. We test it on a development server before going to production. We have the Yoast version 13.3 running in production today.
Here is an overview of our process for updating the plugin:
1 – Download latest version of Yoast
2 – Remove yoast plugin directory in our repository
3 – Copy/ Extract the updated-yoast-plugin.zip inside plugins directory
4 – Stage and commit the updated-yoast-plugin
5 – Build Dev (dev branch) to test in development environment
6 – Merge dev-> master (if dev was successful)
7 – Build productionOur process stops at the stage 5.When we update via admin, it goes well, that’s is why I asked about any process during update made via admin interface.
Thanks in advance!
Thanks for your reply @onlyincebu
Since we update via build process using Jenkis, we download the plugin directly from Yoast and extract it locally on our repository. We made several validations (diff and md5 hash comparing downloaded latest version), and the plugin used in the build process of our application wasn’t corrupted.
Untill the version 13.3 we didn’t experience any problems with our deploys via Jenkis.
Just to make sure: Is there any process that happens when you install the plugin via admin?
Thanks for your answer @priscillamc
We compared the plugin files (diff) after the build process with the files from the manual update, there were no differences between them, so we assumed the files were ok.
Is there any process that happens during the update via admin interface that could impact this?
Once again, thanks in advance!