How to get a release to automatically include the latest package even if it is prerelease

Leslie's Avatar


02 Aug, 2017 11:10 PM

We have a install where there are 2 packages are deployed. ARC is used so the first package is always whatever was just pushed to octopus including prerelease packages, this is what we want. The second package will only ever use the most recent stable and will never pick the pre-release package that is already on the server and newer than the latest stable. Is there a way to specify in the Deploy package task that it can use pre-release packages if they exist?

  1. Support Staff 1 Posted by Kenneth Bates on 04 Aug, 2017 12:12 AM

    Kenneth Bates's Avatar

    Hi Leslie,

    Thanks for getting in touch! Unfortunately you've hit upon a limitation with our ARC feature, where it can't create a release for a package with a pre-release tag. ARC was really designed for older versions of TFS, where the build process wasn't easily changeable, so it's capabilities are limited.

    If you're currently using a build server, we'd strongly recommend creating your releases from there. We have extensions for a lot of the popular build servers which are available on our downloads page.

    The benefit here is they use Octo.exe under the hood, which is a much more versatile approach that works well when using tags on your package versions (among other benefits). We have comprehensive documentation on integrating Octopus with build servers that you can reference here.

    Let me know if this helps, how you go and if you have any further questions. :)

    Kind regards,


  2. Paul Stovell closed this discussion on 20 Nov, 2017 05:33 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac