The demo sites are constructed when Jenkins periodically calls buildkit's civibuild command. Sites follow a naming convention, e.g.
- Build description: Drupal ("d") with CiviCRM 4.4.
- Build type / build alias: d44
- URL: http://d44.demo.civicrm.org
Creating a new demo site falls into a few steps. For this document, we'll assume that you want to add a demo for Drupal with Civi v9.9 ("d99" aka "d99.demo.civicrm.org").
Build aliases are defined in src/civibuild.aliases.sh. Build types are defined in app/config.
If it's not already present, add "d99" to civibuild.aliases.sh. You should probably test the new build-alias locally to ensure that it works:
civibuild create d99 --url http://d99.localhost
Submit and merge any changes to buildkit.
If you've made changes to the build aliases or build types, then:
ssh www-demo.civicrm.osuosl.org
sudo -u webeditor -H bash
cd /srv/buildkit
git pull
bin/civi-download-tools
Make sure DNS for d99.demo.civicrm.org points to the www-demo server.
nslookup www-demo.civicrm.osuosl.org
nslookup d99.demo.civicrm.org
And make vhost files:
ssh www-demo.civicrm.osuosl.org
sudo bash
cd /etc/apache2/sites-available/
cp {d44,d99}.demo.civicrm.org.offline
cp {d44,d99}.demo.civicrm.org.online
vi d99.demo.civicrm.org.{online,offline}
- Navigate to the demo job on test.civicrm.org.
- Click "Configure"
- In the BLDNAME axis, add a row for "d99"
- Save
The job on Jenkins should run periodically by itself, but you may want test it manually:
- Click "Build with parameters"
- Check "d99". Uncheck everything else.
- Run the build. Watch the console to make sure it works.