Ocotpus Deploy pulling old teamcity artefact

We have a setup where we are using the Teamcity plugin to create releases with Octopus Deploy.
It all works great, except, it pulls down the previous package.
So Teamcity builds version 3.5.6.
When octopus deploy does the release, it uses 3.5.5.
I don’t know whether there is something missing or a caching issue with Teamcity, but any insight would be great.


Hi Joseph,

Thanks for reaching out. This is a very common issue with Teamcity related to the fact that the artifacts are only available after the build finished**. Check our doco for the string “delayed package publishing”

Best regards,