The NuGet actions in Continua are a wrapper around the nuget command line. If you're having trouble using any of the NuGet actions, please refer to the Command Line Reference.

The Nuget Push action is used to publish a NuGet package to a NuGet Package Feed.

NuGet Push


A friendly name for this action (will be displayed in the actions workflow area).


Determines if this action will be run within the relevant stage.


Determines the location of the nupkg file.


The API Key for the NuGet server which this package is being published to.

Command Line Version

Select the version of the NuGet command line that is installed on the agent. Some other settings and options may be unavailable depending which the command line version is selected.


The Using drop down is populated with any property collector whose namespace matches the pattern defined by the NuGet Push action. The pattern for this action is ^NuGet.*

If you create a property collector for this action, make sure you select the Path Finder PlugIn type and give it a name that will match the pattern above in blue. Example names listed here, search the table's Plugin column for "NuGet Push".

For more in-depth explanations on property collectors see Property Collectors.

Alternatively, you can select the Custom option from the Using drop down list and specify a path in the resulting input field that will be displayed. Please read Why it's a good idea to use a property collector before using this option.


Configuration File

The NuGet configuation file. If not specified, file %AppData%\NuGet\NuGet.config is used as configuration file.


Specify the URL for the server to push to. If not specified, the action will fail, unless the DefaultPushSource value is set in the NuGet config file. [-Source]

Exclude symbols

If this option is ticked, any existing symbols package will not be pushed to a symbol server. [-NoSymbols]

Symbol Server

This field is visible only if 'Exclude symbols' is NOT ticked.

Specify the symbol server URL. If not specified,  is used when pushing to [-SymbolSource]

Symbol API Key

This field is visible only if 'Exclude symbols' is NOT ticked.

The API key for the symbol server. It's recommended you put this value in a variable. [-SymbolApiKey]

Skip duplicate packages

If a package and version already exists, skip it and continue with the next package in the push, if any. [-SkipDuplicate]

No service endpoint

Don't append 'api/v2/packages' to the source URL. [-NoServiceEndpoint]

Disable buffering

Disables buffering when pushing to an HTTP(s) server to decrease memory usage. [-DisableBuffering]



Specifies the timeout for pushing to a server in seconds. Leave blank or zero to default to 300 seconds (5 minutes). [-Timeout]


How much information should the command line output? [-Verbosity]

Force English output

Forces the command line to run using an invariant, English-based culture. [-ForceEnglishOutput]

Treat failure as warning

Tick to continue build on failure marking the action with a warning status.

Ignore warnings

If this is ticked, any warnings logged will not mark the action with a warning status.


Environment Variables

Multiple environment variables can be defined - one per line. These are set before the command line is run.

Log environment variables

If this is ticked, environment variable values are written to the build log. 

Generate system environment variables

Tick this checkbox to set up a list of new environment variables prefixed with 'ContinuaCI.' for all current system expression objects and variables.

Mask sensitive variable values in system environment variables

This checkbox is visible only if the 'Generate system environment variables' checkbox is ticked.

If this is ticked, the values of any variables marked as sensitive will be masked with **** when setting system environment variables. Clear this to expose the values.

  • No labels