Update Pantheon's Upstream

Update Pantheon's Upstream

1. Go to upstream test site, uls-upstream-test

   • Make sure the test site has the latest upstream.
   • If site needs to be updated. Apply the upstream. Create a local instance. Run composer install. Commit and push the changes created by running composer install.

2. Click on admin development site (make sure the site is in SFTP mode, so you can check what plugins need to be updated)

3. Check plugins updates, core updates, and core theme updates to be added to the new upstream

4. Go to Wordpress (WP) dashboard and click on updates to check plugins compatibility with WordPress core latest version installed in your wp instance

5. Create local repo of the upstream, ci-jenkins-pantheon-wordpress

   git clone git@github.com:cul-it/ci-jenkins-pantheon-wordpress.git
   

   I am using SourceTree as my git GUI, but you can use terminal or your prefered git client.

6. Open Sourcetree and double click REMOTES > origin > master to get a local master branch under your local branches

7. Click on Git Flow button and hit OK

8. Select your local develop branch

9. Create a new feature, ex: "wordpress_update"

10. In your code editor, open your local upstream repo ci-jenkins-pantheon-wordpress's folder

11. Open changelog.md and update plugins, culu theme, paid plugins, custom plugins, core wp updates, or remove plugins. If you need to updated paid plugin, update them in their respectives repos

12. Open composer.json file and update this file based on the changes of the changelog.md file

13. Go to terminal

    rm composer.lock
    

14. Then run

    composer install
    

If you get this error:

Fatal error: Allowed memory size of 1610612736 bytes exhausted (tried to allocate 4096 bytes) in phar:///usr/local/bin/composer.phar/src/Composer/DependencyResolver/RuleWatchGraph.php on line 52

Type, export COMPOSER_MEMORY_LIMIT=-1, for fixing the error and then run again, composer install

15. Go to sourcetree and commit yout changes

16. Click git flow and finish the feature created

17. On development branch push to remote development branch

18. After that jenkings will kick off a job

Then go to patheon and check [Continuous Integration Jenkins Pantheon Wordpress] (https://dashboard.pantheon.io/sites/a700ef3d-b210-44c1-8563-68a10650aa74#dev/code) Jenkins will create a multidev env and merge into dev. Check jenkins jobs number which will be the name of the muiltidev branch.

If job runs succesfullty go to develop branch on ci-jenkins-pantheon-wordpress

19. Create a new release.

20. Push to the release you have created

21. Go to git flow and finish current release

22. Name your tag. Ex: New upstream version

23. Go to master branch and push to github master. Jenkin will run again over the master branch.

24. If test is successful go to wp-ci-library-cornell-edu and see if there is a new upstream.

25. Apply upstream