Package Selection

Package Selection

Summary

When deploying the Chocolatey for Business Azure Environment, you are prompted to select packages to internalize.

This page shows the packages we bundle as recommendations, and discusses how to source other packages to automatically publish to your new Chocolatey for Business Azure Environment.

Recommendations

We provide bundles of packages that are commonly used by Chocolatey for Business customers:

Bundle Contains
All Google Chrome
Mozilla Firefox
Microsoft Edge
Microsoft VS Code
Microsoft PowerShell
Microsoft Office 365 ProPlus
Notepad++
Adobe Reader
Slack
Microsoft Teams
Zoom
Google Drive
Microsoft OneDrive
Skype
VSCode PowerShell
Git
GIMP
VLC
SysInternals
Azure-CLI
AzCopy
1password
PuTTY
Java Runtime Environment
Minimal Google Chrome
Microsoft Edge
Microsoft VS Code
Microsoft PowerShell
Microsoft Office 365 ProPlus
Notepad++
Adobe Reader
Slack
Microsoft Teams
Zoom
None -

You can remove any of these packages from your repository without using them by logging into Nexus, browsing to the ChocolateyTest and ChocolateyInternal repositories, and deleting the package from each.

Custom Packages

You can add custom packages using the Specify any other packages textbox.

Please provide these as a comma-separated list, e.g.

nexus-repository, notepadplusplus, sublimetext3

:choco-warning: WARNING

We recommend you review and test all packages before internalizing and deploying them from the Chocolatey Community Repository.

Adding Packages Post-Deployment

You can download and internalize packages after the deployment of your environment.

To do so, log into Jenkins at https://<FQDN>/jenkins, and click the Schedule a Build... icon on the right of the Internalize packages from the Community Repository job. This will take you to a screen where you can add Package IDs as a semicolon-separated list to the P_PKG_LIST parameter, e.g.

nexus-repository; notepadplusplus; sublimetext3

Start the internalize job by clicking Build.

The specified packages will then be downloaded and pushed to your ChocolateyTest repository, ready for testing, and then be promoted to the ChocolateyInternal repository either by you or by the Update production repository job.

There are further details on these default jobs here.