![]() I’m using TeamCity to create the Octopus release and the release number field seems to be populated correctly.įrom the log though it seems to be using that value in the version parameter, not the packageversion parameter: ![]() Release 1.0.0.508 created successfully!Īs you can see I’m trying to deploy 508 but it grabbed 506 and labelled it 508.Īlso, in Octopus I have it set to use the version number from the Nuget package but it’s not doing that and it’s labelling it as 508 in Octopus as well. 1 Copy to Azure Storage 1.0.0.506 Latest available in NuGet repository Using version number provided on command-line. Finding latest NuGet package for step: Copy to Azure Storage It specifies the version when it creates the release so then everything gets messed up because it believes it’s a newer version that it actually is. Occasionally the Octopus step will grab an old version of the Nuget package and deploy it. ![]() I have two separate steps in TeamCity, one to create the Nuget package and one to create the release in Octopus.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |