Step 1: Review Your Packages

Step 2: Choose Your Integration Method

Step 3: Copy Your Script or Download Config

Option 1: Copy Script

Option 2: Download Config

Step 4: Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)

Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the packages and push them to a repository
  Download Packages

Option 2: Internalized Package (Reliable, Scalable)

Open Source
- Download the packages:
  Download Packages
- Follow manual internalization instructions
Package Internalizer (C4B)
- Run: (additional options)
- For package and dependencies run:
- Automate package internalization

Step 5: Copy Your Script

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###

#### We initialize a few things that are needed by this script - there are no other requirements.
$ErrorActionPreference = "Stop"

#### Set TLS 1.2 (3072) as that is the minimum required by various up-to-date repositories.
#### Use integers because the enumeration value for TLS 1.2 won't exist
#### in .NET 4.0, even though they are addressable if .NET 4.5+ is
#### installed (.NET 4.5 is an in-place upgrade).
[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072

#### We use this variable for future REST calls.
$RequestArguments = @{
    UseBasicParsing = $true
}

## 2. TOP LEVEL VARIABLES ##

### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$NugetRepositoryUrl = "INTERNAL REPO URL"

### b. Internal Repository Credential ###
#### If required, add the repository access credential here
# $NugetRepositoryCredential = [PSCredential]::new(
#     "username",
#     ("password" | ConvertTo-SecureString -AsPlainText -Force)
# )
# $RequestArguments.Credential = $NugetRepositoryCredential

### c. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it
$ChocolateyDownloadUrl = "$($NugetRepositoryUrl.TrimEnd('/'))/package/chocolatey.2.4.0.nupkg"

### d. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService"

#### ii. If using a Client Salt, add it here
# $ChocolateyCentralManagementClientSalt = "clientsalt"

#### iii. If using a Service Salt, add it here
# $ChocolateyCentralManagementServiceSalt = "servicesalt"

## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository

#### Download the Nupkg, appending .zip to the filename to handle archive cmdlet limitations
if (-not (Get-Command choco.exe -ErrorAction SilentlyContinue)) {
    $TempDirectory = Join-Path $env:Temp "chocolateyInstall"
    if (-not (Test-Path $TempDirectory -PathType Container)) {
        $null = New-Item -Path $TempDirectory -ItemType Directory
    }
    $DownloadedNupkg = Join-Path $TempDirectory "$(Split-Path $ChocolateyDownloadUrl -Leaf).zip"
    Invoke-WebRequest -Uri $ChocolateyDownloadUrl -OutFile $DownloadedNupkg @RequestArguments

    #### Extract the Nupkg, and run the chocolateyInstall script
    if (Get-Command Microsoft.PowerShell.Archive\Expand-Archive -ErrorAction SilentlyContinue) {
        Microsoft.PowerShell.Archive\Expand-Archive -Path $DownloadedNupkg -DestinationPath $TempDirectory -Force
    } else {
        # PowerShell versions <4.0 do not have this function available
        try {
            $shellApplication = New-Object -ComObject Shell.Application
            $zipPackage = $shellApplication.NameSpace($DownloadedNupkg)
            $destinationFolder = $shellApplication.NameSpace($TempDirectory)
            $destinationFolder.CopyHere($zipPackage.Items(), 0x10)
        } catch {
            Write-Warning "Unable to unzip package using built-in compression."
            throw $_
        }
    }

    & $(Join-Path $TempDirectory "tools\chocolateyInstall.ps1")
}

if (-not (Get-Command choco.exe -ErrorAction SilentlyContinue)) {
    refreshenv
}

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# choco feature enable -n useFipsCompliantChecksums

### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
choco config set --name cacheLocation --value C:\ProgramData\chocolatey\cache

#### Increase timeout to at least 4 hours
choco config set --name commandExecutionTimeoutSeconds --value 14400

#### Turn off download progress when running choco through integrations
choco feature disable --name showDownloadProgress

### c. Sources ###
#### Remove the default community package repository source
choco source list --limitoutput | ConvertFrom-Csv -Header 'Name', 'Location' -Delimiter '|' | ForEach-Object {
    if ($_.Location -eq 'https://community.chocolatey.org/api/v2/') {
        choco source remove -n $_.Name
    }
}

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here

#### NOTE: This EXAMPLE may require changes
if ($NugetRepositoryCredential) {
    choco source add --name ChocolateyInternal --source $NugetRepositoryUrl --user $NugetRepositoryCredential.UserName --password $NugetRepositoryCredential.GetNetworkCredential().Password --priority 1
} else {
    choco source add --name ChocolateyInternal --source $NugetRepositoryUrl --priority 1
}

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
choco upgrade chocolatey --confirm

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
choco install chocolatey-license --source $NugetRepositoryUrl --confirm

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
if ("chocolatey-license" -in (choco list --localonly --limitoutput | ConvertFrom-Csv -Header "Name" -Delimiter "|").Name) {
    choco source disable --name chocolatey.licensed
} else {
    Write-Warning "Not disabling 'chocolatey.licensed' feed, as Chocolatey-License has not been installed."
}

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
if ("chocolatey-license" -in (choco list --localonly --limitoutput | ConvertFrom-Csv -Header "Name" -Delimiter "|").Name) {
    choco install chocolatey.extension --source $NugetRepositoryUrl --confirm
} else {
    Write-Warning "Not installing 'chocolatey.extension', as Chocolatey-License has not been installed."
}

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
choco feature disable --name showNonElevatedWarnings
choco feature enable --name useBackgroundService
choco feature enable --name useBackgroundServiceWithNonAdministratorsOnly
choco feature enable --name allowBackgroundServiceUninstallsFromUserInstallsOnly
choco config set --name allowedBackgroundServiceCommands --value "install,upgrade,uninstall"

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if ($ChocolateyCentralManagementUrl) {
    choco install chocolatey-agent --source $NugetRepositoryUrl --confirm
    choco config set --name CentralManagementServiceUrl --value $ChocolateyCentralManagementUrl
    if ($ChocolateyCentralManagementClientSalt) {
        choco config set --name centralManagementClientCommunicationSaltAdditivePassword --value $ChocolateyCentralManagementClientSalt
    }
    if ($ChocolateyCentralManagementServiceSalt) {
        choco config set --name centralManagementServiceCommunicationSaltAdditivePassword --value $ChocolateyCentralManagementServiceSalt
    }
    choco feature enable --name useChocolateyCentralManagement
    choco feature enable --name useChocolateyCentralManagementDeployments
}

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### i. chocolatey.chocolatey
##### You will require the chocolatey.chocolatey collection to be installed
##### on all machines using this playbook.
##### Please see https://github.com/chocolatey/chocolatey-ansible/#installing-the-collection-from-ansible-galaxy

- name: Install and Configure Chocolatey
  hosts: all

## 2. TOP LEVEL VARIABLES ##
  vars:

### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
    nuget_repository_url: INTERNAL REPO URL

### b. Internal Repository Credential ###
#### If required, add the repository access credential here and
#### uncomment lines with source_username and source_password below
#    nuget_repository_username: username
#    nuget_repository_password: password

### c. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
#    chocolatey_central_management_url: https://chocolatey-central-management:24020/ChocolateyManagementService

#### ii. If using a Client Salt, add it here
#    chocolatey_central_management_client_salt: clientsalt

#### iii. If using a Service Salt, add it here
#    chocolatey_central_management_service_salt: servicesalt

## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository

  tasks:
  - name: Install chocolatey
    win_chocolatey:
      name: chocolatey
      source: ""{{ nuget_repository_url }}""
      # source_username: ""{{ nuget_repository_username }}""
      # source_password: ""{{ nuget_repository_password }}""

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
#   - name: Enable FIPS compliance
#     win_chocolatey_feature:
#       name: useFipsCompliantChecksums
#       state: enabled

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
  - name: Set the cache location
    win_chocolatey_config:
      name: cacheLocation
      state: present
      value: C:\ProgramData\chocolatey\cache

#### Increase timeout to at least 4 hours
  - name: Set the command execution timeout
    win_chocolatey_config:
      name: commandExecutionTimeoutSeconds
      state: present
      value: 14400

#### Turn off download progress when running choco through integrations
  - name: Disable showing download progress
    win_chocolatey_feature:
      name: showDownloadProgress
      state: disabled

### c. Sources ###
#### Remove the default community package repository source
  - name: Remove Chocolatey Community Repository
    win_chocolatey_source:
      name: chocolatey
      state: absent

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE may require changes
  - name: Add Internal Repository
    win_chocolatey_source:
      name: ChocolateyInternal
      state: present
      source: {{ nuget_repository_url }}
      # source_username: {{ nuget_repository_username }}
      # source_password: {{ nuget_repository_password }}
      priority: 1

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
  - name: Upgrade Chocolatey
    win_chocolatey:
      name: chocolatey
      state: latest

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
  - name: Install Chocolatey License
    win_chocolatey:
      name: chocolatey-license
      source: ChocolateyInternal
      state: latest

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
  - name: Disable Chocolatey Community Repository
    win_chocolatey_source:
      name: chocolatey.licensed
      state: disabled

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
  - name: Install Chocolatey Extension
    win_chocolatey:
      name: chocolatey.extension
      source: ChocolateyInternal
      state: latest

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
  - name: Hide not-elevated warnings
    win_chocolatey_feature:
      name: showNonElevatedWarnings
      state: disabled

  - name: Use background mode for self-service
    win_chocolatey_feature:
      name: useBackgroundService
      state: enabled

  - name: Use background service for non-admins
    win_chocolatey_feature:
      name: useBackgroundServiceWithNonAdministratorsOnly
      state: enabled

  - name: Allow background uninstallation for user installs
    win_chocolatey_feature:
      name: allowBackgroundServiceUninstallsFromUserInstallsOnly
      state: enabled

  - name: Set allowed background service commands
    win_chocolatey_config:
      name: backgroundServiceAllowedCommands
      state: present
      value: install,upgrade,uninstall

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
  - name: Install Chocolatey Agent
    when: chocolatey_central_management_url is defined
    win_chocolatey:
      name: chocolatey-agent
      source: ChocolateyInternal
      state: latest

  - name: Set the Central Management Service URL
    when: chocolatey_central_management_url is defined
    win_chocolatey_config:
      name: CentralManagementServiceUrl
      state: present
      value: {{ chocolatey_central_management_url }}

  - name: Set the Central Management Client Salt
    when: chocolatey_central_management_client_salt is defined
    win_chocolatey_config:
      name: centralManagementClientCommunicationSaltAdditivePassword
      state: present
      value: {{ chocolatey_central_management_client_salt }}

  - name: Set the Central Management Service Salt
    when: chocolatey_central_management_service_salt is defined
    win_chocolatey_config:
      name: centralManagementServiceCommunicationSaltAdditivePassword
      state: present
      value: {{ chocolatey_central_management_service_salt }}

  - name: Use Central Management
    when: chocolatey_central_management_url is defined
    win_chocolatey_feature:
      name: useChocolateyCentralManagement
      state: enabled

  - name: Use Central Management Deployments
    when: chocolatey_central_management_url is defined
    win_chocolatey_feature:
      name: useChocolateyCentralManagementDeployments
      state: enabled

See docs at https://docs.chef.io/resource_chocolatey_package.html.

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### The Chocolatey resources are available with any recent version of Chef.
#### We utilise the Chocolatey recipe to install the Chocolatey binaries.
include_recipe "chocolatey"

## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
NugetRepositoryUrl = "INTERNAL REPO URL"

### b. Internal Repository Credential ###
#### If required, add the repository access credential here
# NugetRepositoryUsername = "username"
# NugetRepositoryPassword = "password"

### c. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
ChocolateyNupkgUrl = "INTERNAL REPO URL/package/chocolatey.2.4.0.nupkg",

### d. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService"

#### ii. If using a Client Salt, add it here
# ChocolateyCentralManagementClientSalt = "clientsalt"

#### iii. If using a Service Salt, add it here
# ChocolateyCentralManagementServiceSalt = "servicesalt"

## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
node['chocolatey']['install vars'] = {
  'chocolateyDownloadUrl' => "#{ChocolateyNupkgUrl}",
}

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# chocolatey_feature 'useFipsCompliantChecksums' do
#   action :enable
# end

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
chocolatey_config 'cacheLocation' do
  value 'C:\ProgramData\chocolatey\cache'
end

#### Increase timeout to at least 4 hours
chocolatey_config 'commandExecutionTimeoutSeconds' do
  value '14400'
end

#### Turn off download progress when running choco through integrations
chocolatey_feature 'showDownloadProgress' do
  action :disable
end

### c. Sources ###
#### Remove the default community package repository source
chocolatey_source 'chocolatey' do
  action :remove
end

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here

#### NOTE: This EXAMPLE may require changes
chocolatey_source 'ChocolateyInternal' do
  source "#{NugetRepositoryUrl}"
  priority 1
  action   :add
end

execute 'ChocolateyInternal' do
  command "choco source add --name ChocolateyInternal -s #{NugetRepositoryUrl} -u=#{NugetRepositoryUsername} -p=#{NugetRepositoryPassword} --priority=1"
  only_if { NugetRepositoryUsername != nil || NugetRepositoryPassword != nil }
end

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
chocolatey_package 'chocolatey' do
  action :upgrade
  source "#{NugetRepositoryUrl}"
end

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
chocolatey_package 'chocolatey-license' do
  action :install
  source "#{NugetRepositoryUrl}"
end

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
chocolatey_source 'chocolatey.licensed' do
  action            :disable
end

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
chocolatey_package 'chocolatey.extention' do
  action     install
  source     "#{NugetRepositoryUrl}"
end

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
chocolatey_feature 'showNonElevatedWarnings' do
  action :disable
end

chocolatey_feature 'useBackgroundService' do
  action :enable
end

chocolatey_feature 'useBackgroundServiceWithNonAdministratorsOnly' do
  action :enable
end

chocolatey_feature 'allowBackgroundServiceUninstallsFromUserInstallsOnly' do
  action :enable
end

chocolatey_config 'backgroundServiceAllowedCommands' do
  value 'install,upgrade,uninstall'
end

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
chocolatey_package 'chocolatey-agent' do
  action     install
  source     "#{NugetRepositoryUrl}"
  # user       "#{NugetRepositoryUsername}"
  # password   "#{NugetRepositoryPassword}"
  only_if { ChocolateyCentralManagementUrl != nil }
end

chocolatey_config 'CentralManagementServiceUrl' do
  value  "#{ChocolateyCentralManagementUrl}"
  only_if { ChocolateyCentralManagementUrl != nil }
end

chocolatey_config 'centralManagementClientCommunicationSaltAdditivePassword' do
  value   "#{ChocolateyCentralManagementClientSalt}"
  only_if { ChocolateyCentralManagementClientSalt != nil }
end

chocolatey_config 'centralManagementServiceCommunicationSaltAdditivePassword' do
  value   "#{ChocolateyCentralManagementServiceSalt}"
  only_if { ChocolateyCentralManagementServiceSalt != nil }
end

chocolatey_feature 'useChocolateyCentralManagement' do
  action :enable
  only_if { ChocolateyCentralManagementUrl != nil }
end

chocolatey_feature 'useChocolateyCentralManagementDeployments' do
  action :enable
  only_if { ChocolateyCentralManagementUrl != nil }
end

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.

If Applicable - Chocolatey Configuration/Installation


#requires -Modules cChoco
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### i. Requires chocolatey\cChoco DSC module to be installed on the machine compiling the DSC manifest
#### NOTE: This will need to be installed before running the DSC portion of this script
if (-not (Get-Module cChoco -ListAvailable)) {
    $null = Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
    if (($PSGallery = Get-PSRepository -Name PSGallery).InstallationPolicy -ne "Trusted") {
        Set-PSRepository -Name PSGallery -InstallationPolicy Trusted
    }
    Install-Module -Name cChoco
    if ($PSGallery.InstallationPolicy -ne "Trusted") {
        Set-PSRepository -Name PSGallery -InstallationPolicy $PSGallery.InstallationPolicy
    }
}

#### ii. Requires a hosted copy of the install.ps1 script
##### This should be available to download without authentication.
##### The original script can be found here: https://community.chocolatey.org/install.ps1

Configuration ChocolateyConfig {
## 2. TOP LEVEL VARIABLES ##
    param(
### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
        $NugetRepositoryUrl      = "INTERNAL REPO URL",

### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
        $ChocolateyNupkgUrl      = "INTERNAL REPO URL/package/chocolatey.2.4.0.nupkg",

### c. Internal Repository Credential ###
#### If required, add the repository access credential here
#        $NugetRepositoryCredential = [PSCredential]::new(
#            "username",
#            ("password" | ConvertTo-SecureString -AsPlainText -Force)
#        ),

### d. Install.ps1 URL
#### The path to the hosted install script:
        $ChocolateyInstallPs1Url = "https://community.chocolatey.org/install.ps1"

### e. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
#        $ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService",

#### ii. If using a Client Salt, add it here
#        $ChocolateyCentralManagementClientSalt = "clientsalt",

#### iii. If using a Service Salt, add it here
#        $ChocolateyCentralManagementServiceSalt = "servicesalt"
    )
    Import-DscResource -ModuleName PSDesiredStateConfiguration
    Import-DscResource -ModuleName cChoco

    Node 'localhost' {
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
        Environment chocoDownloadUrl {
            Name  = "chocolateyDownloadUrl"
            Value = $ChocolateyNupkgUrl
        }

        cChocoInstaller installChocolatey {
            DependsOn = "[Environment]chocoDownloadUrl"
            InstallDir = Join-Path $env:ProgramData "chocolatey"
            ChocoInstallScriptUrl = $ChocolateyInstallPs1Url
        }

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
#        cChocoFeature featureFipsCompliance {
#            FeatureName = "useFipsCompliantChecksums"
#        }

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
        cChocoConfig cacheLocation {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            ConfigName = "cacheLocation"
            Value      = "C:\ProgramData\chocolatey\cache"
        }

#### Increase timeout to at least 4 hours
        cChocoConfig commandExecutionTimeoutSeconds {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            ConfigName = "commandExecutionTimeoutSeconds"
            Value      = 14400
        }

#### Turn off download progress when running choco through integrations
        cChocoFeature showDownloadProgress {
            DependsOn   = "[cChocoInstaller]installChocolatey"
            FeatureName = "showDownloadProgress"
            Ensure      = "Absent"
        }

### c. Sources ###
#### Remove the default community package repository source
        cChocoSource removeCommunityRepository {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            Name       = "chocolatey"
            Ensure     = "Absent"
        }

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here.
#### NOTE: This EXAMPLE may require changes
        cChocoSource addInternalSource {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            Name        = "ChocolateyInternal"
            Source      = $NugetRepositoryUrl
            Credentials = $NugetRepositoryCredential
            Priority    = 1
        }

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
        cChocoPackageInstaller updateChocolatey {
            DependsOn   = "[cChocoSource]addInternalSource", "[cChocoSource]removeCommunityRepository"
            Name        = "chocolatey"
            AutoUpgrade = $true
        }

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
        cChocoPackageInstaller chocolateyLicense {
            DependsOn = "[cChocoPackageInstaller]updateChocolatey"
            Name      = "chocolatey-license"
        }

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
        Script disableLicensedSource {
            DependsOn  = "[cChocoPackageInstaller]chocolateyLicense"
            GetScript  = {
                $Source = choco source list --limitoutput | `
                    ConvertFrom-Csv -Delimiter '|' -Header Name, Source, Disabled | `
                    Where-Object Name -eq "chocolatey.licensed"

                return @{
                    Result = if ($Source) {
                        [bool]::Parse($Source.Disabled)
                    } else {
                        Write-Warning "Source 'chocolatey.licensed' was not present."
                        $true  # Source does not need disabling
                    }
                }
            }
            SetScript  = {
                $null = choco source disable --name "chocolatey.licensed"
            }
            TestScript = {
                $State = [ScriptBlock]::Create($GetScript).Invoke()
                return $State.Result
            }
        }

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
        cChocoPackageInstaller chocolateyLicensedExtension {
            DependsOn = "[Script]disableLicensedSource"
            Name      = "chocolatey.extension"
        }

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
        cChocoFeature hideElevatedWarnings {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "showNonElevatedWarnings"
            Ensure      = "Absent"
        }

        cChocoFeature useBackgroundService {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "useBackgroundService"
            Ensure      = "Present"
        }

        cChocoFeature useBackgroundServiceWithNonAdmins {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "useBackgroundServiceWithNonAdministratorsOnly"
            Ensure      = "Present"
        }

        cChocoFeature useBackgroundServiceUninstallsForUserInstalls {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "allowBackgroundServiceUninstallsFromUserInstallsOnly"
            Ensure      = "Present"
        }

        cChocoConfig allowedBackgroundServiceCommands {
            DependsOn   = "[cChocoFeature]useBackgroundService"
            ConfigName = "backgroundServiceAllowedCommands"
            Value       = "install,upgrade,uninstall"
        }

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
        if ($ChocolateyCentralManagementUrl) {
            cChocoPackageInstaller chocolateyAgent {
                DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
                Name      = "chocolatey-agent"
            }

            cChocoConfig centralManagementServiceUrl {
                DependsOn   = "[cChocoPackageInstaller]chocolateyAgent"
                ConfigName = "CentralManagementServiceUrl"
                Value       = $ChocolateyCentralManagementUrl
            }

            if ($ChocolateyCentralManagementClientSalt) {
                cChocoConfig centralManagementClientSalt {
                    DependsOn  = "[cChocoPackageInstaller]chocolateyAgent"
                    ConfigName = "centralManagementClientCommunicationSaltAdditivePassword"
                    Value      = $ChocolateyCentralManagementClientSalt
                }
            }

            if ($ChocolateyCentralManagementServiceSalt) {
                cChocoConfig centralManagementServiceSalt {
                    DependsOn  = "[cChocoPackageInstaller]chocolateyAgent"
                    ConfigName = "centralManagementServiceCommunicationSaltAdditivePassword"
                    Value      = $ChocolateyCentralManagementServiceSalt
                }
            }

            cChocoFeature useCentralManagement {
                DependsOn   = "[cChocoPackageInstaller]chocolateyAgent"
                FeatureName = "useChocolateyCentralManagement"
                Ensure      = "Present"
            }

            cChocoFeature useCentralManagementDeployments {
                DependsOn   = "[cChocoPackageInstaller]chocolateyAgent"
                FeatureName = "useChocolateyCentralManagementDeployments"
                Ensure      = "Present"
            }
        }
    }
}

# If working this into an existing configuration with a good method for
$ConfigData = @{
    AllNodes = @(
        @{
            NodeName                    = "localhost"
            PSDscAllowPlainTextPassword = $true
        }
    )
}

try {
    Push-Location $env:Temp
    $Config = ChocolateyConfig -ConfigurationData $ConfigData
    Start-DscConfiguration -Path $Config.PSParentPath -Wait -Verbose -Force
} finally {
    Pop-Location
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### i. Requires puppetlabs/chocolatey module
####  See https://forge.puppet.com/puppetlabs/chocolatey


## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$_repository_url = 'INTERNAL REPO URL'

### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
$_choco_download_url = 'INTERNAL REPO URL/package/chocolatey.2.4.0.nupkg'

### c. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $_chocolatey_central_management_url = 'https://chocolatey-central-management:24020/ChocolateyManagementService'

#### ii. If using a Client Salt, add it here
# $_chocolatey_central_management_client_salt = "clientsalt"

#### iii. If using a Service Salt, add it here
# $_chocolatey_central_management_service_salt = 'servicesalt'


## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
### Note: `chocolatey_download_url is completely different than normal
###  source locations. This is directly to the bare download url for the
###  chocolatey.nupkg, similar to what you see when you browse to
###  https://community.chocolatey.org/api/v2/package/chocolatey
class {'chocolatey':
  chocolatey_download_url => $_choco_download_url,
  use_7zip                => false,
}


## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations

#chocolateyfeature {'useFipsCompliantChecksums':
#  ensure => enabled,
#}

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
chocolateyconfig {'cacheLocation':
  value => 'C:\ProgramData\chocolatey\cache',
}

#### Increase timeout to at least 4 hours
chocolateyconfig {'commandExecutionTimeoutSeconds':
  value => '14400',
}

#### Turn off download progress when running choco through integrations
chocolateyfeature {'showDownloadProgress':
  ensure => disabled,
}

### c. Sources ###
#### Remove the default community package repository source
chocolateysource {'chocolatey':
  ensure   => absent,
  location => 'https://community.chocolatey.org/api/v2/',
}

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here

#### NOTE: This EXAMPLE requires changes
chocolateysource {'internal_chocolatey':
  ensure             => present,
  location           => $_repository_url,
  priority           => 1,
  username           => 'optional',
  password           => 'optional,not ensured',
  bypass_proxy       => true,
  admin_only         => false,
  allow_self_service => false,
}

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/

package {'chocolatey':
  ensure   => latest,
  provider => chocolatey,
  source   => $_repository_url,
}


## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/guides/organizations/organizational-deployment-guide#exercise-4-create-a-package-for-the-license

# TODO: Add resource for installing/ensuring the chocolatey-license package
package {'chocolatey-license':
  ensure   => latest,
  provider => chocolatey,
  source   => $_repository_url,
}

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
## Disabled sources still need all other attributes until
## https://tickets.puppetlabs.com/browse/MODULES-4449 is resolved.
## Password is necessary with user, but not ensurable, so it should not
## matter what it is set to here. If you ever do get into trouble here,
## the password is your license GUID.
chocolateysource {'chocolatey.licensed':
  ensure   => disabled,
  priority => '10',
  user     => 'customer',
  password => '1234',
  require  => Package['chocolatey-license'],
}

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
package {'chocolatey.extension':
  ensure   => latest,
  provider => chocolatey,
  source   => $_repository_url,
  require  => Package['chocolatey-license'],
}

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
chocolateyfeature {'showNonElevatedWarnings':
  ensure => disabled,
}

chocolateyfeature {'useBackgroundService':
  ensure => enabled,
}

chocolateyfeature {'useBackgroundServiceWithNonAdministratorsOnly':
  ensure => enabled,
}

chocolateyfeature {'allowBackgroundServiceUninstallsFromUserInstallsOnly':
  ensure => enabled,
}

chocolateyconfig {'backgroundServiceAllowedCommands':
  value => 'install,upgrade,uninstall',
}

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if $_chocolatey_central_management_url {
  package {'chocolatey-agent':
    ensure   => latest,
    provider => chocolatey,
    source   => $_repository_url,
    require  => Package['chocolatey-license'],
  }

  chocolateyconfig {'CentralManagementServiceUrl':
    value   => $_chocolatey_central_management_url,
  }

  if $_chocolatey_central_management_client_salt {
    chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword':
      value => $_chocolatey_central_management_client_salt,
    }
  }

  if $_chocolatey_central_management_service_salt {
    chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword':
      value => $_chocolatey_central_management_client_salt,
    }
  }

  chocolateyfeature {'useChocolateyCentralManagement':
    ensure  => enabled,
    require => Package['chocolatey-agent'],
  }

  chocolateyfeature {'useChocolateyCentralManagementDeployments':
    ensure  => enabled,
    require => Package['chocolatey-agent'],
  }
}

Need Help? View our docs or file an issue.

There is already a version of this package in your Script Builder

Current Version	New Version

Downloads:

5,488

Downloads of v 7.0.3212:

401

Last Update:

04 Apr 2022

Package Maintainer(s):

mkevenaar

Software Author(s):

Appveyor Systems Inc.

Tags:

appveyor-server admin

AppVeyor Server (Team Edition)

7.0.3212 | Updated: 04 Apr 2022

Downloads:

5,488

Downloads of v 7.0.3212:

401

Maintainer(s):

mkevenaar

Software Author(s):

Appveyor Systems Inc.

Tags:

appveyor-server admin

AppVeyor Server (Team Edition) 7.0.3212

Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Appveyor Systems Inc. The inclusion of Appveyor Systems Inc. trademark(s), if any, upon this webpage is solely to identify Appveyor Systems Inc. goods or services and not for commercial purposes.

All Checks are Passing

3 Passing Tests

Show Checks

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install AppVeyor Server (Team Edition), run the following command from the command line or from PowerShell:

To upgrade AppVeyor Server (Team Edition), run the following command from the command line or from PowerShell:

To uninstall AppVeyor Server (Team Edition), run the following command from the command line or from PowerShell:

NOTE

This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)

Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download

Option 2: Internalized Package (Reliable, Scalable)

Open Source
- Download the package:
  Download
- Follow manual internalization instructions

Package Internalizer (C4B)

Run: (additional options)

choco download appveyor-server --internalize --source=https://community.chocolatey.org/api/v2/

For package and dependencies run:

choco push --source="'INTERNAL REPO URL'"

Automate package internalization

3. Copy Your Script

choco upgrade appveyor-server -y --source="'INTERNAL REPO URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade appveyor-server -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode


- name: Install appveyor-server
  win_chocolatey:
    name: appveyor-server
    version: '7.0.3212'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'appveyor-server' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '7.0.3212'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller appveyor-server
{
    Name     = "appveyor-server"
    Version  = "7.0.3212"
    Source   = "INTERNAL REPO URL"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'appveyor-server':
  ensure   => '7.0.3212',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Package Approved

This package was approved as a trusted package on 21 Oct 2024.

Description

AppVeyor CI on your own server

Install in minutes on Windows, Linux or Mac. Run unlimited pipelines locally, in Docker or any cloud.

Works with GitHub, Bitbucket, GitLab, Azure Repos or your favorite source control
Run Windows and Linux builds in parallel in the same Docker pipeline
Run builds on Azure, AWS or GCP and pay for build minutes only
Free for unlimited users, projects, jobs, clouds and agents

Please Note: This is an automatically updated package. If you find it is
out of date by more than a day or two, please contact the maintainer(s) and
let them know the package is no longer updating correctly.

Files

legal\LICENSE.txt


From: https://www.appveyor.com/terms-of-service/

Terms of Service
By accessing this website you agree to be bound by the terms and conditions set out below.

INTERPRETATION
Definitions. Where used in this Agreement, each of the following words and phrases shall have the meanings set out below:
“Agreement” means this Terms of Service Agreement, and all references to “hereto”, “herein”, “hereof”, “hereby” and “hereunder”, and to similar expressions, refer to this Agreement and not to any particular section or portion of it. References to “section”, “subsection” or “article” refer to the applicable section, subsection or article of this Agreement, as the case may be;
“AppVeyor Account” has such meaning ascribed to it in Section 6.2;
“AppVeyor On-Premise” means the downloadable program created by AppVeyor for building, testing, and deploying applications;
“AppVeyor Software” means the software created by AppVeyor, including any Updates thereto which provision the Services;
“AppVeyor” means AppVeyor Systems Inc., including its affiliated entities and operations;
“AppVeyor Build Cloud” means AppVeyor-managed build infrastructure that can be hosted on Cloud Platform or Virtualization Servers;
“Build Agent” means the downloadable program created by AppVeyor to execute build scenarios;
“Build Environment” has such meaning ascribed to it in Section 4.2;
“Cloud Platform” means a platform for cloud computing that provides virtual machines on demand, including without limitation, Microsoft Azure, Google Compute Engine and Amazon Web Services;
“Community Support” means discussion forums and interactive areas on the Site, including chat rooms and bulletin board services;
“Content” means all information, data, text, software, music, sound, photographs, graphics, video, images, other multi-media elements and any other materials available through the Community Support or otherwise;
“Custom Plan” has such meaning ascribed to it in Section 6.3;
“Deployment Agent” means the downloadable program created by AppVeyor for deploying build assets to a customer hosting environment;
“End User License Agreement” means AppVeyor’s End User License Agreement located at www.appveyor.com/eula;
“Free Plan” has such meaning ascribed to it in Section 6.3;
“General Site Information” has such meaning ascribed to it in Section 4.1;
“GitHub Plan” means a Subscription Plan offered through the GitHub Marketplace at https://github.com/marketplace/appveyor;
“Host Agent” means the downloadable program created by AppVeyor for provisioning build virtual machines on remote computers;
“Post” means the act of uploading, posting, emailing, transmitting or otherwise making available Content through the Community Support or otherwise;
“Personal Information” means information about an identifiable individual, and includes such things as gender, age, ethnicity and financial information, health information, consumer preference information, user profiles and identification numbers;
“Privacy Policy” means AppVeyor’s privacy policy located at www.appveyor.com/privacy-policy, as updated from time to time;
“Private Build Cloud” means build infrastructure which is owned by the User and can be hosted on Cloud Platform or Virtualization Servers;
“Site” means AppVeyor’s website located at www.appveyor.com. including all services, tools, forums and other content and information made available on the website;
“Services” means the services AppVeyor provides the User on the Site, including but not limited to:
the provision of developer tools for building, testing, deploying and managing applications;
support services, such as the Community Support; and
any and all other business applications and online services that may be provided by AppVeyor;
“Subscription Period” means, for a Subscription Plan, the monthly or annual period, as applicable, beginning upon payment of a particular subscription fee and ending on the same day of the subsequent calendar month or anniversary date, as applicable, for which payment was remitted;
“Subscription Plan” has such meaning ascribed to it in Section 6.3;
“Taxes” means any and all local, state, provincial, federal, national, use, excise, sales, and value added taxes;
“Third-Parties” means web application providers that own or have the rights to web applications that are built, deployed, managed or used in any manner thereof in connection with the Services and any software associated with the Services, which may include but are not limited those Third-Parties set out in Section 5.3, and “Third-Party means any one of them;
“Third-Party Account” has such meaning ascribed to it in Section 6.2;
“Third-Party Arrangements” has such meaning ascribed to it in Section 5.2;
“Updates” means periodically released versions of the AppVeyor Software which include updates, modifications, corrections and replacements to the AppVeyor Software;
“User” or “you” means any individual, on their own behalf or on behalf of an entity whom they are authorized to represent which has entered into this Agreement with AppVeyor;
“User Build Cloud” means build infrastructure which is owned by the User;
“User Code” has such meaning ascribed to it in Section 10.1; and
“Virtualization Servers” means physical servers with software installed for creating virtual machines, including without limitation, Hyper-V, Docker and VMWare.
ACCEPTANCE OF TERMS
The Site and the Services are offered subject to acceptance without modification of all of the terms and conditions contained in this Agreement. For greater certainty, this Agreement shall be deemed to include all other operating rules, policies and procedures that are referred to herein or that may otherwise be published on the Site, as they may amended from time to time as described herein, including but not limited to the Privacy Policy and the End User License Agreement.
By accessing the Site or using any of the Services, you are agreeing to be bound by this Agreement. If you do not agree with any part of this Agreement or do not consent to be bound hereunder, then you may not access the Site or use any of the Services.
The Services are available only to Users who can form legally binding contracts under the applicable laws (and in the case of individuals, who are at least 18 years old). Otherwise, the User is prohibited from accessing, registering for or using any of the Services.
CONSENT AND CHANGES
Consent. The User acknowledges that the User has read the Privacy Policy (as it may be updated from time to time) and hereby consents to the collection, use and disclosure by AppVeyor and its agents of the User’s Personal Information (whether previously collected or to be collected) for the purposes identified in the Privacy Policy.
Changes.
AppVeyor may, at its sole discretion and with or without notice, at any time, update, modify or terminate operation of the Site (including without limitation, any of the Services). By continuing to use the Site and/or Services, you are consenting to those changes.
AppVeyor may, at its sole discretion and with or without notice, amend or replace this Agreement, in whole or in part, from time to time. Change notices may be communicated by postings at the Site and/or electronic mail to the User, but as AppVeyor is under no obligation to do so, you should therefore periodically check this Agreement. If you do not agree to any modifications, you should stop your use of the Site and/or Services. The User’s continued use of the Site and/or Services will constitute a binding acceptance by the User of this Agreement and any subsequent modifications thereto. The User can review the most current version of this Agreement at any time at www.appveyor.com/terms-of-service.
SITE AND SERVICES
Services and General Site Content. The Site offers access to the Services. In addition to the Services, the Site also includes general information (“General Site Information”) about AppVeyor and the Services, which may include but is not limited to information about pricing, blog entries, tutorials, testimonials, software descriptions, user-generated content, messages, information, data, graphics, news articles, photographs, images, illustrations, software and other such content.
Build Environment. As part of the Services, AppVeyor provides Users a set of tools to continuously build and test their applications in a virtualized isolated environment (the “Build Environment”). Based on the Services selected by the User, the Build Environment can be virtual machine hosted on an AppVeyor Build Cloud or a User Build Cloud. A Build Environment includes the following features, as may be modified from time to time:
every build runs on a fresh virtual machine which is not shared with other builds and the state of which is not preserved between consequent builds;
after the build is finished its virtual machine is decommissioned;
build worker virtual machines have firewall enabled and blocking all incoming traffic, but certain firewall rules may be User enabled to access build worker from outside the firewall (for example: PowerShell remoting and RDP);
Build Environment virtual machines communicate to the Services via encrypted HTTPS protocol;
build time varies depending on the programming language, size of the project, external dependencies and Build Environment used;
maximum allowed run time for a build is specified in Plan and build is cancelled if not finished within such timeframe.
No Liability. The User acknowledges and agrees that modifications to the Services, which for greater certainty, may include modifications to the Build Environments, may affect the User’s builds and AppVeyor is not liable for any damage or work interruption relating to such modifications.
THIRD-PARTIES
Third-Parties. AppVeyor and any Third-Parties are separate legal entities that are not affiliated with each other, unless otherwise disclosed by AppVeyor at its sole discretion. This Agreement is between the User and AppVeyor. Third-Parties are not providing the Services and are not responsible for the Services.
User Engaged. You may engage Third-Parties in connection with the Services and have other agreements with Third-Parties (“Third-Party Arrangements”), and you acknowledge and agree that:
Third-Party Arrangements apply between the User and such Third-Parties and is outside of AppVeyor’s relationship with you; and
this Agreement will not in any way alter any of the terms or conditions of any Third-Party Arrangement the User may have with any Third-Parties for their products or services.
AppVeyor Engaged. AppVeyor may engage Third-Parties in the provision of the Services from time to time in its sole discretion, including to utilize Cloud Platforms and Virtualization Servers owned by Third-Parties.
Payments to Third-Parties. Third-Parties may charge the User for the provision of their respective products and services in accordance with their prices and payment terms, and you acknowledge and agree that:
you are solely responsible for the payment of any and all fees associated with any Third-Parties, including without limitation, charges due to Third-Parties used in connection with User Build Clouds; and
AppVeyor is not responsible for any charges the User incurs from Third-Parties due to the User’s use of the Services or for any other reason, and the User is not entitled to receive any refunds or credits from AppVeyor thereof.
USER ACCESS, REGISTRATION AND SUBSCRIPTION
Browsing. Users who wish to browse the Site for General Site Information may access the General Site Information and are not required to register an account on the Site, provided that any User must, as a condition to accessing General Site Information, accept the terms of this Agreement and comply with the obligations described herein, such acceptance evidenced by your ongoing use of the Site.
Registration.
Except for Users of the free version of AppVeyor On-Premise, Users who wish to have full access to the Site and use the Services are required to register an account on the Site (an “AppVeyor Account”) by (i) creating a new user account; or (ii) logging in with an existing account with certain Third-Party developers (a “Third-Party Account”). Users of the free version of AppVeyor On-Premise may use such Service without registering an account, provided that they provide their name and email for AppVeyor’s record-keeping purposes and agree to these Terms of Service, the EULA and Privacy Policy.
Users registering an AppVeyor Account by creating a new user account must provide AppVeyor with a password and a valid email address, and such Users agree (i) that all such information is true, accurate and complete as of the time when registration occurs, and (ii) to provide us with any updates as may be required to ensure such information continues to be accurate.
Users registering an AppVeyor Account by logging in with a Third-Party Account expressly authorize AppVeyor to receive and share, certain of your information that is available on or through such Third-Party Account, including, without limitation, the User’s profile information and certain other information.
Users are responsible for maintaining the confidentiality of such User’s AppVeyor Account and are solely responsible for all activities resulting from the use of and activities conducted through the User’s AppVeyor Account.
Free and Subscription Plans.
Users who wish to use the Services available under the free plan offered on the Site, as may be modified or discontinued from time to time at the sole discretion of AppVeyor (the “Free Plan”) and/or free trials of Subscription Plans, must: (i) register an AppVeyor Account; and (ii) provide AppVeyor with certain requested information as required.
(b)	Users who wish to use the Services available under subscription plans must:
for plans available on the Site: (A) register an AppVeyor Account; and (B) subscribe to one of the subscription plans offered on the Site, as may be modified or discontinued from time to time at the sole discretion of AppVeyor (the “Subscription Plans”) and/or create a custom plan with AppVeyor (a “Custom Plan”);
for GitHub Plans, complete all requirements of the GitHub Marketplace at https://github.com/marketplace/appveyor; and
provide AppVeyor with certain requested information as required, including but not limited payment information, if applicable.
By using any of the Services by subscribing to a Subscription Plan and/or creating a Custom Plan, in addition to continuing to be bound by this Agreement, you are agreeing to be bound by the terms and conditions underlying such selected Subscription Plan or Custom Plan, as applicable.
PLAN TERMS
Free Plans. The Free Plan and free trials of the Subscription Plans, and the paid Subscription Plans are offered on the Site..
GitHub Plans. The GitHub Plans are offered through the GitHub Marketplace at https://github.com/marketplace/appveyor.
Custom Plans. Users who wish to create Custom Plans may contact AppVeyor at [email protected].
Payment Terms. Payment terms apply to Subscription Plans, which for greater certainty includes, but is not limited to, AppVeyor On-Premise Plans, GitHub Plans, and Custom Plans. Payment and pricing terms:
for Subscription Plans, can be found on the Site; and
for Custom Plans, are as determined by mutual agreement between the User and AppVeyor.
Renewal.
Free trials of the Services available under Subscription Plans will automatically expire at the expiry of the trial period and be converted into the Free Plan unless you affirmatively subscribe for such Subscription Plan prior to the expiry date.
Services available under Subscription Plans are subscription-based for the Subscription Period. Accordingly, upon subscribing for and remitting payment in respect of the Services available under a Subscription Plan, the User will receive such Services for the Subscription Period. For further clarity, if the Subscription Period is monthly, if a User purchases and remits the associated fees in respect of such Services on the 15th day of the month, the User will have a valid subscription to such Services until the 15th day of the subsequent month. If the Subscription Period is annually, the User will have a valid subscription to such Services until the anniversary date of the date the User purchases and remits the associated fees in respect of such Services. To ensure prompt and continuous delivery of such Services, the Subscription Period is renewed automatically at the end of each Subscription Period, and the User will incur the then-current fees, on a recurring-basis, on the last day of their Subscription Period in payment of the subsequent Subscription Period, each and every month or year, as applicable, until the User terminates such Services pursuant to this Agreement.
Paid Services available under Custom Plans are as determined by mutual agreement between the User and AppVeyor.
CANCELLATION AND TERMINATION
AppVeyor reserves the right to refuse or cancel orders, terminate AppVeyor Accounts and terminate the Services, at any time in its sole discretion, with or without notice, for any reason whatsoever, with or without cause. In the event that AppVeyor terminates your AppVeyor Account and/or the Services and the User has remitted fees in respect of the Services that extends beyond the date of termination,
if such termination is with cause, including without limitation, a breach of this Agreement or other violation, the purchased Services will be forfeited by the User without any right to receive a refund; or
if such termination is without cause, AppVeyor will return such fees to the User for the unused portion of the Subscription Period that extends beyond the date of termination.
The User may terminate the User’s AppVeyor Account and/or the Services at any time, for any reason whatsoever, through AppVeyor user interface. In the event that the User exercises its option to terminate the User’s AppVeyor Account and/or the Services, the User acknowledges and agrees that any fees that the User remitted in respect of the Services, irrespective of whether such fees were remitted in connection with any unused portion of the Services that may extend beyond the date of termination:
if the Services are provided under a monthly Subscription Period, will be forfeited by the User without any right to receive a refund; and
if the Services are provided under an annual Subscription Period, will be forfeited by the User without any right to receive a refund, unless the User notifies AppVeyor of its election to terminate no later than 30 days from the start of the current Subscription Period.
The User acknowledges and agrees that any fees that the User remitted in respect of the Services provided through a GitHub Plan will be forfeited by the User without any right to receive a refund, irrespective of whether such fees were remitted in connection with any unused portion of the Services that may extend beyond the date of any termination.
LICENSE TO ACCESS USER CODE
Each User subscribing to the Services, upon submitting any source code (or any update or modification to source code previously submitted) (the “User Code”) for purposes of using the Services for building, testing and deployment thereof, hereby grants to AppVeyor (and its successors, assigns and affiliates, if any) a worldwide, non-exclusive, royalty-free, fully paid license to reproduce, host, store, modify and transmit the User Code solely for the purpose of performing the actions required to undertake and effect the Services with respect to the User Code. With respect to each license grant made by a User at each User Code submission, such license shall terminate and be of no further force and effect upon completion of the build, test, deploy and results cycle undertaken by the Services with respect to the User Code. By accessing the Site or using any of the Services, in addition to agreeing to be bound by this Agreement, the User is deemed to assent to such license grant when, as and if required where any such test is performed by AppVeyor.
The User:
acknowledges that AppVeyor requires the license granted in Section 10.1 for the provision of the Services;
acknowledges that after submitting any User Code (including any updates, modifications or edits to previously submitted source code) for review and testing with the Services, the User retains full and identical rights in and to the User Code which such User may have owned or held prior to submitting, and no conveyance or assignment (other than the license grant described above) is intended to be effected nor shall actually be effected by submitting the content; and
represents and warrants that the User: (i) is the owner or rights holder of all necessary rights to effect the license grant described above, including any and all copyrights in and to the submitted User Code; (ii) has the full and complete right to agree to this Agreement and to grant the license described above, and no further permissions are required from, nor payments required to be made to, any other person in connection with the actions taken in furtherance of the Services; and (iii) is not aware that any portion of the submitted User Code infringes, or is likely to infringe, the rights (including, without limitation, rights of copyright, privacy or publicity; moral rights; or other intellectual property rights) of any person, or violate any law, regulation, ordinance, statute or judicial or governmental order.
ACCESS TO USER HOSTING ENVIRONMENT
Each User subscribing to the Services hereby grants AppVeyor access to its hosting environment where, following testing and verification of the User Code, AppVeyor will deploy the verified portions of the User Code into the hosting environment. AppVeyor agrees to use such access solely to deploy tested and verified User Code. By accessing the Site or using any of the Services, the User is deemed to assent to AppVeyor’s access to the User’s hosting environment for the sole purpose of deploying the verified portions of the User Code into the environment, and for no other purpose.
The User:
acknowledges that AppVeyor requires the access granted in Section 11.1 for the provision of the Services;
acknowledges that AppVeyor shall not be responsible for any bugs, worms, viruses or dysfunctional code (collectively, the “Bugs”) deployed therein to the extent such Bugs were unknown or unknowable to AppVeyor at the time the User Code was supplied to AppVeyor for testing; and
agrees that, to the extent the User Code, whether or not modified by the User following deployment by AppVeyor, causes any failure in functionality of a User’s product or service, whether directly or indirectly, AppVeyor shall not be liable for any such failure of functionality.
UPDATES
AppVeyor will provide all Updates to the User, without additional charge.
Use of any Update with or in place of the AppVeyor Software is subject to the terms of this Agreement.
WARRANTY DISCLAIMER
APPVEYOR DISCLAIMS AND, TO THE EXTENT PERMITTED AT LAW, THE USER WAIVES ALL REPRESENTATIONS, WARRANTIES OR CONDITIONS, WHETHER EXPRESSED, STATUTORY OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OR CONDITION OF MERCHANTABILITY, MERCHANTABLE QUALITY, DURABILITY, TITLE, NON-INFRINGEMENT OR FITNESS FOR A PARTICULAR PURPOSE WITH RESPECT TO THE SITE AND SERVICES AND ANY OTHER ITEMS OR SERVICES PROVIDED HEREUNDER.
AppVeyor does not represent or warrant that the Site or the Services are or will be accurate, complete, reliable or current, or that the Site or the Services will operate error free or uninterrupted or that the Site or the Services are free of viruses or other harmful components. Some jurisdictions do not allow the exclusion of implied warranties, so the exclusions in Section 13 may not apply to all Users.
AppVeyor does not warrant that the Services will meet the requirements of the User. AppVeyor is not responsible for problems caused by changes in, or modifications to, the operating characteristics of any computer hardware or operating system for which the Services are procured, nor is AppVeyor responsible for problems which result from the use of the Services in conjunction with software of third parties or with hardware which are incompatible with the operating system for which the Services are being procured.
The User acknowledges that AppVeyor is not responsible for any interruption or suspension of the Site or the Services, regardless of the cause of the interruption or suspension.
THE SITE AND THE SERVICES ARE PROVIDED ON AN “AS IS” BASIS WITHOUT REPRESENTATIONS, WARRANTIES OR CONDITIONS OF ANY KIND, EXPRESS, IMPLIED OR STATUTORY. THE USER EXPRESSLY AGREES THAT ALL USE OF THE SITE AND THE SERVICES IS AT THE USER’S SOLE RISK. THE USER AGREES THAT APPVEYOR ASSUMES NO LIABILITY IF THE SITE OR THE SERVICES ARE UNAVAILABLE AT ANY TIME, OR FOR THE TIMELINESS, DELETION, MISDELIVERY, VALIDITY, ACCURACY, COMPLETENESS, INTEGRITY, QUALITY AND TIMELINESS, OR FAILURE TO DELIVER OR STORE THE SITE OR THE SERVICES OR ANY CONTENT, COMMUNICATIONS OR PERSONALIZATION SETTINGS. APPVEYOR DOES NOT REPRESENT OR ENDORSE THE RELIABILITY, VALIDITY, ACCURACY, COMPLETENESS, INTEGRITY, QUALITY AND TIMELINESS OF ANY CONTENT, OTHER COMMUNICATION OR OTHER INFORMATION POSTED THROUGH THE SITE OR THE SERVICES BY APPVEYOR, ITS SUBLICENSEES, PARTNERS OR REPRESENTATIVES, THIRD-PARTIES, USER OF THE SERVICES, LICENSEES OR ANY OTHER PERSON OR ENTITY. THE USER ACKNOWLEDGES THAT ANY USE, NON-USE OR RELIANCE UPON ANY SUCH CONTENT, OTHER COMMUNICATION OR OTHER INFORMATION WILL BE AT THE USER’S SOLE RISK. You acknowledge and agree that your sole remedy for any problems or dissatisfaction with the Services is to terminate your account and discontinue use of the SITE AND THE Services.
LIMITATION OF LIABILITIES
To the extent permitted by law, in no event will AppVeyor, Third-Parties or any of their respective affiliates, licensees, partners or suppliers or the directors, officers, employees, agents, representatives or customers of any of them, be liable for any direct, incidental, punitive, exemplary, aggravated, indirect, special or consequential damages, or any other damages of any kind, including but not limited to loss of profits, failure to realize expected savings or loss of data, for any cause of action whatsoever and whether in contract, tort (including negligence) or any other legal or equitable theory arising out of or in any way connected with use of the Site or the Services. Some jurisdictions do not allow the limitation of liability for incidental, consequential or other damages so the limitation or exclusion in Section 14 may not apply to all Users.
Every exemption from liability, limitation and condition contained in this Agreement for the benefit of AppVeyor and every defence and immunity of any nature applicable to AppVeyor or to which AppVeyor is entitled under this Agreement will also be available and will extend to protect each of AppVeyor, Third-Parties or any of their respective affiliates, licensees, partners or suppliers or the directors, officers, employees, agents, representatives or customers of any of them. For the purpose of all such provisions, AppVeyor is and will be deemed to be acting as agent and trustee on behalf of and for the benefit of all such persons.
To the maximum extent permissible under applicable law, AppVeyor, on behalf of itself and its directors, officers, employees, contractors, developers, suppliers and any other related service-providers, disclaims any and all liability for:
special, incidental, indirect or consequential damages (including loss of profits); and
punitive and exemplary damages, arising out of this Agreement or with respect to the installation, implementation, customization, use, operation, training, maintenance or support of the Site and the Services, even if AppVeyor or its developers or suppliers have been apprised of the possibility of such damages.
The limitations of this Section 14 shall apply to all causes of action, whether based on breach of warranty, breach of condition, breach of contract, fundamental breach or any other form of breach, negligence, other tort claims, strict liability or any other legal or equitable theory.
SECURITY
User Code.
As part of the Services, AppVeyor builds and tests User Code.
User Code resides in repository, which may be:
self-hosted Git, Mercurial, TFVC or Subversion repository;
hosted on GitHub, BitBucket, Visual Studio Team Services, Kiln or GitLab; or
hosted on other services.
In the provision of building and testing Services, AppVeyor downloads (clones) User Code to the Build Environment, which for greater certainty does not leave the boundaries of the Build Environment and is only retained in the Build Environment for the duration of the build using such User Code.
When a build is completed, the virtual machine handling such User Code is either deleted or restored to initial state and the User Code is removed from such virtual machine.
AppVeyor will not access User Code, build virtual machines, build and environment configurations, logs or artifacts without the User’s permission. By requesting any Services, you are deemed to be granting such permission to AppVeyor for the provision of such Services.
AppVeyor uses SSH keys or OAuth tokens whenever possible to clone code repository.
GitHub Scopes.
When authorized to access the User’s GitHub account, as applicable, AppVeyor will request the following OAuth scopes:
Public repositories:
read:org as required to get the list of organization public repositories customer has access to;
admin:repo_hook as required to create repository webhook when adding a project in AppVeyor;
repo:status as required to create commit status when a build is finished;
Private and public repositories:
repo as required to list user and organization private repositories, manage repository webhooks and SSH deployment keys, and create commit status when a build is finished.
Payment and other sensitive information.
When an application in AppVeyor accepts credit cards for any of the Services, User credit card information is not stored on the AppVeyor servers or database. Credit card details entered on the Site go directly to Stripe API via HTTPS and never reaches the AppVeyor servers. When such credit card information is validated by Stripe API, AppVeyor receives a special token which is used for making a payment. AppVeyor recommends that you refer to Stripe API's privacy policies for more information.
When an application in AppVeyor accepts any other sensitive information, such as passwords, OAuth tokens, SSH keys, project and environment configurations, such sensitive information is stored in the AppVeyor database in encrypted form.
Third-Parties. AppVeyor may engage Third-Parties in the provision of the Services, from time to time. By accessing the Site or using any of the Services, you are authorizing AppVeyor to share information, including your Personal Information, with Third-Parties solely for the purpose of performing the applicable Services, as determined by AppVeyor in its sole discretion. For more information, AppVeyor recommends that you refer to the applicable Third-Party’s terms of service and privacy policies.
USE OF INFORMATION
You hereby agree that you shall not use any information contained in this Site or the links to this Site in any claims, proceedings, suits or actions against AppVeyor, its suppliers or affiliates. You may not post, publish, reproduce, transmit or otherwise distribute information or material on the Site:
constituting or encouraging conduct that would constitute a criminal offence or give rise to civil liability;
which is protected by copyright, or other intellectual property right or derivative works thereof, without obtaining permission of the copyright holder; or
otherwise use this Site in a way that is contrary to law or which would adversely impact use of the Site or the Internet by other users including the posting or transmitting of other information or software containing viruses or other disruptive components.
LINKAGE
This Site may contain links to other websites that are not under the control of AppVeyor and AppVeyor is not responsible for and makes no representations or warranties concerning the contents of any linked website or any link contained in a linked website. It is your responsibility to verify any information contained within the links before relying on it. The information contained in the links may be changed or updated at any time without notice. AppVeyor provides links to you only as a convenience and the inclusion of any link does not imply endorsement, investigation or verification by AppVeyor of the linked site. Your use of the linked websites may be subject to terms and conditions contained in these websites, which you should locate and review.
COOKIES
AppVeyor uses cookies to enhance each User’s experience on the Site. Cookies are small files of information that are stored onto your device which save and retrieve information about your visit to the Site. By continuing to use the Site and/or the Services, you are agreeing to AppVeyor’s use of cookies and similar technologies. You can learn more about these technologies at allaboutcookies.org. If you do not wish to have cookies placed on your device, you may manage cookies in your browser before using the Site. Disabling cookies may impede proper functioning of certain features on the Site.
MONITORING
AppVeyor is under no obligation to monitor the Site and assumes no responsibility or liability should its content be modified or altered in any way without AppVeyor’s consent.
COPYRIGHT AND TRADEMARKS POLICIES
The materials displayed as part of the Site and the Services are provided by AppVeyor for informational purposes only. Neither the whole nor any part of this work may be copied, scanned, reproduced or transmitted, in any form or by any means without the prior written permission of AppVeyor. You should assume everything you see or read on this site is copyrighted unless otherwise noted. You are free to use the content for non-commercial purposes, provided you do not modify it and provided you retain all copyrights and other proprietary notices contained in the content. You require AppVeyor’s written consent to copy or display any portion of the content for redistribution to third parties or for commercial purposes. The trademarks, logos, service marks and other names and icons identifying products and services and displayed as part of the Site and the Services are owned by or licensed to AppVeyor. Nothing contained on this site gives you or any other person the right or licence to use any trademark displayed on this site without the express permission of AppVeyor.
VIRUSES
AppVeyor assumes no responsibility and shall not be liable for any damages to or viruses that may infect your computer equipment or other property on account of your access to, use of or browsing in the Site or your downloading of any materials, data, text or images from the Site.
SUPPORT SERVICES
Support Site. AppVeyor will provide support to all Users on its support site located at https://help.appveyor.com or https://appveyor.tenderapp.com/, where Users may access Community Support and Post public or private discussions, at the User’s option, at https://help.appveyor.com/discussion/new.
Community Support. AppVeyor will provide Community Support to all Users.
You agree to use the Community Support in accordance with the following Code of Conduct:
You will keep Content provided to you through the Community Support as private and confidential and will not give such Content to anyone without the permission of the person who provided it to you.
You will not use the Community Support to engage in any form of harassment or offensive behavior. Without limitation, you will not Post any Content that is libelous, defamatory, abusive, harassing, tortious, pornographic, obscene, vulgar or offensive, or racially, ethnically or otherwise objectionable. You will not use the Community Support to harm minors in any way.
You will not forward chain letters, or otherwise cause, instigate, or assist in the distribution of spam through the Community Support.
You will not use the Community Support to infringe the privacy rights, property rights, or any other rights of any person.
You will not Post any Content if the Posting of such Content is a breach of any law or a breach of any contractual or fiduciary relationship (such as inside information, or proprietary or confidential information learned or disclosed as part of an employment relationship or under a non-disclosure agreement). You will not Post any Content that, or use the Community Support in any way which:
violates, plagiarizes or infringes upon the rights of any third party, including but not limited to any rights under copyright, trademark or patent laws, or privacy or other personal or proprietary rights; or
is fraudulent or otherwise unlawful or violates any law.
You will not use the Community Support to distribute, promote, or otherwise publish any Content containing any solicitation for funds, advertising or solicitation for goods or services.
You will not use the Community Support to Post any Content that contains any viruses, Trojan horses, worms, time bombs, cancelbots, corrupted files, spyware or any other similar software or programs that might damage the operation of a mobile phone, computer or other property of any other person, or do anything else that might cause harm to the Community Support, the systems of AppVeyor, any third parties, or adversely affect the experience of other users of the Site or AppVeyor’s related services or software.
You will not Post any contact information including, but not limited to, email addresses, “instant messenger” nicknames, telephone numbers, postal addresses, URLs, or full names through publicly readable posts or user profiles.
You will not use the Community Support to Post credit card numbers or similar numbers or information.
You will not use the Community Support to impersonate any person or entity (including, but not limited to, any AppVeyor official, forum leader, guide or host) or falsely state or otherwise misrepresent your affiliation with a person or entity.
You will not forge headers or otherwise manipulate identifiers in order to disguise the origin of any Content transmitted through the Community Support.
You will not falsify or delete any copyright management information, such as author attributions, legal or other property notices or proprietary designations or labels of the origin or source of software or other material contained in Content.
You will comply with all applicable laws regarding the transmission of technical data exported from, or imported into, Canada, the United States or the country in which you reside.
AppVeyor does not take any responsibility, and assumes no liability, for any Content Posted or otherwise sent or received by you or any third party, or for any mistakes, defamation, slander, libel, omissions, falsehoods, obscenity, pornography or profanity you may encounter, or for any loss or damage of any kind incurred by you or any other person as a result of the use of any Content Posted or otherwise made available through the Community Support. The Community Support is only a forum, and AppVeyor is not liable for any statements, representations or Content provided by users. For greater certainty, AppVeyor is not liable for in case any sensitive information is accidentally posted by customer on public forums. The User should contact AppVeyor team at [email protected] to remove that information.
AppVeyor reserves the right, but is not obligated, to monitor any activity and communication within the Community Support, including but not limited to messages, public postings, and other multimedia elements as they become available, to ensure that your use of the Community Support conforms to this Agreement. AppVeyor may investigate any complaint and suspected or reported violation of this Agreement, and take any action that it deems appropriate. AppVeyor reserves the right and has absolute discretion to remove, screen or edit any activity, Content, communication, user profiles, public postings, or messages within the Services that violate this Agreement or are otherwise objectionable. In order to cooperate with legitimate governmental requests, subpoenas or court orders, to protect systems and customers of AppVeyor, or to ensure the integrity and operation of the business and systems of AppVeyor, AppVeyor may access and disclose any information it considers necessary or appropriate, including, without limitation, user information, Content, communications, usage history, and Postings.
TAXES AND TARIFFS
The User shall, besides other amounts payable under this Agreement, pay all Taxes, except for taxes imposed on AppVeyor’s income generally, as well as customs duties or tariffs, levied or imposed by reason of the transactions contemplated in this Agreement, including any new Taxes introduced during the term of this Agreement. Concurrently with payment of the applicable fees hereunder, the User shall remit to AppVeyor all Taxes due. If any Taxes are required to be withheld, then the User shall pay AppVeyor an amount such that the net amount after withholding of such Taxes shall equal the amount that would have been otherwise payable under this Agreement.
INDEMNITY
The User agrees to defend, indemnify and hold harmless AppVeyor, Third-Parties, their affiliates, licensees, partners and suppliers, and the directors, officers, employees, agents, representatives and customers of each of them, from:
any loss or damages, including without limitation actual legal fees, which they may suffer from the User’s activities on or use of the Site or the Services, including without limitation (i) any violation of this Agreement by you, (ii) in connection with your use of the Site or the Services, (iii) the placement or transmission of any message or information on the Site by you, (iv) your violation or of any law, rule, regulation or rights of others in connection with your use of any of the Site or the Services, including, without limitation, infringement of anyone else’s intellectual property rights, or (v) any charges or complaints made by other parties against you, and
any claim or demand, including actual legal fees, made by any third party due to or arising out of Content that the User Posts. The User will cooperate as fully as reasonably required in the defense of any claim. AppVeyor reserves the right to assume the exclusive defense and control of any matter otherwise subject to indemnification by the User; provided, however, that the User will remain liable for any such claim and for the costs of defense.
AppVeyor shall have the right to control the defense of all claims, lawsuits, and other proceedings based on a claim that the Site or the Services used within the scope of this Agreement infringes any copyright, patent, or trade secret of a third party. In no event shall the User settle any such claim, lawsuit, or proceeding without AppVeyor’s prior written approval, and AppVeyor shall have no liability for any settlement or compromise made without its consent. AppVeyor shall have no liability for any claim under this Section if said infringement claim is based on the use of a superseded or altered version of the Site or Services or in the event such claim is based upon any modification or enhancement to the Site or Services made by the User. In the event a third party infringement claim is sustained in a final judgment from which no further appeal is taken or possible, or if the User’s use of the Site or Services is enjoined by a court, or if AppVeyor believes the Site or Services infringe the intellectual property rights of a third party, then AppVeyor shall, in its sole election and at its expense either:
procure for the User the right to continue to use the Site and Services pursuant to this Agreement;
replace or modify the Site and Services to make it non-infringing, provided that such replacement or modification does not materially decrease the functionality of the Site or Services; or
terminate this Agreement, including the Services.
This Section states the entire liability of AppVeyor and its suppliers with respect to any claim of infringement of the intellectual property or proprietary rights of others.
GENERAL
Wherever the singular or the masculine is used herein, the same shall be deemed to include the plural or the feminine or the body politic or corporate where the context or the parties so require.
The headings to the clauses of this Agreement are inserted for convenience only and shall not affect the construction hereof.
This Agreement, including the Privacy Policy, the End User License Agreement any other terms and conditions governing the use of the Site and the Services, constitute the entire agreement between you and AppVeyor with respect to your access to the Site and use of the Services, and supersede all prior and contemporaneous agreements between you and AppVeyor relating to same.
If any one or more of the provisions contained in this Agreement should be invalid, illegal or unenforceable in any respect in any jurisdiction, the validity, legality and enforceability of such provision or provisions shall not in any way be affected or impaired thereby in any other jurisdiction and the validity, legality and enforceability of the remaining provisions contained herein shall not in any way be affected or impaired thereby.
AppVeyor’s failure to insist upon or enforce strict performance of any provision of this Agreement shall not be construed as a waiver of any provision or rights contained in this Agreement.
By visiting the Site, you agree that this Agreement shall be governed by the laws of the province of British Columbia and the federal laws of Canada applicable therein and you agree to be bound by the laws of these jurisdictions.
All prices are quoted in U.S. dollars and do not include applicable taxes or shipping and handling.
The Site and the information contained herein do not constitute an offer or a solicitation of an offer for the purchase or sale of any securities.

legal\VERIFICATION.png

legal\VERIFICATION.txt

VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The installer have been downloaded from their official download link listed on <https://www.appveyor.com/releases/>
and can be verified like this:

1. Download the following installers:
  32-Bit: <https://www.appveyor.com/downloads/appveyor/appveyor-server.msi>
2. You can use one of the following methods to obtain the checksum
  - Use powershell function 'Get-Filehash'
  - Use chocolatey utility 'checksum.exe'

  checksum type: sha256
  checksum32: C23525691D170B1F33456092220049E2264F90A515BF7CF62C819327D97C5EC8

File 'LICENSE.txt' is obtained from <https://www.appveyor.com/terms-of-service/>

File 'VERIFICATION.png' is a screenshot of <https://twitter.com/mkevenaar/status/1133442273121787904>

tools\appveyor-server.msi

md5: 8898D15D30A9EC1234D8842A0EB88A61 | sha1: CC5A3429396BFED062C0CEB0CB0BBBC4BD8404F8 | sha256: C23525691D170B1F33456092220049E2264F90A515BF7CF62C819327D97C5EC8 | sha512: 9FB7DCB6934E3C33261F5DF8D8E0FEE39A82785B121DD84DF4EF2F1F0686589DC2B0C81F845EDB2CBAFA6C175D6C6C177AE183192BFDC7BB491BBC8BF3AE9A77

tools\chocolateyinstall.ps1

$ErrorActionPreference = 'Stop';

$toolsDir       = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  fileType      = 'msi'
  file          = "$toolsDir\appveyor-server.msi"
  softwareName  = 'AppVeyor Server*'
  silentArgs    = "/qn /norestart /l*v `"$env:TEMP\$env:ChocolateyPackageName.$env:ChocolateyPackageVersion.log`""
  validExitCodes= @(0,1641,3010)
}

Install-ChocolateyInstallPackage @packageArgs

Virus Scan Results

appveyor-server.7.0.3212.nupkg (b80178115bcd) - ## / 40
appveyor-server.msi (c23525691d17) - ## / 55

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version History

Version	Downloads	Last Updated	Status
AppVeyor Server (Team Edition) 7.0.3212	401	Monday, April 4, 2022	Approved
AppVeyor Server (Team Edition) 7.0.3150	126	Thursday, February 17, 2022	Approved
AppVeyor Server (Team Edition) 7.0.2942	1978	Thursday, October 1, 2020	Approved
AppVeyor Server (Team Edition) 7.0.2915	207	Monday, August 17, 2020	Approved
AppVeyor Server (Team Edition) 7.0.2914	166	Monday, August 17, 2020	Approved
AppVeyor Server (Team Edition) 7.0.2546	541	Wednesday, November 6, 2019	Approved
AppVeyor Server (Team Edition) 7.0.2417	226	Friday, September 27, 2019	Approved
AppVeyor Server (Team Edition) 7.0.2396	215	Thursday, September 26, 2019	Approved
AppVeyor Server (Team Edition) 7.0.2375	226	Thursday, September 5, 2019	Approved
AppVeyor Server (Team Edition) 7.0.2353	238	Sunday, August 11, 2019	Approved
AppVeyor Server (Community Edition) 7.0.2329	249	Saturday, August 3, 2019	Approved
AppVeyor Server (Community Edition) 7.0.2184	240	Tuesday, June 4, 2019	Approved
AppVeyor Server (Community Edition) 7.0.2150.20190529	296	Wednesday, May 29, 2019	Approved
AppVeyor Server (Community Edition) 7.0.2150	196	Saturday, May 25, 2019	Approved
AppVeyor Server (Community Edition) 7.0.2126	183	Friday, May 24, 2019	Approved

Appveyor Systems Inc.

Release Notes

https://www.appveyor.com/releases/

Dependencies

This package has no dependencies.

Discussion for the AppVeyor Server (Team Edition) Package

Ground Rules:

This discussion is only about AppVeyor Server (Team Edition) and the AppVeyor Server (Team Edition) package. If you have feedback for Chocolatey, please contact the Google Group.
This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
Tell us what you love about the package or AppVeyor Server (Team Edition), or tell us what needs improvement.
Share your experiences with the package, or extra configuration or gotchas that you've found.
If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.

Resources

Events

Courses

5,488

401

04 Apr 2022

AppVeyor Server (Team Edition)

AppVeyor Server (Team Edition) 7.0.3212

All Checks are Passing

Deployment Method: Individual Install, Upgrade, & Uninstall

Deployment Method:

1. Enter Your Internal Repository Url

2. Setup Your Environment

1. Ensure you are set for organizational deployment

2. Get the package into your environment

3. Copy Your Script

4. If applicable - Chocolatey configuration/installation

Ground Rules: