![]() (Plus, what happens when the build server needs to reboot for maintenance/updates?) I'm not willing to leave my account logged in all the time, so that's a non-starter. The problem with that scenario is that the Dropbox user needs to be logged into the machine for the sync to take place. The obvious option is to install the Dropbox client on the build server and simply copy the installer artifact to the shared folder. So I needed a way to get TeamCity build artifacts into Dropbox easily. My partners are already comfortable with receiving installers via Dropbox and I didn't feel like setting up and maintaining an FTP server (in addition to setting them up with FTP clients). ![]() Once I had the project building on check-ins and running all the automated tests, I really wanted to get to the point where I could release a new version with a button push. Up to this point I'd been building the installers manually and shipping them to my partners for testing via a shared Dropbox folder. ![]() I've got an instance of TeamCity running on an Azure VM that I use for build and deployment automation, and a few weeks ago I finally got around to setting up the build, tests, and packaging of a Windows desktop application I've been working on for a while. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |