Build in OttoFMS Inbox not listed under Default Build

OttoDeploy
1

I’m able to publish a build from my staging server to the OttoFMS Inbox of the production server and have confirmed the zip is there. However, when I then create a deployment, and select PROD as the Default Source, I don’t see the build listed under Default Build. I only see builds in PROD’s OttoFMS Outbox, not Inbox. What am I missing? Is there an interim step to move the build out of the Inbox?

2

Hi Brad,

Welcome to the community. :slight_smile:

The way this works is a bit counter intuitive. We probably need to address this in the future. But here is how this works now.

What happens is that the destination server checks it’s own inbox first for the build before checking the other servers OutBox. If it finds the Build already in the inbox it just uses it.

So you’ll want to leave the Source server set to the server that made the build. And then choose the build that was published from the drop down. The deployment will see that the build is already in the Inbox, since you published it there, and just use it.

Let me know if that helps.

Todd

3

Thank you very much, Todd. That did the trick.

4

We are planning on adding a discrete “get a build from the inbox” option in the next version of OttoFMS/OttoDeploy, which should make this more clear.

-Kyle

1 Like
5

Hey Brad,

In OttoFMS version 4.6.2 and OttoDeploy version 1.3.0 we added a new “Build Inbox” source type which allows you to discretely choose the build inbox as your source. It will properly list the builds in the inbox and display them to you in OttoDeploy. Thanks for the report!

-Kyle

6

Thank you, Kyle! That is great. Appreciate the response you guys have shown, and for a free product!