I just pushed up a new version of OctoPack. It fixes an issue whereby OctoPack would sometimes install to the wrong projects depending on how you attempt to install it.
OctoPack also now allows you to use the <files> element in your NuSpec file to specify exactly the files you want to include. For example:
<?xml version="1.0"?>
<package xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">
<metadata>
<!-- ... snip ... --->
</metadata>
<files>
<file src="bin\*.dll" target="bin" />
<file src="Content\*.css" target="Content" />
</files>
</package>Here we’re being explicit about which files to include in the package. OctoPack won’t attempt to add anything else or resolve any of the paths; it will just tell NuGet.exe to package it up. All paths are assumed to be relative to the project directory (the directory containing your .csproj file).
Happy packaging!
Tags:
Related posts
Certificates Feature
Certificates can be uploaded in PFX, PEM, or DER formats, and may include private-keys. They can be scoped to Environments and\or Tenants.
Deploying to no targets
As part of Octopus Deploy 3.8.7 we released a new feature related to Elastic and Transient Environments that we thought warranted a call out.
Octopus Deploy 3.7 - Effortless step templates
The new release of Octopus Deploy steps it up a notch by improving the UI for adding a step template, providing direct access to community step templates from a project's deployment process and improving the management of step templates in the library.
