Fundraising/Cluster/Civicrm staging server
Overview
The staging server is part of fr-techs fundraising cluster. The database on it is manually updated from live every few months. The server is configured for some ticket in code review. The quick and effective to see whether the pr is working.
Deploying to staging
You can pull the commit on to frdev1002. From the gerrit page for your change, click the Download dropdown in the top right, select "anonymous http" in the panel that appears, and copy the second command, labeled "Cherry Pick".
Then on frdev1001, paste it into the staging CiviCRM directory, e.g.
cd /srv/org.wikimedia.civicrm
- then pasted the command copied from gerrit, something like below
git fetch "https://gerrit.wikimedia.org/r/a/wikimedia/fundraising/crm/civicrm" refs/changes/24/513024/1 && git cherry-pick FETCH_HEAD
- After pull the pr from gerrit, run `wmf-cv flush` to flush system cache.
- After that we can run any wmf-cv cmd to do the testing from recent PR
- Run `mysql dev_civicrm` to check the staging database.
- then you can make comparison with the civicrm and the dev_civicrm to see how staging works for the new pr you pulled in.
If you want to pull a CiviCRM core PR onto staging:
- you can make a patch locally if you have core as a remote for a git repo in /core:
git fetch origin pull/35212/head && git cherry-pick FETCH_HEAD && git format-patch HEAD^
- or you can get a patch from github by adding .patch to the end of a PR's URL.
- then on staging in wmf:
git apply --directory core your.patch
Permissions issues
If you run into a permissions issue because of a patch or checkout that someone else applied previously, you can run civicrm_fix_dev_perms to make all dirs under /srv/org.wikimedia.civicrm to be group writable.