3 days ago, my DEV team reported that TeamCity was, all of a sudden, failing to create a new release in Octopus.
After verifying the packages exist in Artifactory and that Octopus can see them when I “test” the feed, I attempted to manually create a release and am seeing the error message in the subject, when I hover my cursor of the Exclamation Mark next to the Last package version. There are no versions listed in the Latest column. I was able to manually create a release, using the version number of the latest packages, but when viewing the packages inside the release, they don’t say "Published ", but are stuck “Loading…”.
Here are the relevant logs from TeamCity:
[2016-03-17 15:01:16,333] out - Handshaking with Octopus server: http://octopus/
[2016-03-17 15:01:16,975] out - Handshake successful. Octopus version: 3.3.1; API version: 3.0.0
[2016-03-17 15:01:16,979] out - Finding project: ActionManagement
[2016-03-17 15:01:17,425] out - Finding deployment process for project: ActionManagement
[2016-03-17 15:01:17,658] out - Finding release template…
[2016-03-17 15:01:18,112] out - Resolving NuGet package versions…
[2016-03-17 15:01:18,114] out - The version number for step ‘DeployFiltersViewModelAPIWebApp’ cannot be automatically resolved because the feed or package ID is dynamic.
[2016-03-17 15:01:18,114] out - The version number for step ‘DeployActionManagementPackage’ cannot be automatically resolved because the feed or package ID is dynamic.
[2016-03-17 15:01:18,114] out - The version number for step ‘DeployCaseEmailService’ cannot be automatically resolved because the feed or package ID is dynamic.
[2016-03-17 15:01:18,114] out - The version number for step ‘DeployHubSyncService’ cannot be automatically resolved because the feed or package ID is dynamic.
[2016-03-17 15:01:18,114] out - The version number for step ‘DeployTriggerService’ cannot be automatically resolved because the feed or package ID is dynamic.
[2016-03-17 15:01:18,115] out - The version number for step ‘DeployCaseMigrationService’ cannot be automatically resolved because the feed or package ID is dynamic.
[2016-03-17 15:01:18,115] out - Using version number provided on command-line.
[2016-03-17 15:01:18,115] out - Release plan for release: 19.1.26.81
[2016-03-17 15:01:18,115] out - Steps:
[2016-03-17 15:01:18,116] out - # Name Version Source
[2016-03-17 15:01:18,116] out - — ------------------------------ --------------- ------------------------------------
[2016-03-17 15:01:18,116] out - 1 DeployFiltersViewModelAPIWebApp ERROR Cannot resolve
[2016-03-17 15:01:18,116] out - 2 DeployActionManagementPackage ERROR Cannot resolve
[2016-03-17 15:01:18,116] out - 3 DeployCaseEmailService ERROR Cannot resolve
[2016-03-17 15:01:18,117] out - 4 DeployHubSyncService ERROR Cannot resolve
[2016-03-17 15:01:18,117] out - 5 DeployTriggerService ERROR Cannot resolve
[2016-03-17 15:01:18,117] out - 6 DeployCaseMigrationService ERROR Cannot resolve
[2016-03-17 15:01:18,117] out -
[2016-03-17 15:01:18,118] out - Package versions could not be resolved for one or more of the package steps in this release. See the errors above for details. Either ensure the latest version of the package can be automatically resolved, or set the version to use specifically by using the --package argument.