Artifact Publishing - Asynchronous?
Hi,
The following screenshot shows the log for publishing an artifact, and then creating an Octopus release using that artifact. My question is, once TC logs that the artifact is published, is it guaranteed that version will be available on the TC nuget feed? As you can see from the screenshot, when Octopus queries for the latest version, it is receiving the prior version, not the current version just published.

We have ~90 build configurations, all from the same template, that do the same exact thing, and we have never seen this before. Our Octopus projects are also identical except for the associated variables, and we are certain that nothing in the project could be causing this.
Thanks,
Matthew
Please sign in to leave a comment.
Just ran a test and inserted a 10 second powershell wait between the two steps and it resolved the issue. It appears that this process is asynch and you cannot be guaranteed it will be available on the nuget feed.