Hi
I’m trying to specify what packages to use when creating a release from TeamCity (v 10.0.4. Octopus v 3.8.1. TC plugin v 4.5.1, have also tried TC plugin v 3.4.2).
- TeamCity builds project, creates packages of type *.zip
- Another TC project has artifact dependency on the one above, with rule: *.zip => someFolder
step 1: OctopusDeploy: Push packages. Using packages path: someFolder*.zip
step 2: OctopusDeploy: Create release. using additional command line arguments: --packagesFolder=someFolder
(I notice that the “=”-sign is automatically removed when step is running, guess this is correct)
I have tried using just a folder name (“someFolder”) , but also full path to a folder (“c:\tcAgent\work{guid}\someFolder”) but none seems to work.
All I get in the log is: "The package version for some steps was not specified. Going to try and resolve those automatically…"
This happens for all packages for all steps. The “latest version” that octopus finds is the same as the version that exists in the “someFolder” that I specified. Not difficult to verify as I only have three packages in use. (Note: per now we only have packages with 0.0.counter as version, but later on we will have x.y.z but still want to be able to build 0.0-packages, so we need this functionality to work before updating version numbers)
Do you have any idea of what could be the reason for octopus not being able to pick out the version numbers? Could it be due to that I am using *.zip instead of *.nuget?
Any help is greatly appreciated!
Thanks!
-Gard E.
