ProGet Documentation

Package Promotion and Deployment

  • Last Modified: 2018-08-29

Package Promotion

Packages can be promoted from one feed to another. This is useful for maintaining feeds with separate levels of quality (such as Development, Production, etc), and also to easily curate selected packages from an external source to an approved repository.

This feature is available in paid and trial ProGet editions.

Check out our Promote Packages with ProGet video for a quick look at some of the ways to use Package Promotion.

Promoted Package

Deployment Records

When a package is deployed from a feed using a tool (such as BuildMaster or Hedgehog) ProGet records information about that deployment, such as the target and the user that performed the deployment.

Deployment Records

Custom Records

Consumers of any package type may customize the GET request with the following HTTP headers:

  • X-ProGet-Deployment-Application - (Required) - the application or tool doing the deployment e.g. NuGet, BuildMaster, Some Custom Tool
  • X-ProGet-Deployment-Description - (Required) - brief summary of deployment
  • X-ProGet-Deployment-Target - (Required) - string that identifies where the package was installed, typically the server name
  • X-ProGet-Deployment-Url - (Optional) - URL that links to more information about the deployment
  • X-ProGet-Deployment-UserName - (Optional) - name of the user performing the deployment, defaults to authenticated user
  • X-ProGet-Deployment-Date - (Optional) - ISO 8601 UTC date of deployment, or current date if not supplied

Have a question? Try the Q&A Forum

Our documentation is now Open Source and on GitHub. We highly encourage our users to contribute and get involved! .