Push Package
- 17 Feb 2022
- 1 Minute to read
- Print
- DarkLight
- PDF
Push Package
- Updated on 17 Feb 2022
- 1 Minute to read
- Print
- DarkLight
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
This is generated from the built in components of Otter 3.0.0, and may be different than what you have installed (especially if you have extensions); go to [User Icon] -> Documentation within your BuildMaster instance to see exactly what operations are available.
Push Package
Uploads a universal package to a ProGet feed.
Script usage:
ProGet::Push-Package( [Credentials: <text>], Feed: <text>, FilePath: <text>, [Group: <text>], [Name: <text>], [Version: <text>], [Description: <text>], [Title: <text>], [Icon: <text>], [Dependencies: <@(text)>], [Server: <text>], [UserName: <text>], [Password: <text>], [PackageSource: <text>] );
Arguments:
Name | Format | Script Usage | Usage Notes |
---|---|---|---|
Credentials | text | Credentials | |
☆ Feed name | text | Feed | This argument is required. |
☆ Package file path | text | FilePath | This argument is required. |
Group name | text | Group | |
Package name | text | Name | |
Version | text | Version | |
Description | text | Description | The package description supports Markdown syntax. |
Title | text | Title | |
Icon | text | Icon | A string of an absolute url pointing to an image to be displayed in the ProGet UI (at both 64px and 128px); if package:// is used as the protocol, ProGet will search within the package and serve that image instead |
Dependencies | @(text) | Dependencies | Dependencies should be supplied as a list, each consisting of a package identification string; this string is formatted as follows:
|
ProGet server URL | text | Server | |
ProGet user name | text | UserName | The name of a user in ProGet that can access the specified feed. |
ProGet password | text | Password | The password of a user in ProGet that can access the specified feed. |
Package source | text | PackageSource |
Note: If uploading to a Package Source, use the ProGet::PushPackageFile operation instead.
Example:
# Push ProfitCalc-$ReleaseNumber.upack to the "ApplicationPackages" package source ProGet::Push-Package ( PackageSource: ApplicationPackages, FilePath: ProfitCalc-$ReleaseNumber.upack );
Was this article helpful?