"Deploy a Package" step using wrong artifact

Octopus Server
, , ,
1

I have a process step of “Deploy a Package” with a condition of Channel=Release, but the step is deploying a package from my Dev channel.

I have put a pre-release tag on my version rules for my Release channel of ^.*-dev to try and prevent the dev packages from getting picked up as well.

In the Dashboard in Octopus the versions look correct, but when I deploy in Octopus I can see that is is picking up the dev package:

Deploying package: C:\Octopus\Files\SecureCom.SCScheduleAPI@S2.15.2.9-dev@699288044B9CCF4FB30C5335A8722573.nupkg
Purging the directory ‘C:\Deploy\SecureCom\SCScheduleAPI-2.15.2.8-release’
Copying package contents to ‘C:\Deploy\SecureCom\SCScheduleAPI-2.15.2.8-release’
Copied 245 files

The dev package does have a higher version than the release package: 2.15.2.9-dev > 2.15.2.8-release.
I’ve tried about everything I know but am having no luck.

Thanks for the help!

5

For anyone finding this thread and wanting to know the solution:

The following regex will select all packages that dont have “-dev” for the pre-release tags: ^(?!.*dev$).*$

6

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.