Adobe Creative Cloud Updates

aamporter setup

The updates to Creative Cloud apps are imported into the Orchard munki repository from the autopkg build host using Tim Suttons tool aamporter. Currently there is a folder named /srv/munki/aamporter on stelmaria.oucs.ox.ac.uk which contains:

• the aamporter script (the folder is a git clone of the Github repo so can git pull if it is updated.

• a number of plists that were generated by running aamporter.py --build-product-plist [path/to/CCP/pkg/file.ccp] [--munki-update-for BaseProductPkginfoName] on each of the CC apps generated with Creative Cloud Packager.

• a plist for aamporter itself which contains the following settings:

   1 <?xml version="1.0" encoding="UTF-8"?>
   2 <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
   3 <plist version="1.0">
   4 <dict>
   5         <key>munkiimport_options</key>
   6         <array>
   7                 <string>--catalog=testing</string>
   8         </array>
   9         <key>munki_repo_destination_path</key>
  10         <string>Adobe_CC_2015/Updates</string>
  11 </dict>
  12 </plist>

Importing into munki

Run the shell script (important: as the autopkg user!) sudo -u autopkg -i /srv/munki/orchard_repo/autoaamporter.sh (this is not part of aamporter but is a wrapper to automate it) which does the following:

   1 #!/bin/bash
   2 
   3 ls -G /srv/munki/aamporter/Adobe* | xargs /srv/munki/aamporter/aamporter.py --munkiimport --make-catalogs

This will send each product plist to aamporter where it will figure out which updates need downloading, download them if they are not cached and then import them into munki according to aamporter.plist (therefore into the testing catalog), and finally running makecatalogs.