Diff for "AutoPkg/Contributing/Checklist"

Differences between revisions 9 and 11 (spanning 2 versions)

Post-Acceptance Checklist for Orchard Administrators

After you have deemed a new set of autopkg recipes meet our guidelines and perform as they should, do the following:

Merge the pull request into the master branch of the relevant repository using the green button on Github, which closes the pull request.
On the build host, do a sudo -u autopkg git pull in the relevant repository's local directory.
If this is in the orchard-recipes repo, please also do a sudo -u autopkg git push autopkg master to update the version in the main autopkg repo. This does not need to be done for overrides, or private recipes.
Upload a 256x256 png file of the icon, named the same as the munki pkginfo's Name key to /srv/munki/orchard_repo/icons on the build host.
Run sudo -u autopkg autopkg run RecipeName.munki to run the recipe and import its output into Munki on the build host.
If this runs without problems, wait for the next munki-staging run (00 and 30 minutes past the hour) to complete and then move the resultant pkg to 'To Stable' on Trello (the first version of a pkg is always considered stable, future versions should be staging into testing if the recipe is correct)
Now add the munki recipe/override to the autobuild - create a symbolic as the autopkg user, link to it in the /srv/autopkg/BuildRecipes folder on the build host.
Finally create the entry for the software in the relevant section(s) in the manifest(s) /srv/munki/orchard_repo/manifests on the build host].
Inform the author of the recipes that the software is now available in the Orchard Software Centre and to test.

-  ⇤ ← Revision 9 as of 2017-06-21 10:50:23 → 
  Size: 1769
  Editor: oucs0162
  Comment:
+   ← Revision 11 as of 2018-01-25 14:34:55 → ⇥
  Size: 1830
  Editor: ouit0213
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 7:
-. If this is in the ```orchard-recipes``` repo, please allso do a {{{sudo -u autopkg git push autopkg master}}} to update the version in the main autopkg repo. This does not need to be done for overrides, or private recipes.
+. If this is in the ```orchard-recipes``` repo, please also do a {{{sudo -u autopkg git push autopkg master}}} to update the version in the main autopkg repo. This does not need to be done for overrides, or private recipes.
 Line 11:
-. Now add the munki recipe/override to the autobuild - create a symbolic link to it in the {{{/srv/autopkg/BuildRecipes}}} folder on the [[Infrastructure/BuildHost|build host]].
 0. Finally create the entry for the software in the relevant section(s) in the manifest(s) on the [[Infrastructure/MunkiHost|munki host]].
+. Now add the munki recipe/override to the autobuild - create a symbolic as the autopkg user, link to it in the {{{/srv/autopkg/BuildRecipes}}} folder on the [[Infrastructure/BuildHost|build host]].
 0. Finally create the entry for the software in the relevant section(s) in the manifest(s) {{{/srv/munki/orchard_repo/manifests}}} on the [[Infrastructure/BuildHost|build host]]].