Fetching a build is still painful slow. In addition to getting 500 Otto errors or 502 error on console while it is happening.
It was faster to download the build and then re-upload it to the destination server.
~300 MB is taking over 10 minutes to fetch. (is this a data center config issue?)
I had a deployment with two sub deployments I wanted to test the first sub-deployment and hit the > to just run that one and it succeeded. However it immediately removed the build from the inbox!
Is there a setting that I didn’t discover to keep builds?
At the moment there is not a setting to keep builds in the inbox. We know that we need a way to keep them, but we’re trying to strike a balance between keeping builds and preventing errors from “cached” builds, which would be old builds of the same name already being in the inbox.
Is there a way, yet, to keep the build in the inbox or somewhere else that can be automated? Often I may need to run separate Deployments. And the build keeps getting removed.
Sometimes, i will pull and old build from a non-public storage, and need to migrate a file manually. Like one off processes that aren’t worth automating at this point.
At the moment you could use build publishing to keep your builds in a tertiary location where they would not be deleted. For example you could send them to an offsite location and then pull them down on your destination server. At the moment there is no flag to keep the build in the inbox after a deployment is run.
If it’s a big file, there are obviously challenges with moving them around. But I have other options as needed. Just more manual than I like because of some factors I can’t control.
If the offsite location is also AWS, and the file is big, then we also get hit with egress fees. Again, I can find other ways.
Being able to avoid some of those other options by having a switch we can flip… and decide for ourselves, would help a ton. And I can only blame myself for not cleaning up if I use it.
Yeah I totally get the not wanting to move the files on and off the server over and over. It is slower and it could result in charges depending on where you’re sending them to and from. I’ll push this up our list a bit to try and get it in soon.
