The Octo actions in Continua are a wrapper around the octo command line. If you're having trouble using any of the Octo actions, please refer to the Command Line Reference.
The Octo Pack action creates a package (.nupkg or .zip) from files on disk, without needing a .nuspec or .csproj.
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.
The Id of the package. [---id]
The format of the package. [---format]
The version of the package. This must be in semantic version format. If left empty, it will default to a timestamp-based version. [---version]
The folder containing files and folders to pack. If left empty, it will default to the workspace folder.
Specify the directory for the generated package file. Relative to the working folder. [---outFolder]
The Using drop down is populated with any property collector whose namespace matches the pattern defined by the Octo Pack action. The pattern for this action is ^Octo.*
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 "Octo Pack".
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.
Add an author to the package metadata. [---author]
The title of the package. [---title]
A description of the package. [---description]
Release notes for this version of the package. [---releaseNotes]
Path to a file containing release notes for this version of the package. [---releaseNotesFile]
Add a file pattern to include, relative to the base path. If left empty, defaults to all files e.g. **. [---include]
If this ticked, existing package files with the same Id/version will be overwritten. [---overwrite]
Verbose output. [--verbose]
How long to wait for the action to finish running before timing out. Leaving this blank (or zero) will default to 86400 seconds (24 hours).
Tick to continue build on failure marking the action with a warning status.
If this is ticked, any warnings logged will not mark the action with a warning status.
Multiple environment variables can be defined - one per line. These are set before the command line is run.
If this is ticked, environment variable values are written to the build log.
Tick this checkbox to set up a list of new environment variables prefixed with 'ContinuaCI.' for all current system expression objects and 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.