Octopus TFS extension - creating the nuget package fails

Legacy Uncategorised
1

I’m trying out the extension for a vNext build. I have a step to create the package, but if fails with

1    2016-08-24T08:42:02.3808401Z ##[command]"C:\Agent\tasks\OctopusPack\1.2.28\Octo.exe" pack --id="MyProject" --format=NuPkg --version=2.0.160824.2 --outFolder="c:\Agent\Work\3\b\" --basePath="c:\Agent\Work\3\b\MyProject\" --author="Me" --title="MyPackage" --description="My database" --releaseNotes="" --releaseNotesFile="c:\Agent\Work\3\s" --overwrite=False
2    2016-08-24T08:42:02.9298576Z Octopus Deploy Command Line Tool, version 3.3.17+Branch.master.Sha.8455da7cab7e8ed1f89eb4baa22d743b11717f65
3    2016-08-24T08:42:03.7839039Z The release notes file 'c:\Agent\Work\3\s' could not be found
4    2016-08-24T08:42:03.7869038Z Packing MyProject version 2.0.160824.2...
5    2016-08-24T08:42:03.8999093Z System.ArgumentException: Illegal characters in path.
6    2016-08-24T08:42:03.9029095Z    at System.IO.Path.CheckInvalidPathChars(String path, Boolean checkAdditional)
7    2016-08-24T08:42:03.9059236Z    at System.IO.Path.Combine(String path1, String path2)
8    2016-08-24T08:42:03.9069157Z    at Octopus.Cli.Commands.NuGetPackageBuilder.BuildPackage(String basePath, IList`1 includes, ManifestMetadata metadata, String outFolder, Boolean overwrite)
9    2016-08-24T08:42:03.9079092Z    at Octopus.Cli.Commands.PackCommand.Execute(String[] commandLineArguments)
10  2016-08-24T08:42:03.9089125Z    at Octopus.Cli.Program.Main(String[] args)
11  2016-08-24T08:42:03.9099206Z Exit code: -3
12  2016-08-24T08:42:04.6019465Z ##[error]Process 'Octo.exe' exited with code '-3'.

I’m not sure why or what the invalid character would be. Logging provides the actual octo.exe command that gets run. When I copy that and run on the build server, it works!!!

Has anyone encountered this before?

2

Sigh. I had the source and output path with a backslash at the end. It doesn’t seem to like that. Works fine once removed. Might be nice if it handled that better.

3

Hi Daniel,

Glad to hear you were able to sort this out. Could you show me screenshots of the full screen of where did you had these values with backslashes? I’d like to reproduce this myself and file a bug to handle it better like you said.

Thanks!
Dalmiro

4

Sure thing Dalmiro. Attached. Thanks.

backslashes.JPG
backslashes.JPG933×372 24.6 KB

5

Thanks for that screenshot! Github issue submitted for the fix: https://github.com/OctopusDeploy/Issues/issues/2663

Cheers
Dalmiro

6

Notice:

This issue has been closed due to inactivity. If you encounter the same or a similar issue and require help, please open a new discussion (if we asked for logs or extra details in this thread, consider including them in the new thread). If you are the creator of this thread and believe it should not be closed let us know via our support email.