Default Extension Installation
If your product installation can access the internet (specifically the
simply navigate to the Admin > Extensions page to browse and install the latest available
Offline or Previous Version Extension Installation
For installations that are restricted from accessing the internet, or if you with to install a version other than the latest, extensions can also be installed manually:
- Download the desired version of the extension from the public ProGet feed
Copy the extension file (
Jenkins.upack) to the extensions path. Visit the Admin > Advanced Settings page within your product instance to determine where extensions are stored by examining the Extensions.ExtensionsPath setting.
Ensure the file is named exactly
Jenkins.upackin the extensions directory, and that no other files with the same name exist in that directory, even with a different extension. For example, make sure to delete an existing
Jenkins.inedoxfile if you are installing
Restart the product's Windows service: Admin > Service > Stop then Start (e.g.
- Restart the product's Web application, either the IIS application pool or the Integrated Web Server service: Admin > Service > Restart Web App
- Verify that the new extension has been loaded (Admin > Extensions)
To access pre-release versions of this extension, you can configure your product installation to use Inedo's public ProGet instance to download extension packages.
To configure your product installation to point to the pre-release feed, visit the Admin > Advanced Settings page within the product installation and set the Extensions.UpdateFeedUrl value to:
This feed has a connector configured to the default URL (i.e.
if there are no pre-release versions, the latest will always be available.