✓ NuGet Package Template Applied
This Inedo-developed template provides you with quick access to recommended settings for an application using CI/CD with a NuGet package with source in GitHubTo select a different settings template, go to
Advanced Settings.
| Setting |
Description |
|
|
Package Source Configured
|
This is used to to connect to a package feed to push and/or pull packages. |
Secure Resources
|
|
Package Source Name
|
$PackageSource = NuGetLibraries |
Variables
|
|
Package Name
|
$PackageName = Inedo.Agents.PowerShell |
Variables
|
|
Source Control Connection
|
A credential must be configured at the application or system level to provides information to connect to a source control repository. |
Credentials
|
|
Release Pipeline
|
The "Release" pipeline is used to get source by configured branch, build and test artifacts, deploy to a series of targets on-demand or automatically once approvals are received, and create a tag in the repository. |
Pipelines
|
|
Variable Prompts
|
The "Default" release template is used to prompt for additional configuration such as a $Branch when creating BuildMaster builds or releases. |
Release Templates
|
|
Build OtterScript plan
|
The "Build" OtterScript plan is used to get source code by branch, builds package, and publishes as a CI prerelease. |
Scripts
|
|
RepackageAsRC OtterScript plan
|
The "RepackageAsRC" OtterScript plan is used to repackages the package as an RC-prerelease for further testing. |
Scripts
|
|
Release OtterScript plan
|
The "Release" OtterScript plan is used to repackages the package as a stable package and tags source control. |
Scripts
|
Optional Features
| Setting |
Description |
|
|
Build Trigger
|
A build trigger can be created to automatically trigger a build in the application when a commit gets pushed to a repository. |
Triggers
|
