• Diff for "AutoPkg/Contributing/Checklist"
Last updated at 2021-05-04 13:35:21 by ouit0213
Differences between revisions 1 and 10 (spanning 9 versions)
⇤ ← Revision 1 as of 2016-06-20 12:42:00 →
Size: 1269
Editor: ouit0354
Comment:
← Revision 10 as of 2017-06-21 10:51:36 → ⇥
Size: 1768
Editor: oucs0162
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
 0. Merge the pull request into the master branch of the relevant repository, which closes the pull request.
 0. On the [[AutoPkg/BuildHost|build host]], do a git pull in the relevant repository's local directory.
 0. Run {{{sudo -u autopkg autopkg run RecipeName.munki}}} to run the recipe and import its output into Munki on the [[AutoPkg/BuildHost|build host]].		  0. Merge the pull request into the master branch of the relevant repository using the green button on Github, which closes the pull request.
 0. On the [[Infrastructure/BuildHost|build host]], do a {{{sudo -u autopkg git pull}}} in the relevant repository's local directory.
 0. 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.
 0. 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 [[Infrastructure/BuildHost|build host]].
 0. Run {{{sudo -u autopkg autopkg run RecipeName.munki}}} to run the recipe and import its output into Munki on the [[Infrastructure/BuildHost|build host]].
Line 9: Line 11:
 0. Now add the munki recipe to the autobuild - create a symbolic link to it in the {{{/srv/autopkg/BuildRecipes}}} folder on the [[AutoPkg/BuildHost|build host]].
 0. Finally create the entry for the software in the relevant section(s) in the manifest(s) on the [[Munki/MunkiHost|munki host]].		  0. 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]].

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:

  1. Merge the pull request into the master branch of the relevant repository using the green button on Github, which closes the pull request.

  2. On the build host, do a sudo -u autopkg git pull in the relevant repository's local directory.

  3. 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.

  4. 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.

  5. Run sudo -u autopkg autopkg run RecipeName.munki to run the recipe and import its output into Munki on the build host.

  6. 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)

  7. Now add the munki recipe/override to the autobuild - create a symbolic link to it in the /srv/autopkg/BuildRecipes folder on the build host.

  8. Finally create the entry for the software in the relevant section(s) in the manifest(s) on the munki host.

  9. Inform the author of the recipes that the software is now available in the Orchard Software Centre and to test.
Orchard is a close co-operation of
JOIN US